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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.168.66.172
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 13796
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.168.66.172.			IN	A

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

;; Query time: 63 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 25 19:39:44 CST 2022
;; MSG SIZE  rcvd: 107
Host info
172.66.168.104.in-addr.arpa domain name pointer 104-168-66-172-host.colocrossing.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
172.66.168.104.in-addr.arpa	name = 104-168-66-172-host.colocrossing.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
84.242.124.74 attack
Feb 22 18:13:48 mail sshd[23610]: Invalid user server from 84.242.124.74
Feb 22 18:13:48 mail sshd[23610]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.242.124.74
Feb 22 18:13:48 mail sshd[23610]: Invalid user server from 84.242.124.74
Feb 22 18:13:50 mail sshd[23610]: Failed password for invalid user server from 84.242.124.74 port 40940 ssh2
...
2020-02-23 07:45:43
182.50.130.51 attackspambots
Automatic report - XMLRPC Attack
2020-02-23 07:47:21
221.120.44.149 attackbots
$f2bV_matches
2020-02-23 08:00:48
112.26.7.149 attack
$f2bV_matches
2020-02-23 07:56:35
47.50.246.114 attackspam
Invalid user shoping from 47.50.246.114 port 42716
2020-02-23 07:43:40
91.123.24.196 attack
frenzy
2020-02-23 07:49:08
111.229.36.119 attackspam
Invalid user discover from 111.229.36.119 port 33090
2020-02-23 07:39:07
104.236.63.99 attackspambots
Feb 23 02:42:09 server sshd\[11811\]: Invalid user developer from 104.236.63.99
Feb 23 02:42:09 server sshd\[11811\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.236.63.99 
Feb 23 02:42:12 server sshd\[11811\]: Failed password for invalid user developer from 104.236.63.99 port 47210 ssh2
Feb 23 02:46:16 server sshd\[13065\]: Invalid user user0 from 104.236.63.99
Feb 23 02:46:16 server sshd\[13065\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.236.63.99 
...
2020-02-23 07:48:54
49.88.112.75 attackspam
Feb 22 20:53:07 ip-172-30-0-108 sshd[26187]: refused connect from 49.88.112.75 (49.88.112.75)
Feb 22 20:54:11 ip-172-30-0-108 sshd[26199]: refused connect from 49.88.112.75 (49.88.112.75)
Feb 22 20:55:15 ip-172-30-0-108 sshd[26273]: refused connect from 49.88.112.75 (49.88.112.75)
...
2020-02-23 07:57:50
113.88.14.165 attackbots
2020-02-21 17:13:08 server sshd[20692]: Failed password for invalid user ovhuser from 113.88.14.165 port 34444 ssh2
2020-02-23 07:35:39
82.127.66.48 attackbots
Invalid user demo from 82.127.66.48 port 59776
2020-02-23 07:34:02
190.181.60.2 attackspam
Invalid user guest from 190.181.60.2 port 35678
2020-02-23 07:32:48
211.159.189.104 attackbotsspam
2020-02-21 17:30:02 server sshd[21225]: Failed password for invalid user root from 211.159.189.104 port 48416 ssh2
2020-02-23 07:35:04
103.125.190.121 attackbotsspam
Honeypot hit.
2020-02-23 07:49:54
122.51.229.98 attackbotsspam
Invalid user guest from 122.51.229.98 port 50906
2020-02-23 07:38:54

Recently Reported IPs

104.168.66.18 104.168.66.168 104.168.66.180 101.109.192.166
177.252.187.153 104.168.66.192 104.168.66.199 104.168.66.194
104.168.66.196 104.168.66.202 104.168.66.208 104.168.66.190
104.168.66.182 104.168.66.186 104.168.66.206 104.168.66.2
101.109.192.182 101.109.192.196 101.109.192.204 104.168.90.240