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

;; QUESTION SECTION:
;104.21.40.193.			IN	A

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

;; Query time: 54 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 23 03:59:04 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 193.40.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 193.40.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
222.186.175.220 attack
WordPress hacking :: 2019-10-21 14:00:44,588 fail2ban.actions        [889]: NOTICE  [sshd] Ban 222.186.175.220
2019-10-21 14:20:52,853 fail2ban.actions        [889]: NOTICE  [sshd] Ban 222.186.175.220
2019-10-21 15:11:18,096 fail2ban.actions        [889]: NOTICE  [sshd] Ban 222.186.175.220
2019-10-21 16:51:30,859 fail2ban.actions        [889]: NOTICE  [sshd] Ban 222.186.175.220
2019-10-21 23:11:55,197 fail2ban.actions        [889]: NOTICE  [sshd] Ban 222.186.175.220
2019-10-27 20:24:11
45.132.170.82 attackspam
[portscan] Port scan
2019-10-27 20:30:43
93.185.75.61 attack
" "
2019-10-27 20:16:21
87.197.166.67 attack
Oct 27 13:09:35 MK-Soft-VM6 sshd[25322]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=87.197.166.67 
Oct 27 13:09:36 MK-Soft-VM6 sshd[25322]: Failed password for invalid user thomas from 87.197.166.67 port 38565 ssh2
...
2019-10-27 20:15:42
178.33.130.196 attackspam
Oct 27 13:09:36 vmanager6029 sshd\[28591\]: Invalid user pc01 from 178.33.130.196 port 55656
Oct 27 13:09:36 vmanager6029 sshd\[28591\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.33.130.196
Oct 27 13:09:38 vmanager6029 sshd\[28591\]: Failed password for invalid user pc01 from 178.33.130.196 port 55656 ssh2
2019-10-27 20:12:23
46.61.235.111 attackbotsspam
2019-10-27T05:53:19.499763abusebot-5.cloudsearch.cf sshd\[28934\]: Invalid user cn from 46.61.235.111 port 34706
2019-10-27 19:57:16
177.85.116.242 attackbots
2019-10-27T12:09:16.560324abusebot-7.cloudsearch.cf sshd\[29565\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.85.116.242  user=root
2019-10-27 20:27:59
198.57.203.54 attackbotsspam
Automatic report - Banned IP Access
2019-10-27 20:13:24
96.251.179.98 attack
SSH Bruteforce attack
2019-10-27 20:02:06
54.37.139.235 attack
Oct 27 13:47:31 server sshd\[15310\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=235.ip-54-37-139.eu  user=root
Oct 27 13:47:33 server sshd\[15310\]: Failed password for root from 54.37.139.235 port 56732 ssh2
Oct 27 14:07:02 server sshd\[20091\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=235.ip-54-37-139.eu  user=root
Oct 27 14:07:04 server sshd\[20091\]: Failed password for root from 54.37.139.235 port 36482 ssh2
Oct 27 14:10:38 server sshd\[21024\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=235.ip-54-37-139.eu  user=root
...
2019-10-27 20:07:28
222.169.36.14 attack
Honeypot attack, port: 5555, PTR: PTR record not found
2019-10-27 20:35:39
49.232.171.28 attackspambots
Oct 26 13:48:09 uapps sshd[26975]: User r.r from 49.232.171.28 not allowed because not listed in AllowUsers
Oct 26 13:48:09 uapps sshd[26975]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.171.28  user=r.r
Oct 26 13:48:11 uapps sshd[26975]: Failed password for invalid user r.r from 49.232.171.28 port 48278 ssh2
Oct 26 13:48:11 uapps sshd[26975]: Received disconnect from 49.232.171.28: 11: Bye Bye [preauth]
Oct 26 14:11:15 uapps sshd[27226]: User r.r from 49.232.171.28 not allowed because not listed in AllowUsers
Oct 26 14:11:15 uapps sshd[27226]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.171.28  user=r.r
Oct 26 14:11:17 uapps sshd[27226]: Failed password for invalid user r.r from 49.232.171.28 port 48124 ssh2
Oct 26 14:11:17 uapps sshd[27226]: Received disconnect from 49.232.171.28: 11: Bye Bye [preauth]
Oct 26 14:26:43 uapps sshd[27324]: Failed password for invalid use........
-------------------------------
2019-10-27 20:21:56
217.182.220.124 attackspambots
Oct 27 07:16:27 ws19vmsma01 sshd[99239]: Failed password for root from 217.182.220.124 port 58772 ssh2
...
2019-10-27 20:09:24
185.176.27.166 attackspambots
TCP Port Scanning
2019-10-27 20:36:32
61.183.178.194 attack
Oct 27 06:00:29 www sshd\[185572\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.183.178.194  user=root
Oct 27 06:00:31 www sshd\[185572\]: Failed password for root from 61.183.178.194 port 3923 ssh2
Oct 27 06:06:05 www sshd\[185663\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.183.178.194  user=root
...
2019-10-27 19:59:24

Recently Reported IPs

104.21.40.145 104.21.40.230 104.21.40.40 104.21.40.9
104.21.41.103 95.124.162.43 104.21.41.223 255.199.22.4
104.21.41.95 104.21.42.119 104.21.42.184 104.21.42.193
104.21.42.249 104.21.42.49 104.21.42.83 104.21.43.135
104.21.43.29 104.21.43.6 104.21.45.17 104.21.45.173