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: Ashburn

Region: Virginia

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

;; QUESTION SECTION:
;52.20.152.249.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 18:49:02 CST 2025
;; MSG SIZE  rcvd: 106
Host info
249.152.20.52.in-addr.arpa domain name pointer ec2-52-20-152-249.compute-1.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
249.152.20.52.in-addr.arpa	name = ec2-52-20-152-249.compute-1.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
118.173.224.63 attackspam
Unauthorized connection attempt detected from IP address 118.173.224.63 to port 23
2020-02-14 09:36:10
49.233.140.233 attackbotsspam
Invalid user fqn from 49.233.140.233 port 51832
2020-02-14 09:22:25
49.235.202.65 attack
Invalid user auto from 49.235.202.65 port 54793
2020-02-14 09:56:12
76.164.234.122 attackbotsspam
Feb 14 02:44:06 debian-2gb-nbg1-2 kernel: \[3903872.473269\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=76.164.234.122 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=240 ID=32700 PROTO=TCP SPT=43332 DPT=14400 WINDOW=1024 RES=0x00 SYN URGP=0
2020-02-14 09:49:10
177.91.87.13 attack
Automatic report - Port Scan Attack
2020-02-14 09:50:22
194.15.36.53 attackbotsspam
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-14 09:46:44
54.39.44.47 attackbots
Invalid user lines from 54.39.44.47 port 42490
2020-02-14 09:40:15
45.83.65.183 attackbotsspam
Unauthorized connection attempt detected from IP address 45.83.65.183 to port 23
2020-02-14 09:21:37
164.132.196.134 attackbots
2020-2-14 12:06:42 AM: failed ssh attempt
2020-02-14 09:36:26
202.168.205.181 attackspambots
2020-02-14T02:00:49.386539  sshd[31165]: Invalid user tw from 202.168.205.181 port 27082
2020-02-14T02:00:49.400924  sshd[31165]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.168.205.181
2020-02-14T02:00:49.386539  sshd[31165]: Invalid user tw from 202.168.205.181 port 27082
2020-02-14T02:00:51.123579  sshd[31165]: Failed password for invalid user tw from 202.168.205.181 port 27082 ssh2
...
2020-02-14 09:47:28
49.235.144.143 attackspambots
SSH brute force
2020-02-14 09:57:43
195.136.206.230 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-14 09:27:14
194.28.5.110 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-14 09:32:50
193.112.104.178 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-14 09:53:05
142.93.207.14 attack
Feb 13 23:02:44 pi sshd[28431]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.207.14  user=root
Feb 13 23:02:46 pi sshd[28431]: Failed password for invalid user root from 142.93.207.14 port 47466 ssh2
2020-02-14 09:54:57

Recently Reported IPs

67.109.181.17 15.94.204.150 152.132.153.41 196.72.198.42
108.197.78.138 151.223.54.35 59.195.100.178 226.80.180.24
12.69.31.32 167.191.182.67 155.55.190.102 37.244.160.160
25.126.127.164 179.192.153.241 247.208.223.125 182.193.205.170
8.210.157.244 220.45.249.22 8.97.142.204 138.0.123.52