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

;; QUESTION SECTION:
;112.80.136.57.			IN	A

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

;; Query time: 27 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 05:52:09 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 57.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 57.136.80.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
113.255.14.123 attack
Honeypot attack, port: 5555, PTR: 123-14-255-113-on-nets.com.
2020-02-02 23:36:39
109.110.171.177 attackspam
20/2/2@08:40:25: FAIL: Alarm-Network address from=109.110.171.177
...
2020-02-02 23:08:56
195.62.78.23 attackspam
Jan 31 16:58:59 ms-srv sshd[9505]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.62.78.23
Jan 31 16:59:01 ms-srv sshd[9505]: Failed password for invalid user user from 195.62.78.23 port 58752 ssh2
2020-02-02 23:29:23
195.39.140.129 attackbotsspam
Dec 31 14:36:24 ms-srv sshd[33112]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.39.140.129
Dec 31 14:36:26 ms-srv sshd[33112]: Failed password for invalid user admin from 195.39.140.129 port 1135 ssh2
2020-02-02 23:38:40
221.194.44.151 attack
DATE:2020-02-02 16:09:41, IP:221.194.44.151, PORT:1433 MSSQL brute force auth on honeypot server (honey-neo-dc)
2020-02-02 23:13:58
222.186.15.10 attackspam
2020-02-02T10:40:49.312706vostok sshd\[7288\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.15.10  user=root | Triggered by Fail2Ban at Vostok web server
2020-02-02 23:42:52
202.62.88.126 attackbots
Honeypot attack, port: 445, PTR: PTR record not found
2020-02-02 23:24:52
118.89.160.141 attackspam
Brute force SMTP login attempted.
...
2020-02-02 23:29:41
111.231.119.188 attackspam
Unauthorized connection attempt detected from IP address 111.231.119.188 to port 2220 [J]
2020-02-02 23:04:50
195.88.66.108 attack
Oct 15 21:57:51 ms-srv sshd[11444]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.88.66.108  user=root
Oct 15 21:57:53 ms-srv sshd[11444]: Failed password for invalid user root from 195.88.66.108 port 46394 ssh2
2020-02-02 23:19:21
37.152.188.197 attack
Feb  2 17:26:01 taivassalofi sshd[10780]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.152.188.197
Feb  2 17:26:03 taivassalofi sshd[10780]: Failed password for invalid user testftp from 37.152.188.197 port 56616 ssh2
...
2020-02-02 23:33:16
185.234.219.82 attack
Rude login attack (64 tries in 1d)
2020-02-02 23:07:06
211.72.106.115 attackbots
DATE:2020-02-02 16:09:33, IP:211.72.106.115, PORT:1433 MSSQL brute force auth on honeypot server (honey-neo-dc)
2020-02-02 23:39:50
210.4.119.89 attackspam
DATE:2020-02-02 16:09:29, IP:210.4.119.89, PORT:1433 MSSQL brute force auth on honeypot server (honey-neo-dc)
2020-02-02 23:49:38
106.12.22.23 attackspam
Feb  2 16:04:36 lnxded64 sshd[1440]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.22.23
Feb  2 16:04:38 lnxded64 sshd[1440]: Failed password for invalid user tester from 106.12.22.23 port 56264 ssh2
Feb  2 16:09:45 lnxded64 sshd[2888]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.22.23
2020-02-02 23:12:28

Recently Reported IPs

112.80.137.108 112.80.137.160 112.80.137.219 112.80.137.27
112.80.137.92 112.80.138.157 112.80.138.184 112.80.138.188
112.80.138.253 112.80.138.179 112.80.138.25 112.80.139.170
112.80.139.14 112.80.138.83 112.80.139.35 112.80.139.248
112.80.138.254 112.80.214.172 112.80.248.152 112.80.25.250