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
112.80.136.135 attackspam
Unauthorized connection attempt detected from IP address 112.80.136.135 to port 8088
2020-06-01 00:45:42
112.80.136.245 attack
Unauthorized connection attempt detected from IP address 112.80.136.245 to port 3389 [J]
2020-03-02 21:35:54
112.80.136.176 attack
Unauthorized connection attempt detected from IP address 112.80.136.176 to port 8081 [J]
2020-03-02 18:41:32
112.80.136.214 attackbotsspam
Unauthorized connection attempt detected from IP address 112.80.136.214 to port 9999 [T]
2020-01-10 09:22:18
112.80.136.219 attackspam
Unauthorized connection attempt detected from IP address 112.80.136.219 to port 8118
2020-01-02 21:21:29
112.80.136.25 attack
The IP has triggered Cloudflare WAF. CF-Ray: 543405f8ef3b6cfe | WAF_Rule_ID: 1112824 | WAF_Kind: firewall | CF_Action: challenge | Country: CN | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: GET | Host: blog.skk.moe | User-Agent: Mozilla/5.0 (Linux; U; Android 4.3; en-us; SM-N900T Build/JSS15J) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30 | CF_DC: SJC. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2019-12-12 03:33:44
112.80.136.8 attackspambots
The IP has triggered Cloudflare WAF. CF-Ray: 5415f75a7ae2288c | WAF_Rule_ID: 3b40188685924a32bf11d40edea05a27 | WAF_Kind: firewall | CF_Action: challenge | Country: CN | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: GET | Host: disqus.skk.moe | User-Agent: Mozilla/5.077692140 Mozilla/5.0 (Windows NT 6.1; Trident/7.0; rv:11.0) like Gecko | CF_DC: SJC. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2019-12-08 04:38:18
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 112.80.136.239
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 58155
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;112.80.136.239.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 16:08:40 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 239.136.80.112.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 239.136.80.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
124.156.54.74 attack
Unauthorized connection attempt detected from IP address 124.156.54.74 to port 5357 [J]
2020-01-13 00:57:07
210.117.8.140 attackbots
Unauthorized connection attempt detected from IP address 210.117.8.140 to port 80 [J]
2020-01-13 01:16:15
47.112.105.39 attack
Unauthorized connection attempt detected from IP address 47.112.105.39 to port 80 [J]
2020-01-13 01:09:13
208.64.33.89 attackspambots
Unauthorized connection attempt detected from IP address 208.64.33.89 to port 2220 [J]
2020-01-13 01:16:42
139.199.100.81 attackbots
Unauthorized connection attempt detected from IP address 139.199.100.81 to port 2220 [J]
2020-01-13 00:54:38
51.38.234.224 attackspam
Jan 12 15:58:54 server sshd\[13225\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=224.ip-51-38-234.eu  user=root
Jan 12 15:58:55 server sshd\[13225\]: Failed password for root from 51.38.234.224 port 48428 ssh2
Jan 12 16:10:26 server sshd\[16347\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=224.ip-51-38-234.eu  user=root
Jan 12 16:10:28 server sshd\[16347\]: Failed password for root from 51.38.234.224 port 35904 ssh2
Jan 12 16:13:05 server sshd\[16804\]: Invalid user satheesh from 51.38.234.224
Jan 12 16:13:05 server sshd\[16804\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=224.ip-51-38-234.eu 
...
2020-01-13 01:08:24
27.105.198.188 attackbots
Unauthorized connection attempt detected from IP address 27.105.198.188 to port 4567 [J]
2020-01-13 01:11:01
122.116.244.43 attackbots
Unauthorized connection attempt detected from IP address 122.116.244.43 to port 4567 [J]
2020-01-13 00:58:16
98.128.130.63 attack
Unauthorized connection attempt detected from IP address 98.128.130.63 to port 5555 [J]
2020-01-13 01:32:20
179.25.191.134 attack
Unauthorized connection attempt detected from IP address 179.25.191.134 to port 80 [J]
2020-01-13 01:21:15
27.94.194.207 attack
Unauthorized connection attempt detected from IP address 27.94.194.207 to port 2220 [J]
2020-01-13 01:11:28
49.233.75.234 attack
Unauthorized connection attempt detected from IP address 49.233.75.234 to port 2220 [J]
2020-01-13 01:08:46
84.232.241.233 attackbotsspam
Unauthorized connection attempt detected from IP address 84.232.241.233 to port 4567 [J]
2020-01-13 01:04:54
118.216.180.155 attackspam
Unauthorized connection attempt detected from IP address 118.216.180.155 to port 81 [J]
2020-01-13 01:28:51
162.62.17.202 attackspam
Unauthorized connection attempt detected from IP address 162.62.17.202 to port 30 [J]
2020-01-13 00:54:17

Recently Reported IPs

112.80.136.22 112.80.136.3 112.80.136.251 112.80.136.19
112.80.136.191 112.80.136.36 112.80.136.238 112.80.136.44
112.80.136.55 112.80.136.74 112.80.136.87 112.80.136.93
112.80.136.98 112.80.137.110 112.80.136.84 112.80.137.123
112.80.136.78 112.80.137.134 112.80.137.159 112.80.137.16