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: None

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

;; QUESTION SECTION:
;112.80.136.65.			IN	A

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

;; Query time: 70 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Mar 07 22:54:10 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 65.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 65.136.80.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
62.234.139.150 attack
Unauthorized connection attempt detected from IP address 62.234.139.150 to port 2220 [J]
2020-01-18 04:11:50
49.233.183.7 attackspam
Unauthorized connection attempt detected from IP address 49.233.183.7 to port 2220 [J]
2020-01-18 04:45:28
94.23.212.137 attackbotsspam
Unauthorized connection attempt detected from IP address 94.23.212.137 to port 2220 [J]
2020-01-18 04:09:40
61.252.141.83 attack
SSH login attempts.
2020-01-18 04:43:41
147.102.101.238 attack
Unauthorized connection attempt detected from IP address 147.102.101.238 to port 22 [T]
2020-01-18 04:29:11
179.191.224.126 attackbotsspam
Jan 17 18:59:51 ns392434 sshd[2739]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.191.224.126  user=root
Jan 17 18:59:53 ns392434 sshd[2739]: Failed password for root from 179.191.224.126 port 44188 ssh2
Jan 17 19:11:36 ns392434 sshd[3025]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.191.224.126  user=root
Jan 17 19:11:38 ns392434 sshd[3025]: Failed password for root from 179.191.224.126 port 50730 ssh2
Jan 17 19:13:41 ns392434 sshd[3042]: Invalid user usuarios from 179.191.224.126 port 39498
Jan 17 19:13:41 ns392434 sshd[3042]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.191.224.126
Jan 17 19:13:41 ns392434 sshd[3042]: Invalid user usuarios from 179.191.224.126 port 39498
Jan 17 19:13:43 ns392434 sshd[3042]: Failed password for invalid user usuarios from 179.191.224.126 port 39498 ssh2
Jan 17 19:15:42 ns392434 sshd[3056]: Invalid user q from 179.191.224.126 port 56510
2020-01-18 04:24:23
117.232.127.50 attackspam
Invalid user sybase from 117.232.127.50 port 50760
2020-01-18 04:36:48
157.245.86.176 attack
Unauthorized connection attempt detected from IP address 157.245.86.176 to port 2220 [J]
2020-01-18 04:28:17
206.189.137.113 attack
Invalid user user from 206.189.137.113 port 51142
2020-01-18 04:18:42
49.233.183.158 attack
Unauthorized connection attempt detected from IP address 49.233.183.158 to port 2220 [J]
2020-01-18 04:14:54
103.86.51.93 attackbotsspam
Unauthorized connection attempt detected from IP address 103.86.51.93 to port 2220 [J]
2020-01-18 04:41:22
123.20.229.142 attackbotsspam
Invalid user admin from 123.20.229.142 port 45507
2020-01-18 04:34:17
165.22.58.247 attackspambots
Jan 17 11:52:34 server sshd\[19501\]: Invalid user support from 165.22.58.247
Jan 17 11:52:34 server sshd\[19501\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.58.247 
Jan 17 11:52:36 server sshd\[19501\]: Failed password for invalid user support from 165.22.58.247 port 52544 ssh2
Jan 17 19:33:45 server sshd\[5955\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.58.247  user=root
Jan 17 19:33:47 server sshd\[5955\]: Failed password for root from 165.22.58.247 port 39778 ssh2
...
2020-01-18 04:26:36
54.37.197.94 attack
Unauthorized connection attempt detected from IP address 54.37.197.94 to port 2220 [J]
2020-01-18 04:12:07
122.252.239.5 attackspam
Unauthorized connection attempt detected from IP address 122.252.239.5 to port 2220 [J]
2020-01-18 04:34:46

Recently Reported IPs

112.80.136.250 112.80.136.69 112.80.137.120 112.80.137.137
112.80.137.141 112.80.137.170 112.80.137.178 112.80.137.180
112.80.137.187 112.80.137.188 112.80.137.193 112.80.137.204
112.80.137.21 112.80.137.234 112.80.137.44 112.80.137.6
112.80.137.66 112.80.137.7 112.80.137.73 112.80.137.88