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
124.156.107.252 attackspambots
3x Failed Password
2020-04-08 08:37:56
94.191.60.71 attackspam
Apr  8 01:50:31 vpn01 sshd[17680]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.191.60.71
Apr  8 01:50:32 vpn01 sshd[17680]: Failed password for invalid user user from 94.191.60.71 port 56098 ssh2
...
2020-04-08 08:15:35
220.78.28.68 attackspam
SSH Invalid Login
2020-04-08 08:24:55
37.187.105.36 attack
Ssh brute force
2020-04-08 08:21:25
49.232.58.113 attack
SSH Authentication Attempts Exceeded
2020-04-08 08:20:24
222.112.178.113 attack
Apr  7 22:57:38 vlre-nyc-1 sshd\[31678\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.112.178.113  user=root
Apr  7 22:57:41 vlre-nyc-1 sshd\[31678\]: Failed password for root from 222.112.178.113 port 50750 ssh2
Apr  7 23:06:32 vlre-nyc-1 sshd\[31940\]: Invalid user marie from 222.112.178.113
Apr  7 23:06:32 vlre-nyc-1 sshd\[31940\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.112.178.113
Apr  7 23:06:34 vlre-nyc-1 sshd\[31940\]: Failed password for invalid user marie from 222.112.178.113 port 56892 ssh2
...
2020-04-08 08:24:32
136.53.67.174 attackbots
SSH Invalid Login
2020-04-08 08:35:01
175.207.13.22 attack
Apr  8 01:43:15 XXX sshd[19649]: Invalid user test from 175.207.13.22 port 50384
2020-04-08 08:30:40
125.124.63.87 attackspambots
$f2bV_matches
2020-04-08 08:37:38
218.111.21.86 attackspam
SSH Invalid Login
2020-04-08 08:25:08
49.235.15.230 attackbots
Apr  8 00:03:19 mail sshd[17137]: Invalid user ubuntu from 49.235.15.230
Apr  8 00:03:19 mail sshd[17137]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.15.230
Apr  8 00:03:19 mail sshd[17137]: Invalid user ubuntu from 49.235.15.230
Apr  8 00:03:21 mail sshd[17137]: Failed password for invalid user ubuntu from 49.235.15.230 port 38632 ssh2
Apr  8 00:15:47 mail sshd[4248]: Invalid user internal from 49.235.15.230
...
2020-04-08 08:19:21
142.44.247.115 attackspam
Apr  7 19:43:14 ws12vmsma01 sshd[16851]: Invalid user test from 142.44.247.115
Apr  7 19:43:17 ws12vmsma01 sshd[16851]: Failed password for invalid user test from 142.44.247.115 port 53902 ssh2
Apr  7 19:49:04 ws12vmsma01 sshd[17667]: Invalid user user from 142.44.247.115
...
2020-04-08 08:34:33
106.12.139.149 attack
$f2bV_matches
2020-04-08 08:41:58
89.100.21.40 attackbots
SSH Invalid Login
2020-04-08 08:15:55
14.215.165.133 attack
SSH brute force
2020-04-08 08:22:41

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