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

;; QUESTION SECTION:
;112.80.136.12.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 12 00:37:05 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 12.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 12.136.80.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
193.201.224.76 attack
May 20 05:30:26 ms-srv sshd[25169]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.201.224.76
May 20 05:30:28 ms-srv sshd[25169]: Failed password for invalid user admin from 193.201.224.76 port 55163 ssh2
2020-02-03 04:16:29
103.242.173.118 attackbots
Portscan or hack attempt detected by psad/fwsnort
2020-02-03 04:12:41
92.118.37.67 attack
Feb  2 21:29:16 mail kernel: [84817.117275] [UFW BLOCK] IN=eth0 OUT= MAC=00:16:3c:05:0d:89:f8:66:f2:68:66:ff:08:00 SRC=92.118.37.67 DST=77.73.69.240 LEN=40 TOS=0x00 PREC=0x00 TTL=250 ID=58640 PROTO=TCP SPT=47648 DPT=22799 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2020-02-03 04:33:38
140.246.225.169 attackspambots
Unauthorized connection attempt detected from IP address 140.246.225.169 to port 2220 [J]
2020-02-03 04:29:15
112.200.108.74 attackbotsspam
DATE:2020-02-02 16:07:05, IP:112.200.108.74, PORT:1433 MSSQL brute force auth on honeypot server (honey-neo-dc)
2020-02-03 04:27:45
185.91.141.236 attackspam
Honeypot attack, port: 81, PTR: PTR record not found
2020-02-03 04:08:16
193.203.204.248 attack
Jun 29 12:09:50 ms-srv sshd[53950]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.203.204.248
Jun 29 12:09:52 ms-srv sshd[53950]: Failed password for invalid user admin from 193.203.204.248 port 37486 ssh2
2020-02-03 04:13:37
41.32.116.82 attackspambots
Automatic report - Port Scan Attack
2020-02-03 04:21:07
112.15.38.2 attack
#710 - [112.15.38.248] Closing connection (IP still banned)
#710 - [112.15.38.248] Closing connection (IP still banned)
#710 - [112.15.38.248] Closing connection (IP still banned)
#710 - [112.15.38.248] Closing connection (IP still banned)

........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=112.15.38.2
2020-02-03 04:22:25
73.100.211.143 attack
Feb  2 21:23:16 sso sshd[13484]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=73.100.211.143
Feb  2 21:23:18 sso sshd[13484]: Failed password for invalid user deploy from 73.100.211.143 port 34966 ssh2
...
2020-02-03 04:25:09
184.105.247.194 attackspambots
Unauthorized connection attempt detected from IP address 184.105.247.194 to port 873 [J]
2020-02-03 04:13:20
122.225.62.94 attackspambots
Honeypot attack, port: 445, PTR: PTR record not found
2020-02-03 04:11:18
60.54.88.98 attackspambots
Feb  2 16:24:57 pl3server sshd[940]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=60.54.88.98  user=r.r
Feb  2 16:24:59 pl3server sshd[940]: Failed password for r.r from 60.54.88.98 port 23154 ssh2
Feb  2 16:24:59 pl3server sshd[940]: Connection closed by 60.54.88.98 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=60.54.88.98
2020-02-03 04:15:14
144.76.29.149 attackbots
20 attempts against mh-misbehave-ban on milky
2020-02-03 04:10:59
200.201.158.197 attackbotsspam
Unauthorized connection attempt detected from IP address 200.201.158.197 to port 2220 [J]
2020-02-03 04:15:35

Recently Reported IPs

112.80.133.148 112.80.136.122 112.80.136.137 112.80.136.17
112.80.136.201 112.80.136.205 112.80.136.225 112.80.136.237
112.80.136.247 112.80.136.30 112.80.136.39 112.80.136.41
112.80.136.58 112.80.136.66 112.80.137.12 112.80.137.131
112.80.137.142 112.80.137.151 112.80.137.163 112.80.137.217