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

;; QUESTION SECTION:
;214.2.14.65.			IN	A

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

;; Query time: 128 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 11 08:18:46 CST 2023
;; MSG SIZE  rcvd: 104
Host info
Host 65.14.2.214.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
server can't find 214.2.14.65.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
190.120.197.21 attack
Unauthorized connection attempt detected from IP address 190.120.197.21 to port 1433
2019-12-29 03:17:25
188.226.171.36 attackbots
2019-12-28T14:52:14.391293shield sshd\[6694\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.226.171.36  user=root
2019-12-28T14:52:15.792972shield sshd\[6694\]: Failed password for root from 188.226.171.36 port 53000 ssh2
2019-12-28T14:55:42.941359shield sshd\[7521\]: Invalid user fritz from 188.226.171.36 port 56564
2019-12-28T14:55:42.945548shield sshd\[7521\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.226.171.36
2019-12-28T14:55:45.235283shield sshd\[7521\]: Failed password for invalid user fritz from 188.226.171.36 port 56564 ssh2
2019-12-29 03:43:11
189.232.124.185 attackspam
Unauthorized connection attempt detected from IP address 189.232.124.185 to port 23
2019-12-29 03:17:51
54.188.166.113 attackbots
Unauthorized connection attempt detected from IP address 54.188.166.113 to port 8984
2019-12-29 03:09:38
189.19.105.192 attack
Unauthorized connection attempt detected from IP address 189.19.105.192 to port 445
2019-12-29 03:18:46
91.187.123.233 attack
Unauthorized connection attempt detected from IP address 91.187.123.233 to port 445
2019-12-29 03:03:47
189.144.160.189 attack
Unauthorized connection attempt detected from IP address 189.144.160.189 to port 81
2019-12-29 03:18:25
196.52.43.55 attackspam
Unauthorized connection attempt detected from IP address 196.52.43.55 to port 443
2019-12-29 03:40:48
35.193.129.95 attack
Unauthorized connection attempt detected from IP address 35.193.129.95 to port 6380
2019-12-29 03:34:59
213.108.116.120 attack
Unauthorized connection attempt detected from IP address 213.108.116.120 to port 80
2019-12-29 03:37:15
187.11.209.202 attack
Unauthorized connection attempt detected from IP address 187.11.209.202 to port 8080
2019-12-29 03:20:23
81.174.25.195 attackbotsspam
Unauthorized connection attempt detected from IP address 81.174.25.195 to port 8080
2019-12-29 03:05:11
164.68.105.70 attackspambots
Port 22 Scan, PTR: None
2019-12-29 03:22:00
202.152.13.178 attackbotsspam
Unauthorized connection attempt from IP address 202.152.13.178 on Port 445(SMB)
2019-12-29 03:14:25
107.189.10.141 attack
Unauthorized connection attempt detected from IP address 107.189.10.141 to port 22
2019-12-29 03:24:55

Recently Reported IPs

18.197.227.110 12.131.60.56 8.45.38.110 201.52.107.231
209.23.110.21 5.60.177.153 149.200.23.60 97.64.126.229
147.246.190.95 48.245.37.229 83.48.43.113 225.5.230.87
5.121.196.156 171.237.194.55 94.21.52.242 58.219.205.49
128.63.27.240 54.241.33.66 86.124.127.16 29.235.13.6