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

;; QUESTION SECTION:
;112.80.136.124.			IN	A

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

;; Query time: 72 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 124.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 124.136.80.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
78.128.113.67 attackbots
Jul 18 21:58:26 relay postfix/smtpd\[1744\]: warning: unknown\[78.128.113.67\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul 18 21:58:33 relay postfix/smtpd\[13946\]: warning: unknown\[78.128.113.67\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul 18 22:09:10 relay postfix/smtpd\[13946\]: warning: unknown\[78.128.113.67\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul 18 22:09:17 relay postfix/smtpd\[20475\]: warning: unknown\[78.128.113.67\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul 18 22:09:43 relay postfix/smtpd\[18147\]: warning: unknown\[78.128.113.67\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-07-19 04:09:51
116.237.89.3 attack
firewall-block, port(s): 445/tcp
2019-07-19 03:43:37
14.185.144.162 attackbots
$f2bV_matches
2019-07-19 04:22:03
110.235.211.53 attackbotsspam
Automatic report - Port Scan Attack
2019-07-19 03:45:33
103.110.89.148 attack
$f2bV_matches
2019-07-19 04:15:22
85.117.235.115 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2019-07-19 04:15:39
85.67.203.144 attackbotsspam
MultiHost/MultiPort Probe, Scan, Hack -
2019-07-19 03:41:39
46.105.244.17 attackspambots
Jul 18 19:57:40 mail sshd\[9594\]: Invalid user guest1 from 46.105.244.17 port 40834
Jul 18 19:57:40 mail sshd\[9594\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.105.244.17
Jul 18 19:57:42 mail sshd\[9594\]: Failed password for invalid user guest1 from 46.105.244.17 port 40834 ssh2
Jul 18 20:03:32 mail sshd\[9684\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.105.244.17  user=backup
Jul 18 20:03:34 mail sshd\[9684\]: Failed password for backup from 46.105.244.17 port 36936 ssh2
...
2019-07-19 04:06:55
89.36.215.248 attackspam
Jul 18 23:07:52 server01 sshd\[3663\]: Invalid user ahmadi from 89.36.215.248
Jul 18 23:07:52 server01 sshd\[3663\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.36.215.248
Jul 18 23:07:54 server01 sshd\[3663\]: Failed password for invalid user ahmadi from 89.36.215.248 port 43424 ssh2
...
2019-07-19 04:19:30
201.22.95.52 attack
vps1:sshd-InvalidUser
2019-07-19 03:58:14
85.105.128.131 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-07-19 04:21:31
211.23.61.194 attackbots
Jul 18 21:06:27 srv206 sshd[17457]: Invalid user ivan from 211.23.61.194
...
2019-07-19 04:24:12
177.68.148.10 attackspam
Jul 18 16:22:03 debian sshd\[30124\]: Invalid user louise from 177.68.148.10 port 54198
Jul 18 16:22:03 debian sshd\[30124\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.68.148.10
Jul 18 16:22:05 debian sshd\[30124\]: Failed password for invalid user louise from 177.68.148.10 port 54198 ssh2
...
2019-07-19 04:22:45
106.13.22.75 attack
http
2019-07-19 03:43:54
122.140.52.64 attackbotsspam
firewall-block, port(s): 23/tcp
2019-07-19 03:41:11

Recently Reported IPs

112.80.127.186 112.80.136.159 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