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

;; QUESTION SECTION:
;112.80.136.160.			IN	A

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

;; Query time: 92 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 160.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 160.136.80.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
206.189.77.137 attackspam
Attempted connection to port 3389.
2020-04-15 06:27:20
222.186.173.238 attackspambots
Apr 14 23:38:40 santamaria sshd\[8565\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.238  user=root
Apr 14 23:38:43 santamaria sshd\[8565\]: Failed password for root from 222.186.173.238 port 33676 ssh2
Apr 14 23:38:59 santamaria sshd\[8573\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.238  user=root
...
2020-04-15 06:04:59
51.254.220.20 attackspambots
Apr 14 23:01:34 localhost sshd\[22002\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.254.220.20  user=root
Apr 14 23:01:37 localhost sshd\[22002\]: Failed password for root from 51.254.220.20 port 39930 ssh2
Apr 14 23:05:23 localhost sshd\[22250\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.254.220.20  user=syslog
Apr 14 23:05:25 localhost sshd\[22250\]: Failed password for syslog from 51.254.220.20 port 37242 ssh2
Apr 14 23:08:27 localhost sshd\[22344\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.254.220.20  user=root
...
2020-04-15 06:19:49
167.172.153.137 attackspam
Bruteforce detected by fail2ban
2020-04-15 06:12:10
89.248.160.150 attack
89.248.160.150 was recorded 22 times by 13 hosts attempting to connect to the following ports: 40798,40804,40793. Incident counter (4h, 24h, all-time): 22, 120, 11204
2020-04-15 06:24:25
114.237.109.151 attackbotsspam
SpamScore above: 10.0
2020-04-15 06:18:57
196.52.43.119 attack
Fail2Ban Ban Triggered
2020-04-15 05:52:52
132.232.3.234 attackspambots
Apr 14 22:37:21 xeon sshd[1940]: Failed password for invalid user ntps from 132.232.3.234 port 45438 ssh2
2020-04-15 05:50:24
163.172.159.139 attackspambots
SSH Invalid Login
2020-04-15 05:55:57
222.186.180.41 attackspambots
Apr 15 00:19:08 srv206 sshd[2877]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.41  user=root
Apr 15 00:19:10 srv206 sshd[2877]: Failed password for root from 222.186.180.41 port 38028 ssh2
...
2020-04-15 06:20:55
187.141.71.27 attackbotsspam
Invalid user MMR from 187.141.71.27 port 52888
2020-04-15 06:10:41
139.59.58.115 attackspam
Apr 14 18:16:55 ny01 sshd[28996]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.58.115
Apr 14 18:16:57 ny01 sshd[28996]: Failed password for invalid user flw from 139.59.58.115 port 43658 ssh2
Apr 14 18:21:13 ny01 sshd[29607]: Failed password for root from 139.59.58.115 port 52034 ssh2
2020-04-15 06:27:50
45.235.86.21 attack
Apr 14 22:31:40 vmd26974 sshd[11724]: Failed password for root from 45.235.86.21 port 48392 ssh2
...
2020-04-15 06:02:27
41.226.165.197 attackspam
20/4/14@16:49:21: FAIL: Alarm-Network address from=41.226.165.197
20/4/14@16:49:22: FAIL: Alarm-Network address from=41.226.165.197
...
2020-04-15 06:16:42
120.132.101.8 attackbots
(sshd) Failed SSH login from 120.132.101.8 (CN/China/-): 5 in the last 3600 secs
2020-04-15 06:07:33

Recently Reported IPs

112.79.152.81 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 112.80.138.253 112.80.138.179