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

;; QUESTION SECTION:
;104.21.39.213.			IN	A

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

;; Query time: 55 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 21:39:55 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 213.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 213.39.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
217.61.5.122 attackspambots
Unauthorized connection attempt detected from IP address 217.61.5.122 to port 2220 [J]
2020-01-30 20:18:19
178.63.193.201 attackspam
30.01.2020 10:49:49 - Wordpress fail 
Detected by ELinOX-ALM
2020-01-30 20:31:08
49.88.112.68 attack
SSH Brute Force
2020-01-30 20:23:45
43.248.125.101 attack
Unauthorized connection attempt detected from IP address 43.248.125.101 to port 2220 [J]
2020-01-30 20:28:50
124.106.41.140 attackbots
Automatic report - Port Scan Attack
2020-01-30 20:19:34
187.74.66.86 attackbots
firewall-block, port(s): 23/tcp
2020-01-30 20:16:01
106.12.10.119 attack
Unauthorized connection attempt detected from IP address 106.12.10.119 to port 2220 [J]
2020-01-30 20:11:42
157.245.198.83 attackspam
Jan 30 12:57:00 debian-2gb-nbg1-2 kernel: \[2644682.448912\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=157.245.198.83 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x40 TTL=242 ID=57948 PROTO=TCP SPT=32767 DPT=8545 WINDOW=1024 RES=0x00 SYN URGP=0
2020-01-30 20:11:09
89.42.252.124 attackspambots
Unauthorized connection attempt detected from IP address 89.42.252.124 to port 2220 [J]
2020-01-30 20:37:37
132.232.21.26 attackbotsspam
132.232.21.26 - - \[30/Jan/2020:06:57:37 +0100\] "POST /xmlrpc.php HTTP/1.0" 200 738 "-" "Apache-HttpClient/4.5.2 \(Java/1.8.0_151\)"
132.232.21.26 - - \[30/Jan/2020:06:57:38 +0100\] "POST /xmlrpc.php HTTP/1.0" 200 738 "-" "Apache-HttpClient/4.5.2 \(Java/1.8.0_151\)"
132.232.21.26 - - \[30/Jan/2020:06:57:38 +0100\] "POST /xmlrpc.php HTTP/1.0" 200 738 "-" "Apache-HttpClient/4.5.2 \(Java/1.8.0_151\)"
2020-01-30 20:08:20
101.36.150.59 attackbots
$f2bV_matches
2020-01-30 19:57:20
119.28.29.169 attack
2020-01-30T06:56:08.428310vostok sshd\[31526\]: Invalid user himagouri from 119.28.29.169 port 48066 | Triggered by Fail2Ban at Vostok web server
2020-01-30 20:14:23
89.25.222.22 attackbots
Jan 30 12:10:42 MK-Soft-Root2 sshd[15533]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.25.222.22 
Jan 30 12:10:45 MK-Soft-Root2 sshd[15533]: Failed password for invalid user japendra from 89.25.222.22 port 6202 ssh2
...
2020-01-30 20:09:47
51.158.186.14 attack
Jan 30 14:21:11 hosting sshd[9638]: Invalid user jalambika from 51.158.186.14 port 50578
...
2020-01-30 20:00:42
167.71.217.175 attackspam
Unauthorized connection attempt detected from IP address 167.71.217.175 to port 2220 [J]
2020-01-30 20:07:22

Recently Reported IPs

104.21.39.208 16.7.232.88 104.21.39.214 104.21.39.216
104.21.39.218 104.21.39.223 104.21.39.224 104.21.39.228
104.21.39.23 104.21.39.230 104.21.39.232 104.21.39.235
104.21.39.238 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