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

;; QUESTION SECTION:
;112.80.136.159.			IN	A

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

;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 05:52:05 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 159.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 159.136.80.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
91.243.162.154 attackbotsspam
Unauthorized connection attempt from IP address 91.243.162.154 on Port 445(SMB)
2020-03-30 01:39:29
122.51.234.16 attack
$f2bV_matches
2020-03-30 01:37:36
58.37.230.85 attackspambots
Mar 29 16:33:57 host sshd[16855]: Invalid user z from 58.37.230.85 port 12181
...
2020-03-30 01:43:49
115.76.222.232 attackbotsspam
Automatic report - Port Scan Attack
2020-03-30 02:06:36
200.29.111.182 attack
Mar 29 19:17:26 tuxlinux sshd[22261]: Invalid user mkx from 200.29.111.182 port 43657
Mar 29 19:17:26 tuxlinux sshd[22261]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.29.111.182 
Mar 29 19:17:26 tuxlinux sshd[22261]: Invalid user mkx from 200.29.111.182 port 43657
Mar 29 19:17:26 tuxlinux sshd[22261]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.29.111.182 
Mar 29 19:17:26 tuxlinux sshd[22261]: Invalid user mkx from 200.29.111.182 port 43657
Mar 29 19:17:26 tuxlinux sshd[22261]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.29.111.182 
Mar 29 19:17:27 tuxlinux sshd[22261]: Failed password for invalid user mkx from 200.29.111.182 port 43657 ssh2
...
2020-03-30 01:36:44
176.14.81.8 attackbots
Unauthorized connection attempt from IP address 176.14.81.8 on Port 445(SMB)
2020-03-30 01:43:29
106.13.172.200 attackbotsspam
Mar 29 12:38:01 powerpi2 sshd[31685]: Invalid user bnt from 106.13.172.200 port 43626
Mar 29 12:38:03 powerpi2 sshd[31685]: Failed password for invalid user bnt from 106.13.172.200 port 43626 ssh2
Mar 29 12:44:49 powerpi2 sshd[32279]: Invalid user wangyue from 106.13.172.200 port 46468
...
2020-03-30 02:02:21
115.79.214.209 attackbots
Automatic report - Port Scan Attack
2020-03-30 01:31:29
180.128.8.7 attackspam
Triggered by Fail2Ban at Ares web server
2020-03-30 02:10:34
200.44.233.245 attackbotsspam
Attempt to attack host OS, exploiting network vulnerabilities, on 29-03-2020 13:45:10.
2020-03-30 01:39:09
35.225.177.93 attack
2020-03-29T16:11:59.092191Z a924fd98062a New connection: 35.225.177.93:51384 (172.17.0.3:2222) [session: a924fd98062a]
2020-03-29T16:21:27.804934Z e24d67078b4b New connection: 35.225.177.93:52694 (172.17.0.3:2222) [session: e24d67078b4b]
2020-03-30 02:01:30
185.132.53.56 attack
Mar 29 15:10:43 master sshd[23563]: Failed password for root from 185.132.53.56 port 57060 ssh2
2020-03-30 01:40:41
106.124.135.232 attack
SSH Brute-Forcing (server1)
2020-03-30 01:51:14
114.219.56.124 attackbotsspam
fail2ban/Mar 29 12:41:45 h1962932 sshd[9821]: Invalid user pht from 114.219.56.124 port 36902
Mar 29 12:41:45 h1962932 sshd[9821]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.219.56.124
Mar 29 12:41:45 h1962932 sshd[9821]: Invalid user pht from 114.219.56.124 port 36902
Mar 29 12:41:47 h1962932 sshd[9821]: Failed password for invalid user pht from 114.219.56.124 port 36902 ssh2
Mar 29 12:45:00 h1962932 sshd[9916]: Invalid user jcp from 114.219.56.124 port 42806
2020-03-30 01:50:53
192.99.245.147 attackbots
$f2bV_matches
2020-03-30 01:27:28

Recently Reported IPs

112.80.136.124 112.79.152.81 112.80.136.160 112.80.136.125
112.80.136.163 112.8.50.236 112.80.136.196 112.80.136.200
112.80.136.28 112.80.136.50 112.80.136.60 112.80.137.108
112.80.136.57 112.80.137.160 112.80.137.219 112.80.137.27
112.80.137.92 112.80.138.157 112.80.138.184 112.80.138.188