Is amazonaws.com a scam site? Scam, spam & reviews
https://aws.amazon.com/ Scores & key points
Caution signals ⓘ
- [Medium] No valid SSL/TLS certificate found.
- [Low] Security headers such as HSTS and CSP are missing or insufficient.
- [Low] Cookie security attributes are insufficient (total 3).
Reputation
Review summary — amazonaws.com
Overall 83 (Mostly safe)Multiple security indicators are favorable and there are few major risk signals.
Strengths
- HSTS enabled
- SPF configured
- DMARC configured
- Domain age ≥ 1 year
Weaknesses
- No valid SSL/TLS certificate
- CSP not set
Detailed review — amazonaws.com
Domain review
Domain created: 2005-08-18T02:10:45Z (≈ 20y 4m). Registrar: MarkMonitor Inc.. Hosting / AS: AMAZON-02, US — United States. Popularity: OPR 4.75/10. Reputation: GSB clean WebRisk clean. Email security: SPF On, DMARC quarantine.
Shop / transaction review
No mixed content detected. No mixed content detected. Structured data: Organization Absent, contactPoint Absent. Hidden text ratio 0%.
Technical review
HTTP 200 Success · Server AMAZON-02, US. HSTS Off (preload: Unknown). Applies 3/6 security headers. DNSSEC Off. Email security: SPF On, DMARC quarantine. MTA‑STS policy: None. TLS‑RPT Off. security.txt: not available. Missing cookie attributes: Secure×1 / HttpOnly×1 / SameSite×1. JS obfuscation score 0. Reputation: GSB clean, WebRisk clean → overall Good.
Explanation — strengths and stability
Age: about (≈ 20y 4m) (created on 2005-08-18T02:10:45Z).
GSB clean
WebRisk clean
Email security: SPF On, DMARC quarantine.
Applies 3/6 security headers.
No mixed content detected.
Looking at operator information together with trust metrics helps you judge brand/merchant consistency and the likelihood of long‑term operation.
Checking payment page security (HTTPS enforcement, form target host consistency, script integrity) along with customer support and return policy gives a more accurate sense of real‑world trust.
In parallel, applying security headers, automated certificate renewal, email domain protection (DMARC/TLS‑RPT), and removing mixed content will improve overall reliability and delivery/search stability.
Explanation — risks and areas to improve
Without HSTS, downgrade and man‑in‑the‑middle attacks can weaken HTTPS enforcement. Enable HSTS and prepare for preload registration.
Missing key security headers leaves the site vulnerable to clickjacking, MIME sniffing, and data leakage.
Without DNSSEC, trust relies solely on parent name servers and DNS tampering risks can be higher in some environments.
Without MTA‑STS, SMTP TLS enforcement is weaker.
Without TLS‑RPT, it is harder to collect TLS failure signals and operational insight.
Without security.txt, the vulnerability disclosure channel is unclear and response may be delayed.
Cookies without Secure / HttpOnly / SameSite can be vulnerable to theft or session fixation attacks.
This analysis is an automated, data‑based opinion for reference only. Please verify the information yourself before paying or downloading anything.
About this report
- First analysis: -
- Last updated: 2025-12-13 16:22:44
Claim website ownership
Traffic signals
Performance
Security headers
- HSTS ⓘ
- Content‑Security‑Policy ⓘ
- X‑Content‑Type‑Options ⓘ
- X‑Frame‑Options ⓘ
- Referrer‑Policy ⓘ
- Permissions‑Policy ⓘ
add_header Content-Security-Policy "default-src 'self'; img-src 'self' data:; object-src 'none'; base-uri 'self'";
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
add_header Permissions-Policy "geolocation=(); microphone=(); camera=()" always;
Set-Cookie: name=value; Path=/; Secure; HttpOnly; SameSite=Lax
aws_lang=en
Domain lineage
-
2005-08-18Domain registered: 2005-08-18T02:10:45Z
Essentials
DMARC details
v=DMARC1; p=quarantine; sp=none; pct=100; rua=mailto:aws-marketing-email-dmarc-rua-reports@dmarc.amazonaws.com; ruf=mailto:aws-marketing-email-dmarc-ruf-reports@dmarc.amazonaws.comv=DMARC1; p=quarantine; sp=none; pct=100; rua=mailto:aws-marketing-email-dmarc-rua-reports@dmarc.amazonaws.com; ruf=mailto:aws-marketing-email-dmarc-ruf-reports@dmarc.amazonaws.comThreat insight
- Using invalid or expired SSL/TLS certificates triggers browser warnings and increases the risk of man‑in‑the‑middle attacks or confusion with phishing sites. Check certificate status regularly.
- Without HSTS, downgrade and man‑in‑the‑middle attacks can weaken HTTPS enforcement. Enable HSTS and prepare for preload registration.
The risk score of this site is calculated by combining browser security headers, SSL status, mixed content, email domain protection (SPF/DMARC), redirect/obfuscation patterns, and the results of Google Safe Browsing and WebRisk. There are currently few clear signs of malicious behavior, but insufficient security headers or email protection can increase the risk of phishing or man‑in‑the‑middle attacks. Before entering important information, re‑check the domain spelling and how you reached the site (ads, DMs, shortened URLs, etc.). Before entering payment or personal information, verify operator information (company/contact), HTTPS enforcement, DMARC/TLS‑RPT, and check for mixed content.
Deep scan (HTML / headers)
- Some cookie security attributes (Secure/HttpOnly/SameSite) are missing.
- The site heavily relies on third‑party resources.
For session/login cookies, always set Secure, HttpOnly, and SameSite.
Set‑Cookie (samples)
aws-priv=eyJ2IjoxLCJldSI6MCwic3QiOjB9; Version=1; Comment="Anonymous cookie for privacy regulations"; Domain=.aws.amazon.com; Max-Age=31536000; Expires=Sun, 13 Dec 2026 16:22:44 GMT; Path=/; Secure</code><br><code>aws_lang=en; Domain=.amazon.com; Path=/
User scenarios
If you make a payment on this site
Some technical or reputation signals suggest caution. Check the address bar, HTTPS and browser warnings before entering payment details. Mixed or non-encrypted (HTTP) resources or weak TLS can expose payment data or session tokens on some networks.
If you log in or enter personal data
Some script, content or header patterns warrant caution. Compare the login link with official sources before entering credentials. Missing cookie security attributes or cross-domain POST forms can make sessions easier to steal or misuse. After logging in, watch for unusual account or billing activity.
Server location ⓘ
History
Change ⓘ --Recently added sites
Reviews
Average - / total 0
Checksum 64cf30d6b5dee6b4cc331b0f44b2033c580952511b984c0cbc4cec03a91f4dcb
Social ⓘ
Platforms that this site may be using.