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

;; QUESTION SECTION:
;104.22.66.239.			IN	A

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

;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 21 05:27:21 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 239.66.22.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 239.66.22.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
35.199.74.148 attack
SSH Brute Force, server-1 sshd[19819]: Failed password for invalid user dev from 35.199.74.148 port 39026 ssh2
2019-08-01 02:05:46
213.32.69.98 attackbots
2019-07-31T12:56:43.053052abusebot-6.cloudsearch.cf sshd\[18050\]: Invalid user apache2 from 213.32.69.98 port 39530
2019-08-01 02:08:19
82.64.25.207 attack
Invalid user pi from 82.64.25.207 port 37780
2019-08-01 01:15:48
104.131.224.81 attack
2019-07-31T16:50:57.046849abusebot-5.cloudsearch.cf sshd\[9748\]: Invalid user date from 104.131.224.81 port 34401
2019-08-01 01:43:55
69.180.36.173 attackbotsspam
Jul 31 16:11:03 localhost sshd\[16288\]: Invalid user guest from 69.180.36.173 port 55426
Jul 31 16:11:03 localhost sshd\[16288\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.180.36.173
Jul 31 16:11:04 localhost sshd\[16288\]: Failed password for invalid user guest from 69.180.36.173 port 55426 ssh2
2019-08-01 01:17:19
218.62.122.35 attackbotsspam
Jul 31 18:52:58 debian sshd\[23054\]: Invalid user b from 218.62.122.35 port 46442
Jul 31 18:52:58 debian sshd\[23054\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.62.122.35
...
2019-08-01 02:07:16
195.154.169.244 attackbotsspam
SSH bruteforce (Triggered fail2ban)
2019-08-01 01:53:14
36.73.240.18 attackbotsspam
Unauthorized connection attempt from IP address 36.73.240.18 on Port 445(SMB)
2019-08-01 01:48:50
96.88.93.30 attackspambots
Jul 31 19:50:51 [munged] sshd[4696]: Invalid user sparc from 96.88.93.30 port 59448
Jul 31 19:50:51 [munged] sshd[4696]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=96.88.93.30
2019-08-01 02:16:37
123.16.53.239 attackspambots
Unauthorised access (Jul 31) SRC=123.16.53.239 LEN=52 TTL=115 ID=25083 DF TCP DPT=445 WINDOW=8192 SYN
2019-08-01 01:42:52
79.249.249.128 attackbotsspam
SSH Bruteforce Attack
2019-08-01 01:16:35
196.45.48.59 attackbotsspam
Invalid user sybase from 196.45.48.59 port 39968
2019-08-01 01:52:55
189.89.157.206 attackspambots
Automatic report - Banned IP Access
2019-08-01 01:53:41
187.189.20.149 attackspam
Jul 31 12:15:33 MK-Soft-VM4 sshd\[28535\]: Invalid user mysql from 187.189.20.149 port 17186
Jul 31 12:15:33 MK-Soft-VM4 sshd\[28535\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.189.20.149
Jul 31 12:15:35 MK-Soft-VM4 sshd\[28535\]: Failed password for invalid user mysql from 187.189.20.149 port 17186 ssh2
...
2019-08-01 01:54:12
40.114.73.9 attackspam
SSH authentication failure x 6 reported by Fail2Ban
...
2019-08-01 01:35:47

Recently Reported IPs

104.22.66.218 104.22.66.99 104.22.66.251 104.22.67.126
104.22.66.71 104.22.67.123 104.22.67.128 104.22.67.133
104.22.67.120 104.22.67.136 104.22.67.140 104.22.67.160
104.22.67.174 104.22.67.161 104.22.68.253 104.22.69.133
104.22.68.161 104.22.68.133 104.22.69.161 104.22.69.253