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

;; QUESTION SECTION:
;112.80.136.196.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 05:52:07 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 196.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 196.136.80.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
34.93.44.102 attackbots
php WP PHPmyadamin ABUSE blocked for 12h
2019-08-23 02:51:35
51.158.187.105 attackbotsspam
Aug 22 01:24:57 hcbb sshd\[16171\]: Invalid user eye from 51.158.187.105
Aug 22 01:24:57 hcbb sshd\[16171\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.158.187.105
Aug 22 01:25:00 hcbb sshd\[16171\]: Failed password for invalid user eye from 51.158.187.105 port 60142 ssh2
Aug 22 01:29:05 hcbb sshd\[16572\]: Invalid user allen from 51.158.187.105
Aug 22 01:29:05 hcbb sshd\[16572\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.158.187.105
2019-08-23 03:13:04
150.95.110.73 attackspambots
Aug 22 18:16:23 ns315508 sshd[5173]: Invalid user www from 150.95.110.73 port 55976
Aug 22 18:16:23 ns315508 sshd[5173]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=150.95.110.73
Aug 22 18:16:23 ns315508 sshd[5173]: Invalid user www from 150.95.110.73 port 55976
Aug 22 18:16:25 ns315508 sshd[5173]: Failed password for invalid user www from 150.95.110.73 port 55976 ssh2
Aug 22 18:21:03 ns315508 sshd[5217]: Invalid user sai from 150.95.110.73 port 44074
...
2019-08-23 03:05:38
218.92.1.142 attackspambots
Aug 22 14:05:23 TORMINT sshd\[26265\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.1.142  user=root
Aug 22 14:05:25 TORMINT sshd\[26265\]: Failed password for root from 218.92.1.142 port 30206 ssh2
Aug 22 14:06:14 TORMINT sshd\[26370\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.1.142  user=root
...
2019-08-23 02:22:31
119.3.179.89 attackspambots
$f2bV_matches
2019-08-23 02:35:14
118.114.246.42 attack
SASL Brute Force
2019-08-23 02:29:50
77.247.108.174 attackbotsspam
Port scanning 5060
2019-08-23 02:53:03
80.211.0.160 attackspambots
Aug 22 15:18:40 localhost sshd\[17024\]: Invalid user fmw from 80.211.0.160 port 39856
Aug 22 15:18:40 localhost sshd\[17024\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.211.0.160
Aug 22 15:18:42 localhost sshd\[17024\]: Failed password for invalid user fmw from 80.211.0.160 port 39856 ssh2
2019-08-23 02:27:18
186.147.35.76 attack
Aug 22 19:06:20 server sshd\[13895\]: Invalid user 123456 from 186.147.35.76 port 48313
Aug 22 19:06:20 server sshd\[13895\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.147.35.76
Aug 22 19:06:22 server sshd\[13895\]: Failed password for invalid user 123456 from 186.147.35.76 port 48313 ssh2
Aug 22 19:11:25 server sshd\[5407\]: Invalid user ian123 from 186.147.35.76 port 42442
Aug 22 19:11:25 server sshd\[5407\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.147.35.76
2019-08-23 02:21:20
182.16.103.136 attack
Aug 22 18:55:20 legacy sshd[2822]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.16.103.136
Aug 22 18:55:22 legacy sshd[2822]: Failed password for invalid user sll from 182.16.103.136 port 48696 ssh2
Aug 22 19:01:37 legacy sshd[2976]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.16.103.136
...
2019-08-23 02:39:33
112.35.46.21 attackbots
Automatic report - Banned IP Access
2019-08-23 02:21:57
222.127.99.45 attackbotsspam
Aug 22 08:46:50 sachi sshd\[28069\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.127.99.45  user=root
Aug 22 08:46:52 sachi sshd\[28069\]: Failed password for root from 222.127.99.45 port 54578 ssh2
Aug 22 08:51:52 sachi sshd\[28615\]: Invalid user chuan from 222.127.99.45
Aug 22 08:51:52 sachi sshd\[28615\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.127.99.45
Aug 22 08:51:54 sachi sshd\[28615\]: Failed password for invalid user chuan from 222.127.99.45 port 50215 ssh2
2019-08-23 03:12:00
159.203.82.104 attackbots
2019-08-22T12:55:25.232638abusebot-6.cloudsearch.cf sshd\[23907\]: Invalid user petru from 159.203.82.104 port 36112
2019-08-23 03:03:22
14.192.49.47 attackbotsspam
php WP PHPmyadamin ABUSE blocked for 12h
2019-08-23 02:46:11
51.143.132.213 attackbots
Aug 22 19:54:01 tux-35-217 sshd\[31077\]: Invalid user mon from 51.143.132.213 port 39964
Aug 22 19:54:01 tux-35-217 sshd\[31077\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.143.132.213
Aug 22 19:54:03 tux-35-217 sshd\[31077\]: Failed password for invalid user mon from 51.143.132.213 port 39964 ssh2
Aug 22 19:58:43 tux-35-217 sshd\[31111\]: Invalid user laurie from 51.143.132.213 port 58624
Aug 22 19:58:43 tux-35-217 sshd\[31111\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.143.132.213
...
2019-08-23 02:25:08

Recently Reported IPs

112.8.50.236 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 112.80.138.253 112.80.138.179
112.80.138.25 112.80.139.170 112.80.139.14 112.80.138.83