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

;; QUESTION SECTION:
;104.21.39.238.			IN	A

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

;; Query time: 24 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 21:40:53 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 238.39.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 238.39.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
14.102.17.34 attack
Jan 14 04:07:24 ny01 sshd[25675]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.102.17.34
Jan 14 04:07:26 ny01 sshd[25675]: Failed password for invalid user jim from 14.102.17.34 port 45308 ssh2
Jan 14 04:08:44 ny01 sshd[25817]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.102.17.34
2020-01-14 17:47:27
177.194.230.199 attackspam
Unauthorized connection attempt detected from IP address 177.194.230.199 to port 83 [J]
2020-01-14 17:55:25
124.156.50.129 attack
Unauthorized connection attempt detected from IP address 124.156.50.129 to port 81 [J]
2020-01-14 17:58:49
113.173.110.24 attack
Unauthorized connection attempt detected from IP address 113.173.110.24 to port 83 [J]
2020-01-14 17:33:57
185.217.68.102 attack
Unauthorized connection attempt detected from IP address 185.217.68.102 to port 2220 [J]
2020-01-14 17:53:41
170.106.36.200 attack
Unauthorized connection attempt detected from IP address 170.106.36.200 to port 8000 [J]
2020-01-14 17:27:59
222.184.101.98 attackbotsspam
Unauthorized connection attempt detected from IP address 222.184.101.98 to port 2220 [J]
2020-01-14 17:48:24
103.61.101.51 attackbots
Unauthorized connection attempt detected from IP address 103.61.101.51 to port 80 [J]
2020-01-14 18:05:48
114.38.177.26 attackspam
Unauthorized connection attempt detected from IP address 114.38.177.26 to port 23 [J]
2020-01-14 18:01:24
168.228.115.250 attack
Unauthorized connection attempt detected from IP address 168.228.115.250 to port 23 [J]
2020-01-14 17:28:32
190.29.16.177 attackspambots
Unauthorized connection attempt detected from IP address 190.29.16.177 to port 23 [J]
2020-01-14 17:52:32
119.237.13.66 attackbotsspam
Unauthorized connection attempt detected from IP address 119.237.13.66 to port 5555 [J]
2020-01-14 17:32:11
124.156.240.138 attackbotsspam
Unauthorized connection attempt detected from IP address 124.156.240.138 to port 2376 [J]
2020-01-14 17:57:33
131.255.168.168 attackbotsspam
Unauthorized connection attempt detected from IP address 131.255.168.168 to port 88 [J]
2020-01-14 17:30:32
124.156.245.157 attackbotsspam
Unauthorized connection attempt detected from IP address 124.156.245.157 to port 8887 [J]
2020-01-14 17:31:15

Recently Reported IPs

104.21.39.235 104.21.39.239 104.21.39.242 104.21.39.243
104.21.39.248 104.21.39.29 104.21.39.31 104.21.39.34
104.21.39.36 104.21.39.42 147.43.159.69 104.21.39.5
104.21.39.53 104.21.39.64 104.21.39.67 104.21.39.7
104.21.39.70 104.21.39.74 75.85.165.146 104.21.39.75