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

;; QUESTION SECTION:
;104.21.48.18.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 23:05:09 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 18.48.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 18.48.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
51.136.112.67 attack
" "
2020-05-16 13:22:01
104.168.28.214 attackbots
(sshd) Failed SSH login from 104.168.28.214 (US/United States/104-168-28-214-host.colocrossing.com): 12 in the last 3600 secs
2020-05-16 13:32:14
177.53.7.41 attack
email spam
2020-05-16 13:21:06
121.79.131.234 attackbots
May 16 04:56:08 nextcloud sshd\[19145\]: Invalid user safarrel from 121.79.131.234
May 16 04:56:08 nextcloud sshd\[19145\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.79.131.234
May 16 04:56:11 nextcloud sshd\[19145\]: Failed password for invalid user safarrel from 121.79.131.234 port 48372 ssh2
2020-05-16 13:31:19
138.68.50.18 attackbotsspam
Invalid user training from 138.68.50.18 port 44196
2020-05-16 13:18:10
186.193.2.22 attack
proto=tcp  .  spt=39231  .  dpt=25  .     Found on   Blocklist de       (160)
2020-05-16 13:25:32
49.232.16.47 attack
May 15 20:21:24 ws12vmsma01 sshd[33829]: Failed password for invalid user sammer from 49.232.16.47 port 47152 ssh2
May 15 20:26:53 ws12vmsma01 sshd[34680]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.16.47  user=root
May 15 20:26:55 ws12vmsma01 sshd[34680]: Failed password for root from 49.232.16.47 port 51350 ssh2
...
2020-05-16 13:50:44
107.173.40.211 attack
2020-05-16 05:32:58 dovecot_login authenticator failed for \(User\) \[107.173.40.211\]: 535 Incorrect authentication data \(set_id=computer@ift.org.ua\)2020-05-16 05:33:04 dovecot_login authenticator failed for \(User\) \[107.173.40.211\]: 535 Incorrect authentication data \(set_id=computer@ift.org.ua\)2020-05-16 05:33:15 dovecot_login authenticator failed for \(User\) \[107.173.40.211\]: 535 Incorrect authentication data \(set_id=computer@ift.org.ua\)
...
2020-05-16 13:24:39
91.134.248.211 attackbotsspam
LGS,WP GET /wp-login.php
2020-05-16 13:14:34
139.199.159.77 attackbots
2020-05-16T03:46:04.9469471240 sshd\[13431\]: Invalid user tracy from 139.199.159.77 port 54692
2020-05-16T03:46:04.9515621240 sshd\[13431\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.159.77
2020-05-16T03:46:06.5281211240 sshd\[13431\]: Failed password for invalid user tracy from 139.199.159.77 port 54692 ssh2
...
2020-05-16 13:24:25
139.59.66.101 attack
May 16 04:40:51 piServer sshd[29813]: Failed password for root from 139.59.66.101 port 38908 ssh2
May 16 04:44:54 piServer sshd[30206]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.66.101 
May 16 04:44:55 piServer sshd[30206]: Failed password for invalid user explorer from 139.59.66.101 port 42046 ssh2
...
2020-05-16 13:15:13
36.66.4.62 attack
[Fri May 15 21:25:02.997922 2020] [:error] [pid 160980] [client 36.66.4.62:40932] [client 36.66.4.62] ModSecurity: Access denied with code 403 (phase 2). Operator GE matched 5 at TX:anomaly_score. [file "/usr/share/modsecurity-crs/rules/REQUEST-949-BLOCKING-EVALUATION.conf"] [line "91"] [id "949110"] [msg "Inbound Anomaly Score Exceeded (Total Score: 8)"] [severity "CRITICAL"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-generic"] [hostname "200.132.59.214"] [uri "/user/soapCaller.bs"] [unique_id "Xr8y3mXaAQVjgJelI8TAEQAAAAI"]
...
2020-05-16 13:40:05
69.28.234.137 attackbotsspam
May 15 08:02:26 : SSH login attempts with invalid user
2020-05-16 13:37:24
122.168.190.130 attackspambots
firewall-block, port(s): 445/tcp
2020-05-16 13:16:35
91.106.193.72 attack
May 16 04:27:41 vps639187 sshd\[11836\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.106.193.72  user=root
May 16 04:27:43 vps639187 sshd\[11836\]: Failed password for root from 91.106.193.72 port 41858 ssh2
May 16 04:31:44 vps639187 sshd\[11895\]: Invalid user tbd from 91.106.193.72 port 51698
May 16 04:31:44 vps639187 sshd\[11895\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.106.193.72
...
2020-05-16 13:26:34

Recently Reported IPs

104.21.48.179 104.21.48.187 104.21.48.188 104.21.48.189
104.21.48.193 171.94.241.212 104.21.48.194 104.21.48.195
104.21.48.199 104.21.48.20 104.21.48.200 104.21.48.203
104.21.48.209 118.59.159.219 104.21.48.21 46.22.181.4
104.21.48.210 104.21.48.213 104.21.48.215 104.21.48.217