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

;; QUESTION SECTION:
;112.80.136.200.			IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 05:52:08 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 200.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 200.136.80.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
81.29.215.84 attackspambots
CMS (WordPress or Joomla) login attempt.
2020-04-15 18:15:40
68.66.248.35 attackspambots
xmlrpc attack
2020-04-15 18:14:52
188.114.110.217 attackbotsspam
$f2bV_matches
2020-04-15 18:19:27
103.217.135.124 attackbotsspam
Telnet/23 MH Probe, Scan, BF, Hack -
2020-04-15 18:13:57
91.217.63.14 attack
2020-04-15T09:59:26.477553shield sshd\[9247\]: Invalid user liliana from 91.217.63.14 port 53488
2020-04-15T09:59:26.483602shield sshd\[9247\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.217.63.14
2020-04-15T09:59:28.560013shield sshd\[9247\]: Failed password for invalid user liliana from 91.217.63.14 port 53488 ssh2
2020-04-15T10:03:23.053432shield sshd\[10025\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.217.63.14  user=root
2020-04-15T10:03:25.335147shield sshd\[10025\]: Failed password for root from 91.217.63.14 port 57666 ssh2
2020-04-15 18:11:26
182.61.1.161 attack
5x Failed Password
2020-04-15 18:20:38
51.254.37.192 attack
2020-04-15T02:53:21.939697linuxbox-skyline sshd[134460]: Invalid user deploy from 51.254.37.192 port 52040
...
2020-04-15 17:49:05
45.95.168.111 attackbotsspam
MAIL: User Login Brute Force Attempt
2020-04-15 18:08:26
66.135.227.178 attackbots
(imapd) Failed IMAP login from 66.135.227.178 (US/United States/mail.dellew.com): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: Apr 15 08:24:10 ir1 dovecot[566034]: imap-login: Disconnected (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=66.135.227.178, lip=5.63.12.44, TLS, session=
2020-04-15 17:56:07
198.98.62.43 attackspam
198.98.62.43 was recorded 16 times by 10 hosts attempting to connect to the following ports: 53413. Incident counter (4h, 24h, all-time): 16, 18, 291
2020-04-15 17:53:51
1.193.39.196 attackbots
Apr 15 10:26:33 DAAP sshd[29425]: Invalid user pmc2 from 1.193.39.196 port 55070
Apr 15 10:26:33 DAAP sshd[29425]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.193.39.196
Apr 15 10:26:33 DAAP sshd[29425]: Invalid user pmc2 from 1.193.39.196 port 55070
Apr 15 10:26:35 DAAP sshd[29425]: Failed password for invalid user pmc2 from 1.193.39.196 port 55070 ssh2
...
2020-04-15 18:08:42
222.186.180.147 attackspambots
Apr 15 12:11:47 * sshd[24634]: Failed password for root from 222.186.180.147 port 53612 ssh2
Apr 15 12:12:01 * sshd[24634]: error: maximum authentication attempts exceeded for root from 222.186.180.147 port 53612 ssh2 [preauth]
2020-04-15 18:18:36
67.219.145.13 attack
SpamScore above: 10.0
2020-04-15 17:48:35
45.133.99.16 attackspambots
Apr 15 11:28:44 mail postfix/smtpd\[16520\]: warning: unknown\[45.133.99.16\]: SASL PLAIN authentication failed: \
Apr 15 11:28:44 mail postfix/smtpd\[16354\]: warning: unknown\[45.133.99.16\]: SASL PLAIN authentication failed: \
Apr 15 11:28:47 mail postfix/smtpd\[16354\]: warning: unknown\[45.133.99.16\]: SASL PLAIN authentication failed: \
Apr 15 11:28:47 mail postfix/smtpd\[16541\]: warning: unknown\[45.133.99.16\]: SASL PLAIN authentication failed: \
2020-04-15 18:07:59
119.188.246.155 attack
postfix
2020-04-15 17:57:46

Recently Reported IPs

112.80.136.196 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 112.80.139.35