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
91.134.140.32 attackbots
Jun 28 07:17:49 herz-der-gamer sshd[1790]: Invalid user test from 91.134.140.32 port 45172
Jun 28 07:17:49 herz-der-gamer sshd[1790]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.134.140.32
Jun 28 07:17:49 herz-der-gamer sshd[1790]: Invalid user test from 91.134.140.32 port 45172
Jun 28 07:17:51 herz-der-gamer sshd[1790]: Failed password for invalid user test from 91.134.140.32 port 45172 ssh2
...
2019-06-28 13:58:11
193.112.208.153 attack
[FriJun2807:16:45.0558382019][:error][pid6260:tid47523401717504][client193.112.208.153:54100][client193.112.208.153]ModSecurity:Accessdeniedwithcode403\(phase2\).Matchof"rx\(MSWebServicesClientProtocol\|WormlyBot\|webauth@cmcm\\\\\\\\.com\)"against"REQUEST_HEADERS:User-Agent"required.[file"/usr/local/apache.ea3/conf/modsec_rules/20_asl_useragents.conf"][line"390"][id"397989"][rev"1"][msg"Atomicorp.comWAFRules:MSIE6.0detected\(DisableifyouwanttoallowMSIE6\)"][severity"WARNING"][hostname"ledpiu.ch"][uri"/wp-content/plugins/xt-woo-quick-view-lite/license.txt"][unique_id"XRWivY2CfksQKqSDdiVt7wAAAIk"][FriJun2807:16:51.9283472019][:error][pid6261:tid47523481786112][client193.112.208.153:54219][client193.112.208.153]ModSecurity:Accessdeniedwithcode403\(phase2\).Matchof"rx\(MSWebServicesClientProtocol\|WormlyBot\|webauth@cmcm\\\\\\\\.com\)"against"REQUEST_HEADERS:User-Agent"required.[file"/usr/local/apache.ea3/conf/modsec_rules/20_asl_useragents.conf"][line"390"][id"397989"][rev"1"][
2019-06-28 14:32:12
139.59.78.236 attack
SSH Bruteforce Attack
2019-06-28 13:52:33
116.206.92.77 attackbots
CloudCIX Reconnaissance Scan Detected, PTR: PTR record not found
2019-06-28 14:04:05
220.191.249.253 attack
CloudCIX Reconnaissance Scan Detected, PTR: PTR record not found
2019-06-28 14:25:27
102.165.49.30 attackbotsspam
CloudCIX Reconnaissance Scan Detected, PTR: PTR record not found
2019-06-28 14:17:18
128.14.209.246 attackspambots
3389BruteforceFW21
2019-06-28 01:18:50
130.162.66.198 attack
frenzy
2019-06-28 13:57:41
77.247.109.39 attack
CloudCIX Reconnaissance Scan Detected, PTR: PTR record not found
2019-06-28 14:20:27
125.64.94.201 attack
CloudCIX Reconnaissance Scan Detected, PTR: PTR record not found
2019-06-28 14:30:33
199.116.138.170 attackspam
CloudCIX Reconnaissance Scan Detected, PTR: PTR record not found
2019-06-28 13:55:53
178.128.47.207 attackspambots
CloudCIX Reconnaissance Scan Detected, PTR: PTR record not found
2019-06-28 13:51:41
185.53.91.50 attackbotsspam
CloudCIX Reconnaissance Scan Detected, PTR: PTR record not found
2019-06-28 13:57:01
117.158.156.32 attack
CloudCIX Reconnaissance Scan Detected, PTR: PTR record not found
2019-06-28 14:13:16
168.205.110.230 attack
SMTP-sasl brute force
...
2019-06-28 14:10:59

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