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: United States

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

;; QUESTION SECTION:
;104.21.94.172.			IN	A

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

;; Query time: 66 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 03:18:24 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 172.94.21.104.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 172.94.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
216.172.183.202 attack
Dictionary attack on login resource.
2019-06-23 13:38:30
114.27.174.101 attackspam
37215/tcp
[2019-06-22]1pkt
2019-06-23 13:26:15
111.249.33.252 attackbots
37215/tcp
[2019-06-22]1pkt
2019-06-23 13:57:44
190.12.178.212 attackbotsspam
Invalid user qo from 190.12.178.212 port 59988
2019-06-23 13:38:01
174.126.222.32 attackbotsspam
port scan and connect, tcp 8080 (http-proxy)
2019-06-23 13:44:46
119.115.93.121 attack
5500/tcp
[2019-06-22]1pkt
2019-06-23 13:36:41
27.78.213.21 attack
445/tcp
[2019-06-22]1pkt
2019-06-23 14:19:16
185.15.37.86 attackspam
[portscan] Port scan
2019-06-23 13:24:41
111.93.180.182 attack
ports scanning
2019-06-23 14:08:32
114.7.112.106 attackspambots
20 attempts against mh-ssh on beach.magehost.pro
2019-06-23 13:25:33
156.206.136.168 attackspam
23/tcp
[2019-06-22]1pkt
2019-06-23 13:56:16
205.209.174.222 attackspambots
slow and persistent scanner
2019-06-23 14:22:00
62.254.112.121 attackspam
Jun 23 02:11:51 localhost sshd\[2430\]: Invalid user admin from 62.254.112.121 port 6225
Jun 23 02:11:51 localhost sshd\[2430\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.254.112.121
Jun 23 02:11:53 localhost sshd\[2430\]: Failed password for invalid user admin from 62.254.112.121 port 6225 ssh2
2019-06-23 14:13:01
220.76.205.178 attack
Jun 23 02:08:10 mail1 sshd\[21852\]: Invalid user istclass from 220.76.205.178 port 52277
Jun 23 02:08:10 mail1 sshd\[21852\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.76.205.178
Jun 23 02:08:12 mail1 sshd\[21852\]: Failed password for invalid user istclass from 220.76.205.178 port 52277 ssh2
Jun 23 02:12:06 mail1 sshd\[23652\]: Invalid user fabio from 220.76.205.178 port 43741
Jun 23 02:12:06 mail1 sshd\[23652\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.76.205.178
...
2019-06-23 13:59:41
14.228.227.16 attackbots
445/tcp
[2019-06-22]1pkt
2019-06-23 14:24:18

Recently Reported IPs

104.21.94.171 104.21.94.166 104.21.94.170 104.21.94.167
104.21.94.176 104.21.94.173 104.21.94.178 104.21.94.179
104.21.94.180 104.21.94.18 104.21.94.187 104.21.94.182
104.21.94.184 104.21.94.185 104.21.94.188 104.21.94.192
104.21.94.19 104.21.94.190 104.21.94.191 104.21.94.193