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

;; QUESTION SECTION:
;52.214.164.222.			IN	A

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

;; Query time: 65 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 11 06:40:06 CST 2022
;; MSG SIZE  rcvd: 107
Host info
222.164.214.52.in-addr.arpa domain name pointer ec2-52-214-164-222.eu-west-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
222.164.214.52.in-addr.arpa	name = ec2-52-214-164-222.eu-west-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
212.102.37.182 attackbots
Malicious/Probing: /wp/wp-includes/wlwmanifest.xml
2020-09-07 17:02:50
101.231.124.6 attackspambots
"fail2ban match"
2020-09-07 16:52:42
111.229.78.212 attackbots
SCAN: Host Sweep CloudCIX Reconnaissance Scan Detected, PTR: PTR record not found
2020-09-07 17:07:56
104.206.128.70 attack
 TCP (SYN) 104.206.128.70:58505 -> port 21, len 44
2020-09-07 16:50:19
87.251.74.201 attackspambots
2020-09-06 04:59:54 Reject access to port(s):3389 1 times a day
2020-09-07 16:45:56
172.110.8.121 attack
Port Scan: TCP/80
2020-09-07 17:04:34
223.167.110.183 attackspam
265/tcp 21561/tcp 6497/tcp...
[2020-08-31/09-06]26pkt,9pt.(tcp)
2020-09-07 16:57:07
49.88.112.116 attackbots
SSH bruteforce
2020-09-07 16:35:07
2.50.170.54 attack
1599410962 - 09/06/2020 18:49:22 Host: 2.50.170.54/2.50.170.54 Port: 23 TCP Blocked
...
2020-09-07 16:55:15
190.205.59.6 attack
Port scan denied
2020-09-07 17:04:15
154.237.65.36 attackspam
Honeypot attack, port: 445, PTR: PTR record not found
2020-09-07 16:27:18
91.192.136.43 attackbotsspam
Sep  7 08:09:32 santamaria sshd\[6562\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.192.136.43  user=root
Sep  7 08:09:34 santamaria sshd\[6562\]: Failed password for root from 91.192.136.43 port 46004 ssh2
Sep  7 08:13:21 santamaria sshd\[6599\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.192.136.43  user=root
...
2020-09-07 16:44:32
95.239.24.240 attackspambots
Automatic report - Port Scan Attack
2020-09-07 16:51:23
103.253.3.214 attackbots
(sshd) Failed SSH login from 103.253.3.214 (ID/Indonesia/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Sep  6 23:08:15 server5 sshd[20487]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.253.3.214  user=mysql
Sep  6 23:08:17 server5 sshd[20487]: Failed password for mysql from 103.253.3.214 port 38360 ssh2
Sep  6 23:21:52 server5 sshd[26996]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.253.3.214  user=root
Sep  6 23:21:54 server5 sshd[26996]: Failed password for root from 103.253.3.214 port 35964 ssh2
Sep  6 23:26:53 server5 sshd[29374]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.253.3.214  user=root
2020-09-07 16:33:54
111.19.164.38 attackbotsspam
Port probing on unauthorized port 1433
2020-09-07 17:01:54

Recently Reported IPs

16.159.127.128 152.23.73.180 100.244.60.189 178.90.14.158
82.29.112.224 211.182.98.29 18.2.17.18 76.161.251.187
193.175.232.48 79.183.212.89 22.36.218.158 113.182.158.50
40.218.84.153 182.184.5.205 63.205.94.83 145.26.142.189
206.24.240.249 163.233.65.254 107.160.35.119 83.247.200.125