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

;; QUESTION SECTION:
;112.80.136.11.			IN	A

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

;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 21 00:18:36 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 11.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 11.136.80.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
103.81.84.140 attackspam
$f2bV_matches
2020-02-23 13:59:07
94.232.124.233 attack
Feb 23 07:09:14 markkoudstaal sshd[23811]: Failed password for root from 94.232.124.233 port 49248 ssh2
Feb 23 07:12:18 markkoudstaal sshd[24349]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.232.124.233
Feb 23 07:12:20 markkoudstaal sshd[24349]: Failed password for invalid user test from 94.232.124.233 port 35313 ssh2
2020-02-23 14:14:29
183.108.60.167 attackbots
Unauthorized connection attempt detected from IP address 183.108.60.167 to port 23 [J]
2020-02-23 14:43:30
222.186.30.167 attackspam
Feb 23 11:48:01 areeb-Workstation sshd[26569]: Failed password for root from 222.186.30.167 port 16393 ssh2
Feb 23 11:48:03 areeb-Workstation sshd[26569]: Failed password for root from 222.186.30.167 port 16393 ssh2
...
2020-02-23 14:18:24
140.143.140.242 attackspambots
Feb 23 06:47:05 dedicated sshd[21991]: Invalid user diana from 140.143.140.242 port 52302
2020-02-23 13:55:28
37.252.86.205 attack
1582433811 - 02/23/2020 05:56:51 Host: 37.252.86.205/37.252.86.205 Port: 445 TCP Blocked
2020-02-23 14:02:46
45.143.221.49 attackbotsspam
Trying ports that it shouldn't be.
2020-02-23 14:05:51
165.227.206.114 attackspam
$f2bV_matches
2020-02-23 14:26:06
148.70.18.221 attackspambots
Unauthorized connection attempt detected from IP address 148.70.18.221 to port 2220 [J]
2020-02-23 14:18:42
212.64.23.30 attackspambots
Feb 23 02:56:27 firewall sshd[23471]: Invalid user dev from 212.64.23.30
Feb 23 02:56:30 firewall sshd[23471]: Failed password for invalid user dev from 212.64.23.30 port 39068 ssh2
Feb 23 03:00:53 firewall sshd[23567]: Invalid user user from 212.64.23.30
...
2020-02-23 14:47:04
134.175.243.183 attack
Unauthorized connection attempt detected from IP address 134.175.243.183 to port 22
2020-02-23 14:21:20
141.212.122.137 attackbotsspam
Feb 23 05:56:43 debian-2gb-nbg1-2 kernel: \[4693007.577083\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=141.212.122.137 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=236 ID=54321 PROTO=TCP SPT=45392 DPT=63029 WINDOW=65535 RES=0x00 SYN URGP=0
2020-02-23 14:06:15
129.28.188.21 attack
$f2bV_matches
2020-02-23 14:07:06
112.85.42.181 attackspam
SSH Brute-Force attacks
2020-02-23 14:14:48
51.68.215.199 attack
POST /wp-login.php HTTP/1.1 200 2442 Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0
2020-02-23 14:16:49

Recently Reported IPs

112.8.92.222 112.80.136.2 112.80.136.246 112.80.136.252
112.80.137.102 112.80.137.104 112.80.137.140 112.80.137.177
112.80.137.208 112.80.137.224 112.80.137.61 112.80.137.82
112.80.137.85 112.80.138.163 112.80.138.224 112.80.138.32
112.80.138.37 112.80.138.5 112.80.138.76 112.80.138.85