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

;; QUESTION SECTION:
;104.164.122.66.			IN	A

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

;; Query time: 25 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri May 20 11:10:44 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 66.122.164.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.122.164.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
206.189.190.32 attackbotsspam
Jul 15 07:26:19 ip-172-31-1-72 sshd\[14769\]: Invalid user revista from 206.189.190.32
Jul 15 07:26:19 ip-172-31-1-72 sshd\[14769\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.190.32
Jul 15 07:26:21 ip-172-31-1-72 sshd\[14769\]: Failed password for invalid user revista from 206.189.190.32 port 50374 ssh2
Jul 15 07:30:46 ip-172-31-1-72 sshd\[14860\]: Invalid user jenkins from 206.189.190.32
Jul 15 07:30:46 ip-172-31-1-72 sshd\[14860\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.190.32
2019-07-15 18:19:45
121.14.59.252 attackspam
[SMB remote code execution attempt: port tcp/445]
*(RWIN=1024)(07151032)
2019-07-15 18:51:26
180.109.64.234 attackbots
Automatic report - Port Scan Attack
2019-07-15 18:40:14
212.88.123.198 attackbotsspam
Jul 15 16:03:47 vibhu-HP-Z238-Microtower-Workstation sshd\[11213\]: Invalid user jirka from 212.88.123.198
Jul 15 16:03:47 vibhu-HP-Z238-Microtower-Workstation sshd\[11213\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.88.123.198
Jul 15 16:03:49 vibhu-HP-Z238-Microtower-Workstation sshd\[11213\]: Failed password for invalid user jirka from 212.88.123.198 port 42400 ssh2
Jul 15 16:10:35 vibhu-HP-Z238-Microtower-Workstation sshd\[12788\]: Invalid user marvin from 212.88.123.198
Jul 15 16:10:35 vibhu-HP-Z238-Microtower-Workstation sshd\[12788\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.88.123.198
...
2019-07-15 18:48:55
150.95.110.27 attack
fail2ban honeypot
2019-07-15 18:43:46
124.243.198.190 attack
SSH Brute Force
2019-07-15 18:57:22
110.185.166.137 attack
Jul 15 06:23:50 ip-172-30-0-179 sshd\[22790\]: Invalid user carapp from 110.185.166.137\
Jul 15 06:23:53 ip-172-30-0-179 sshd\[22797\]: Invalid user carapp from 110.185.166.137\
Jul 15 06:23:57 ip-172-30-0-179 sshd\[22799\]: Invalid user carapp from 110.185.166.137\
Jul 15 06:24:00 ip-172-30-0-179 sshd\[22801\]: Invalid user hfsdk from 110.185.166.137\
Jul 15 06:24:06 ip-172-30-0-179 sshd\[22803\]: Invalid user hfsdk from 110.185.166.137\
Jul 15 06:24:08 ip-172-30-0-179 sshd\[22805\]: Invalid user recog from 110.185.166.137\
2019-07-15 18:37:25
103.80.117.214 attackspam
Automatic report - Banned IP Access
2019-07-15 18:52:16
103.254.120.222 attackbotsspam
Jul 15 10:13:40 vps647732 sshd[11572]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.254.120.222
Jul 15 10:13:42 vps647732 sshd[11572]: Failed password for invalid user debian from 103.254.120.222 port 60112 ssh2
...
2019-07-15 18:56:53
165.22.177.186 attack
timhelmke.de 165.22.177.186 \[15/Jul/2019:08:24:21 +0200\] "POST /wp-login.php HTTP/1.1" 200 5593 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
timhelmke.de 165.22.177.186 \[15/Jul/2019:08:24:24 +0200\] "POST /wp-login.php HTTP/1.1" 200 5582 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-07-15 18:27:22
178.46.214.227 attack
" "
2019-07-15 18:24:38
152.136.36.250 attackbots
Jun 30 20:56:46 [snip] sshd[5473]: Invalid user nathalie from 152.136.36.250 port 40712
Jun 30 20:56:46 [snip] sshd[5473]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.136.36.250
Jun 30 20:56:48 [snip] sshd[5473]: Failed password for invalid user nathalie from 152.136.36.250 port 40712 ssh2[...]
2019-07-15 18:47:49
79.137.35.70 attack
Jul 15 09:28:42 h2177944 sshd\[16641\]: Invalid user nginx from 79.137.35.70 port 45910
Jul 15 09:28:42 h2177944 sshd\[16641\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.137.35.70
Jul 15 09:28:44 h2177944 sshd\[16641\]: Failed password for invalid user nginx from 79.137.35.70 port 45910 ssh2
Jul 15 09:33:29 h2177944 sshd\[16964\]: Invalid user mqm from 79.137.35.70 port 44308
...
2019-07-15 18:31:05
89.175.152.22 attackspam
Jul 15 09:09:50 ns3042688 courier-imapd: LOGIN FAILED, method=PLAIN, ip=\[::ffff:89.175.152.22\]
...
2019-07-15 18:58:39
45.6.27.171 attack
Jul 15 08:19:09 rigel postfix/smtpd[32407]: connect from unknown[45.6.27.171]
Jul 15 08:19:14 rigel postfix/smtpd[32407]: warning: unknown[45.6.27.171]: SASL CRAM-MD5 authentication failed: authentication failure
Jul 15 08:19:14 rigel postfix/smtpd[32407]: warning: unknown[45.6.27.171]: SASL PLAIN authentication failed: authentication failure
Jul 15 08:19:16 rigel postfix/smtpd[32407]: warning: unknown[45.6.27.171]: SASL LOGIN authentication failed: authentication failure


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=45.6.27.171
2019-07-15 18:39:11

Recently Reported IPs

222.1.4.246 104.164.122.67 104.164.122.68 104.164.122.69
104.164.122.70 104.164.122.71 104.164.122.72 104.164.122.73
104.164.122.74 104.164.122.75 104.164.122.76 104.164.122.78
104.164.122.79 104.164.122.81 104.164.122.82 104.164.122.83
104.164.122.84 104.164.122.85 104.164.122.86 104.164.122.87