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

;; QUESTION SECTION:
;66.216.214.122.			IN	A

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

;; Query time: 36 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 09:37:52 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 122.214.216.66.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server:		183.60.82.98
Address:	183.60.82.98#53

** server can't find 122.214.216.66.in-addr.arpa: SERVFAIL

Related IP info:
Related comments:
IP Type Details Datetime
101.68.70.14 attackbotsspam
Jun 23 02:57:49 cp sshd[11181]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.68.70.14
Jun 23 02:57:49 cp sshd[11181]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.68.70.14
2019-06-23 10:17:52
198.27.67.173 attack
Jun 23 02:18:57 srv206 sshd[12893]: Invalid user sysadm from 198.27.67.173
Jun 23 02:18:57 srv206 sshd[12893]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns506646.ip-198-27-67.net
Jun 23 02:18:57 srv206 sshd[12893]: Invalid user sysadm from 198.27.67.173
Jun 23 02:18:59 srv206 sshd[12893]: Failed password for invalid user sysadm from 198.27.67.173 port 49602 ssh2
...
2019-06-23 10:31:41
197.55.79.234 attackspambots
ssh failed login
2019-06-23 09:49:43
168.232.130.147 attackspam
Unauthorized access to SSH at 23/Jun/2019:00:19:28 +0000.
Received:  (SSH-2.0-libssh2_1.7.0)
2019-06-23 10:23:56
90.105.43.187 attackspam
SSH bruteforce (Triggered fail2ban)
2019-06-23 10:34:27
183.196.178.167 attack
ports scanning
2019-06-23 09:47:28
92.119.160.125 attack
23.06.2019 01:51:08 Connection to port 2621 blocked by firewall
2019-06-23 10:19:42
185.145.37.183 attackbotsspam
NAME : SUBNET-H-27 CIDR : 185.145.36.0/23 | STATUS : 200 ROBOT {Looking for resource vulnerabilities} DDoS Attack Germany - block certain countries :) IP: 185.145.37.183  Denial-of-Service Attack (DoS) Detected and Blocked by ADMIN  - data recovery https://help-dysk.pl
2019-06-23 10:06:51
93.84.117.222 attack
fail2ban honeypot
2019-06-23 09:52:55
196.203.31.154 attack
SSH Brute Force, server-1 sshd[17568]: Failed password for root from 196.203.31.154 port 49233 ssh2
2019-06-23 10:27:04
34.77.68.176 attack
rain
2019-06-23 10:16:14
106.251.239.244 attackspambots
Jun 23 02:35:56 [munged] sshd[11925]: Invalid user ken from 106.251.239.244 port 56134
Jun 23 02:35:56 [munged] sshd[11925]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.251.239.244
2019-06-23 10:11:44
74.82.47.12 attackspambots
1561249247 - 06/23/2019 02:20:47 Host: scan-11b.shadowserver.org/74.82.47.12 Port: 523 UDP Blocked
2019-06-23 09:46:07
46.242.119.214 attack
SSH Bruteforce @ SigaVPN honeypot
2019-06-23 10:29:02
80.82.77.139 attackspam
Trying ports that it shouldn't be.
2019-06-23 10:07:09

Recently Reported IPs

45.165.70.129 9.126.223.9 146.213.230.198 214.196.121.116
93.187.105.62 71.122.194.56 171.90.44.54 100.243.17.167
255.65.60.29 155.189.211.229 16.129.7.5 188.17.116.136
96.104.161.89 20.19.192.180 30.250.231.203 203.81.166.243
176.37.173.9 19.86.227.103 150.195.140.152 253.224.63.45