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

;; QUESTION SECTION:
;112.80.136.109.			IN	A

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

;; Query time: 46 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 03:10:23 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 109.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 109.136.80.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
113.160.244.98 attack
445/tcp 445/tcp 445/tcp...
[2019-05-24/07-02]7pkt,1pt.(tcp)
2019-07-02 15:02:18
201.90.19.116 attackspam
@LucianNitescu Personal Honeypot Network <<<>>> Donate at paypal.me/LNitescu <<<>>> 2019-07-02 00:07:23,589 INFO [shellcode_manager] (201.90.19.116) no match, writing hexdump (cab454e8119eb82b5076736c946b54c1 :2060529) - MS17010 (EternalBlue)
2019-07-02 14:18:50
86.89.82.173 attack
Automatic report - SSH Brute-Force Attack
2019-07-02 14:35:00
165.22.101.1 attackspam
Jul  2 06:36:50 localhost sshd\[20599\]: Invalid user oracle from 165.22.101.1 port 51722
Jul  2 06:36:50 localhost sshd\[20599\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.101.1
Jul  2 06:36:52 localhost sshd\[20599\]: Failed password for invalid user oracle from 165.22.101.1 port 51722 ssh2
2019-07-02 14:16:33
75.119.196.29 attack
:: port:21 (ftp) 
:: port:80 (http) 
:: port:443 (https) 
Drop:75.119.196.29 
GET: /old/wp-admin/
2019-07-02 14:52:15
189.206.135.106 attackbotsspam
@LucianNitescu Personal Honeypot Network <<<>>> Donate at paypal.me/LNitescu <<<>>> 2019-07-02 02:30:48,814 INFO [amun_request_handler] PortScan Detected on Port: 445 (189.206.135.106)
2019-07-02 15:02:48
118.25.135.84 attackbotsspam
Feb 13 04:09:10 motanud sshd\[32186\]: Invalid user suporte from 118.25.135.84 port 49468
Feb 13 04:09:10 motanud sshd\[32186\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.25.135.84
Feb 13 04:09:12 motanud sshd\[32186\]: Failed password for invalid user suporte from 118.25.135.84 port 49468 ssh2
2019-07-02 14:23:01
93.157.87.134 attackbots
5555/tcp 5555/tcp 5555/tcp
[2019-05-14/07-02]3pkt
2019-07-02 15:06:42
41.72.105.171 attack
Jul  2 05:17:32 animalibera sshd[28764]: Invalid user scan from 41.72.105.171 port 61369
...
2019-07-02 14:53:48
122.225.80.218 attackspam
@LucianNitescu Personal Honeypot Network <<<>>> Donate at paypal.me/LNitescu <<<>>> 2019-07-02 06:01:59,562 INFO [amun_request_handler] PortScan Detected on Port: 445 (122.225.80.218)
2019-07-02 15:06:13
41.44.245.167 attack
@LucianNitescu Personal Honeypot Network <<<>>> Donate at paypal.me/LNitescu <<<>>> 2019-07-02 02:32:17,277 INFO [amun_request_handler] PortScan Detected on Port: 445 (41.44.245.167)
2019-07-02 14:36:25
89.201.5.167 attackspam
Jul  2 03:52:05 localhost sshd\[8323\]: Invalid user guillaume from 89.201.5.167 port 36046
Jul  2 03:52:05 localhost sshd\[8323\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.201.5.167
Jul  2 03:52:06 localhost sshd\[8323\]: Failed password for invalid user guillaume from 89.201.5.167 port 36046 ssh2
...
2019-07-02 14:26:02
118.163.180.57 attack
445/tcp 445/tcp 445/tcp...
[2019-05-02/07-02]12pkt,1pt.(tcp)
2019-07-02 14:30:07
31.31.199.53 attackspam
1562039516 - 07/02/2019 05:51:56 Host: 31.31.199.53/31.31.199.53 Port: 2000 TCP Blocked
2019-07-02 14:31:55
201.87.233.89 attackspam
445/tcp 445/tcp 445/tcp...
[2019-05-05/07-02]5pkt,1pt.(tcp)
2019-07-02 14:24:12

Recently Reported IPs

112.78.4.212 112.80.136.127 112.80.136.136 112.78.4.203
112.80.136.151 112.8.115.14 112.80.136.158 112.8.223.42
112.78.4.18 112.80.136.172 112.80.136.154 112.80.139.160
112.80.139.163 112.80.139.181 112.80.139.178 112.80.139.19
112.80.139.197 112.80.139.201 112.80.139.190 112.80.139.195