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: unknown

Region: unknown

Country: Republic of China (ROC)

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.21.189.222
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 8579
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;113.21.189.222.			IN	A

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

;; Query time: 38 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jul 17 03:52:51 CST 2020
;; MSG SIZE  rcvd: 118
Host info
222.189.21.113.in-addr.arpa domain name pointer static-ip-222-189-21-113.rev.dyxnet.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
222.189.21.113.in-addr.arpa	name = static-ip-222-189-21-113.rev.dyxnet.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
217.64.108.66 attackbots
May 11 06:35:33 piServer sshd[3003]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.64.108.66 
May 11 06:35:35 piServer sshd[3003]: Failed password for invalid user test_user from 217.64.108.66 port 60342 ssh2
May 11 06:43:15 piServer sshd[3834]: Failed password for root from 217.64.108.66 port 39592 ssh2
...
2020-05-11 16:18:54
134.122.98.166 attackbotsspam
Wordpress malicious attack:[octablocked]
2020-05-11 16:44:13
106.12.26.160 attack
Invalid user postgres from 106.12.26.160 port 40988
2020-05-11 16:11:28
223.240.89.38 attack
May 11 06:09:29 host sshd[16096]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.240.89.38  user=root
May 11 06:09:31 host sshd[16096]: Failed password for root from 223.240.89.38 port 52590 ssh2
...
2020-05-11 16:08:43
211.90.37.75 attackbots
SSH Brute Force
2020-05-11 16:50:45
200.17.114.136 attack
May 11 08:54:32  sshd\[23694\]: Invalid user unt from 200.17.114.136May 11 08:54:34  sshd\[23694\]: Failed password for invalid user unt from 200.17.114.136 port 33940 ssh2
...
2020-05-11 16:23:09
222.186.169.192 attack
May 11 08:06:37 game-panel sshd[13622]: Failed password for root from 222.186.169.192 port 3374 ssh2
May 11 08:06:40 game-panel sshd[13622]: Failed password for root from 222.186.169.192 port 3374 ssh2
May 11 08:06:43 game-panel sshd[13622]: Failed password for root from 222.186.169.192 port 3374 ssh2
May 11 08:06:46 game-panel sshd[13622]: Failed password for root from 222.186.169.192 port 3374 ssh2
2020-05-11 16:18:25
120.237.123.242 attack
$f2bV_matches
2020-05-11 16:29:16
159.89.115.126 attack
May 11 09:05:14 rotator sshd\[27942\]: Invalid user beth from 159.89.115.126May 11 09:05:17 rotator sshd\[27942\]: Failed password for invalid user beth from 159.89.115.126 port 57388 ssh2May 11 09:08:41 rotator sshd\[28142\]: Invalid user web from 159.89.115.126May 11 09:08:43 rotator sshd\[28142\]: Failed password for invalid user web from 159.89.115.126 port 36278 ssh2May 11 09:12:13 rotator sshd\[28956\]: Invalid user cochiloco from 159.89.115.126May 11 09:12:16 rotator sshd\[28956\]: Failed password for invalid user cochiloco from 159.89.115.126 port 43404 ssh2
...
2020-05-11 16:16:46
125.91.109.232 attack
$f2bV_matches
2020-05-11 16:10:13
185.164.138.21 attackspam
Invalid user uftp from 185.164.138.21 port 55314
2020-05-11 16:28:59
112.3.29.179 attackspambots
Unauthorized connection attempt detected from IP address 112.3.29.179 to port 6151
2020-05-11 16:35:24
82.221.105.6 attackbots
Unauthorized connection attempt detected from IP address 82.221.105.6 to port 9981
2020-05-11 16:39:16
50.236.62.30 attackbotsspam
k+ssh-bruteforce
2020-05-11 16:45:22
178.154.200.42 attack
[Mon May 11 10:51:22.428763 2020] [:error] [pid 23437:tid 140213476472576] [client 178.154.200.42:63048] [client 178.154.200.42] ModSecurity: Access denied with code 403 (phase 2). Pattern match "^[\\\\d.:]+$" at REQUEST_HEADERS:Host. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "696"] [id "920350"] [msg "Host header is a numeric IP address"] [data "103.27.207.197"] [severity "WARNING"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "OWASP_CRS"] [tag "OWASP_CRS/PROTOCOL_VIOLATION/IP_HOST"] [tag "WASCTC/WASC-21"] [tag "OWASP_TOP_10/A7"] [tag "PCI/6.5.10"] [hostname "103.27.207.197"] [uri "/"] [unique_id "XrjLuvgemFO2kgrCZmQY5AAAAC8"]
...
2020-05-11 16:49:03

Recently Reported IPs

213.43.97.20 101.17.42.43 128.252.97.198 60.167.182.147
95.163.164.127 104.211.142.129 122.51.80.103 61.144.96.20
208.91.198.55 194.33.45.141 197.218.137.34 45.225.160.235
94.25.164.150 115.127.82.138 104.237.226.100 58.243.125.108
154.124.246.80 43.250.165.233 138.68.221.125 62.217.146.114