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

;; QUESTION SECTION:
;104.22.64.66.			IN	A

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

;; Query time: 21 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 03:42:16 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 66.64.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 66.64.22.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
27.216.51.101 attackspambots
Unauthorised access (Oct 17) SRC=27.216.51.101 LEN=40 TTL=49 ID=8953 TCP DPT=8080 WINDOW=49768 SYN 
Unauthorised access (Oct 16) SRC=27.216.51.101 LEN=40 TTL=49 ID=35628 TCP DPT=8080 WINDOW=49768 SYN 
Unauthorised access (Oct 16) SRC=27.216.51.101 LEN=40 TTL=49 ID=37919 TCP DPT=8080 WINDOW=30144 SYN 
Unauthorised access (Oct 15) SRC=27.216.51.101 LEN=40 TTL=49 ID=10306 TCP DPT=8080 WINDOW=18416 SYN 
Unauthorised access (Oct 14) SRC=27.216.51.101 LEN=40 TTL=49 ID=37297 TCP DPT=8080 WINDOW=18416 SYN 
Unauthorised access (Oct 14) SRC=27.216.51.101 LEN=40 TTL=49 ID=60508 TCP DPT=8080 WINDOW=59200 SYN
2019-10-18 05:00:30
103.39.135.154 attack
Oct 17 11:10:36 fv15 sshd[2778]: reveeclipse mapping checking getaddrinfo for m154.amazezone.us [103.39.135.154] failed - POSSIBLE BREAK-IN ATTEMPT!
Oct 17 11:10:36 fv15 sshd[2778]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.39.135.154  user=r.r
Oct 17 11:10:37 fv15 sshd[2778]: Failed password for r.r from 103.39.135.154 port 57602 ssh2
Oct 17 11:10:38 fv15 sshd[2778]: Received disconnect from 103.39.135.154: 11: Bye Bye [preauth]
Oct 17 11:22:15 fv15 sshd[9334]: reveeclipse mapping checking getaddrinfo for m154.amazezone.us [103.39.135.154] failed - POSSIBLE BREAK-IN ATTEMPT!
Oct 17 11:22:18 fv15 sshd[9334]: Failed password for invalid user nj2sc from 103.39.135.154 port 38394 ssh2
Oct 17 11:22:18 fv15 sshd[9334]: Received disconnect from 103.39.135.154: 11: Bye Bye [preauth]
Oct 17 11:26:36 fv15 sshd[13540]: reveeclipse mapping checking getaddrinfo for m154.amazezone.us [103.39.135.154] failed - POSSIBLE BREAK-IN ATTEMP........
-------------------------------
2019-10-18 05:14:48
84.170.213.179 attackspambots
IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/84.170.213.179/ 
 DE - 1H : (76)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : DE 
 NAME ASN : ASN3320 
 
 IP : 84.170.213.179 
 
 CIDR : 84.128.0.0/10 
 
 PREFIX COUNT : 481 
 
 UNIQUE IP COUNT : 29022208 
 
 
 WYKRYTE ATAKI Z ASN3320 :  
  1H - 1 
  3H - 3 
  6H - 6 
 12H - 10 
 24H - 20 
 
 DateTime : 2019-10-17 21:52:30 
 
 INFO : Port SSH 22 Scan Detected and Blocked by ADMIN  - data recovery
