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
84.228.102.23 attackbotsspam
Automatic report - Port Scan Attack
2020-02-17 16:41:34
210.131.2.29 attack
SSH login attempts.
2020-02-17 16:16:11
77.40.3.157 attackbots
IP: 77.40.3.157
Ports affected
    Simple Mail Transfer (25) 
    Message Submission (587) 
ASN Details
   AS12389 Rostelecom
   Russia (RU)
   CIDR 77.40.0.0/17
Log Date: 17/02/2020 5:14:07 AM UTC
2020-02-17 16:35:37
196.218.45.172 attackbotsspam
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-17 16:42:27
36.78.132.86 attackspambots
20/2/16@23:57:46: FAIL: Alarm-Network address from=36.78.132.86
...
2020-02-17 16:12:41
222.186.169.43 attack
20/2/16@23:57:51: FAIL: Alarm-Intrusion address from=222.186.169.43
...
2020-02-17 16:05:10
61.28.108.122 attackspam
2020-02-17T09:05:54.634336scmdmz1 sshd[16479]: Invalid user mybotuser from 61.28.108.122 port 2285
2020-02-17T09:05:54.638610scmdmz1 sshd[16479]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.28.108.122
2020-02-17T09:05:54.634336scmdmz1 sshd[16479]: Invalid user mybotuser from 61.28.108.122 port 2285
2020-02-17T09:05:57.399910scmdmz1 sshd[16479]: Failed password for invalid user mybotuser from 61.28.108.122 port 2285 ssh2
2020-02-17T09:11:41.142036scmdmz1 sshd[17090]: Invalid user serveradmin from 61.28.108.122 port 2287
...
2020-02-17 16:14:18
95.183.51.118 attackbotsspam
SSH login attempts.
2020-02-17 16:38:25
137.97.76.178 attackbots
Port probing on unauthorized port 445
2020-02-17 16:22:13
159.89.165.127 attackspambots
>6 unauthorized SSH connections
2020-02-17 16:10:31
193.180.164.162 attackbots
SE_RESILANS-MNT_<177>1581925987 [1:2522047:3973] ET TOR Known Tor Relay/Router (Not Exit) Node TCP Traffic group 48 [Classification: Misc Attack] [Priority: 2] {TCP} 193.180.164.162:15691
2020-02-17 16:08:55
182.253.226.212 attackspam
Feb 17 05:57:45 vmd17057 sshd\[29854\]: Invalid user browser from 182.253.226.212 port 37228
Feb 17 05:57:45 vmd17057 sshd\[29854\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.253.226.212
Feb 17 05:57:48 vmd17057 sshd\[29854\]: Failed password for invalid user browser from 182.253.226.212 port 37228 ssh2
...
2020-02-17 16:09:35
172.81.237.219 attackbots
Feb 17 05:57:32 dev sshd\[32489\]: Invalid user userftp from 172.81.237.219 port 49364
Feb 17 05:57:32 dev sshd\[32489\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.81.237.219
Feb 17 05:57:34 dev sshd\[32489\]: Failed password for invalid user userftp from 172.81.237.219 port 49364 ssh2
2020-02-17 16:29:23
222.186.175.212 attackspambots
Feb 17 00:58:04 debian sshd[32541]: Unable to negotiate with 222.186.175.212 port 15272: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1 [preauth]
Feb 17 03:23:11 debian sshd[6787]: Unable to negotiate with 222.186.175.212 port 39984: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1 [preauth]
...
2020-02-17 16:31:41
185.4.132.135 attackbots
02/17/2020-09:06:04.398516 185.4.132.135 Protocol: 6 ET TOR Known Tor Exit Node Traffic group 36
2020-02-17 16:18:27

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