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

;; QUESTION SECTION:
;104.21.54.185.			IN	A

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

;; Query time: 66 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 20 19:34:45 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 185.54.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 185.54.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
181.164.107.226 attackbotsspam
Jul 31 07:00:01 vibhu-HP-Z238-Microtower-Workstation sshd\[21759\]: Invalid user alex from 181.164.107.226
Jul 31 07:00:01 vibhu-HP-Z238-Microtower-Workstation sshd\[21759\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.164.107.226
Jul 31 07:00:03 vibhu-HP-Z238-Microtower-Workstation sshd\[21759\]: Failed password for invalid user alex from 181.164.107.226 port 50418 ssh2
Jul 31 07:05:37 vibhu-HP-Z238-Microtower-Workstation sshd\[21905\]: Invalid user usbmuxd from 181.164.107.226
Jul 31 07:05:37 vibhu-HP-Z238-Microtower-Workstation sshd\[21905\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.164.107.226
...
2019-07-31 09:38:15
67.205.138.125 attackbotsspam
[Aegis] @ 2019-07-31 00:31:47  0100 -> Attempted Administrator Privilege Gain: ET SCAN LibSSH Based Frequent SSH Connections Likely BruteForce Attack
2019-07-31 09:53:56
103.17.53.148 attack
Jul 31 03:25:28 h2177944 sshd\[8567\]: Invalid user howard from 103.17.53.148 port 36316
Jul 31 03:25:28 h2177944 sshd\[8567\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.17.53.148
Jul 31 03:25:30 h2177944 sshd\[8567\]: Failed password for invalid user howard from 103.17.53.148 port 36316 ssh2
Jul 31 03:30:23 h2177944 sshd\[8854\]: Invalid user frappe from 103.17.53.148 port 60682
...
2019-07-31 09:57:45
136.144.169.229 attackspam
Jul 31 00:37:20 jupiter sshd\[4041\]: Invalid user penrod from 136.144.169.229
Jul 31 00:37:20 jupiter sshd\[4041\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=136.144.169.229
Jul 31 00:37:22 jupiter sshd\[4041\]: Failed password for invalid user penrod from 136.144.169.229 port 35267 ssh2
...
2019-07-31 10:11:01
81.149.211.134 attackbotsspam
2019-07-31T02:01:38.333351abusebot-6.cloudsearch.cf sshd\[15346\]: Invalid user teamcity from 81.149.211.134 port 60469
2019-07-31 10:04:44
142.54.101.146 attack
Jul 31 01:59:08 localhost sshd\[99871\]: Invalid user zimbra from 142.54.101.146 port 29751
Jul 31 01:59:08 localhost sshd\[99871\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.54.101.146
Jul 31 01:59:10 localhost sshd\[99871\]: Failed password for invalid user zimbra from 142.54.101.146 port 29751 ssh2
Jul 31 02:03:41 localhost sshd\[100056\]: Invalid user muhahaha from 142.54.101.146 port 42394
Jul 31 02:03:41 localhost sshd\[100056\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.54.101.146
...
2019-07-31 10:06:06
128.201.8.10 attack
Brute force SMTP login attempts.
2019-07-31 09:51:56
196.216.228.102 attack
Automatic report - SSH Brute-Force Attack
2019-07-31 10:27:20
175.212.62.83 attackspambots
DATE:2019-07-31 04:02:53, IP:175.212.62.83, PORT:ssh SSH brute force auth (ermes)
2019-07-31 10:22:19
54.36.148.30 attackspam
Automatic report - Banned IP Access
2019-07-31 10:25:05
124.156.164.41 attackbotsspam
Jul 31 04:05:23 dedicated sshd[23455]: Invalid user master from 124.156.164.41 port 38680
2019-07-31 10:13:17
91.134.141.89 attackbots
Jul 31 04:58:54 docs sshd\[8373\]: Invalid user regina from 91.134.141.89Jul 31 04:58:56 docs sshd\[8373\]: Failed password for invalid user regina from 91.134.141.89 port 44632 ssh2Jul 31 05:02:51 docs sshd\[8450\]: Invalid user campus from 91.134.141.89Jul 31 05:02:54 docs sshd\[8450\]: Failed password for invalid user campus from 91.134.141.89 port 38946 ssh2Jul 31 05:06:53 docs sshd\[8527\]: Invalid user usuario1 from 91.134.141.89Jul 31 05:06:55 docs sshd\[8527\]: Failed password for invalid user usuario1 from 91.134.141.89 port 33224 ssh2
...
2019-07-31 10:18:35
116.228.166.194 attackspam
port scan/probe/communication attempt
2019-07-31 10:16:13
80.85.86.175 attackbots
port scan/probe/communication attempt
2019-07-31 10:26:49
109.116.196.174 attackbotsspam
Jul 30 19:32:19 TORMINT sshd\[17745\]: Invalid user db2admin from 109.116.196.174
Jul 30 19:32:19 TORMINT sshd\[17745\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.116.196.174
Jul 30 19:32:21 TORMINT sshd\[17745\]: Failed password for invalid user db2admin from 109.116.196.174 port 38850 ssh2
...
2019-07-31 10:23:55

Recently Reported IPs

104.21.54.170 104.21.54.164 104.21.54.194 104.21.54.175
104.21.54.165 104.21.54.150 104.18.31.119 104.21.54.39
104.21.54.42 104.21.54.214 104.21.54.172 104.21.54.24
104.21.54.192 104.21.54.36 104.18.31.130 104.18.31.133
104.21.57.250 104.21.57.222 104.21.57.82 104.21.57.66