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

;; QUESTION SECTION:
;104.21.21.57.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 18:57:41 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 57.21.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 57.21.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
173.44.222.230 attackspambots
(From eric@talkwithwebvisitor.com) Cool website!

My name’s Eric, and I just found your site - drbrianferris.info - while surfing the net. You showed up at the top of the search results, so I checked you out. Looks like what you’re doing is pretty cool.
 
But if you don’t mind me asking – after someone like me stumbles across drbrianferris.info, what usually happens?

Is your site generating leads for your business? 
 
I’m guessing some, but I also bet you’d like more… studies show that 7 out 10 who land on a site wind up leaving without a trace.

Not good.

Here’s a thought – what if there was an easy way for every visitor to “raise their hand” to get a phone call from you INSTANTLY… the second they hit your site and said, “call me now.”

You can –
  
Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number.  It lets you know IMMEDIATELY – so that you can talk to that lead while they’re literally looking over you
2020-02-26 23:43:04
79.114.192.235 attack
Port 8080 (HTTP proxy) access denied
2020-02-27 00:19:45
212.64.29.78 attackspam
$f2bV_matches
2020-02-26 23:37:44
142.93.212.85 attack
RDP Brute-Force (honeypot 9)
2020-02-27 00:20:31
45.237.140.120 attack
Feb 26 19:10:52 gw1 sshd[25566]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.237.140.120
Feb 26 19:10:54 gw1 sshd[25566]: Failed password for invalid user jocelyn from 45.237.140.120 port 59424 ssh2
...
2020-02-26 23:53:32
180.253.62.48 attack
1582724233 - 02/26/2020 14:37:13 Host: 180.253.62.48/180.253.62.48 Port: 445 TCP Blocked
2020-02-26 23:40:31
23.225.151.187 attackbotsspam
Feb 26 05:29:25 hanapaa sshd\[28468\]: Invalid user chenyang from 23.225.151.187
Feb 26 05:29:25 hanapaa sshd\[28468\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.225.151.187
Feb 26 05:29:27 hanapaa sshd\[28468\]: Failed password for invalid user chenyang from 23.225.151.187 port 48092 ssh2
Feb 26 05:35:14 hanapaa sshd\[28942\]: Invalid user xor from 23.225.151.187
Feb 26 05:35:14 hanapaa sshd\[28942\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.225.151.187
2020-02-26 23:47:37
212.144.102.107 attackbots
$f2bV_matches
2020-02-27 00:07:12
201.16.246.71 attackspam
Feb 26 10:46:48 plusreed sshd[10273]: Invalid user mella from 201.16.246.71
...
2020-02-26 23:58:36
124.195.173.123 attack
suspicious action Wed, 26 Feb 2020 10:37:04 -0300
2020-02-26 23:54:19
13.69.246.137 attackspambots
Password spraying
2020-02-27 00:14:53
167.114.251.164 attackspambots
2020-02-26T16:12:39.935833  sshd[320]: Invalid user sys from 167.114.251.164 port 40437
2020-02-26T16:12:39.949066  sshd[320]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.114.251.164
2020-02-26T16:12:39.935833  sshd[320]: Invalid user sys from 167.114.251.164 port 40437
2020-02-26T16:12:41.432298  sshd[320]: Failed password for invalid user sys from 167.114.251.164 port 40437 ssh2
...
2020-02-26 23:41:36
45.235.86.21 attackbots
Feb 26 15:45:50 sso sshd[28379]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.235.86.21
Feb 26 15:45:52 sso sshd[28379]: Failed password for invalid user userftp from 45.235.86.21 port 42200 ssh2
...
2020-02-26 23:43:53
212.169.239.61 attackbots
$f2bV_matches
2020-02-26 23:57:51
212.251.232.194 attackbotsspam
$f2bV_matches
2020-02-26 23:44:42

Recently Reported IPs

104.21.21.55 104.21.21.59 104.21.21.60 104.21.21.61
104.21.21.62 104.21.21.66 104.21.21.78 104.21.21.81
104.21.21.84 104.21.21.85 104.21.21.9 104.21.21.90
104.21.21.91 104.21.21.92 104.21.21.93 104.21.21.98
104.21.22.100 104.21.22.104 104.21.22.105 34.95.238.210