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

;; QUESTION SECTION:
;112.80.136.22.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 16:08:41 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 22.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 22.136.80.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
62.99.119.151 attackbotsspam
20/5/13@13:21:41: FAIL: IoT-Telnet address from=62.99.119.151
...
2020-05-14 03:36:48
181.31.101.35 attackbotsspam
May 13 21:34:51 inter-technics sshd[7022]: Invalid user soporte from 181.31.101.35 port 43809
May 13 21:34:51 inter-technics sshd[7022]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.31.101.35
May 13 21:34:51 inter-technics sshd[7022]: Invalid user soporte from 181.31.101.35 port 43809
May 13 21:34:53 inter-technics sshd[7022]: Failed password for invalid user soporte from 181.31.101.35 port 43809 ssh2
May 13 21:39:26 inter-technics sshd[7333]: Invalid user amanda from 181.31.101.35 port 24513
...
2020-05-14 03:47:19
134.209.57.3 attack
May 13 21:06:34 sip sshd[246041]: Invalid user sarah from 134.209.57.3 port 55994
May 13 21:06:36 sip sshd[246041]: Failed password for invalid user sarah from 134.209.57.3 port 55994 ssh2
May 13 21:14:21 sip sshd[246150]: Invalid user test from 134.209.57.3 port 49396
...
2020-05-14 03:22:17
167.114.251.164 attackspam
May 13 18:32:49 ns3033917 sshd[17711]: Invalid user ftp from 167.114.251.164 port 60663
May 13 18:32:51 ns3033917 sshd[17711]: Failed password for invalid user ftp from 167.114.251.164 port 60663 ssh2
May 13 18:38:41 ns3033917 sshd[17739]: Invalid user demo from 167.114.251.164 port 43559
...
2020-05-14 03:13:24
210.183.21.48 attackbotsspam
Invalid user yanss from 210.183.21.48 port 31666
2020-05-14 03:20:25
78.189.190.149 attackbotsspam
Unauthorized connection attempt from IP address 78.189.190.149 on Port 445(SMB)
2020-05-14 03:16:49
208.68.39.220 attackspam
May 13 19:35:13 host sshd[5773]: Invalid user traffic from 208.68.39.220 port 39524
...
2020-05-14 03:08:36
52.26.66.228 attackbotsspam
05/13/2020-19:56:33.271190 52.26.66.228 Protocol: 6 SURICATA TLS invalid record/traffic
2020-05-14 03:18:03
223.4.70.106 attackbots
Invalid user lab from 223.4.70.106 port 43472
2020-05-14 03:39:44
62.171.138.177 attackspam
Invalid user paulb from 62.171.138.177 port 42534
2020-05-14 03:28:59
165.227.58.61 attackspam
2020-05-13T15:24:23.479880abusebot-3.cloudsearch.cf sshd[8887]: Invalid user ubuntu from 165.227.58.61 port 57908
2020-05-13T15:24:23.487130abusebot-3.cloudsearch.cf sshd[8887]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.58.61
2020-05-13T15:24:23.479880abusebot-3.cloudsearch.cf sshd[8887]: Invalid user ubuntu from 165.227.58.61 port 57908
2020-05-13T15:24:25.520701abusebot-3.cloudsearch.cf sshd[8887]: Failed password for invalid user ubuntu from 165.227.58.61 port 57908 ssh2
2020-05-13T15:33:19.937830abusebot-3.cloudsearch.cf sshd[9520]: Invalid user admin from 165.227.58.61 port 41064
2020-05-13T15:33:19.946205abusebot-3.cloudsearch.cf sshd[9520]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.58.61
2020-05-13T15:33:19.937830abusebot-3.cloudsearch.cf sshd[9520]: Invalid user admin from 165.227.58.61 port 41064
2020-05-13T15:33:21.563192abusebot-3.cloudsearch.cf sshd[9520]: Failed pass
...
2020-05-14 03:13:37
157.230.19.72 attack
IP blocked
2020-05-14 03:31:14
51.178.78.154 attackspambots
Unauthorized connection attempt from IP address 51.178.78.154 on Port 445(SMB)
2020-05-14 03:11:49
152.136.220.33 attack
Invalid user qtss from 152.136.220.33 port 52366
2020-05-14 03:24:43
185.143.75.157 attackbotsspam
May 13 21:21:53 relay postfix/smtpd\[15590\]: warning: unknown\[185.143.75.157\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
May 13 21:22:05 relay postfix/smtpd\[10224\]: warning: unknown\[185.143.75.157\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
May 13 21:22:33 relay postfix/smtpd\[15590\]: warning: unknown\[185.143.75.157\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
May 13 21:22:45 relay postfix/smtpd\[9709\]: warning: unknown\[185.143.75.157\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
May 13 21:23:12 relay postfix/smtpd\[17916\]: warning: unknown\[185.143.75.157\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-05-14 03:27:03

Recently Reported IPs

112.80.136.233 112.80.136.239 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