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

;; QUESTION SECTION:
;112.80.136.147.			IN	A

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

;; Query time: 57 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 21 14:43:30 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 147.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 147.136.80.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
89.31.57.5 attack
xmlrpc attack
2019-10-31 12:22:22
45.80.65.83 attack
Oct 31 09:20:55 gw1 sshd[10503]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.80.65.83
Oct 31 09:20:57 gw1 sshd[10503]: Failed password for invalid user sidra from 45.80.65.83 port 36522 ssh2
...
2019-10-31 12:32:26
5.237.84.77 attack
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/5.237.84.77/ 
 
 IR - 1H : (103)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : IR 
 NAME ASN : ASN58224 
 
 IP : 5.237.84.77 
 
 CIDR : 5.237.0.0/16 
 
 PREFIX COUNT : 898 
 
 UNIQUE IP COUNT : 2324736 
 
 
 ATTACKS DETECTED ASN58224 :  
  1H - 1 
  3H - 3 
  6H - 8 
 12H - 19 
 24H - 36 
 
 DateTime : 2019-10-31 04:56:29 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-10-31 12:41:23
176.65.96.111 attackbotsspam
Chat Spam
2019-10-31 12:52:49
142.93.83.218 attackspam
Oct 31 04:09:44 hcbbdb sshd\[29045\]: Invalid user just4now from 142.93.83.218
Oct 31 04:09:44 hcbbdb sshd\[29045\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.83.218
Oct 31 04:09:47 hcbbdb sshd\[29045\]: Failed password for invalid user just4now from 142.93.83.218 port 54340 ssh2
Oct 31 04:14:01 hcbbdb sshd\[29517\]: Invalid user Dubai@123 from 142.93.83.218
Oct 31 04:14:01 hcbbdb sshd\[29517\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.83.218
2019-10-31 12:35:38
79.107.150.130 attackspam
port scan and connect, tcp 23 (telnet)
2019-10-31 12:24:55
220.166.47.4 attackbotsspam
Unauthorised access (Oct 31) SRC=220.166.47.4 LEN=40 TOS=0x10 PREC=0x40 TTL=48 ID=58955 TCP DPT=8080 WINDOW=35265 SYN 
Unauthorised access (Oct 30) SRC=220.166.47.4 LEN=40 TOS=0x10 PREC=0x40 TTL=48 ID=41133 TCP DPT=8080 WINDOW=35265 SYN
2019-10-31 12:21:46
185.176.27.254 attackbotsspam
10/31/2019-00:24:38.924272 185.176.27.254 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-10-31 12:38:44
222.186.180.17 attack
Oct 31 09:45:10 areeb-Workstation sshd[18182]: Failed password for root from 222.186.180.17 port 50788 ssh2
Oct 31 09:45:29 areeb-Workstation sshd[18182]: error: maximum authentication attempts exceeded for root from 222.186.180.17 port 50788 ssh2 [preauth]
...
2019-10-31 12:31:47
107.180.108.7 attackspambots
WordPress login Brute force / Web App Attack on client site.
2019-10-31 12:36:38
212.237.50.34 attack
Oct 31 01:16:34 firewall sshd[3737]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.237.50.34  user=root
Oct 31 01:16:36 firewall sshd[3737]: Failed password for root from 212.237.50.34 port 46008 ssh2
Oct 31 01:20:06 firewall sshd[3792]: Invalid user legal3 from 212.237.50.34
...
2019-10-31 12:20:51
185.17.141.94 attack
Oct 31 01:15:57 dax sshd[21346]: Invalid user anuel from 185.17.141.94
Oct 31 01:15:57 dax sshd[21346]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.17.141.94 
Oct 31 01:15:59 dax sshd[21346]: Failed password for invalid user anuel from 185.17.141.94 port 43184 ssh2
Oct 31 01:16:00 dax sshd[21346]: Received disconnect from 185.17.141.94: 11: Bye Bye [preauth]
Oct 31 01:37:28 dax sshd[24263]: Invalid user oracle from 185.17.141.94
Oct 31 01:37:28 dax sshd[24263]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.17.141.94 
Oct 31 01:37:30 dax sshd[24263]: Failed password for invalid user oracle from 185.17.141.94 port 55294 ssh2
Oct 31 01:37:30 dax sshd[24263]: Received disconnect from 185.17.141.94: 11: Bye Bye [preauth]
Oct 31 01:41:27 dax sshd[24882]: Invalid user local from 185.17.141.94
Oct 31 01:41:27 dax sshd[24882]: pam_unix(sshd:auth): authentication failure; logname= uid=0 ........
-------------------------------
2019-10-31 12:48:53
190.136.122.8 attack
Telnet Server BruteForce Attack
2019-10-31 12:47:50
119.203.240.76 attack
Oct 31 05:50:28 server sshd\[3657\]: User root from 119.203.240.76 not allowed because listed in DenyUsers
Oct 31 05:50:28 server sshd\[3657\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.203.240.76  user=root
Oct 31 05:50:30 server sshd\[3657\]: Failed password for invalid user root from 119.203.240.76 port 12916 ssh2
Oct 31 05:56:05 server sshd\[28760\]: User root from 119.203.240.76 not allowed because listed in DenyUsers
Oct 31 05:56:05 server sshd\[28760\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.203.240.76  user=root
2019-10-31 12:58:11
77.247.108.162 attackspambots
SIPVicious Scanner Detection
2019-10-31 12:49:27

Recently Reported IPs

112.80.136.142 112.80.136.152 112.80.136.169 112.80.136.177
112.80.136.221 112.80.136.222 112.80.136.240 112.80.136.54
248.198.81.46 112.80.136.70 112.80.136.86 113.105.172.35
113.110.229.58 73.225.29.118 113.110.236.77 113.110.242.95
238.185.115.33 113.110.247.136 113.110.72.184 113.110.77.126