Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: Seongnam-si

Region: Gyeonggi-do

Country: South Korea

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 113.199.111.20
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 48183
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;113.199.111.20.			IN	A

;; AUTHORITY SECTION:
.			487	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2024100400 1800 900 604800 86400

;; Query time: 22 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Oct 04 23:20:40 CST 2024
;; MSG SIZE  rcvd: 107
Host info
Host 20.111.199.113.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 20.111.199.113.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
95.213.177.122 attackspambots
Jun 28 10:08:49   TCP Attack: SRC=95.213.177.122 DST=[Masked] LEN=40 TOS=0x08 PREC=0x20 TTL=241  PROTO=TCP SPT=56528 DPT=8080 WINDOW=1024 RES=0x00 SYN URGP=0
2019-06-28 18:56:04
95.85.39.203 attackbotsspam
Jun 28 11:45:06 core01 sshd\[20681\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=95.85.39.203  user=root
Jun 28 11:45:09 core01 sshd\[20681\]: Failed password for root from 95.85.39.203 port 46814 ssh2
...
2019-06-28 18:22:13
189.127.33.235 attackspambots
libpam_shield report: forced login attempt
2019-06-28 18:58:59
203.39.148.165 attack
Jun 28 10:49:33 tuxlinux sshd[50549]: Invalid user usuario from 203.39.148.165 port 60990
Jun 28 10:49:33 tuxlinux sshd[50549]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.39.148.165 
Jun 28 10:49:33 tuxlinux sshd[50549]: Invalid user usuario from 203.39.148.165 port 60990
Jun 28 10:49:33 tuxlinux sshd[50549]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.39.148.165 
Jun 28 10:49:33 tuxlinux sshd[50549]: Invalid user usuario from 203.39.148.165 port 60990
Jun 28 10:49:33 tuxlinux sshd[50549]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.39.148.165 
Jun 28 10:49:35 tuxlinux sshd[50549]: Failed password for invalid user usuario from 203.39.148.165 port 60990 ssh2
...
2019-06-28 18:46:39
76.104.243.253 attackbotsspam
Jun 28 09:10:02 dev0-dcde-rnet sshd[24512]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=76.104.243.253
Jun 28 09:10:03 dev0-dcde-rnet sshd[24512]: Failed password for invalid user zhuan from 76.104.243.253 port 47148 ssh2
Jun 28 09:19:26 dev0-dcde-rnet sshd[24530]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=76.104.243.253
2019-06-28 18:58:42
124.156.185.149 attack
$f2bV_matches
2019-06-28 18:52:05
201.182.66.19 attackbots
2019-06-28T05:09:20.149562abusebot-8.cloudsearch.cf sshd\[28322\]: Invalid user chris from 201.182.66.19 port 48428
2019-06-28 18:37:42
61.219.11.153 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2019-06-28 18:23:40
119.42.175.200 attackbots
Jun 28 11:23:37 dev sshd\[6896\]: Invalid user zimbra from 119.42.175.200 port 50604
Jun 28 11:23:37 dev sshd\[6896\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.42.175.200
...
2019-06-28 18:19:10
189.89.223.162 attack
libpam_shield report: forced login attempt
2019-06-28 18:55:09
185.244.143.3 attackspambots
Excessive Port-Scanning
2019-06-28 18:17:51
118.25.27.67 attack
Jun 28 11:09:03 apollo sshd\[24577\]: Invalid user president from 118.25.27.67Jun 28 11:09:05 apollo sshd\[24577\]: Failed password for invalid user president from 118.25.27.67 port 50734 ssh2Jun 28 11:12:21 apollo sshd\[24579\]: Invalid user assetto from 118.25.27.67
...
2019-06-28 19:00:07
151.20.100.11 attackspam
$f2bV_matches
2019-06-28 18:51:37
187.237.130.98 attack
Jun 27 23:48:06 nbi-636 sshd[11779]: Invalid user kh from 187.237.130.98 port 43964
Jun 27 23:48:08 nbi-636 sshd[11779]: Failed password for invalid user kh from 187.237.130.98 port 43964 ssh2
Jun 27 23:48:08 nbi-636 sshd[11779]: Received disconnect from 187.237.130.98 port 43964:11: Bye Bye [preauth]
Jun 27 23:48:08 nbi-636 sshd[11779]: Disconnected from 187.237.130.98 port 43964 [preauth]
Jun 27 23:51:25 nbi-636 sshd[12244]: User r.r from 187.237.130.98 not allowed because not listed in AllowUsers
Jun 27 23:51:25 nbi-636 sshd[12244]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.237.130.98  user=r.r
Jun 27 23:51:27 nbi-636 sshd[12244]: Failed password for invalid user r.r from 187.237.130.98 port 52658 ssh2
Jun 27 23:51:27 nbi-636 sshd[12244]: Received disconnect from 187.237.130.98 port 52658:11: Bye Bye [preauth]
Jun 27 23:51:27 nbi-636 sshd[12244]: Disconnected from 187.237.130.98 port 52658 [preauth]
Jun 27 23:53:07 nb........
-------------------------------
2019-06-28 18:25:59
168.228.148.207 attack
Brute force attempt
2019-06-28 18:54:21

Recently Reported IPs

113.199.162.119 113.180.178.66 113.18.61.45 113.198.243.246
113.180.50.14 113.18.5.211 113.199.128.184 113.18.92.224
113.180.95.167 113.180.197.46 113.180.117.43 113.180.134.141
113.180.205.207 113.180.251.251 113.180.15.193 113.181.100.32
113.180.153.61 113.180.255.250 113.180.204.216 113.180.229.94