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

;; QUESTION SECTION:
;112.80.136.255.			IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 25 13:10:35 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 255.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 255.136.80.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
114.7.163.86 attack
Feb 17 05:58:37 mars sshd[5582]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.7.163.86
Feb 17 05:58:38 mars sshd[5582]: Failed password for invalid user vds from 114.7.163.86 port 59029 ssh2
...
2020-02-17 14:56:04
114.47.83.195 attackspam
Unauthorized connection attempt detected from IP address 114.47.83.195 to port 445
2020-02-17 14:49:27
107.183.242.58 attack
Port probing on unauthorized port 445
2020-02-17 14:28:12
129.213.36.226 attackbots
Feb 17 05:56:50 sd-53420 sshd\[21672\]: Invalid user newuser from 129.213.36.226
Feb 17 05:56:50 sd-53420 sshd\[21672\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.213.36.226
Feb 17 05:56:52 sd-53420 sshd\[21672\]: Failed password for invalid user newuser from 129.213.36.226 port 48050 ssh2
Feb 17 05:58:45 sd-53420 sshd\[21853\]: Invalid user test from 129.213.36.226
Feb 17 05:58:45 sd-53420 sshd\[21853\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.213.36.226
...
2020-02-17 14:47:43
70.95.63.117 attack
W 31101,/var/log/nginx/access.log,-,-
2020-02-17 14:37:52
138.197.195.52 attackspambots
$f2bV_matches
2020-02-17 14:55:46
196.219.113.46 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-17 14:51:03
203.124.15.85 attackspam
SSH login attempts.
2020-02-17 14:36:37
167.71.102.136 attack
" "
2020-02-17 14:53:30
195.191.88.99 attackspam
ssh brute force
2020-02-17 14:38:34
74.6.136.150 attackbotsspam
SSH login attempts.
2020-02-17 15:02:21
91.134.140.242 attack
Feb 17 07:40:48 lnxded64 sshd[11903]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.134.140.242
Feb 17 07:40:48 lnxded64 sshd[11903]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.134.140.242
2020-02-17 14:56:23
104.47.49.36 attackbotsspam
SSH login attempts.
2020-02-17 14:46:08
2.238.193.59 attackspambots
Feb 17 01:58:36 vps46666688 sshd[12218]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=2.238.193.59
Feb 17 01:58:38 vps46666688 sshd[12218]: Failed password for invalid user svn from 2.238.193.59 port 38746 ssh2
...
2020-02-17 14:57:26
122.219.108.171 attackspam
(sshd) Failed SSH login from 122.219.108.171 (JP/Japan/171.168/29.108.219.122.in-addr.arpa): 2 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Feb 17 05:58:51 ubnt-55d23 sshd[6292]: Invalid user sentry from 122.219.108.171 port 46278
Feb 17 05:58:53 ubnt-55d23 sshd[6292]: Failed password for invalid user sentry from 122.219.108.171 port 46278 ssh2
2020-02-17 14:30:24

Recently Reported IPs

112.80.136.206 112.80.136.42 112.80.136.46 112.80.136.216
112.80.136.5 109.202.26.210 112.80.136.80 112.80.136.9
112.80.137.164 112.80.137.183 112.80.137.20 112.80.137.186
112.80.137.201 112.80.138.104 112.80.137.255 112.80.138.112
112.80.138.113 112.80.137.213 112.80.138.204 112.80.138.180