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

;; QUESTION SECTION:
;104.21.59.194.			IN	A

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

;; Query time: 24 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 19 03:30:34 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 194.59.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 194.59.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
174.138.44.201 attackbotsspam
WordPress login Brute force / Web App Attack on client site.
2020-05-31 06:30:50
197.234.193.46 attackbots
727. On May 30 2020 experienced a Brute Force SSH login attempt -> 3 unique times by 197.234.193.46.
2020-05-31 06:25:57
123.206.36.174 attackbots
Invalid user exile from 123.206.36.174 port 48774
2020-05-31 06:26:13
180.76.162.19 attack
2020-05-30T20:42:33.026333shield sshd\[3033\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.162.19  user=root
2020-05-30T20:42:35.444153shield sshd\[3033\]: Failed password for root from 180.76.162.19 port 45162 ssh2
2020-05-30T20:45:42.953984shield sshd\[3540\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.162.19  user=root
2020-05-30T20:45:44.318053shield sshd\[3540\]: Failed password for root from 180.76.162.19 port 38414 ssh2
2020-05-30T20:48:49.671758shield sshd\[3952\]: Invalid user crystal from 180.76.162.19 port 59920
2020-05-31 06:18:13
2a01:4f8:191:8463::2 attackspam
20 attempts against mh-misbehave-ban on plane
2020-05-31 06:30:06
196.4.80.2 attack
Unauthorized connection attempt from IP address 196.4.80.2 on Port 445(SMB)
2020-05-31 06:21:09
190.151.105.182 attack
Invalid user tplink from 190.151.105.182 port 46312
2020-05-31 06:34:23
70.37.75.157 attack
1215. On May 30 2020 experienced a Brute Force SSH login attempt -> 1 unique times by 70.37.75.157.
2020-05-31 06:37:07
218.56.11.236 attackspam
SSH Invalid Login
2020-05-31 06:45:20
92.46.93.153 attackbotsspam
Port probing on unauthorized port 5900
2020-05-31 06:24:22
59.56.236.76 attack
Spammer_1
2020-05-31 06:37:30
104.248.61.192 attack
Invalid user test from 104.248.61.192 port 60848
2020-05-31 06:32:35
106.52.17.214 attackspambots
100. On May 30 2020 experienced a Brute Force SSH login attempt -> 1 unique times by 106.52.17.214.
2020-05-31 06:15:24
198.206.243.23 attack
Invalid user biuro from 198.206.243.23 port 45474
2020-05-31 06:49:40
14.29.160.194 attackspam
SSH Invalid Login
2020-05-31 06:42:21

Recently Reported IPs

104.21.59.247 104.21.6.145 104.21.60.157 104.21.6.105
104.21.6.62 104.21.60.124 104.21.60.171 104.21.60.222
104.21.60.165 104.21.60.128 104.21.59.74 104.21.60.58
104.21.61.133 104.21.61.172 104.21.62.165 104.21.62.215
104.21.62.129 104.21.62.132 104.21.61.213 104.21.62.177