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

;; QUESTION SECTION:
;112.80.136.136.			IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 03:10:24 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 136.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 136.136.80.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
182.74.169.98 attackspam
Jul 16 13:09:10 [munged] sshd[20945]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.74.169.98
2019-07-17 00:24:38
120.52.152.17 attackbotsspam
16.07.2019 16:41:19 Connection to port 2083 blocked by firewall
2019-07-17 01:11:12
185.230.127.230 attackspam
Invalid user admin from 185.230.127.230 port 56731
2019-07-17 00:19:59
45.55.12.248 attack
Jul 16 17:44:46 vpn01 sshd\[30201\]: Invalid user bngara from 45.55.12.248
Jul 16 17:44:46 vpn01 sshd\[30201\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.12.248
Jul 16 17:44:48 vpn01 sshd\[30201\]: Failed password for invalid user bngara from 45.55.12.248 port 59634 ssh2
2019-07-16 23:59:35
170.0.125.229 attackbotsspam
[Aegis] @ 2019-07-16 12:09:09  0100 -> Multiple attempts to send e-mail from invalid/unknown sender domain.
2019-07-17 00:21:29
178.128.3.152 attackspambots
Jul 16 15:20:09 MK-Soft-VM4 sshd\[24950\]: Invalid user test02 from 178.128.3.152 port 37698
Jul 16 15:20:09 MK-Soft-VM4 sshd\[24950\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.3.152
Jul 16 15:20:11 MK-Soft-VM4 sshd\[24950\]: Failed password for invalid user test02 from 178.128.3.152 port 37698 ssh2
...
2019-07-17 01:12:02
78.110.79.88 attack
Jul 16 12:58:11 shared02 sshd[27090]: Invalid user admin from 78.110.79.88
Jul 16 12:58:11 shared02 sshd[27090]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=78.110.79.88
Jul 16 12:58:13 shared02 sshd[27090]: Failed password for invalid user admin from 78.110.79.88 port 47293 ssh2
Jul 16 12:58:14 shared02 sshd[27090]: Connection closed by 78.110.79.88 port 47293 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=78.110.79.88
2019-07-17 01:13:07
82.64.68.167 attack
Jul 16 14:49:01 icinga sshd[14304]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.64.68.167
Jul 16 14:49:03 icinga sshd[14304]: Failed password for invalid user teste from 82.64.68.167 port 38260 ssh2
...
2019-07-17 01:08:50
222.188.50.217 attack
Jul 16 12:50:43 m3061 sshd[25634]: Invalid user admin from 222.188.50.217
Jul 16 12:50:43 m3061 sshd[25634]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.188.50.217


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=222.188.50.217
2019-07-17 00:01:27
58.219.239.243 attackspam
abuse-sasl
2019-07-17 01:09:14
202.79.26.106 attack
Jul 16 12:49:59 server02 sshd[17895]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.79.26.106
Jul 16 12:49:59 server02 sshd[17898]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.79.26.106
Jul 16 12:49:59 server02 sshd[17903]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.79.26.106
Jul 16 12:49:59 server02 sshd[17894]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.79.26.106
Jul 16 12:49:59 server02 sshd[17893]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.79.26.106
Jul 16 12:49:59 server02 sshd[17901]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.79.26.106

........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=202.79.26.106
2019-07-17 00:04:22
198.71.235.49 attackspam
fail2ban honeypot
2019-07-17 00:09:51
60.169.94.22 attack
abuse-sasl
2019-07-17 00:03:45
5.196.72.58 attack
Jul 16 09:18:44 cac1d2 sshd\[27250\]: Invalid user passwd from 5.196.72.58 port 58192
Jul 16 09:18:44 cac1d2 sshd\[27250\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.196.72.58
Jul 16 09:18:47 cac1d2 sshd\[27250\]: Failed password for invalid user passwd from 5.196.72.58 port 58192 ssh2
...
2019-07-17 00:35:57
188.174.24.42 attackspam
Jul x@x
Jul x@x
Jul x@x
Jul x@x
Jul x@x
Jul x@x
Jul x@x
.... truncated .... 
p3-login: x@x
Jul x@x
Jul 16 11:39:47 xb3 postfix/smtpd[7539]: connect from ppp-188-174-24-42.dynamic.mnet-online.de[188.174.24.42]
Jul 16 11:39:47 xb3 postfix/smtpd[7539]: SSL_accept error from ppp-188-174-24-42.dynamic.mnet-online.de[188.174.24.42]: -1
Jul 16 11:39:47 xb3 postfix/smtpd[7539]: lost connection after STARTTLS from ppp-188-174-24-42.dynamic.mnet-online.de[188.174.24.42]
Jul 16 11:39:47 xb3 postfix/smtpd[7539]: disconnect from ppp-188-174-24-42.dynamic.mnet-online.de[188.174.24.42]
Jul 16 11:39:47 xb3 postfix/smtpd[9158]: connect from ppp-188-174-24-42.dynamic.mnet-online.de[188.174.24.42]
Jul 16 11:39:47 xb3 postfix/smtpd[9158]: CF0CD1804A3D8C: client=ppp-188-174-24-42.dynamic.mnet-online.de[188.174.24.42], sasl_method=LOGIN, sasl_username=x@x
Jul 16 11:39:48 xb3 postfix/smtpd[9158]: disconnect from ppp-188-174-24-42.dynamic.mnet-online.de[188.174.24.42]
Jul x@x
Jul x@x
Jul x@x
J........
-------------------------------
2019-07-17 01:06:25

Recently Reported IPs

112.80.136.127 112.78.4.203 112.80.136.151 112.8.115.14
112.80.136.158 112.8.223.42 112.78.4.18 112.80.136.172
112.80.136.154 112.80.139.160 112.80.139.163 112.80.139.181
112.80.139.178 112.80.139.19 112.80.139.197 112.80.139.201
112.80.139.190 112.80.139.195 113.102.206.136 113.102.206.186