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.66.104.41 attack
The IP has triggered Cloudflare WAF. CF-Ray: 5410875db8eeeb29 | WAF_Rule_ID: 53b8357af6d244d3a132bcf913c3a388 | WAF_Kind: firewall | CF_Action: drop | Country: CN | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: GET | Host: img.skk.moe | User-Agent: Mozilla/4.054101423 Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1) | CF_DC: LAX. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2019-12-08 03:36:01
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 112.66.104.180
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12237
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;112.66.104.180.			IN	A

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

;; Query time: 54 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 13:32:05 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 180.104.66.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 180.104.66.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
167.71.201.123 attack
Jul 29 06:55:54 tux-35-217 sshd\[23133\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.201.123  user=root
Jul 29 06:55:56 tux-35-217 sshd\[23133\]: Failed password for root from 167.71.201.123 port 35762 ssh2
Jul 29 07:02:55 tux-35-217 sshd\[23137\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.201.123  user=root
Jul 29 07:02:56 tux-35-217 sshd\[23137\]: Failed password for root from 167.71.201.123 port 48824 ssh2
...
2019-07-29 13:11:57
168.205.108.59 attack
Brute force attempt
2019-07-29 13:27:38
177.220.172.145 attackspambots
Jul 29 05:34:04 lnxded63 sshd[32666]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.220.172.145
2019-07-29 13:44:22
123.206.178.65 attackbotsspam
2019-07-29T04:19:17.191511abusebot-7.cloudsearch.cf sshd\[19290\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.206.178.65  user=root
2019-07-29 13:20:23
192.210.152.159 attackbotsspam
Invalid user COMIDC from 192.210.152.159 port 48098
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.210.152.159
Failed password for invalid user COMIDC from 192.210.152.159 port 48098 ssh2
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.210.152.159  user=root
Failed password for root from 192.210.152.159 port 44760 ssh2
2019-07-29 13:48:03
62.210.127.244 attackbots
Jul 29 00:33:28 lnxmail61 postfix/smtpd[2993]: warning: [munged]:[62.210.127.244]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul 29 00:33:28 lnxmail61 postfix/smtpd[2993]: lost connection after AUTH from [munged]:[62.210.127.244]
Jul 29 00:33:34 lnxmail61 postfix/smtpd[2993]: warning: [munged]:[62.210.127.244]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul 29 00:33:34 lnxmail61 postfix/smtpd[2993]: lost connection after AUTH from [munged]:[62.210.127.244]
Jul 29 00:33:45 lnxmail61 postfix/smtpd[11794]: warning: [munged]:[62.210.127.244]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul 29 00:33:45 lnxmail61 postfix/smtpd[11794]: lost connection after AUTH from [munged]:[62.210.127.244]
2019-07-29 13:12:52
188.187.189.206 attackbotsspam
k+ssh-bruteforce
2019-07-29 13:42:31
18.191.169.73 attack
2019-07-29T02:09:19.589611abusebot-6.cloudsearch.cf sshd\[5131\]: Invalid user cn from 18.191.169.73 port 42978
2019-07-29 12:54:15
121.201.38.177 attack
Too many connections or unauthorized access detected from Oscar banned ip
2019-07-29 13:53:01
108.36.94.38 attack
Jul 29 04:37:45 srv-4 sshd\[13262\]: Invalid user server\^2012 from 108.36.94.38
Jul 29 04:37:45 srv-4 sshd\[13262\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=108.36.94.38
Jul 29 04:37:46 srv-4 sshd\[13262\]: Failed password for invalid user server\^2012 from 108.36.94.38 port 50311 ssh2
...
2019-07-29 13:44:57
198.27.67.17 attack
Automatic report - Banned IP Access
2019-07-29 12:59:43
175.124.43.123 attackspam
Jul 29 01:24:31 minden010 sshd[9309]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.124.43.123
Jul 29 01:24:33 minden010 sshd[9309]: Failed password for invalid user king111!!! from 175.124.43.123 port 40616 ssh2
Jul 29 01:29:45 minden010 sshd[11066]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.124.43.123
...
2019-07-29 13:19:19
206.189.134.83 attackbots
Triggered by Fail2Ban
2019-07-29 13:05:39
112.85.42.227 attackbotsspam
Jul 28 23:41:28 aat-srv002 sshd[29947]: Failed password for root from 112.85.42.227 port 39642 ssh2
Jul 28 23:42:12 aat-srv002 sshd[29975]: Failed password for root from 112.85.42.227 port 37863 ssh2
Jul 28 23:44:27 aat-srv002 sshd[30012]: Failed password for root from 112.85.42.227 port 11897 ssh2
...
2019-07-29 12:52:35
23.129.64.200 attackspambots
SSH invalid-user multiple login try
2019-07-29 13:06:40

Recently Reported IPs

112.66.104.166 112.66.104.182 112.66.104.187 112.66.104.249
112.66.104.202 112.66.104.193 112.66.104.86 112.66.105.105
112.66.104.73 112.66.105.139 112.66.104.82 112.66.105.160
112.66.105.154 112.66.105.164 112.66.104.22 112.66.105.193
112.66.105.227 112.66.105.218 112.66.105.176 112.66.105.239