52.217.167.157 — 1 open port, 0 known CVEs, network Amazon.com, Inc.

Known CVEs on this host

1open port

8names pointing here

0known CVEs

0known exploited

Open ports and CVEs as of our latest check of this host, 2026-07-05.

No known CVEs on this host.

Network: Amazon.com, Inc. AS16509
Open ports: 80 · at our latest check, 2026-07-05
Location: United States US
Hostname: s3-website-us-east-1.amazonaws.com · reverse DNS, checked 2026-10-05
Route: 52.217.160.0/19 · announced by Amazon.com, Inc. AS16509 RPKI valid
Organisation: Amazon.com, Inc. · Enterprise
Cloud: Amazon Web Services · S3 · region us-east-1
Registry network: AT-88-Z · 52.192.0.0 - 52.223.191.255 · Amazon Technologies Inc. · ARIN
Abuse contact: [email protected] · for AT-88-Z
First seen: 2026-07-05 08:50 UTC
Last seen alive: 2026-07-05 08:52 UTC
Hosted domains: 8 names point here

Reputation

Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.

Services (1)

80/tcp HTTP AmazonS3 first 2026-07-05 · last 2026-07-05

Status: 301 Moved Permanently
Title: 301 Moved Permanently
Server: AmazonS3

Raw response

HTTP/1.1 301 Moved Permanently
x-amz-error-code: WebsiteRedirect
x-amz-error-message: Request does not contain a bucket name.
x-amz-request-id: TZ93NVEP6ZM8N2JP
x-amz-id-2: WGW60t74sKLA8TBvrzMZzu8YvwlmIc8tL9fKVAu8hTWqiqC1vFsnBPmc8hAd74mwa0lHPFKv/2c=
Location: https://aws.amazon.com/s3/
Content-Type: text/html; charset=utf-8
Content-Length: 348
Date: Sun, 05 Jul 2026 08:50:57 GMT
Server: AmazonS3

Port history

Every port that has answered a connection on this address, and when. A port is listed as open above only when a service was identified on it. Times are UTC.

Hostnames pointing to this address

8 names · as answered by each domain's own name servers

beartronics.comfirst seen 2026-10-10

birghtinnovations.comfirst seen 2026-10-11

eshengxiang.comfirst seen 2026-10-12

geckro.comfirst seen 2026-10-13

luziasantiago.comfirst seen 2026-10-14

mechinate.comfirst seen 2026-10-14

patfitzgerald.comfirst seen 2026-10-16

rethinkcommunications.comfirst seen 2026-10-16

Report an issue with this page