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

;; QUESTION SECTION:
;104.21.53.85.			IN	A

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

;; Query time: 54 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 00:02:37 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 85.53.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 85.53.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
109.130.144.166 attack
Jun 29 23:08:51 minden010 sshd[21536]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.130.144.166
Jun 29 23:08:53 minden010 sshd[21536]: Failed password for invalid user semenov from 109.130.144.166 port 33816 ssh2
Jun 29 23:08:59 minden010 sshd[21580]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.130.144.166
...
2019-06-30 07:42:38
92.119.160.150 attack
firewall-block, port(s): 1111/tcp
2019-06-30 07:15:10
89.248.168.3 attackbotsspam
firewall-block, port(s): 1052/tcp, 1053/tcp
2019-06-30 07:18:28
59.124.222.3 attackspambots
Trying to (more than 3 packets) bruteforce (not open) Samba/Microsoft-DS port 445
2019-06-30 07:40:22
168.228.148.167 attackbots
SASL PLAIN auth failed: ruser=...
2019-06-30 07:43:13
80.82.78.104 attackbots
firewall-block, port(s): 3399/tcp
2019-06-30 07:21:33
187.109.59.1 attackbotsspam
SMTP-sasl brute force
...
2019-06-30 07:48:28
92.50.248.124 attackbots
Scanning (more than 2 packets) random ports - tries to find possible vulnerable services
2019-06-30 07:17:54
209.141.62.45 attackspam
Jun 29 23:29:28 vmi181237 sshd\[30565\]: refused connect from 209.141.62.45 \(209.141.62.45\)
Jun 29 23:29:33 vmi181237 sshd\[30572\]: refused connect from 209.141.62.45 \(209.141.62.45\)
Jun 29 23:29:39 vmi181237 sshd\[30580\]: refused connect from 209.141.62.45 \(209.141.62.45\)
Jun 29 23:29:44 vmi181237 sshd\[30587\]: refused connect from 209.141.62.45 \(209.141.62.45\)
Jun 29 23:29:50 vmi181237 sshd\[30595\]: refused connect from 209.141.62.45 \(209.141.62.45\)
2019-06-30 07:28:21
92.118.160.17 attackspam
Scanning (more than 2 packets) random ports - tries to find possible vulnerable services
2019-06-30 07:16:56
191.53.118.144 attack
$f2bV_matches
2019-06-30 07:54:51
83.97.20.36 attack
29.06.2019 23:19:34 Connection to port 47094 blocked by firewall
2019-06-30 07:20:41
106.2.124.185 attackbotsspam
port scan and connect, tcp 8080 (http-proxy)
2019-06-30 07:54:25
82.102.173.84 attackspam
29.06.2019 23:07:59 Connection to port 3010 blocked by firewall
2019-06-30 07:21:15
116.110.33.12 attack
Trying to (more than 3 packets) bruteforce (not open) Samba/Microsoft-DS port 445
2019-06-30 07:35:48

Recently Reported IPs

104.21.53.83 104.21.53.88 104.21.53.89 104.21.53.9
104.21.53.91 104.21.53.92 104.21.53.94 104.21.53.96
104.21.53.97 104.21.53.99 236.143.178.73 104.21.54.10
104.21.54.104 104.21.54.106 104.21.54.11 104.21.54.111
104.21.54.117 171.38.2.199 104.21.54.119 104.21.54.122