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:
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2025, American Registry for Internet Numbers, Ltd.
#


NetRange:       52.0.0.0 - 52.79.255.255
CIDR:           52.64.0.0/12, 52.0.0.0/10
NetName:        AT-88-Z
NetHandle:      NET-52-0-0-0-1
Parent:         NET52 (NET-52-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       
Organization:   Amazon Technologies Inc. (AT-88-Z)
RegDate:        1991-12-19
Updated:        2024-02-05
Comment:        Geofeed http://ip-ranges.amazonaws.com/geo-ip-feed.csv
Ref:            https://rdap.arin.net/registry/ip/52.0.0.0



OrgName:        Amazon Technologies Inc.
OrgId:          AT-88-Z
Address:        410 Terry Ave N.
City:           Seattle
StateProv:      WA
PostalCode:     98109
Country:        US
RegDate:        2011-12-08
Updated:        2024-01-24
Comment:        All abuse reports MUST include:
Comment:        * src IP
Comment:        * dest IP (your IP)
Comment:        * dest port
Comment:        * Accurate date/timestamp and timezone of activity
Comment:        * Intensity/frequency (short log extracts)
Comment:        * Your contact details (phone and email) Without these we will be unable to identify the correct owner of the IP address at that point in time.
Ref:            https://rdap.arin.net/registry/entity/AT-88-Z


OrgAbuseHandle: AEA8-ARIN
OrgAbuseName:   Amazon EC2 Abuse
OrgAbusePhone:  +1-206-555-0000 
OrgAbuseEmail:  trustandsafety@support.aws.com
OrgAbuseRef:    https://rdap.arin.net/registry/entity/AEA8-ARIN

OrgNOCHandle: AANO1-ARIN
OrgNOCName:   Amazon AWS Network Operations
OrgNOCPhone:  +1-206-555-0000 
OrgNOCEmail:  amzn-noc-contact@amazon.com
OrgNOCRef:    https://rdap.arin.net/registry/entity/AANO1-ARIN

OrgRoutingHandle: ARMP-ARIN
OrgRoutingName:   AWS RPKI Management POC
OrgRoutingPhone:  +1-206-555-0000 
OrgRoutingEmail:  aws-rpki-routing-poc@amazon.com
OrgRoutingRef:    https://rdap.arin.net/registry/entity/ARMP-ARIN

OrgRoutingHandle: IPROU3-ARIN
OrgRoutingName:   IP Routing
OrgRoutingPhone:  +1-206-555-0000 
OrgRoutingEmail:  aws-routing-poc@amazon.com
OrgRoutingRef:    https://rdap.arin.net/registry/entity/IPROU3-ARIN

OrgTechHandle: ANO24-ARIN
OrgTechName:   Amazon EC2 Network Operations
OrgTechPhone:  +1-206-555-0000 
OrgTechEmail:  amzn-noc-contact@amazon.com
OrgTechRef:    https://rdap.arin.net/registry/entity/ANO24-ARIN


#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2025, American Registry for Internet Numbers, Ltd.
#
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 52.72.114.140
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56291
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;52.72.114.140.			IN	A

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

;; Query time: 2 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Oct 11 00:01:47 CST 2025
;; MSG SIZE  rcvd: 106
Host info
140.114.72.52.in-addr.arpa domain name pointer ec2-52-72-114-140.compute-1.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
140.114.72.52.in-addr.arpa	name = ec2-52-72-114-140.compute-1.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
51.255.168.30 attackspambots
Nov 30 11:28:08 firewall sshd[24473]: Invalid user liping from 51.255.168.30
Nov 30 11:28:10 firewall sshd[24473]: Failed password for invalid user liping from 51.255.168.30 port 40658 ssh2
Nov 30 11:31:06 firewall sshd[24520]: Invalid user leonides from 51.255.168.30
...
2019-12-01 03:57:13
24.53.151.95 attackbotsspam
Autoban   24.53.151.95 ABORTED AUTH
2019-12-01 03:40:10
186.195.90.4 attackspam
Unauthorized connection attempt from IP address 186.195.90.4 on Port 445(SMB)
2019-12-01 03:36:16
140.213.38.132 attackbotsspam
Unauthorized connection attempt from IP address 140.213.38.132 on Port 445(SMB)
2019-12-01 03:53:28
118.69.32.167 attack
2019-11-30T14:31:38.996746homeassistant sshd[20052]: Failed password for invalid user kraggerud from 118.69.32.167 port 49944 ssh2
2019-11-30T19:31:53.306215homeassistant sshd[13365]: Invalid user taiga from 118.69.32.167 port 48180
2019-11-30T19:31:53.312741homeassistant sshd[13365]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.69.32.167
...
2019-12-01 03:34:18
45.163.59.242 attackbotsspam
Microsoft-Windows-Security-Auditing
2019-12-01 03:50:45
5.139.208.17 attackbots
Nov 30 18:07:51 sso sshd[13923]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.139.208.17
Nov 30 18:07:53 sso sshd[13923]: Failed password for invalid user dumpy from 5.139.208.17 port 45584 ssh2
...
2019-12-01 03:33:31
103.215.80.81 attack
Nov 30 13:49:38 ws22vmsma01 sshd[109648]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.215.80.81
Nov 30 13:49:40 ws22vmsma01 sshd[109648]: Failed password for invalid user kraatz from 103.215.80.81 port 40926 ssh2
...
2019-12-01 03:47:51
112.175.150.13 attackspam
Nov 30 19:52:58 h2177944 sshd\[23804\]: Invalid user test from 112.175.150.13 port 55453
Nov 30 19:52:58 h2177944 sshd\[23804\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.175.150.13
Nov 30 19:53:00 h2177944 sshd\[23804\]: Failed password for invalid user test from 112.175.150.13 port 55453 ssh2
Nov 30 19:56:40 h2177944 sshd\[23972\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.175.150.13  user=root
...
2019-12-01 03:42:21
122.51.128.9 attackspam
Invalid user pane from 122.51.128.9 port 40800
2019-12-01 03:58:10
220.142.220.68 attackspambots
firewall-block, port(s): 2323/tcp
2019-12-01 04:01:47
113.116.92.193 attack
Unauthorized connection attempt from IP address 113.116.92.193 on Port 445(SMB)
2019-12-01 03:59:23
137.74.199.177 attack
Nov 30 20:46:50 MK-Soft-VM6 sshd[17828]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=137.74.199.177 
Nov 30 20:46:52 MK-Soft-VM6 sshd[17828]: Failed password for invalid user kravi from 137.74.199.177 port 60520 ssh2
...
2019-12-01 04:07:13
79.137.75.5 attack
Nov 30 15:31:10 mail sshd\[23362\]: Invalid user git from 79.137.75.5
Nov 30 15:31:10 mail sshd\[23362\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.137.75.5
Nov 30 15:31:13 mail sshd\[23362\]: Failed password for invalid user git from 79.137.75.5 port 44868 ssh2
...
2019-12-01 03:52:43
116.111.165.112 attack
Unauthorized connection attempt from IP address 116.111.165.112 on Port 445(SMB)
2019-12-01 03:58:23

Recently Reported IPs

20.169.108.13 206.42.225.250 58.212.237.216 124.31.104.181
159.0.75.209 159.0.75.81 159.0.75.76 43.199.229.129
54.83.151.136 42.236.17.214 27.185.229.20 47.92.132.12
47.92.113.136 47.92.224.96 142.93.107.221 39.98.33.79
39.103.128.74 27.185.229.26 83.143.119.10 154.44.1.92