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 of America (the)

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

;; QUESTION SECTION:
;66.16.164.10.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 06:35:56 CST 2025
;; MSG SIZE  rcvd: 105
Host info
10.164.16.66.in-addr.arpa domain name pointer static-66-16-164-10.dsl.cavtel.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
10.164.16.66.in-addr.arpa	name = static-66-16-164-10.dsl.cavtel.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
220.85.104.202 attack
Dec 23 05:45:15 wbs sshd\[445\]: Invalid user mfs from 220.85.104.202
Dec 23 05:45:15 wbs sshd\[445\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.85.104.202
Dec 23 05:45:17 wbs sshd\[445\]: Failed password for invalid user mfs from 220.85.104.202 port 22995 ssh2
Dec 23 05:51:35 wbs sshd\[1104\]: Invalid user server from 220.85.104.202
Dec 23 05:51:35 wbs sshd\[1104\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.85.104.202
2019-12-24 04:04:36
106.12.78.199 attackbotsspam
Dec 23 16:58:03 nextcloud sshd\[15395\]: Invalid user jasper from 106.12.78.199
Dec 23 16:58:03 nextcloud sshd\[15395\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.78.199
Dec 23 16:58:05 nextcloud sshd\[15395\]: Failed password for invalid user jasper from 106.12.78.199 port 44178 ssh2
...
2019-12-24 03:46:40
51.159.35.94 attack
Dec 23 22:29:10 webhost01 sshd[9075]: Failed password for root from 51.159.35.94 port 48170 ssh2
Dec 23 22:34:41 webhost01 sshd[9156]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.159.35.94
...
2019-12-24 04:02:03
41.139.230.99 attackbotsspam
Dec 23 14:55:48 flomail dovecot: imap-login: Disconnected (auth failed, 1 attempts in 12 secs): user=, method=PLAIN, rip=41.139.230.99, lip=10.140.194.78, TLS: Disconnected, session=
2019-12-24 03:40:00
129.204.45.214 attackbotsspam
Apr 16 17:46:12 yesfletchmain sshd\[16521\]: Invalid user weblogic from 129.204.45.214 port 55994
Apr 16 17:46:12 yesfletchmain sshd\[16521\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.45.214
Apr 16 17:46:14 yesfletchmain sshd\[16521\]: Failed password for invalid user weblogic from 129.204.45.214 port 55994 ssh2
Apr 16 17:49:35 yesfletchmain sshd\[16796\]: Invalid user aguie from 129.204.45.214 port 54908
Apr 16 17:49:35 yesfletchmain sshd\[16796\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.45.214
...
2019-12-24 03:33:18
167.250.15.7 attackspambots
port scan and connect, tcp 23 (telnet)
2019-12-24 03:55:06
124.105.25.33 attackspambots
Fail2Ban Ban Triggered
2019-12-24 04:05:48
167.99.65.138 attackspam
Dec 23 17:01:30 icinga sshd[11615]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.65.138
Dec 23 17:01:32 icinga sshd[11615]: Failed password for invalid user winna from 167.99.65.138 port 32828 ssh2
...
2019-12-24 03:33:00
124.127.250.162 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-12-24 03:49:57
2a02:c7d:725a:300:47e:a8b3:ee74:13a8 attack
MLV GET /wp-login.php
2019-12-24 03:52:36
129.204.201.27 attackspambots
Dec 11 08:57:27 yesfletchmain sshd\[20431\]: User root from 129.204.201.27 not allowed because not listed in AllowUsers
Dec 11 08:57:27 yesfletchmain sshd\[20431\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.201.27  user=root
Dec 11 08:57:29 yesfletchmain sshd\[20431\]: Failed password for invalid user root from 129.204.201.27 port 54350 ssh2
Dec 11 09:06:19 yesfletchmain sshd\[20785\]: Invalid user guest from 129.204.201.27 port 33670
Dec 11 09:06:19 yesfletchmain sshd\[20785\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.201.27
...
2019-12-24 04:08:41
106.13.38.59 attackspam
2019-12-23T15:57:50.568389shield sshd\[8843\]: Invalid user nfs from 106.13.38.59 port 46094
2019-12-23T15:57:50.572810shield sshd\[8843\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.38.59
2019-12-23T15:57:52.909950shield sshd\[8843\]: Failed password for invalid user nfs from 106.13.38.59 port 46094 ssh2
2019-12-23T16:05:21.245633shield sshd\[11386\]: Invalid user mysql from 106.13.38.59 port 45033
2019-12-23T16:05:21.250120shield sshd\[11386\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.38.59
2019-12-24 03:45:18
218.92.0.164 attackspambots
Dec 23 19:28:15 marvibiene sshd[9936]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.164  user=root
Dec 23 19:28:17 marvibiene sshd[9936]: Failed password for root from 218.92.0.164 port 35065 ssh2
Dec 23 19:28:21 marvibiene sshd[9936]: Failed password for root from 218.92.0.164 port 35065 ssh2
Dec 23 19:28:15 marvibiene sshd[9936]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.164  user=root
Dec 23 19:28:17 marvibiene sshd[9936]: Failed password for root from 218.92.0.164 port 35065 ssh2
Dec 23 19:28:21 marvibiene sshd[9936]: Failed password for root from 218.92.0.164 port 35065 ssh2
...
2019-12-24 03:42:43
129.204.42.62 attack
May 23 01:56:26 yesfletchmain sshd\[5871\]: Invalid user write from 129.204.42.62 port 45504
May 23 01:56:26 yesfletchmain sshd\[5871\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.42.62
May 23 01:56:29 yesfletchmain sshd\[5871\]: Failed password for invalid user write from 129.204.42.62 port 45504 ssh2
May 23 02:01:17 yesfletchmain sshd\[5952\]: Invalid user ang from 129.204.42.62 port 56804
May 23 02:01:17 yesfletchmain sshd\[5952\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.42.62
...
2019-12-24 03:34:10
129.204.210.237 attackspam
Apr 24 10:29:28 yesfletchmain sshd\[19541\]: Invalid user sentry from 129.204.210.237 port 56464
Apr 24 10:29:28 yesfletchmain sshd\[19541\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.210.237
Apr 24 10:29:30 yesfletchmain sshd\[19541\]: Failed password for invalid user sentry from 129.204.210.237 port 56464 ssh2
Apr 24 10:32:11 yesfletchmain sshd\[19597\]: Invalid user amssys from 129.204.210.237 port 53262
Apr 24 10:32:11 yesfletchmain sshd\[19597\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.210.237
...
2019-12-24 03:59:19

Recently Reported IPs

206.135.114.241 174.145.133.156 48.110.252.66 152.84.61.173
126.203.91.48 6.41.9.3 80.206.133.79 232.179.16.47
143.160.194.71 197.228.206.175 15.72.36.31 116.229.150.0
190.170.36.64 138.138.101.221 156.126.89.107 37.102.56.62
230.162.122.247 53.247.106.214 160.202.189.166 179.194.18.68