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

;; QUESTION SECTION:
;112.80.136.192.			IN	A

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

;; Query time: 20 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 14 06:39:45 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 192.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 192.136.80.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
176.190.35.100 attack
firewall-block, port(s): 23/tcp
2019-07-31 14:47:12
200.54.108.33 attackspambots
Unauthorized connection attempt from IP address 200.54.108.33 on Port 445(SMB)
2019-07-31 14:17:24
96.9.154.23 attackspambots
firewall-block, port(s): 445/tcp
2019-07-31 15:07:23
163.179.32.100 attackbots
WordpressAttack_WPLogin
2019-07-31 14:18:53
183.6.176.182 attack
Jul 31 02:59:05 xtremcommunity sshd\[830\]: Invalid user ospite from 183.6.176.182 port 37516
Jul 31 02:59:05 xtremcommunity sshd\[830\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.6.176.182
Jul 31 02:59:06 xtremcommunity sshd\[830\]: Failed password for invalid user ospite from 183.6.176.182 port 37516 ssh2
Jul 31 03:04:35 xtremcommunity sshd\[956\]: Invalid user temp1 from 183.6.176.182 port 54511
Jul 31 03:04:35 xtremcommunity sshd\[956\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.6.176.182
...
2019-07-31 15:04:46
144.217.4.14 attack
Jul 31 07:27:49 vps647732 sshd[25173]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.217.4.14
Jul 31 07:27:51 vps647732 sshd[25173]: Failed password for invalid user git from 144.217.4.14 port 44912 ssh2
...
2019-07-31 14:17:51
36.66.117.29 attack
Jul 31 07:53:49 [munged] sshd[20125]: Invalid user nice from 36.66.117.29 port 36324
Jul 31 07:53:49 [munged] sshd[20125]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.66.117.29
2019-07-31 14:29:55
186.91.184.84 attack
Unauthorized connection attempt from IP address 186.91.184.84 on Port 445(SMB)
2019-07-31 14:36:42
189.5.74.236 attack
Jul 30 03:18:55 datentool sshd[24836]: Invalid user natasha from 189.5.74.236
Jul 30 03:18:55 datentool sshd[24836]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.5.74.236 
Jul 30 03:18:57 datentool sshd[24836]: Failed password for invalid user natasha from 189.5.74.236 port 49102 ssh2
Jul 30 03:33:21 datentool sshd[24906]: Invalid user gerencia from 189.5.74.236
Jul 30 03:33:21 datentool sshd[24906]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.5.74.236 
Jul 30 03:33:24 datentool sshd[24906]: Failed password for invalid user gerencia from 189.5.74.236 port 50688 ssh2
Jul 30 03:39:47 datentool sshd[24932]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.5.74.236  user=r.r
Jul 30 03:39:50 datentool sshd[24932]: Failed password for r.r from 189.5.74.236 port 47004 ssh2
Jul 30 03:46:16 datentool sshd[24984]: Invalid user netadmin from 189........
-------------------------------
2019-07-31 14:49:26
117.121.38.246 attackbotsspam
Jul 30 22:21:44 master sshd[14565]: Failed password for invalid user team from 117.121.38.246 port 51962 ssh2
Jul 30 22:57:18 master sshd[14914]: Failed password for invalid user sunsun from 117.121.38.246 port 45384 ssh2
Jul 30 23:03:36 master sshd[15240]: Failed password for root from 117.121.38.246 port 41622 ssh2
Jul 30 23:10:18 master sshd[15261]: Failed password for invalid user info from 117.121.38.246 port 37952 ssh2
Jul 30 23:16:23 master sshd[15288]: Failed password for invalid user sybase from 117.121.38.246 port 33960 ssh2
Jul 30 23:22:37 master sshd[15307]: Did not receive identification string from 117.121.38.246
Jul 30 23:28:37 master sshd[15329]: Failed password for invalid user recovery from 117.121.38.246 port 55060 ssh2
Jul 30 23:34:43 master sshd[15661]: Failed password for invalid user admin from 117.121.38.246 port 51352 ssh2
Jul 30 23:39:59 master sshd[15679]: Failed password for root from 117.121.38.246 port 47212 ssh2
Jul 30 23:45:20 master sshd[15722]: Failed password for invalid use
2019-07-31 14:45:17
119.29.62.104 attackbotsspam
SSH-BruteForce
2019-07-31 14:48:12
119.160.65.12 attackbotsspam
Time:     Tue Jul 30 19:20:46 2019 -0300
IP:       119.160.65.12 (PK/Pakistan/host-12-net-65-160-119.mobilinkinfinity.net.pk)
Failures: 5 (smtpauth)
Interval: 3600 seconds
Blocked:  Permanent Block
2019-07-31 14:57:05
35.201.165.242 attack
2019-07-31T04:11:07.250016abusebot-8.cloudsearch.cf sshd\[11796\]: Invalid user support from 35.201.165.242 port 58100
2019-07-31 14:48:44
116.31.116.2 attack
Port scan attempt detected by AWS-CCS, CTS, India
2019-07-31 14:20:25
180.231.45.132 attackbots
Jul 31 00:31:29 vps65 sshd\[28511\]: Invalid user italy from 180.231.45.132 port 36502
Jul 31 00:31:29 vps65 sshd\[28511\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.231.45.132
...
2019-07-31 15:02:08

Recently Reported IPs

112.80.136.178 112.80.136.241 112.80.136.29 112.80.136.37
112.80.136.52 112.80.136.72 112.80.137.101 112.80.137.133
112.80.137.132 112.80.137.146 112.80.137.165 112.80.137.229
112.80.137.200 112.80.137.243 112.80.137.25 112.80.138.10
112.80.137.70 112.80.138.108 112.80.137.253 112.80.138.127