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

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:
IP Type Details Datetime
111.14.193.246 attack
The IP has triggered Cloudflare WAF. CF-Ray: 5412bd707e1cc39a | WAF_Rule_ID: 1aff1cdfeb5c4074965d7cd85bfc1d4e | WAF_Kind: firewall | CF_Action: challenge | Country: CN | CF_IPClass: noRecord | Protocol: HTTP/2 | Method: GET | Host: api.skk.moe | User-Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36 | CF_DC: SIN. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2019-12-08 06:31:05
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 111.14.1.221
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1537
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;111.14.1.221.			IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 07 15:06:17 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 221.1.14.111.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server:		183.60.82.98
Address:	183.60.82.98#53

** server can't find 221.1.14.111.in-addr.arpa: SERVFAIL

Related IP info:
Related comments:
IP Type Details Datetime
41.67.81.132 attack
Unauthorized connection attempt detected from IP address 41.67.81.132 to port 23 [J]
2020-01-19 07:06:08
81.227.121.65 attackspambots
Unauthorized connection attempt detected from IP address 81.227.121.65 to port 23 [J]
2020-01-19 07:25:36
85.108.67.60 attackbots
Unauthorized connection attempt detected from IP address 85.108.67.60 to port 8080 [J]
2020-01-19 07:25:20
199.223.232.221 attackspam
Unauthorized connection attempt detected from IP address 199.223.232.221 to port 2220 [J]
2020-01-19 07:12:53
94.233.78.142 attack
Unauthorized connection attempt detected from IP address 94.233.78.142 to port 85 [J]
2020-01-19 06:59:15
192.81.135.222 attackspambots
Unauthorized connection attempt detected from IP address 192.81.135.222 to port 443 [J]
2020-01-19 07:14:29
116.104.91.214 attackspam
Unauthorized connection attempt detected from IP address 116.104.91.214 to port 23 [J]
2020-01-19 06:55:24
189.151.133.171 attack
Unauthorized connection attempt detected from IP address 189.151.133.171 to port 2323 [J]
2020-01-19 06:46:47
222.186.42.155 attackspambots
01/18/2020-18:04:09.103613 222.186.42.155 Protocol: 6 ET SCAN Potential SSH Scan
2020-01-19 07:09:26
61.54.40.252 attack
Unauthorized connection attempt detected from IP address 61.54.40.252 to port 23 [J]
2020-01-19 07:03:46
31.201.192.63 attackbotsspam
Unauthorized connection attempt detected from IP address 31.201.192.63 to port 2004 [J]
2020-01-19 07:07:23
185.204.183.144 attack
Unauthorized connection attempt detected from IP address 185.204.183.144 to port 88 [J]
2020-01-19 06:48:34
118.25.142.138 attack
Unauthorized connection attempt detected from IP address 118.25.142.138 to port 2220 [J]
2020-01-19 06:54:53
137.74.199.180 attack
Invalid user ubuntu from 137.74.199.180 port 37802
2020-01-19 07:20:27
79.183.205.198 attackbotsspam
Unauthorized connection attempt detected from IP address 79.183.205.198 to port 82 [J]
2020-01-19 07:01:29

Recently Reported IPs

117.179.137.27 220.198.207.48 85.174.203.239 27.150.87.192
176.106.144.167 196.219.145.70 79.119.193.182 183.13.191.19
60.184.132.201 23.229.8.113 27.150.27.133 223.149.5.65
2.132.242.96 107.172.100.251 83.110.136.69 177.141.17.225
190.71.96.18 103.87.24.245 118.240.7.21 176.44.112.250