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

;; QUESTION SECTION:
;112.80.136.202.			IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 13:33:08 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 202.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 202.136.80.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
194.33.87.229 attackbotsspam
Port scan on 1 port(s): 445
2020-10-14 00:23:34
54.38.139.210 attackbots
Repeated brute force against a port
2020-10-14 00:55:15
125.86.191.19 attack
SSH/22 MH Probe, BF, Hack -
2020-10-14 00:44:20
159.65.154.48 attackbots
Oct 13 16:44:19 ourumov-web sshd\[19162\]: Invalid user scott from 159.65.154.48 port 49628
Oct 13 16:44:19 ourumov-web sshd\[19162\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.154.48
Oct 13 16:44:22 ourumov-web sshd\[19162\]: Failed password for invalid user scott from 159.65.154.48 port 49628 ssh2
...
2020-10-14 00:56:11
192.241.217.83 attackbots
2020-10-13T13:48:59.782637mail.broermann.family sshd[18704]: Failed password for root from 192.241.217.83 port 52026 ssh2
2020-10-13T13:53:49.393888mail.broermann.family sshd[19218]: Invalid user frank from 192.241.217.83 port 56658
2020-10-13T13:53:49.401437mail.broermann.family sshd[19218]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.241.217.83
2020-10-13T13:53:49.393888mail.broermann.family sshd[19218]: Invalid user frank from 192.241.217.83 port 56658
2020-10-13T13:53:52.265677mail.broermann.family sshd[19218]: Failed password for invalid user frank from 192.241.217.83 port 56658 ssh2
...
2020-10-14 00:42:49
218.92.0.133 attack
various type of attack
2020-10-14 00:31:27
67.205.153.4 attackbots
SSH Brute Force
2020-10-14 00:30:36
106.51.78.105 attackspambots
SSH Brute-Force Attack
2020-10-14 00:38:42
125.215.207.44 attackbots
Oct 13 18:13:15 ns3164893 sshd[19168]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.215.207.44
Oct 13 18:13:17 ns3164893 sshd[19168]: Failed password for invalid user carola from 125.215.207.44 port 53626 ssh2
...
2020-10-14 00:25:32
95.29.50.43 attackbotsspam
Unauthorized connection attempt detected from IP address 95.29.50.43 to port 23 [T]
2020-10-14 00:28:44
182.119.249.17 attackbotsspam
Port probing on unauthorized port 23
2020-10-14 01:00:21
151.80.212.71 attack
Attempted WordPress login: "GET /wp-login.php"
2020-10-14 00:54:49
139.99.40.44 attackspambots
Connection to SSH Honeypot - Detected by HoneypotDB
2020-10-14 00:24:05
129.226.160.128 attackspambots
Invalid user ac from 129.226.160.128 port 33448
2020-10-14 01:02:49
103.26.136.173 attackspam
Invalid user nieto from 103.26.136.173 port 48482
2020-10-14 00:52:49

Recently Reported IPs

112.80.136.212 112.80.136.210 112.80.136.211 112.80.136.234
112.80.136.213 112.80.136.229 112.80.136.45 112.80.136.236
112.80.136.243 112.80.136.79 112.80.136.81 112.80.136.83
112.80.137.103 112.80.136.242 112.80.136.95 112.80.136.76
112.80.137.125 112.80.137.126 112.80.136.75 112.80.137.162