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

;; QUESTION SECTION:
;112.80.136.178.			IN	A

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

;; Query time: 53 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 14 06:39:45 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 178.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 178.136.80.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
159.65.133.13 attackbots
Oct  8 22:16:55 server sshd[30745]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.133.13  user=root
Oct  8 22:16:57 server sshd[30745]: Failed password for invalid user root from 159.65.133.13 port 49398 ssh2
Oct  8 22:19:42 server sshd[30824]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.133.13  user=root
Oct  8 22:19:45 server sshd[30824]: Failed password for invalid user root from 159.65.133.13 port 57706 ssh2
2020-10-09 05:17:29
171.252.202.151 attackspam
Unauthorized connection attempt detected from IP address 171.252.202.151 to port 23 [T]
2020-10-09 05:07:54
118.101.192.62 attackspam
Failed password for invalid user wc from 118.101.192.62 port 41925 ssh2
2020-10-09 04:55:49
69.85.84.14 attackbots
Oct  8 17:09:55 vm0 sshd[10275]: Failed password for root from 69.85.84.14 port 47566 ssh2
...
2020-10-09 05:18:32
112.85.42.200 attackbots
Failed password for invalid user from 112.85.42.200 port 47922 ssh2
2020-10-09 05:02:22
51.68.172.217 attackspambots
$f2bV_matches
2020-10-09 05:11:38
141.98.80.22 attackspambots
UTC 10/08/2020 18:12:24 - 83 - Security Services - Alert - 141.98.80.22, 65534, X1 - xxx.xxx.xxx.xxx, 8651, X1 - tcp - TCP scanned port list, 8691, 8611, 8671, 8601, 8661, 8641, 8681, 8631, 8621, 8651 - Probable port scan detected
2020-10-09 05:32:34
74.120.14.18 attack
 UDP 74.120.14.18:30464 -> port 5632, len 30
2020-10-09 05:27:24
107.77.172.133 attackbots
Brute forcing email accounts
2020-10-09 05:25:51
182.52.136.16 attackspambots
Unauthorized connection attempt from IP address 182.52.136.16 on Port 445(SMB)
2020-10-09 05:20:22
114.224.178.217 attack
Oct  8 10:17:39 Tower sshd[6296]: Connection from 114.224.178.217 port 60886 on 192.168.10.220 port 22 rdomain ""
Oct  8 10:17:43 Tower sshd[6296]: Failed password for root from 114.224.178.217 port 60886 ssh2
Oct  8 10:17:43 Tower sshd[6296]: Received disconnect from 114.224.178.217 port 60886:11: Bye Bye [preauth]
Oct  8 10:17:43 Tower sshd[6296]: Disconnected from authenticating user root 114.224.178.217 port 60886 [preauth]
2020-10-09 05:05:13
190.153.174.162 attackbots
Unauthorized connection attempt from IP address 190.153.174.162 on Port 445(SMB)
2020-10-09 05:14:51
138.68.255.120 attackspam
Oct  8 09:25:02 vps46666688 sshd[19317]: Failed password for root from 138.68.255.120 port 39298 ssh2
...
2020-10-09 05:26:55
194.5.206.145 attackspambots
Oct  8 21:38:06 rancher-0 sshd[547736]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=194.5.206.145  user=root
Oct  8 21:38:09 rancher-0 sshd[547736]: Failed password for root from 194.5.206.145 port 50808 ssh2
...
2020-10-09 05:22:13
95.109.88.253 attackbotsspam
SSH invalid-user multiple login attempts
2020-10-09 05:12:41

Recently Reported IPs

112.80.136.166 112.80.136.192 112.80.136.241 112.80.136.29
112.80.136.37 112.80.136.52 112.80.136.72 112.80.137.101
112.80.137.133 112.80.137.132 112.80.137.146 112.80.137.165
112.80.137.229 112.80.137.200 112.80.137.243 112.80.137.25
112.80.138.10 112.80.137.70 112.80.138.108 112.80.137.253