Skip to main content
Scam Lookup
Check Before You Trust
Trust report

amazon.com

Likely safeVisit siteFresh scan · 7/17/2026, 10:24:08 PM

79/100 — likely safe. Most trust signals check out. Verify unfamiliar businesses before big purchases.

Verdict driven by: no privacy policy found; no terms of service found; no contact page found — worth extra caution before trusting.

Top scam signals
  • No privacy policy found
    Legally required in most jurisdictions. Its absence is a real red flag.
  • No terms of service found
    Reputable sites usually publish a terms of service.
  • No contact page found
    Reputable sites usually publish a contact page.
SL Trust Core
79
likely safe
Category breakdown
Identity & Age70/100
1 signal · weight 22
Impersonation Risk100/100
2 signals · weight 22
Red Flags100/100
1 signal · weight 18
Transparency33/100
6 signals · weight 14
Security66/100
8 signals · weight 8
Email100/100
2 signals · weight 4
Infrastructure100/100
4 signals · weight 4
Content38/100
2 signals · weight 3
Performance100/100
1 signal · weight 3
Technical Health100/100
2 signals · weight 2
Positive signals
  • Site responded with 202
  • HTTPS is enforced
  • Fast response (183ms)
  • Served through Cloudflare
  • 3 address record(s) resolved
  • 4 authoritative nameservers
Warnings
  • Missing HSTS
  • Missing Content Security Policy
  • Page has no <title>
  • No privacy policy found
  • No terms of service found
  • No contact page found
Critical
None detected.
Helpful?
Recommendations

Top 6 things to fix

  • high · security
    Add an HSTS header

    Send Strict-Transport-Security: max-age=31536000; includeSubDomains on every response to force browsers onto HTTPS.

  • high · transparency
    Publish a Privacy Policy

    A linked privacy policy is legally required in most jurisdictions and is one of the strongest transparency signals.

  • medium · security
    Publish a Content Security Policy

    A minimal CSP dramatically reduces the impact of XSS. Start with default-src 'self' and iterate.

  • medium · transparency
    Publish Terms of Service

    Reputable commercial sites publish clear terms so users know their rights.

  • medium · transparency
    Add a contact page

    List an email, form, or physical address. Sites without contact info are trusted less by users and search engines.

  • low · content
    Set a page title

    Every page should have a descriptive <title> for browsers and search engines.

Root label
amazon
TLD
.com
Uses punycode (xn--)
no
Mixed-script (homoglyph)
no
Brand match
amazon (this IS the real brand's domain)
Typosquat check
no typosquat pattern
Phishing suffix tokens
none
amazon is the real brand's registered domain
The root label matches the brand exactly — this IS the brand's own domain.
+10
No impersonation patterns detected
Domain doesn't look like a typosquat, doesn't embed a well-known brand, and uses ASCII characters.
+8
Payment red flags
none detected
Urgency / pressure language
none detected
Disposable-domain combo
no
Page text length scanned
159 chars
No scam-correlated language found on the home page
No crypto-only / gift-card / wire-only payment demands, and no obvious urgency tactics.
+6
RDAP returned 403
Final URL
https://www.amazon.com/
Status
202
Response time
183ms
Server
cloudflare
CDN
Cloudflare
Content-Type
text/html; charset=UTF-8
Body size
2 KB
Redirects
1
Redirect chain
  1. 301 → https://www.amazon.com/
Site responded with 202
Final URL: https://www.amazon.com/. Response time 183ms.
+8
HTTPS is enforced
All redirects stayed on HTTPS. Traffic is encrypted end-to-end.
+10
Fast response (183ms)
+6
Served through Cloudflare
Sites behind a major CDN benefit from DDoS protection and edge caching.
+4
A
98.82.161.185, 98.87.170.74, 98.87.170.71
AAAA
—
MX
5 amazon-smtp.amazon.com
NS
ns-1447.awsdns-52.org, ns-1707.awsdns-21.co.uk, ns-264.awsdns-33.com, ns-521.awsdns-01.net
TXT count
61
3 address record(s) resolved
+4
4 authoritative nameservers
+2
crt.sh returned 502
missing: HSTSmissing: Content Security Policymissing: X-Frame-Optionsmissing: X-Content-Type-Optionsmissing: Referrer Policymissing: Permissions Policy
Missing HSTS
Tells browsers to only use HTTPS for this domain.
-4
Missing Content Security Policy
Restricts which scripts and resources the page can load.
-4
Missing X-Frame-Options
Prevents clickjacking by disallowing framing.
-3
Missing X-Content-Type-Options
Blocks MIME-sniffing browser attacks.
-2
Missing Referrer Policy
Controls what referrer information is sent with requests.
-2
Missing Permissions Policy
Restricts access to powerful browser features (camera, mic, etc.).
-2
SPF
v=spf1 include:spf1.amazon.com include:spf2.amazon.com include:amazonses.com -all
DMARC
v=DMARC1;" "p=quarantine;" "pct=100;" "rua=mailto:report@dmarc.amazon.com;" "ruf=mailto:report@dmarc.amazon.com
DMARC policy
quarantine
DKIM selectors found
—
SPF record published
+5
DMARC published (quarantine)
+4
Cloudflare· cdn
Title
Description
—
Language
en
Charset
utf-8
1 technologies detected
Cloudflare
Mobile viewport configured
+2
Page has no <title>
Well-maintained sites always set a page title.
-3
Missing meta description
-2
privacynot found
termsnot found
contactnot found
aboutnot found
refundnot found
shippingnot found
cookiesnot found
No pages linked.
No privacy policy found
Legally required in most jurisdictions. Its absence is a real red flag.
-4
No terms of service found
Reputable sites usually publish a terms of service.
-4
No contact page found
Reputable sites usually publish a contact page.
-4
No about page found
Reputable sites usually publish a about page.
-3
No refund/return policy found
Reputable sites usually publish a refund/return policy.
-3
No cookie policy found
Reputable sites usually publish a cookie policy.
-2
Diagnostics

Scan performance

engine 5.1.0 · report v5
Total scan time
6018 ms
Cache
Miss
Final response
183 ms
Redirects
1
Plugins executed
18
Plugins failed
7
Signal confidence
61%
Per-plugin timings
sitemapfailed · 6000 ms
robotsfailed · 5000 ms
phishstatsfailed · 3500 ms
http183 ms
urlhausfailed · 132 ms
sslfailed · 98 ms
email-security18 ms
dns11 ms
rdapfailed · 2 ms
reputation0 ms
impersonation0 ms
safe-browsingfailed · 0 ms
security-headers0 ms
tech0 ms
content0 ms
redirects0 ms
performance0 ms
red-flags0 ms