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

;; QUESTION SECTION:
;104.21.16.79.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 18:16:21 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 79.16.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 79.16.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
205.185.116.157 attackbots
Scanning
2020-05-01 17:43:07
167.172.36.232 attack
DATE:2020-05-01 09:57:14, IP:167.172.36.232, PORT:ssh SSH brute force auth (docker-dc)
2020-05-01 17:53:32
203.192.204.168 attackbots
Invalid user help from 203.192.204.168 port 60354
2020-05-01 17:43:23
161.117.48.120 attackspam
Invalid user ruzicka from 161.117.48.120 port 49754
2020-05-01 17:56:16
142.93.162.84 attackbotsspam
$f2bV_matches
2020-05-01 18:01:48
205.185.117.22 attackbots
Unauthorized connection attempt detected from IP address 205.185.117.22 to port 22
2020-05-01 17:42:42
134.175.87.31 attack
May  1 08:56:42 localhost sshd[75549]: Invalid user liza from 134.175.87.31 port 40374
May  1 08:56:42 localhost sshd[75549]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.87.31
May  1 08:56:42 localhost sshd[75549]: Invalid user liza from 134.175.87.31 port 40374
May  1 08:56:44 localhost sshd[75549]: Failed password for invalid user liza from 134.175.87.31 port 40374 ssh2
May  1 09:05:04 localhost sshd[76486]: Invalid user test3 from 134.175.87.31 port 49316
...
2020-05-01 18:04:47
108.12.130.32 attackbots
hit -> srv3:22
2020-05-01 18:16:15
222.112.178.113 attack
Invalid user zx from 222.112.178.113 port 52214
2020-05-01 17:38:39
188.166.16.118 attack
Invalid user sinusbot from 188.166.16.118 port 48830
2020-05-01 17:47:11
121.229.54.116 attack
Invalid user sony from 121.229.54.116 port 50790
2020-05-01 18:09:09
111.93.200.50 attack
2020-05-01T06:36:53.898050shield sshd\[25733\]: Invalid user casino from 111.93.200.50 port 35605
2020-05-01T06:36:53.903243shield sshd\[25733\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.93.200.50
2020-05-01T06:36:56.363275shield sshd\[25733\]: Failed password for invalid user casino from 111.93.200.50 port 35605 ssh2
2020-05-01T06:41:32.186114shield sshd\[26308\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.93.200.50  user=root
2020-05-01T06:41:33.612642shield sshd\[26308\]: Failed password for root from 111.93.200.50 port 41377 ssh2
2020-05-01 18:14:21
165.227.203.162 attack
$f2bV_matches
2020-05-01 17:55:15
137.117.80.185 attackspambots
Invalid user jetty from 137.117.80.185 port 42476
2020-05-01 18:04:17
188.131.248.228 attackbotsspam
Invalid user itu from 188.131.248.228 port 56358
2020-05-01 17:47:35

Recently Reported IPs

104.21.16.72 104.21.16.83 104.21.16.84 104.21.16.87
245.187.217.66 104.21.16.89 104.21.16.91 104.21.16.92
104.21.16.93 104.21.16.95 104.21.16.96 104.21.17.10
104.21.17.100 104.21.17.101 104.21.17.103 104.21.17.108
104.21.17.11 104.21.17.111 104.21.17.113 104.21.17.115