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

;; QUESTION SECTION:
;112.80.136.229.			IN	A

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

;; Query time: 65 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 13:33:11 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 229.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 229.136.80.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
54.69.16.110 attackbotsspam
Sending out Netflix spam from IP 54.240.14.174 
(amazon.com / amazonaws.com) 

I have NEVER been a Netflix customer and
never asked for this junk. 

The website spammed out is 

https://www.netflix.com/signup/creditoption?nftoken=BQAbAAEBEA77T6CHfer3tv8qolkSAduAkLFC%2FFYUyiUS4Sdi62TDOAptLP7WiMxUQK74rIuN%2BRXrWDnwU8vxCNSC2khWG0ZmflN2tsqMsqNHMDWRdKmlf6XFVqwlgd%2BFLY2Nz88IH4y3pcuOeFYD5X9L4G9ZZfbRHvrmZF%2FjsAyUI1f5mpTFg3eEFWfNQayYDiVrbb%2FU65EF%2B0XXrVI0T4jKa2zmCB8w5g%3D%3D&lnktrk=EMP&g=AEF2F71097E503EBEB44921E2720235C64526E40&lkid=URL_SIGNUP_CREDIT
IPs: 54.69.16.110, 54.70.73.70, 54.149.101.155,
54.201.91.38, 54.213.182.74, 52.37.77.112,
52.41.20.47, 52.41.193.16
(amazon.com / amazonaws.com) 

amazon are pure scumbags who allow their 
customers to send out spam and do nothing 
about it! 
Report via email and website at 
https://support.aws.amazon.com/#/contacts/report-abuse
2019-09-26 19:35:20
108.162.245.188 attackbotsspam
108.162.245.188 - - [26/Sep/2019:10:41:26 +0700] "GET /favicon.ico HTTP/1.1" 404 2828 "-" "Googlebot-Image/1.0"
2019-09-26 19:13:40
80.82.77.240 attackspambots
09/26/2019-06:31:45.846988 80.82.77.240 Protocol: 6 ET CINS Active Threat Intelligence Poor Reputation IP group 82
2019-09-26 19:14:52
221.0.189.38 attackbots
firewall-block, port(s): 23/tcp
2019-09-26 19:36:12
45.82.153.35 attackspambots
09/26/2019-12:35:25.723410 45.82.153.35 Protocol: 6 ET CINS Active Threat Intelligence Poor Reputation IP group 42
2019-09-26 19:05:46
118.25.98.75 attack
Sep 25 17:38:14 php1 sshd\[31306\]: Invalid user guest5 from 118.25.98.75
Sep 25 17:38:14 php1 sshd\[31306\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.25.98.75
Sep 25 17:38:16 php1 sshd\[31306\]: Failed password for invalid user guest5 from 118.25.98.75 port 53738 ssh2
Sep 25 17:41:46 php1 sshd\[31699\]: Invalid user deb from 118.25.98.75
Sep 25 17:41:46 php1 sshd\[31699\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.25.98.75
2019-09-26 19:08:08
195.154.27.239 attack
Invalid user lulu from 195.154.27.239 port 36869
2019-09-26 18:56:46
94.177.240.20 attack
SIPVicious Scanner Detection, PTR: host20-240-177-94.static.arubacloud.fr.
2019-09-26 19:25:27
94.191.59.106 attackbots
Sep 25 19:26:13 eddieflores sshd\[10289\]: Invalid user server from 94.191.59.106
Sep 25 19:26:13 eddieflores sshd\[10289\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.191.59.106
Sep 25 19:26:15 eddieflores sshd\[10289\]: Failed password for invalid user server from 94.191.59.106 port 45940 ssh2
Sep 25 19:32:36 eddieflores sshd\[10745\]: Invalid user dbps from 94.191.59.106
Sep 25 19:32:36 eddieflores sshd\[10745\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.191.59.106
2019-09-26 19:27:40
139.199.48.217 attackspam
Apr 20 18:04:35 vtv3 sshd\[32458\]: Invalid user vm from 139.199.48.217 port 57820
Apr 20 18:04:35 vtv3 sshd\[32458\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.48.217
Apr 20 18:04:37 vtv3 sshd\[32458\]: Failed password for invalid user vm from 139.199.48.217 port 57820 ssh2
Apr 20 18:08:02 vtv3 sshd\[1805\]: Invalid user cmd from 139.199.48.217 port 54190
Apr 20 18:08:02 vtv3 sshd\[1805\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.48.217
Sep 26 06:57:20 vtv3 sshd\[14100\]: Invalid user kevin from 139.199.48.217 port 44798
Sep 26 06:57:20 vtv3 sshd\[14100\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.48.217
Sep 26 06:57:23 vtv3 sshd\[14100\]: Failed password for invalid user kevin from 139.199.48.217 port 44798 ssh2
Sep 26 07:02:06 vtv3 sshd\[16437\]: Invalid user alx from 139.199.48.217 port 57966
Sep 26 07:02:06 vtv3 sshd\[16437\]: pam_unix
2019-09-26 19:09:04
218.94.136.90 attack
SSH Brute Force, server-1 sshd[12124]: Failed password for invalid user csl from 218.94.136.90 port 12210 ssh2
2019-09-26 19:32:18
162.158.106.93 attack
162.158.106.93 - - [26/Sep/2019:10:41:16 +0700] "GET /js/service-worker/fetch.js HTTP/1.1" 200 6027 "https://web.floware.ml/" "Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.96 Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"
2019-09-26 19:23:33
79.211.72.217 attack
20 attempts against mh-misbehave-ban on pluto.magehost.pro
2019-09-26 19:31:08
77.247.181.165 attackbotsspam
Sep 26 10:57:17 thevastnessof sshd[3840]: Failed password for root from 77.247.181.165 port 30330 ssh2
...
2019-09-26 19:13:52
47.188.154.94 attack
Sep 26 00:53:05 sachi sshd\[26672\]: Invalid user zy from 47.188.154.94
Sep 26 00:53:05 sachi sshd\[26672\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=47.188.154.94
Sep 26 00:53:08 sachi sshd\[26672\]: Failed password for invalid user zy from 47.188.154.94 port 47490 ssh2
Sep 26 00:57:52 sachi sshd\[27077\]: Invalid user katya from 47.188.154.94
Sep 26 00:57:52 sachi sshd\[27077\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=47.188.154.94
2019-09-26 19:05:12

Recently Reported IPs

112.80.136.213 112.80.136.45 112.80.136.236 112.80.136.243
112.80.136.79 112.80.136.81 112.80.136.83 112.80.137.103
112.80.136.242 112.80.136.95 112.80.136.76 112.80.137.125
112.80.137.126 112.80.136.75 112.80.137.162 112.80.137.107
112.80.137.0 112.80.137.192 112.80.137.179 112.80.137.209