Is amazon.com a scam site? Scam, spam & reviews
https://www.amazon.com/ Scores & key points
Overview
アメリカ合衆国の多国籍テクノロジー企業
+107 Show more languages
Caution signals ⓘ
- [Medium] An HTTP error occurred when accessing the landing page.
Reputation
Review summary — amazon.com
Overall 80 (Mostly safe)Multiple security indicators are favorable and there are few major risk signals.
Strengths
- Valid SSL/TLS certificate
- HSTS enabled
- SPF configured
- DMARC configured
- Domain age ≥ 1 year
Weaknesses
- CSP not set
- HTTP error on landing page
Detailed review — amazon.com
Domain review
Domain created: 1994-11-01T05:00:00Z (≈ 31y 0m). Registrar: MarkMonitor Inc.. Hosting / AS: AMAZON-AES, US — United States. Popularity: Tranco #23, OPR 9.29/10. Reputation: GSB clean WebRisk clean. Email security: SPF On, DMARC quarantine. Certificate valid until: 2026-09-21T23:59:59+00:00.
Shop / transaction review
No mixed content detected. No mixed content detected. Structured data: Organization Absent, contactPoint Absent. Hidden text ratio 0%.
Technical review
HTTP 503 Server error · Server AMAZON-AES, US. HSTS Off (preload: Unknown). Applies 1/6 security headers. DNSSEC Off. Email security: SPF On, DMARC quarantine. MTA‑STS policy: None. TLS‑RPT Off. security.txt: available (https://amazon.com/.well-known/security.txt). JS obfuscation score 0. Reputation: GSB clean, WebRisk clean → overall Good.
Explanation — strengths and stability
Age: about (≈ 31y 0m) (created on 1994-11-01T05:00:00Z).
GSB clean
WebRisk clean
Certificate valid until: 2026-09-21T23:59:59+00:00.
Email security: SPF On, DMARC quarantine.
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.
Looking at operator information together with trust metrics helps you judge brand/merchant consistency and the likelihood of long‑term operation.
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-11-17 07:28:51
Claim website ownership
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 X-Content-Type-Options "nosniff" always;
add_header X-Frame-Options "SAMEORIGIN" always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
add_header Permissions-Policy "geolocation=(); microphone=(); camera=()" always;
Essentials
DMARC details
v=DMARC1;p=quarantine;pct=100;rua=mailto:report@dmarc.amazon.com;ruf=mailto:report@dmarc.amazon.comv=DMARC1;p=quarantine;pct=100;rua=mailto:report@dmarc.amazon.com;ruf=mailto:report@dmarc.amazon.comThreat insight
- 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.
- Suspicious JavaScript patterns detected
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)
- Suspicious JavaScript obfuscation patterns have been observed.
- Some cookie security attributes (Secure/HttpOnly/SameSite) are missing.
If unexpected popups, wallet connection requests, or download prompts appear, cancel once and re‑check via official announcements or community channels. For session/login cookies, always set Secure, HttpOnly, and SameSite.
Set‑Cookie (samples)
skin=noskin; path=/; domain=.amazon.com
Server location ⓘ
History
Change ⓘ --Recently added sites
Reviews
Average - / total 0
Checksum b486552e48425fc1546885d37a84ede3fb8a26d4a790f24a3fe16f4b92251f63
Analyzing
Collecting various signals and public data.
- Start
- Fetch DNS / WHOIS
- Check HTTP response
- Verify SSL/TLS
- Query reputation
- Collect PageSpeed data
- Analyze security headers
- Check email security
- Integrate extended signals
- Build report