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

;; QUESTION SECTION:
;104.21.56.102.			IN	A

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

;; Query time: 57 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 02:37:35 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 102.56.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 102.56.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
222.127.30.130 attack
Jan 11 16:44:01 vpn01 sshd[25552]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.127.30.130
Jan 11 16:44:03 vpn01 sshd[25552]: Failed password for invalid user com from 222.127.30.130 port 3003 ssh2
...
2020-01-12 00:08:26
138.197.21.218 attackspam
Jan 11 15:29:27 mail sshd[30727]: Invalid user 23 from 138.197.21.218
...
2020-01-12 00:41:23
139.59.38.169 attack
$f2bV_matches
2020-01-12 00:00:20
178.128.246.123 attack
SSH Brute-Force reported by Fail2Ban
2020-01-12 00:18:05
139.59.41.154 attackbotsspam
$f2bV_matches
2020-01-11 23:58:29
49.88.112.67 attack
Jan 11 17:06:08 v22018053744266470 sshd[6021]: Failed password for root from 49.88.112.67 port 13685 ssh2
Jan 11 17:07:09 v22018053744266470 sshd[6085]: Failed password for root from 49.88.112.67 port 52192 ssh2
...
2020-01-12 00:19:19
138.68.106.62 attackspam
$f2bV_matches
2020-01-12 00:34:49
139.59.38.94 attack
Jan 11 16:16:29 vpn01 sshd[24864]: Failed password for root from 139.59.38.94 port 57042 ssh2
...
2020-01-12 00:00:51
151.80.41.64 attack
SSH Brute-Force attacks
2020-01-12 00:24:07
67.205.57.217 attackspambots
Automatic report - XMLRPC Attack
2020-01-12 00:07:54
151.80.144.39 attackspam
Jan 11 14:47:09 s1 sshd\[23939\]: User root from 151.80.144.39 not allowed because not listed in AllowUsers
Jan 11 14:47:09 s1 sshd\[23939\]: Failed password for invalid user root from 151.80.144.39 port 49474 ssh2
Jan 11 14:49:18 s1 sshd\[23983\]: User root from 151.80.144.39 not allowed because not listed in AllowUsers
Jan 11 14:49:18 s1 sshd\[23983\]: Failed password for invalid user root from 151.80.144.39 port 43042 ssh2
Jan 11 14:51:23 s1 sshd\[24968\]: Invalid user lzw from 151.80.144.39 port 36626
Jan 11 14:51:23 s1 sshd\[24968\]: Failed password for invalid user lzw from 151.80.144.39 port 36626 ssh2
...
2020-01-12 00:42:55
138.68.4.198 attack
$f2bV_matches
2020-01-12 00:31:17
139.199.106.127 attack
Unauthorized SSH login attempts
2020-01-12 00:22:02
138.68.82.220 attackbotsspam
Unauthorized connection attempt detected from IP address 138.68.82.220 to port 2220 [J]
2020-01-12 00:30:36
221.223.192.165 attackbotsspam
Fail2Ban - FTP Abuse Attempt
2020-01-12 00:26:00

Recently Reported IPs

104.21.56.109 104.21.56.138 104.21.56.141 104.21.56.128
104.21.56.127 104.21.56.135 104.21.56.118 104.21.56.142
104.21.56.147 104.21.56.15 104.21.7.46 104.21.56.149
104.21.56.150 104.21.56.151 104.21.56.154 104.21.56.156
104.21.56.158 104.21.56.152 104.21.56.157 104.21.56.17