2019-10-18 05:09:18
36.110.50.217 attackspambots
2019-10-17T20:23:22.678770abusebot-5.cloudsearch.cf sshd\[9274\]: Invalid user pn from 36.110.50.217 port 53474
2019-10-18 04:46:21
105.96.44.37 attackbots
Web Probe / Attack
2019-10-18 05:15:47
191.252.184.219 attackbotsspam
Oct 18 00:15:31 www5 sshd\[7845\]: Invalid user kelvin from 191.252.184.219
Oct 18 00:15:31 www5 sshd\[7845\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=191.252.184.219
Oct 18 00:15:33 www5 sshd\[7845\]: Failed password for invalid user kelvin from 191.252.184.219 port 47948 ssh2
...
2019-10-18 05:16:03
187.44.106.11 attack
Oct 17 10:45:05 tdfoods sshd\[3955\]: Invalid user shsf123 from 187.44.106.11
Oct 17 10:45:05 tdfoods sshd\[3955\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.44.106.11
Oct 17 10:45:07 tdfoods sshd\[3955\]: Failed password for invalid user shsf123 from 187.44.106.11 port 55997 ssh2
Oct 17 10:54:46 tdfoods sshd\[4821\]: Invalid user qwerty-123456 from 187.44.106.11
Oct 17 10:54:46 tdfoods sshd\[4821\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.44.106.11
2019-10-18 05:03:38
14.190.13.195 attack
Oct 17 21:44:32 server378 sshd[31472]: Address 14.190.13.195 maps to static.vnpt.vn, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Oct 17 21:44:32 server378 sshd[31472]: Invalid user admin from 14.190.13.195
Oct 17 21:44:32 server378 sshd[31472]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.190.13.195
Oct 17 21:44:34 server378 sshd[31472]: Failed password for invalid user admin from 14.190.13.195 port 59373 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=14.190.13.195
2019-10-18 04:44:31
181.48.116.50 attackbots
Oct 17 10:36:36 hanapaa sshd\[28899\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.48.116.50  user=root
Oct 17 10:36:38 hanapaa sshd\[28899\]: Failed password for root from 181.48.116.50 port 32964 ssh2
Oct 17 10:39:58 hanapaa sshd\[29329\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.48.116.50  user=root
Oct 17 10:40:00 hanapaa sshd\[29329\]: Failed password for root from 181.48.116.50 port 40534 ssh2
Oct 17 10:43:28 hanapaa sshd\[29575\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.48.116.50  user=root
2019-10-18 05:06:13
201.39.233.40 attack
2019-10-17T20:37:42.760337abusebot-4.cloudsearch.cf sshd\[7007\]: Invalid user qaz\#EDC5tgb from 201.39.233.40 port 60176
2019-10-18 04:43:33
201.251.10.200 attackbots
Feb 27 03:58:17 odroid64 sshd\[12642\]: Invalid user mu from 201.251.10.200
Feb 27 03:58:17 odroid64 sshd\[12642\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.251.10.200
Feb 27 03:58:19 odroid64 sshd\[12642\]: Failed password for invalid user mu from 201.251.10.200 port 57954 ssh2
Mar 15 08:28:01 odroid64 sshd\[20365\]: Invalid user nas from 201.251.10.200
Mar 15 08:28:01 odroid64 sshd\[20365\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.251.10.200
Mar 15 08:28:04 odroid64 sshd\[20365\]: Failed password for invalid user nas from 201.251.10.200 port 42863 ssh2
...
2019-10-18 04:58:18
101.255.52.171 attackbotsspam
Feb 16 18:49:06 microserver sshd[48318]: Invalid user oracle from 101.255.52.171 port 33322
Feb 16 18:49:06 microserver sshd[48318]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.255.52.171
Feb 16 18:49:07 microserver sshd[48318]: Failed password for invalid user oracle from 101.255.52.171 port 33322 ssh2
Feb 16 18:55:30 microserver sshd[49282]: Invalid user team from 101.255.52.171 port 54296
Feb 16 18:55:30 microserver sshd[49282]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.255.52.171
Oct 17 23:30:11 microserver sshd[8960]: Invalid user xiao from 101.255.52.171 port 57662
Oct 17 23:30:11 microserver sshd[8960]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.255.52.171
Oct 17 23:30:13 microserver sshd[8960]: Failed password for invalid user xiao from 101.255.52.171 port 57662 ssh2
Oct 17 23:34:39 microserver sshd[9393]: Invalid user git from 101.255.52.171 port 40772
Oct
2019-10-18 05:17:19
194.182.86.126 attackspambots
Oct 18 02:45:37 lcl-usvr-02 sshd[18199]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=194.182.86.126  user=root
Oct 18 02:45:40 lcl-usvr-02 sshd[18199]: Failed password for root from 194.182.86.126 port 51642 ssh2
Oct 18 02:49:14 lcl-usvr-02 sshd[19030]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=194.182.86.126  user=root
Oct 18 02:49:16 lcl-usvr-02 sshd[19030]: Failed password for root from 194.182.86.126 port 34842 ssh2
Oct 18 02:52:55 lcl-usvr-02 sshd[19881]: Invalid user git from 194.182.86.126 port 46272
...
2019-10-18 04:48:36
95.167.39.12 attack
Oct 17 21:48:58 MK-Soft-Root2 sshd[31339]: Failed password for root from 95.167.39.12 port 53278 ssh2
...
2019-10-18 04:51:17
103.83.105.243 attackspambots
Unauthorised access (Oct 17) SRC=103.83.105.243 LEN=40 PREC=0x20 TTL=237 ID=41154 TCP DPT=139 WINDOW=1024 SYN
2019-10-18 04:51:00

Recently Reported IPs

104.22.64.248 104.22.64.239 104.22.64.254 104.22.64.235
104.22.64.71 104.22.64.72 104.22.64.82 104.22.64.85
104.22.64.81 104.22.64.91 104.22.64.92 104.22.64.96
104.22.64.98 104.22.64.90 104.22.64.95 104.22.65.111
104.22.65.113 104.22.65.124 104.22.65.120 104.22.65.105