Skip to main content
DNS Tool
Engineer's DNS Intelligence Report
Generated 18 Feb 2026, 11:29 UTC
Duration 27.7s
Version v26.20.48
Integrity a4bcd9f0a32c99dfa4ef494f76bfe135df9fefcfe821097374f48ff41e958d9a4d9dae32001b6fdc07894e478c22086e8217c5817d8d491f66a79377a5e2ab32
Subject Domain
amazon.com

Engineer's DNS Intelligence Report

amazon.com
18 Feb 2026, 11:29 UTC · 27.7s ·v26.20.48 · SHA-3-512: a4bc✱✱✱✱ Verify
Executive Methodology
Recon Mode Snapshot Re-analyze New Domain
Footprint 8 SaaS Services
DNS Security & Trust Posture
Risk Level: Low Risk
4 protocols configured, 5 not configured Domain appears to be in deliberate DMARC deployment phase — quarantine fully enforced with reporting, consider upgrading to reject Why we go beyond letter grades
1 recommendation 1 monitoring
Email Spoofing
Protected
Brand Impersonation
Protected
DNS Tampering
Unsigned
Certificate Control
Open
Recommended
Upgrade DMARC policy from quarantine to reject (p=reject) for maximum spoofing protection
Monitoring
External domain dmarc.amazon.com has not authorized amazon.com to send DMARC reports (missing amazon.com._report._dmarc.dmarc.amazon.com TXT record)
Configured
SPF, DMARC (quarantine, 100%), DKIM, BIMI
Not Configured
MTA-STS, TLS-RPT, DANE, DNSSEC, CAA
Priority Actions 5 total Achievable posture: Secure
Medium Enable DNSSEC

DNSSEC is not enabled for this domain. DNSSEC provides cryptographic authentication of DNS responses, preventing cache poisoning and DNS spoofing attacks.

RFC 4035
Medium Upgrade DMARC to Reject

Your DMARC policy is set to quarantine. Upgrade to p=reject for maximum protection — reject instructs receivers to discard spoofed mail entirely rather than quarantining it.

A reject policy provides the strongest protection against domain spoofing.
TypeTXT
Host_dmarc.amazon.com (update existing DMARC record)
Valuev=DMARC1; p=reject; rua=mailto:dmarc-reports@amazon.com
RFC 7489 §6.3
Low Add CAA Records

CAA records specify which Certificate Authorities may issue certificates for your domain, reducing the risk of unauthorized certificate issuance.

CAA constrains which CAs can issue certificates for this domain.
TypeCAA
Hostamazon.com (root of domain — adjust CA to match your provider)
Value0 issue "letsencrypt.org"
RFC 8659
Low Add TLS-RPT Reporting

TLS-RPT (TLS Reporting) sends you reports about TLS connection failures when other servers try to deliver mail to your domain.

TLS-RPT sends you reports about TLS connection failures to your mail servers.
TypeTXT
Host_smtp._tls.amazon.com (SMTP TLS reporting record)
Valuev=TLSRPTv1; rua=mailto:tls-reports@amazon.com
RFC 8460
Low Deploy MTA-STS

MTA-STS enforces TLS encryption for inbound mail delivery, preventing downgrade attacks on your mail transport.

MTA-STS tells sending servers to require TLS when delivering mail to your domain.
TypeTXT
Host_mta-sts.amazon.com (MTA-STS policy record)
Valuev=STSv1; id=amazon.com
RFC 8461
Registrar (RDAP) OBSERVED LIVE
MarkMonitor Inc.
Where domain was purchased
Email Service Provider
Unknown
Moderately Protected
Web Hosting
Unknown
Where website is hosted
DNS Hosting
Unknown
Where DNS records are edited
Email Security Methodology Can this domain be impersonated by email? Unlikely SPF and DMARC quarantine policy enforced

SPF Record RFC 7208 §4 Verified

Does this domain declare who may send email on its behalf? Yes
Success -all 3/10 lookups

SPF valid with strict enforcement (-all), 3/10 lookups

v=spf1 include:spf1.amazon.com include:spf2.amazon.com include:amazonses.com -all
RFC 7489 §10.1: -all may cause rejection before DMARC evaluation, preventing DKIM from being checked
RFC 7208 Conformant — This SPF record conforms to the syntax and semantics defined in RFC 7208 §4.
RFC Failure Mode: Unlike DMARC (where unknown tags are silently ignored per RFC 7489 §6.3), SPF with unrecognized mechanisms produces a PermError per RFC 7208 §4.6 — the record fails loudly rather than silently.
Related CVEs: CVE-2024-7208 (multi-tenant domain spoofing), CVE-2024-7209 (shared SPF exploitation), CVE-2023-51764 (SMTP smuggling bypasses SPF)
SPF hard fail (-all): compliance-strong, but can short-circuit DMARC. RFC 7489 notes that -all can cause some receivers to reject mail during the SMTP transaction — before DKIM is checked and before DMARC can evaluate the result. A message that would pass DMARC via DKIM alignment may be rejected prematurely. For most domains, ~all + DMARC p=reject is the strongest compatible posture — it allows every authentication method (SPF, DKIM, DMARC) to be fully evaluated before a decision is made.
DMARC enforcement is partial (quarantine). -all may preempt DKIM/DMARC evaluation at some receivers. Consider p=reject for full enforcement; ~all is more DMARC-compatible.
Legacy Record — Safe to Delete This is a Sender ID record (spf2.0/pra) from a Microsoft experiment circa 2006 that was never standardized. RFC 7208 §A explicitly deprecates it. No modern mail receiver processes this record. It is safe to delete.
spf2.0/pra include:spf1.amazon.com include:spf2.amazon.com include:amazonses.com -all

DMARC Policy RFC 7489 §6.3 Verified

Are spoofed emails rejected or quarantined? Quarantined, not rejected
Success p=quarantine

DMARC policy quarantine (100%) - good protection

v=DMARC1;p=quarantine;pct=100;rua=mailto:report@dmarc.amazon.com;ruf=mailto:report@dmarc.amazon.com
Alignment: SPF relaxed DKIM relaxed
No np= tag (DMARCbis) — non-existent subdomains inherit p= policy but adding np=reject provides explicit protection against subdomain spoofing
Forensic reporting (ruf) is configured, but most major providers do not send forensic reports. RFC 7489 §7.3 warns that forensic reports can expose PII (full message headers or bodies). Google, Microsoft, and Yahoo do not honour ruf= requests. The DMARCbis draft (draft-ietf-dmarc-dmarcbis) has formally removed ruf= from the specification. Consider removing this tag to simplify your record. RFC 7489 §7.3 — Forensic Reports
Advanced cryptographic posture detected. Domain appears to be in deliberate DMARC deployment phase — quarantine fully enforced with reporting, consider upgrading to reject
RFC 7489 Present — DMARC record published per RFC 7489 §6.3.
Monitoring Posture Note: Quarantine sequesters authentication failures while preserving full DMARC forensic telemetry (RFC 7489 §7). Some organizations maintain quarantine rather than reject as a deliberate monitoring strategy — failed messages are processed and reported but sequestered from the inbox. See NIST SP 800-177 Rev. 1 for enforcement tradeoffs.
DMARCbis (Pending): draft-ietf-dmarc-dmarcbis will elevate DMARC to Standards Track, obsolete RFC 7489, replace pct= with t= (testing flag), add np= (non-existent subdomain policy), and mandate DNS tree walk for policy discovery instead of the Public Suffix List.
Related CVEs: CVE-2024-49040 (Exchange sender spoofing), CVE-2024-7208 (multi-tenant DMARC bypass)

DKIM Records RFC 6376 §3.6 Verified

Are outbound emails cryptographically signed? Not discoverable
Weak Keys

Found 2 DKIM selector(s) but some keys are revoked

Key revoked (p= empty)
Key revoked (p= empty)
zendesk1._domainkey Zendesk
v=DKIM1; p=
zendesk2._domainkey Zendesk
v=DKIM1; p=
RFC Stance: RFC 6376 (Internet Standard) defines the DKIM mechanism. DKIM selectors are not publicly enumerable — absence in a scan does not prove absence of signing.
Known Vulnerabilities: DKIM l= tag body length vulnerability (attacker appends unsigned content to signed mail), weak key exploitation (keys below 1024-bit are cryptographically breakable per RFC 6376 §3.3.3), DKIM replay attacks (re-sending legitimately signed messages at scale)

MTA-STS RFC 8461 §3 Verified

Can attackers downgrade SMTP to intercept mail? Not prevented
Warning

No MTA-STS record found

MTA-STS policy enforcement is evaluated in Mail Transport Security below.

TLS-RPT RFC 8460 §3 Verified

Will failures in TLS delivery be reported? No reporting
Warning

No TLS-RPT record found

DMARC External Reporting Authorization RFC 7489 §7.1

Are external report receivers authorized? Authorization missing
Warning

1 of 1 external reporting domains missing authorization

External Domain Authorization Auth Record
dmarc.amazon.com Unauthorized —
External domain dmarc.amazon.com has not authorized amazon.com to send DMARC reports (missing amazon.com._report._dmarc.dmarc.amazon.com TXT record)

Third-Party Action Required

This authorization record must be created by the external reporting provider, not by you. Per RFC 7489 §7.1, the receiving domain must publish a TXT record to confirm it accepts DMARC reports from your domain.

What to do: Contact your DMARC reporting provider and ask them to publish the authorization TXT record shown above. If you use a managed DMARC service (e.g., Ondmarc, Dmarcian, Valimail), this is typically handled during onboarding — reach out to their support if the record is missing.

Impact if unresolved: Compliant receivers may silently discard aggregate or forensic reports destined for the unauthorized address, reducing your DMARC visibility.

DANE / TLSA Verified Recon Methodology Can mail servers establish identity without a public CA? No
RFC 7672 §3 RFC 6698 §2 Not Configured

No DANE/TLSA records found (checked 1 MX host)

DANE (RFC 7672) binds TLS certificates to DNSSEC-signed DNS records, protecting email transport against man-in-the-middle attacks and rogue CAs. It is the primary transport security standard — MTA-STS (RFC 8461) was created as the alternative for domains that cannot deploy DNSSEC. Over 1 million domains use DANE globally, including Microsoft Exchange Online, Proton Mail, and Fastmail. Best practice: deploy both for defense in depth.
Email Transport Security

Two mechanisms protect email in transit. DANE is the primary standard; MTA-STS is the alternative for domains that cannot deploy DNSSEC:

  • DNSSEC + DANE (RFC 7672) — Cryptographic chain of trust from DNS root to mail server certificate. Eliminates reliance on certificate authorities. No trust-on-first-use weakness. Requires DNSSEC.
  • MTA-STS (RFC 8461) — HTTPS-based policy requiring TLS for mail delivery. Works without DNSSEC but relies on CA trust and is vulnerable on first use (§10). Created for domains where “deploying DNSSEC is undesirable or impractical” (§2).
This domain has neither DANE nor MTA-STS. Mail transport relies on opportunistic TLS without policy enforcement, leaving it vulnerable to downgrade attacks. Deploy DANE (RFC 7672) with DNSSEC for the strongest protection, or MTA-STS (RFC 8461) if DNSSEC is not feasible.

Industry trend: Microsoft Exchange Online enforces inbound DANE with DNSSEC (GA October 2024), and providers like Proton Mail and Fastmail also support DANE. Google Workspace does not support DANE and relies on MTA-STS. Both mechanisms coexist because DANE is backward-compatible — senders skip the check if the domain isn't DNSSEC-signed (RFC 7672 §1.3).

Brand Security Can this brand be convincingly faked? Partially DMARC quarantine policy provides moderate protection but does not fully reject spoofed mail

BIMI BIMI Spec Verified Success VMC SVG

Is the brand identity verified and displayed in inboxes? Yes

BIMI with VMC certificate (from Verified CA)

VMC certificate accessible (from Verified CA) - logo displays in Gmail, Apple Mail, and all major providers.
v=BIMI1;l=https://d3frv9g52qce38.cloudfront.net/amazondefault/order_1424920778_logo.svg;a=https://d3frv9g52qce38.cloudfront.net/amazondefault/amazon_web_services_inc_2026.pem
BIMI Logo
Logo validated (SVG) View full logo

CAA RFC 8659 §4 Verified Warning

Does this domain restrict who can issue TLS certificates? No

No CAA records found - any CA can issue certificates

Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? Partial RFC 9116

security.txt found with issues

Contact

https://hackerone.com/amazonvrp/reports/new

Expires

Missing (required by RFC 9116 §2.5.5)

Policy

https://hackerone.com/amazonvrp
Hiring
Source: https://amazon.com/.well-known/security.txt
Missing required Expires field (RFC 9116 §2.5.5)
AI Surface Scanner Beta Is this domain discoverable by AI — and protected from abuse? No

No AI governance measures detected

llms.txt llmstxt.org
Is this domain publishing AI-readable brand context? No
No llms.txt found
No llms-full.txt found
AI Crawler Governance (robots.txt) RFC 9309 IETF Draft
Are AI crawlers explicitly allowed or blocked? Not blocked
No AI crawler blocking observed — no blocking directives found in robots.txt
Content-Usage Directive IETF Draft
Does the site express AI content-usage preferences? Not Configured
No Content-Usage directive detected. The IETF AI Preferences working group is developing a Content-Usage: directive for robots.txt that lets site owners declare whether their content may be used for AI training and inference. This is an active draft, not yet a ratified standard.
Example: Add Content-Usage: ai=no to robots.txt to deny AI training, or Content-Usage: ai=allow to explicitly permit it. Without this directive, AI crawler behavior depends on individual crawler policies and User-agent rules.
AI Recommendation Poisoning
Is this site trying to manipulate AI recommendations? No
No AI recommendation poisoning indicators found
Hidden Prompt Artifacts
Is hidden prompt-injection text present in the source? No
No hidden prompt-like artifacts detected
Evidence Log (1 item)
TypeDetailSeverityConfidence
robots_txt_no_ai_blocks robots.txt found but no AI-specific blocking directives low Observed
Public Exposure Checks Are sensitive files or secrets exposed? No

No exposed secrets detected in public page source — same-origin, non-intrusive scan of publicly visible page source and scripts.

No exposed secrets, API keys, or credentials were detected in publicly accessible page source or scripts.
What type of scan is this?

This is OSINT (Open Source Intelligence) collection — we check the same publicly accessible URLs that any web browser could visit. No authentication is bypassed, no ports are probed, no vulnerabilities are exploited.

Is this a PCI compliance scan? No. PCI DSS requires scans performed by an Approved Scanning Vendor (ASV) certified by the PCI Security Standards Council. DNS Tool is not an ASV. If you need PCI compliance scanning, engage a certified ASV such as Qualys, Tenable, or Trustwave.

Is this a penetration test? No. Penetration testing involves active exploitation attempts against systems with authorization. Our checks are passive observation of publicly accessible resources — the same methodology used by Shodan, Mozilla Observatory, and other OSINT platforms.

Mail Transport Security Beta Is mail transport encrypted and verified? No No MTA-STS or DANE — mail transport encryption is opportunistic only

No transport encryption policy detected — mail delivery relies on opportunistic TLS

Policy Assessment Primary

No transport enforcement policies detected. Mail delivery relies on opportunistic STARTTLS, which is vulnerable to downgrade attacks (RFC 3207). Consider deploying MTA-STS (RFC 8461) or DANE (RFC 7672).

Telemetry
TLS-RPT not configured — domain has no visibility into TLS delivery failures from real senders
Live Probe Supplementary
Skipped — SMTP probe skipped — outbound TCP port 25 is blocked by cloud hosting provider. This is standard for all major cloud platforms (AWS, GCP, Azure, Replit) as an anti-spam measure. Transport security is assessed via DNS policy records above, which is the standards-aligned primary method per NIST SP 800-177 Rev. 1.
Infrastructure Intelligence Who hosts this domain and what services power it? Direct

ASN / Network Success

Resolved 2 unique ASN(s) across 3 IP address(es)

ASNNameCountry
AS14618 Amazon.com, Inc. US
AS16509 Amazon.com, Inc. US
IPv4 Mappings:
98.82.161.185 → AS16509 (98.80.0.0/12)
98.87.170.71 → AS14618 (98.80.0.0/13)
98.87.170.74 → AS16509 (98.80.0.0/12)

Edge / CDN Success

Domain appears to use direct origin hosting

SaaS TXT Footprint Success 8 services

8 SaaS services detected via DNS TXT verification records

Detects SaaS services that leave DNS TXT verification records (e.g., domain ownership proofs). Does not detect all SaaS platforms — only those indicated by DNS.

ServiceVerification Record
Stripe stripe-verification=45f746e3b195198f419af3f685fdf217532ce552b4b47070b3caefe32555...
Canva canva-site-verification=Hksh9WEUPWP13_SEU1mPMA
Google Workspace google-site-verification=NV91qEfNgqDZOPzwlhXE-KtDUfCBSNgAsdxaFebyh80
Apple apple-domain-verification=dVkKZnu17XS0EN2X
Microsoft 365 MS=4B600B22799EB2CAC0D8FF0A3A3CAECA5EE2BF3A
Cisco Umbrella cisco-ci-domain-verification=1b256bd11daa486ba2fa405d2d5de70f75feb6757dd8993ca8d...
Facebook / Meta facebook-domain-verification=d9u57u52gylohx845ogo1axzpywpmq
Atlassian atlassian-domain-verification=ZT4AapXgobCpXIWoNcd7gtMjZyOUdr4EDFMnFUWrqqqgdaQVbD...
Domain Security Methodology Can DNS responses be tampered with in transit? Possible DNSSEC is not deployed, DNS responses are not cryptographically verified

DNSSEC RFC 4033 §2 Verified Unsigned

DNSSEC not configured - DNS responses are unsigned

Domain does not use DNSSEC. Enable in your registrar's DNS settings (look for "DNSSEC" or "DS records" section).

NS Delegation Verified

8 nameserver(s) configured

Nameservers: ns1.amzndns.co.uk ns1.amzndns.com ns1.amzndns.net ns1.amzndns.org ns2.amzndns.co.uk ns2.amzndns.com ns2.amzndns.net ns2.amzndns.org
Multi-Resolver Verification Recon: Discrepancy detected - Some resolvers returned different results (1 difference found)
Resolver Differences:
TXT: OpenDNS returned different results: [00DcX000002xu6h=1TBcX00000000Xt MS=4B600B22799EB2CAC0D8FF0A3A3CAECA5EE2BF3A TS1760027 ZOOM_verify_6OUC1znUonKMCoyMMGyFfX ZOOM_verify_ARI4AiKALCcjulAUZNwR8S apple-domain-verification=4wbNaeWvAH0pU1yi apple-domain-verification=dVkKZnu17XS0EN2X brevo-code:9be7f7c39958d253a31de6593fa831bc canva-site-verification=Hksh9WEUPWP13_SEU1mPMA]
This may indicate DNS propagation in progress or geo-based DNS routing.
Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

98.82.161.185
98.87.170.71
98.87.170.74
Where the domain points for web traffic

AAAAIPv6 Address

No AAAA records
IPv6 not configured

MXMail Servers

5 amazon-smtp.amazon.com.
Priority + mail server for email delivery

SRVServices

No SRV records
No service-specific routing configured
Web: Reachable (3 IPv4, 0 IPv6) Mail: 1 server Services: None
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? Showing 200 of 862 discovered
How did we find these?
Certificate Transparency Logs Unavailable The results below are from DNS probing only and may be significantly incomplete. CT logs typically reveal hundreds or thousands of additional subdomains via certificate issuance history (RFC 6962).
Re-Analyze to Retry CT Lookup
5952 unique certificates 63 current 799 expired 17 CNAMEs Source: Certificate Transparency + DNS Intelligence
Subdomains discovered via CT logs (RFC 6962), DNS probing of common service names, and CNAME chain traversal.
Certificate Authority Diversity (8 CAs observed across CT log history)
Certificate Authority Certs First Issued Last Issued Status
VeriSign, Inc. 5307 2007-03-09 2015-10-13 Historical
Symantec Corporation 527 2014-01-29 2015-08-10 Historical
DigiCert Inc 96 2007-10-10 2015-05-14 Historical
COMODO CA Limited 6 2011-03-02 2012-03-26 Historical
GeoTrust, Inc. 6 2013-03-28 2014-04-28 Historical
Cybertrust Inc 4 2013-03-03 2014-04-16 Historical
The USERTRUST Network 3 2010-04-13 2010-04-13 Historical
VeriSign Trust Network 2 2008-10-23 2009-08-31 Historical
Showing 200 of 862 discovered subdomains, prioritized by security relevance. All 63 current subdomains are included, plus the most relevant historical entries. Export Full Recon (CSV)
Subdomain Source Status Provider / CNAME Certificates First Seen Issuer(s)
alas.aws.amazon.com CT Log Current alas.cname-proxy.amazon.com 2 2015-05-22T00:00:00 Symantec Corporation, VeriSign, Inc.
analytics.amazon.com DNS Current midway-gateway-4.aea.amazon.com — — —
api-preprod.amazon.com CT Log Current — 2 2012-08-02T00:00:00 VeriSign, Inc.
appstore-sdk.amazon.com CT Log Current — 5 2015-06-17T00:00:00 Symantec Corporation, VeriSign, Inc.
authorcentral.amazon.com CT Log Current — 5 2010-04-07T00:00:00 VeriSign, Inc.
bebemsh.amazon.com CT Log Current — 2 2009-10-27T00:00:00 VeriSign, Inc.
beta.amazon.com DNS Current — — — —
build.amazon.com DNS Current midway-gateway-2-1.aea.amazon.com — — —
cal.amazon.com DNS Current rewrite.amazon.com — — —
checkout.amazon.com DNS Current rewrite.amazon.com — — —
cloud.amazon.com DNS Current — — — —
conference.amazon.com DNS Current midway-gateway-2-2.aea.amazon.com — — —
connect.amazon.com DNS Current midway-gateway-2-1.aea.amazon.com — — —
cs-ext-preprod.amazon.com CT Log Current — 1 2013-07-25T00:00:00 VeriSign, Inc.
docs.amazon.com DNS Current — — — —
dub-salmon.amazon.com CT Log Current — 2 2010-12-29T00:00:00 VeriSign, Inc.
echo.amazon.com CT Log Current alexa.amazon.com 3 2015-07-14T00:00:00 Symantec Corporation, VeriSign, Inc.
email.amazon.com CT Log Current — 1 2013-04-17T00:00:00 VeriSign, Inc.
gru-b-orca.amazon.com CT Log Current — 2 2013-11-19T00:00:00 VeriSign, Inc.
help.amazon.com DNS Current — — — —
hr.amazon.com DNS Current midway-gateway-2-2.aea.amazon.com — — —
https-basic-sedi-qa.amazon.com CT Log Current — 1 2013-08-31T00:00:00 VeriSign, Inc.
https-inbound.amazon.com CT Log Current — 3 2010-10-08T00:00:00 VeriSign, Inc.
https-sedi-eu.amazon.com CT Log Current — 1 2013-07-30T00:00:00 VeriSign, Inc.
identity.amazon.com CT Log Current — 1 2013-02-13T00:00:00 VeriSign, Inc.
images.amazon.com DNS Current d12yb4rynyn0ps.cloudfront.net — — —
iws-froogle-feeds.amazon.com CT Log Current — 2 2010-04-06T00:00:00 VeriSign, Inc.
jp-pre-prod-aw.amazon.com CT Log Current — 3 2014-06-22T00:00:00 VeriSign, Inc.
kumamoto.aws.amazon.com CT Log Current kumamoto.cname-proxy.amazon.com 2 2014-06-27T00:00:00 VeriSign, Inc.
learn.amazon.com DNS Current — — — —
login.amazon.com CT Log Current tp.81a0edd7b-frontier.amazon.com 4 2015-06-16T00:00:00 Symantec Corporation, VeriSign, Inc.
lookout-service-bjs-gamma.amazon.com CT Log Current — 1 2012-12-07T00:00:00 VeriSign, Inc.
m.amazon.com DNS Current — — — —
match-visualsearch-uk.amazon.com CT Log Current match-visualsearch-frontend-uk.amazon.com 2 2015-06-06T00:00:00 Symantec Corporation, VeriSign, Inc.
mobile.amazon.com DNS Current rewrite.amazon.com — — —
monitor-api-public-bjs-in-pdx.amazon.com CT Log Current — 2 2013-03-13T00:00:00 VeriSign, Inc.
monitor.amazon.com DNS Current midway-gateway-2-1.aea.amazon.com — — —
mx1.amazon.com DNS Current — — — —
mx2.amazon.com DNS Current — — — —
orders.amazon.com DNS Current — — — —
orgs.amazon.com CT Log Current — 3 2015-04-28T00:00:00 Symantec Corporation, VeriSign, Inc.
p13n-eu.amazon.com CT Log Current tp.3252680bd-frontier.amazon.com 3 2011-11-01T00:00:00 VeriSign, Inc.
panel.amazon.com DNS Current — — — —
pay.amazon.com DNS Current tp.32437f578-frontier.amazon.com — — —
payment.amazon.com DNS Current payments.amazon.com — — —
payments.amazon.com CT Log Current — 5 2009-10-19T00:00:00 VeriSign, Inc.
prime.amazon.com CT Log Current — 3 2014-07-07T00:00:00 VeriSign, Inc.
register.amazon.com DNS Current — — — —
relay.amazon.com DNS Current tp.b1190b3a2-frontier.amazon.com — — —
s3.amazon.com DNS Current a8ae13f5f7373cd00.awsglobalaccelerator.com — — —
sg-console-ap-southeast-1.console.aws.amazon.com CT Log Current — 3 2011-04-24T00:00:00 VeriSign, Inc.
shop.amazon.com DNS Current s1.amazon.com — — —
store.amazon.com DNS Current s1.amazon.com — — —
studios.amazon.com CT Log Current — 3 2014-06-02T00:00:00 VeriSign, Inc.
support-preview.aws.amazon.com CT Log Current — 1 2014-07-08T00:00:00 VeriSign, Inc.
support.amazon.com DNS Current — — — —
swvgdtt-gateway-eu.amazon.com CT Log Current — 2 2010-12-30T00:00:00 VeriSign, Inc.
textpayme.amazon.com CT Log Current — 2 2009-08-12T00:00:00 VeriSign, Inc.
urmp-1-prod.amazon.com CT Log Current urmp-prod.amazon.com 2 2015-06-19T00:00:00 Symantec Corporation, VeriSign, Inc.
us-east-1.console.aws.amazon.com CT Log Current us-east-1.console.cname-proxy.amazon.com 5 2012-04-14T00:00:00 VeriSign, Inc.
us-west-1.console.aws.amazon.com CT Log Current us-west-1.console.cname-proxy.amazon.com 2 2014-09-15T00:00:00 VeriSign, Inc.
video.amazon.com DNS Current — — — —
wiki.amazon.com DNS Current midway-gateway-1.aea.amazon.com — — —
devicemessaging.us-east-1.amazon.com CT Log Expired — 3 2015-10-13T00:00:00 VeriSign, Inc.
www1.amazon.com CT Log Expired — 4 2015-09-28T00:00:00 VeriSign, Inc.
uedata.amazon.com CT Log Expired — 7 2015-09-11T00:00:00 VeriSign, Inc.
us.amazon.com CT Log Expired — 2 2015-09-11T00:00:00 VeriSign, Inc.
foo.ec2-pinotage.amazon.com CT Log Expired — 1 2015-08-17T00:00:00 VeriSign, Inc.
www7.amazon.com CT Log Expired — 2 2015-08-14T00:00:00 VeriSign, Inc.
www3.amazon.com CT Log Expired — 3 2015-08-12T00:00:00 VeriSign, Inc.
kca-preprod.amazon.com CT Log Expired — 1 2015-08-10T00:00:00 Symantec Corporation
signin.aws.amazon.com CT Log Expired — 8 2015-08-10T00:00:00 Symantec Corporation, VeriSign, Inc., DigiCert Inc
iba-cdn.amazon.com CT Log Expired — 4 2015-08-05T00:00:00 Symantec Corporation, VeriSign, Inc.
api-cdn.amazon.com CT Log Expired — 4 2015-08-05T00:00:00 Symantec Corporation, VeriSign, Inc.
alexa.amazon.com CT Log Expired — 1 2015-07-14T00:00:00 Symantec Corporation
apub-blog.amazon.com CT Log Expired — 5 2015-07-14T00:00:00 Symantec Corporation, VeriSign, Inc.
payments-jp.amazon.com CT Log Expired — 4 2015-07-08T00:00:00 Symantec Corporation, VeriSign, Inc.
gio-catalog-fe.amazon.com CT Log Expired — 5 2015-07-07T00:00:00 Symantec Corporation, VeriSign, Inc.
gio-catalog-eu.amazon.com CT Log Expired — 5 2015-07-02T00:00:00 Symantec Corporation, VeriSign, Inc.
gio-catalog.amazon.com CT Log Expired — 7 2015-06-29T00:00:00 Symantec Corporation, VeriSign, Inc.
www8.amazon.com CT Log Expired — 1 2015-06-27T00:00:00 Symantec Corporation
money-markets-blog.amazon.com CT Log Expired — 9 2015-06-27T00:00:00 Symantec Corporation, VeriSign, Inc.
blogs.aws.amazon.com CT Log Expired — 4 2015-06-27T00:00:00 Symantec Corporation, VeriSign, Inc.
www14.amazon.com CT Log Expired — 1 2015-06-27T00:00:00 Symantec Corporation
tech-book-store.amazon.com CT Log Expired — 4 2015-06-27T00:00:00 Symantec Corporation, VeriSign, Inc.
sesblog.amazon.com CT Log Expired — 5 2015-06-27T00:00:00 Symantec Corporation, VeriSign, Inc.
yukon.aws.amazon.com CT Log Expired — 1 2015-06-27T00:00:00 Symantec Corporation
primenow.amazon.com CT Log Expired — 3 2015-06-27T00:00:00 Symantec Corporation, VeriSign, Inc.
zme-caps.amazon.com CT Log Expired — 5 2015-06-23T00:00:00 Symantec Corporation, VeriSign, Inc.
read.amazon.com CT Log Expired — 5 2015-06-23T00:00:00 Symantec Corporation, VeriSign, Inc.
grstaging.amazon.com CT Log Expired — 4 2015-06-23T00:00:00 Symantec Corporation, VeriSign, Inc.
zme-caps-iad.amazon.com CT Log Expired — 3 2015-06-23T00:00:00 Symantec Corporation, VeriSign, Inc.
urmp-4-prod.amazon.com CT Log Expired — 2 2015-06-19T00:00:00 Symantec Corporation, VeriSign, Inc.
urmp-prod.amazon.com CT Log Expired — 2 2015-06-19T00:00:00 Symantec Corporation, VeriSign, Inc.
urmp-5-prod.amazon.com CT Log Expired — 2 2015-06-19T00:00:00 Symantec Corporation, VeriSign, Inc.
urmp-7-prod.amazon.com CT Log Expired — 2 2015-06-19T00:00:00 Symantec Corporation, VeriSign, Inc.
urmp-3-prod.amazon.com CT Log Expired — 2 2015-06-19T00:00:00 Symantec Corporation, VeriSign, Inc.
urmp-2-prod.amazon.com CT Log Expired — 2 2015-06-19T00:00:00 Symantec Corporation, VeriSign, Inc.
primenow-us.amazon.com CT Log Expired — 1 2015-06-19T00:00:00 Symantec Corporation
credential-locker-service.amazon.com CT Log Expired — 3 2015-06-18T00:00:00 Symantec Corporation, VeriSign, Inc.
dub-orca.amazon.com CT Log Expired — 1 2015-06-18T00:00:00 Symantec Corporation
policysim.aws.amazon.com CT Log Expired — 3 2015-06-17T00:00:00 Symantec Corporation, VeriSign, Inc.
kdk.amazon.com CT Log Expired — 4 2015-06-17T00:00:00 Symantec Corporation, VeriSign, Inc.
apac.account.amazon.com CT Log Expired — 2 2015-06-16T00:00:00 Symantec Corporation, VeriSign, Inc.
whispercast.amazon.com CT Log Expired — 5 2015-06-12T00:00:00 Symantec Corporation, VeriSign, Inc.
mas-ssr.amazon.com CT Log Expired — 4 2015-06-11T00:00:00 Symantec Corporation, VeriSign, Inc.
mas-ssr-fe.amazon.com CT Log Expired — 4 2015-06-11T00:00:00 Symantec Corporation, VeriSign, Inc.
mas-ext.amazon.com CT Log Expired — 5 2015-06-11T00:00:00 Symantec Corporation, VeriSign, Inc.
forums.developer.amazon.com CT Log Expired — 6 2015-06-11T00:00:00 Symantec Corporation, VeriSign, Inc.
sedi.amazon.com CT Log Expired — 5 2015-06-10T00:00:00 Symantec Corporation, VeriSign, Inc.
sea-orca.amazon.com CT Log Expired — 1 2015-06-10T00:00:00 Symantec Corporation
iad-orca.amazon.com CT Log Expired — 1 2015-06-10T00:00:00 Symantec Corporation
agcod-v2-eu.amazon.com CT Log Expired — 3 2015-06-09T00:00:00 Symantec Corporation, VeriSign, Inc.
agcod-v2-fe-gamma.amazon.com CT Log Expired — 3 2015-06-09T00:00:00 Symantec Corporation, VeriSign, Inc.
agcod-v2-gamma.amazon.com CT Log Expired — 4 2015-06-09T00:00:00 Symantec Corporation, VeriSign, Inc.
agcod-v2-fe.amazon.com CT Log Expired — 3 2015-06-09T00:00:00 Symantec Corporation, VeriSign, Inc.
sis.amazon.com CT Log Expired — 5 2015-06-09T00:00:00 Symantec Corporation, VeriSign, Inc.
agcod-v2.amazon.com CT Log Expired — 4 2015-06-09T00:00:00 Symantec Corporation, VeriSign, Inc.
localregister-app.amazon.com CT Log Expired — 3 2015-06-09T00:00:00 Symantec Corporation, VeriSign, Inc.
agcod-v2-eu-gamma.amazon.com CT Log Expired — 3 2015-06-09T00:00:00 Symantec Corporation, VeriSign, Inc.
match-visualsearch-jp.amazon.com CT Log Expired — 2 2015-06-06T00:00:00 Symantec Corporation, VeriSign, Inc.
pulse.amazon.com CT Log Expired — 4 2015-06-05T00:00:00 Symantec Corporation, VeriSign, Inc.
squawk.amazon.com CT Log Expired — 4 2015-06-05T00:00:00 Symantec Corporation, VeriSign, Inc.
access-alexa-na.amazon.com CT Log Expired — 1 2015-06-04T00:00:00 Symantec Corporation
bookextras.amazon.com CT Log Expired — 4 2015-06-04T00:00:00 VeriSign, Inc.
eu.account.amazon.com CT Log Expired — 3 2015-06-03T00:00:00 Symantec Corporation, VeriSign, Inc.
warpspeed.us-east-1.aws.amazon.com CT Log Expired — 1 2015-06-02T00:00:00 Symantec Corporation
marketing.amazon.com CT Log Expired — 1 2015-05-29T00:00:00 Symantec Corporation
advertize.amazon.com CT Log Expired — 1 2015-05-29T00:00:00 Symantec Corporation
adwords.amazon.com CT Log Expired — 1 2015-05-29T00:00:00 Symantec Corporation
advertise.amazon.com CT Log Expired — 1 2015-05-29T00:00:00 Symantec Corporation
www.artistcentral.amazon.com CT Log Expired — 5 2015-05-29T00:00:00 Symantec Corporation, VeriSign, Inc.
advertizing.amazon.com CT Log Expired — 1 2015-05-29T00:00:00 Symantec Corporation
advertising.amazon.com CT Log Expired — 1 2015-05-29T00:00:00 Symantec Corporation
kep.amazon.com CT Log Expired — 3 2015-05-28T00:00:00 Symantec Corporation, VeriSign, Inc.
argileto.amazon.com CT Log Expired — 4 2015-05-28T00:00:00 Symantec Corporation, VeriSign, Inc.
aps.amazon.com CT Log Expired — 5 2015-05-25T00:00:00 Symantec Corporation, VeriSign, Inc.
ps-app-us.amazon.com CT Log Expired — 3 2015-05-25T00:00:00 Symantec Corporation, VeriSign, Inc.
giveaway.amazon.com CT Log Expired — 2 2015-05-22T00:00:00 Symantec Corporation, VeriSign, Inc.
archie-ops.us-east-1.aws.amazon.com CT Log Expired — 2 2015-05-22T00:00:00 Symantec Corporation, VeriSign, Inc.
odcs-na-extern.amazon.com CT Log Expired — 2 2015-05-22T00:00:00 Symantec Corporation, VeriSign, Inc.
assoc-datafeeds-cn.amazon.com CT Log Expired — 4 2015-05-21T00:00:00 VeriSign, Inc.
amp.aws.amazon.com CT Log Expired — 3 2015-05-17T00:00:00 Symantec Corporation, VeriSign, Inc.
codepipeline-preview-console.us-east-1.aws.amazon.com CT Log Expired — 1 2015-05-14T00:00:00 Symantec Corporation
tax-exemption.amazon.com CT Log Expired — 2 2015-05-14T00:00:00 Symantec Corporation, VeriSign, Inc.
cssmmobile.amazon.com CT Log Expired — 3 2015-05-14T00:00:00 Symantec Corporation, VeriSign, Inc.
payments-jp-sandbox.amazon.com CT Log Expired — 1 2015-04-30T00:00:00 Symantec Corporation
aps-fe-master.amazon.com CT Log Expired — 4 2015-04-29T00:00:00 Symantec Corporation, VeriSign, Inc.
aps-master.amazon.com CT Log Expired — 5 2015-04-29T00:00:00 Symantec Corporation, VeriSign, Inc.
aps-eu-master.amazon.com CT Log Expired — 4 2015-04-29T00:00:00 Symantec Corporation, VeriSign, Inc.
kindle-preview.amazon.com CT Log Expired — 5 2015-04-28T00:00:00 Symantec Corporation, VeriSign, Inc.
kindlepreview.amazon.com CT Log Expired — 5 2015-04-28T00:00:00 Symantec Corporation, VeriSign, Inc.
payeecentral.amazon.com CT Log Expired — 2 2015-04-28T00:00:00 Symantec Corporation, VeriSign, Inc.
orgcentral.amazon.com CT Log Expired — 3 2015-04-28T00:00:00 Symantec Corporation, VeriSign, Inc.
org.amazon.com CT Log Expired — 3 2015-04-28T00:00:00 Symantec Corporation, VeriSign, Inc.
auth-zappos-na.amazon.com CT Log Expired — 1 2015-04-25T00:00:00 Symantec Corporation
zappos.amazon.com CT Log Expired — 2 2015-04-25T00:00:00 Symantec Corporation, VeriSign, Inc.
workdocs.ap-southeast-1.amazon.com CT Log Expired — 1 2015-04-24T00:00:00 Symantec Corporation
source.amazon.com CT Log Expired — 4 2015-04-24T00:00:00 Symantec Corporation, VeriSign, Inc.
kdp.amazon.com CT Log Expired — 4 2015-04-22T00:00:00 Symantec Corporation, VeriSign, Inc.
cloudforge-external.lux.amazon.com CT Log Expired — 2 2015-04-22T00:00:00 Symantec Corporation, VeriSign, Inc.
kindleworlds.amazon.com CT Log Expired — 4 2015-04-22T00:00:00 Symantec Corporation, VeriSign, Inc.
paragon-fe.amazon.com CT Log Expired — 1 2015-04-21T00:00:00 Symantec Corporation
kindleworlds-eu.amazon.com CT Log Expired — 3 2015-04-21T00:00:00 Symantec Corporation, VeriSign, Inc.
kdp-eu.amazon.com CT Log Expired — 3 2015-04-21T00:00:00 Symantec Corporation, VeriSign, Inc.
paragon-na.amazon.com CT Log Expired — 3 2015-04-21T00:00:00 Symantec Corporation, VeriSign, Inc.
paragon-eu.amazon.com CT Log Expired — 3 2015-04-21T00:00:00 Symantec Corporation, VeriSign, Inc.
coursematerials.amazon.com CT Log Expired — 2 2015-04-21T00:00:00 Symantec Corporation, VeriSign, Inc.
umass.amazon.com CT Log Expired — 1 2015-04-21T00:00:00 Symantec Corporation
cc.amazon.com CT Log Expired — 4 2015-04-20T00:00:00 Symantec Corporation, VeriSign, Inc.
kindlescout.amazon.com CT Log Expired — 2 2015-04-17T00:00:00 Symantec Corporation, VeriSign, Inc.
af-mobile-api.amazon.com CT Log Expired — 1 2015-04-16T00:00:00 Symantec Corporation
writeon.amazon.com CT Log Expired — 3 2015-04-14T00:00:00 Symantec Corporation, VeriSign, Inc.
writeon-community.amazon.com CT Log Expired — 4 2015-04-14T00:00:00 Symantec Corporation, VeriSign, Inc.
local.amazon.com CT Log Expired — 6 2015-04-14T00:00:00 Symantec Corporation, VeriSign, Inc.
ams.amazon.com CT Log Expired — 6 2015-04-14T00:00:00 Symantec Corporation, VeriSign, Inc.
vap.amazon.com CT Log Expired — 3 2015-04-01T00:00:00 VeriSign, Inc.
glacier-console-eu-west-1.console.aws.amazon.com CT Log Expired — 4 2015-03-25T00:00:00 VeriSign, Inc.
mas-sdk.amazon.com CT Log Expired — 5 2015-03-25T00:00:00 VeriSign, Inc.
r.amazon.com CT Log Expired — 1 2015-03-06T00:00:00 VeriSign, Inc.
atv-ps-eu.amazon.com CT Log Expired — 4 2015-02-13T00:00:00 VeriSign, Inc.
atv-ps-fe.amazon.com CT Log Expired — 4 2015-02-13T00:00:00 VeriSign, Inc.
fals.atv-ps-fe.amazon.com CT Log Expired — 2 2015-02-13T00:00:00 VeriSign, Inc.
fals.atv-ps-eu.amazon.com CT Log Expired — 2 2015-02-13T00:00:00 VeriSign, Inc.
kokanee.amazon.com CT Log Expired — 2 2015-02-05T00:00:00 VeriSign, Inc.
ballard.amazon.com CT Log Expired — 3 2015-02-05T00:00:00 VeriSign, Inc.
wsync.us-east-1.amazon.com CT Log Expired — 3 2015-01-29T00:00:00 VeriSign, Inc.
parker-gateway-na.amazon.com CT Log Expired — 1 2015-01-29T00:00:00 VeriSign, Inc.
storedesignproxy-eu.amazon.com CT Log Expired — 1 2014-11-19T00:00:00 VeriSign, Inc.
www.localregister.amazon.com CT Log Expired — 1 2014-11-15T00:00:00 VeriSign, Inc.
cde-ta-g7g-newstack-preprod.amazon.com CT Log Expired — 3 2014-11-13T00:00:00 VeriSign, Inc.
mas-ssr-fe-ad.amazon.com CT Log Expired — 1 2014-11-13T00:00:00 VeriSign, Inc.
mas-ssr-eu-ad.amazon.com CT Log Expired — 1 2014-11-13T00:00:00 VeriSign, Inc.
series-fe.amazon.com CT Log Expired — 1 2014-11-06T00:00:00 VeriSign, Inc.
arcus.us-west-2.aws.amazon.com CT Log Expired — 1 2014-11-06T00:00:00 VeriSign, Inc.
db-preview.aws.amazon.com CT Log Expired — 1 2014-11-02T00:00:00 VeriSign, Inc.
chicago.aws.amazon.com CT Log Expired — 1 2014-10-23T00:00:00 VeriSign, Inc.
sms-in.amazon.com CT Log Expired — 1 2014-10-12T00:00:00 VeriSign, Inc.
w6.amazon.com CT Log Expired — 1 2014-10-07T00:00:00 VeriSign, Inc.
au-prod-internal.amazon.com CT Log Expired — 2 2014-10-07T00:00:00 VeriSign, Inc.
Showing 200 of 862 discovered subdomains, curated by security relevance. Multiple cooperative discovery methods — including CT logs (RFC 6962), DNS probing, and CNAME chain traversal — feed into a unified view. Well-known service names (mail, vpn, api, sso, admin, etc.), DNS-resolving hosts, and subdomains with the most certificate activity are prioritized. 799 expired-certificate-only subdomains included where relevant. Export Full Recon (CSV)
Δ Changes Detected: TXT Resolver ≠ Authoritative (TTL / CDN rotation / recent change)
Risk: Low - typically resolves within TTL
DNS Intelligence What does DNS look like right now — and what changed over time?
DNS Evidence Diff Side-by-side comparison
Resolver Records (Public DNS cache)
Authoritative Records (Source of truth)
A Synchronized 3 / 3 records
98.82.161.185
98.87.170.74
98.87.170.71
98.82.161.185
98.87.170.74
98.87.170.71
AAAA 0 / 0 records
No records
No records
CAA RFC 8659 §4 0 / 0 records
No records
No records
DMARC _dmarc.amazon.com RFC 7489 §6.3 Synchronized 1 / 1 records
v=DMARC1;p=quarantine;pct=100;rua=mailto:report@dmarc.amazon.com;ruf=mailto:report@dmarc.amazon.com
v=DMARC1;p=quarantine;pct=100;rua=mailto:report@dmarc.amazon.com;ruf=mailto:report@dmarc.amazon.com
MX RFC 5321 Synchronized 1 / 1 records
5 amazon-smtp.amazon.com.
5 amazon-smtp.amazon.com.
NS RFC 1035 Synchronized 8 / 8 records
ns2.amzndns.co.uk.
ns1.amzndns.co.uk.
ns1.amzndns.net.
ns1.amzndns.com.
ns1.amzndns.org.
ns1.amzndns.net.
ns1.amzndns.co.uk.
ns1.amzndns.org.
ns2.amzndns.net.
ns2.amzndns.co.uk.
ns1.amzndns.com.
ns2.amzndns.com.
ns2.amzndns.com.
ns2.amzndns.net.
ns2.amzndns.org.
ns2.amzndns.org.
SOA RFC 1035 Synchronized 1 / 1 records
dns-external-master.amazon.com. hostmaster.amazon.com. 2010197799 180 60 604800 900
dns-external-master.amazon.com. hostmaster.amazon.com. 2010197799 180 60 604800 900
TXT RFC 7208 §4 Propagating 57 / 1 records
uber-domain-verification=01e9f567-7b84-45dd-9326-53992a028b40
TS1760027
wrike-verification=MzI3NzM2ODo2NDk5MjE4NjQ2MWJmOTEwMGMxM2MzNzJmNWJlY2U5ZDU4MmVlNzQ2NWU4MTY5OWJjMjlmYjQ4Mjc5M2JiMzky
—
sending_domain608861=81b0d52095dae60d604e7cbea5e58e1d842f7d950d6673a43feae339b664ca31
—
spf2.0/pra include:spf1.amazon.com include:spf2.amazon.com include:amazonses.com -all
—
box-domain-verification=ffea95cd0e0d61c302198367155b07e74fd534fa1d867662dc9bf9969b6f535d
—
stripe-verification=45f746e3b195198f419af3f685fdf217532ce552b4b47070b3caefe325559a67
—
autodesk-domain-verification=dmryiygGOGBJFJFVo5Bl
—
stripe-verification=a27edc0da55836ea6bb7eac592bf2ca8e246eb652608d54493119df7df005afc
—
canva-site-verification=Hksh9WEUPWP13_SEU1mPMA
—
sending_domain1003771=199bc63a54ace5d8d5c5d08286af86d7049b4afacb5ef7decd6b22cf9e8d5efb
—
stripe-verification=65883709F0B36AB2B73FFC870338AE9F817315DDBB1CAB28910F074F4A8DE1EC
—
uber-domain-verification=5f5cc242-4dbe-4871-b726-bbbe085ff053
—
google-site-verification=NV91qEfNgqDZOPzwlhXE-KtDUfCBSNgAsdxaFebyh80
—
sending_domain949422=43d714838567583460e7720e6049505edb8e25c1ef4321419d41bc5255db7ba5
—
sending_domain197572=555e96ed2e576ced81c89f7001740cb72f9c66aeb136d0d05734aad625766bc1
—
stripe-verification=35A865E5A20C09CD0288F87ACA29DE73FF8A704D21F7310A5AAFF4CB63062E81
—
stripe-verification=C7ABA7B41F5AC26E3C397015A34CD46ACD2130DC8DAAFA7F59AAEFEDBC3FA517
—
sending_domain608861=d33a88e8540c33a1217138cf8a25879734bd35673bb7cfbd639f95c550b33ec4
—
pardot326621=b26a7b44d7c73d119ef9dfd1a24d93c77d583ac50ba4ecedd899a9134734403b
—
pendo-domain-verification=ecbe1a51-954d-4202-ab86-d15e04b96769
—
apple-domain-verification=dVkKZnu17XS0EN2X
—
TS1760027
—
stripe-verification=a5c01aa4d732f4b93154d67983d77982ef1a2db73fecfd4bcd64e224d3ab4075
—
MS=4B600B22799EB2CAC0D8FF0A3A3CAECA5EE2BF3A
—
google-site-verification=G_-mXb0ZYjjGkQVGjpOOB2deSOaVdxVj4i4vozJTREs
—
stripe-verification=8E217BE0FF12B50596BD78EEA3F81E62C6C7A2AC78FBD46DAD95B7D21BA2F8BF
—
sending_domain949422=99a7b44052aefc4dec2abf56189160824664d2fdac00ca962f4455be62b51d56
—
00DcX000002xu6h=1TBcX00000000Xt
—
liveramp-site-verification=jZJKgMEQ_1mdjMhKj02iqNACZ-NJHRWhCEQdQ_OuCMo
—
stripe-verification=76924B623B7105057C67D4F5EAE19F65EE8BD92635581BCACA2CCACA4D38FE1B
—
docker-verification=1779f74e-699a-4d8b-acdc-ce242d73559f
—
uber-domain-verification=0ddb4c64-175c-4e7a-8a7a-f552034222e8
—
neat-pulse-domain-verification-QgvLWLN=f37f2998-0bb3-493b-a3aa-c4ff8f3dce08
—
apple-domain-verification=_j3fIZD8uuYetbG64YKTEpz-8mwyvYrLRqM5CoVZVTk
—
stripe-verification=79C640ED20153B836A623F16A3DCF65E2072948FB80C42D19300514DADF94EC5
—
google-site-verification=14WGW2MdNMxchG8PlinF7LgqqE0OwwHqOq0HKhb7rDQ
—
cisco-ci-domain-verification=1b256bd11daa486ba2fa405d2d5de70f75feb6757dd8993ca8de685a7dfea1df
—
v=spf1 include:spf1.amazon.com include:spf2.amazon.com include:amazonses.com -all
—
stripe-verification=1D421397AAEC571CCBD9F25DDC90F00EDEBC3E74F4047270EC9A13B784579E34
—
sending_domain1003771=f1303d8ee3b86e39db2703b11feb83e1e8b712a9ffc64c3d56505192e5b3bf4f
—
brevo-code:9be7f7c39958d253a31de6593fa831bc
—
uber-domain-verification=7a35217f-6956-41a0-be5c-a28ea2646964
—
google-site-verification=D0RwRb_QApkpApKTFaFlRwbm_yrkey0uokKw0wQUIdk
—
stripe-verification=26EFABF97D624D7F4F3C062366A04C4B1399841F23F275DD81E58D00A981979C
—
sending_domain229492=341509a116ea4311fcb2e489303bf09a139b10ce9b90e5029d2677055cb4dc89
—
facebook-domain-verification=d9u57u52gylohx845ogo1axzpywpmq
—
dell-technologies-domain-verification=amazon.com_2dc4b285-482d-4948-bf92-16e698f2cab9_1738858526
—
ZOOM_verify_ARI4AiKALCcjulAUZNwR8S
—
apple-domain-verification=4wbNaeWvAH0pU1yi
—
lucidlink-verification=QG752KJ3CMZAZTZ3ERMX1AXMCG
—
canva-site-verification=WhUvTbfe6tUQWmIXnQifGA
—
stripe-verification=B0AD8DC1918B8A717E5B6A29C2E04594A9872AB05F8DA24CB762BBA0A0487BC6
—
stripe-verification=6a5d107aa37465eac2101bb1c725b02072689a4fa7bd38b455970baac4979a17
—
sending_domain229492=7cde83fbc5246557c64d9d9ba79f0d11f7ba9eb6127f60451a9aa6f8dead4381
—
atlassian-domain-verification=ZT4AapXgobCpXIWoNcd7gtMjZyOUdr4EDFMnFUWrqqqgdaQVbDvoGpRaIwj/tgPH
—
sending_domain1014172=003846595520e80ec84e8cc47c07e3a71afb855fc743bb92cdec93f88c7a4029
—
ZOOM_verify_6OUC1znUonKMCoyMMGyFfX
—
DNS History Timeline BETA
Your key is sent directly to SecurityTrails and is never stored on our servers. Get an API key
DNS History Timeline BETA

When was a record added, removed, or changed — and could that change be the problem?

Analyze Another Domain

Confirm Your Email Configuration

This tool analyzes DNS records, but to verify actual email delivery, send a test email to Red Sift Investigate. Their tool shows exactly how your emails arrive, including SPF/DKIM/DMARC pass/fail results in the headers.

DATA FRESHNESS & METHODOLOGY

All security-critical records (SPF, DMARC, DKIM, DANE/TLSA, DNSSEC, MTA-STS, TLS-RPT, BIMI, CAA) are queried live from authoritative nameservers and cross-referenced against 5 independent public DNS resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) at the time of each analysis. No security verdict uses cached data.

Registrar data (RDAP) is cached for up to 24 hours because domain ownership and registration details change infrequently. Certificate Transparency logs (subdomain discovery via RFC 6962) are cached for 1 hour because CT entries are append-only historical records. Sections using cached data are marked with a CACHED badge; live queries show LIVE.

Subdomain curation: 862 subdomains were discovered — the most security-relevant are displayed, prioritized by: well-known service names (mail, vpn, api, sso, admin, etc.), DNS-resolving hosts, and subdomains with the most certificate activity. CNAME chain resolution and provider identification run on the curated set for accuracy. The complete list is available via CSV export.

Intelligence Sources

This analysis used 4 DNS resolvers (consensus), reverse DNS (PTR), Team Cymru (ASN attribution), IANA RDAP (registrar), crt.sh (CT logs), and SMTP probing (transport). All using open-standard protocols.

Full List
Verify Report Integrity SHA-3-512 Has this report been altered since generation? Verify below

This cryptographic hash seals the analysis data, domain, timestamp, and tool version into a tamper-evident fingerprint. Any modification to the report data will produce a different hash. This is distinct from the posture hash (used for drift detection) — the integrity hash uniquely identifies this specific report instance.

a4bcd9f0a32c99dfa4ef494f76bfe135df9fefcfe821097374f48ff41e958d9a4d9dae32001b6fdc07894e478c22086e8217c5817d8d491f66a79377a5e2ab32
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 18 Feb 2026, 11:29 UTC.
Download Raw Intelligence Download Checksum (.sha3)

Download the intelligence dump and verify its integrity, like you would a Kali ISO or any critical artifact. The SHA-3-512 checksum covers every byte of the download — deterministic serialization ensures identical hashes across downloads.

After downloading, verify with any of these commands:

Tip: cd ~/Downloads first (or wherever you saved the files).

OpenSSL + Sidecar (macOS, Linux, WSL) 
cat dns-intelligence-amazon.com.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-amazon.com.json
Python 3 (cross-platform) 
python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-amazon.com.json','rb').read()).hexdigest())"
sha3sum (coreutils 9+) 
sha3sum -a 512 dns-intelligence-amazon.com.json
Compare the output against the .sha3 file or the checksum API at /api/analysis/2114/checksum. Hash algorithm: SHA-3-512 (Keccak, NIST FIPS 202).

Every finding in this report is backed by DNS queries you can run yourself. These vetted one-liners reproduce the exact checks used to build this report for amazon.com. Our analysis adds multi-resolver consensus, RFC-based evaluation, and cross-referencing — but the underlying data is always independently verifiable. We are intelligence analysts, not gatekeepers.

DNS Records

Query A records (IPv4) RFC 1035 
dig +noall +answer amazon.com A
Query AAAA records (IPv6) RFC 1035 
dig +noall +answer amazon.com AAAA
Query MX records (mail servers) RFC 1035 
dig +noall +answer amazon.com MX
Query NS records (nameservers) RFC 1035 
dig +noall +answer amazon.com NS
Query TXT records RFC 1035 
dig +noall +answer amazon.com TXT

Email Authentication

Check SPF record RFC 7208 
dig +short amazon.com TXT | grep -i spf
Check DMARC policy RFC 7489 
dig +short _dmarc.amazon.com TXT
Check DKIM key for selector 'zendesk1' RFC 6376 
dig +short zendesk1._domainkey.amazon.com TXT
Check DKIM key for selector 'zendesk2' RFC 6376 
dig +short zendesk2._domainkey.amazon.com TXT

Domain Security

Check DNSSEC DNSKEY records RFC 4035 
dig +dnssec +noall +answer amazon.com DNSKEY
Check DNSSEC DS records RFC 4035 
dig +noall +answer amazon.com DS
Validate DNSSEC chain (requires DNSSEC-validating resolver) RFC 4035 
dig +dnssec +cd amazon.com A @1.1.1.1

Transport Security

Check TLSA record for amazon-smtp.amazon.com RFC 7672 
dig +noall +answer _25._tcp.amazon-smtp.amazon.com TLSA
Verify TLS certificate on primary MX (amazon-smtp.amazon.com) RFC 6698 
openssl s_client -starttls smtp -connect amazon-smtp.amazon.com:25 -servername amazon-smtp.amazon.com 2>/dev/null | openssl x509 -noout -subject -dates
Check MTA-STS DNS record RFC 8461 
dig +short _mta-sts.amazon.com TXT
Fetch MTA-STS policy file RFC 8461 
curl -sL https://mta-sts.amazon.com/.well-known/mta-sts.txt
Check TLS-RPT record RFC 8460 
dig +short _smtp._tls.amazon.com TXT

Brand & Trust

Check BIMI record BIMI Draft 
dig +short default._bimi.amazon.com TXT
Check CAA records (certificate authority authorization) RFC 8659 
dig +noall +answer amazon.com CAA

DNS Records

Check HTTPS/SVCB records RFC 9460 
dig +noall +answer amazon.com HTTPS

Domain Security

Check CDS/CDNSKEY automation records RFC 7344 
dig +noall +answer amazon.com CDS

Infrastructure Intelligence

RDAP domain registration lookup RFC 9083 
curl -sL 'https://rdap.org/domain/amazon.com' | python3 -m json.tool | head -50

Transport Security

Test STARTTLS on primary MX (amazon-smtp.amazon.com) RFC 3207 
openssl s_client -starttls smtp -connect amazon-smtp.amazon.com:25 -servername amazon-smtp.amazon.com </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

Search Certificate Transparency logs RFC 6962 
curl -s 'https://crt.sh/?q=%25.amazon.com&output=json' | python3 -c "import json,sys; [print(e['name_value']) for e in json.load(sys.stdin)]" | sort -u | head -20
Check security.txt RFC 9116 
curl -sL https://amazon.com/.well-known/security.txt | head -20

AI Surface

Check for llms.txt 
curl -sI https://amazon.com/llms.txt | head -5
Check robots.txt for AI crawler rules 
curl -s https://amazon.com/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'

Infrastructure Intelligence

ASN lookup for 98.82.161.185 (Team Cymru) 
dig +short 185.161.82.98.origin.asn.cymru.com TXT
ASN lookup for 98.87.170.71 (Team Cymru) 
dig +short 71.170.87.98.origin.asn.cymru.com TXT
Commands use dig, openssl, and curl — standard tools available on macOS, Linux, and WSL. Results may vary slightly due to DNS propagation timing and resolver caching.
Intelligence Confidence Audit Engine Verified · 9/9 Evaluated
How confident are these results? Each protocol is independently verified against RFC standards. No self-awarded badges.
SPF
Verified 4849 runs
DKIM
Verified 4668 runs
DMARC
Verified 4833 runs
DANE/TLSA
Verified 4652 runs
DNSSEC
Verified 4830 runs
BIMI
Verified 4667 runs
MTA-STS
Verified 4670 runs
TLS-RPT
Verified 4672 runs
CAA
Verified 4664 runs
Maturity: Development → Verified → Consistent → Gold → Gold Master

Appendix: Verification Commands

The core DNS queries behind this report can be independently verified using these standard terminal commands (dig, openssl, curl). DNS Tool adds multi-resolver consensus, RFC-based evaluation, and cross-referencing on top of the raw data shown here.

DNS Records

Query A records (IPv4) (RFC 1035) 
dig +noall +answer amazon.com A
Query AAAA records (IPv6) (RFC 1035) 
dig +noall +answer amazon.com AAAA
Query MX records (mail servers) (RFC 1035) 
dig +noall +answer amazon.com MX
Query NS records (nameservers) (RFC 1035) 
dig +noall +answer amazon.com NS
Query TXT records (RFC 1035) 
dig +noall +answer amazon.com TXT

Email Authentication

Check SPF record (RFC 7208) 
dig +short amazon.com TXT | grep -i spf
Check DMARC policy (RFC 7489) 
dig +short _dmarc.amazon.com TXT
Check DKIM key for selector 'zendesk1' (RFC 6376) 
dig +short zendesk1._domainkey.amazon.com TXT
Check DKIM key for selector 'zendesk2' (RFC 6376) 
dig +short zendesk2._domainkey.amazon.com TXT

Domain Security

Check DNSSEC DNSKEY records (RFC 4035) 
dig +dnssec +noall +answer amazon.com DNSKEY
Check DNSSEC DS records (RFC 4035) 
dig +noall +answer amazon.com DS
Validate DNSSEC chain (requires DNSSEC-validating resolver) (RFC 4035) 
dig +dnssec +cd amazon.com A @1.1.1.1

Transport Security

Check TLSA record for amazon-smtp.amazon.com (RFC 7672) 
dig +noall +answer _25._tcp.amazon-smtp.amazon.com TLSA
Verify TLS certificate on primary MX (amazon-smtp.amazon.com) (RFC 6698) 
openssl s_client -starttls smtp -connect amazon-smtp.amazon.com:25 -servername amazon-smtp.amazon.com 2>/dev/null | openssl x509 -noout -subject -dates
Check MTA-STS DNS record (RFC 8461) 
dig +short _mta-sts.amazon.com TXT
Fetch MTA-STS policy file (RFC 8461) 
curl -sL https://mta-sts.amazon.com/.well-known/mta-sts.txt
Check TLS-RPT record (RFC 8460) 
dig +short _smtp._tls.amazon.com TXT

Brand & Trust

Check BIMI record (BIMI Draft) 
dig +short default._bimi.amazon.com TXT
Check CAA records (certificate authority authorization) (RFC 8659) 
dig +noall +answer amazon.com CAA

DNS Records

Check HTTPS/SVCB records (RFC 9460) 
dig +noall +answer amazon.com HTTPS

Domain Security

Check CDS/CDNSKEY automation records (RFC 7344) 
dig +noall +answer amazon.com CDS

Infrastructure Intelligence

RDAP domain registration lookup (RFC 9083) 
curl -sL 'https://rdap.org/domain/amazon.com' | python3 -m json.tool | head -50

Transport Security

Test STARTTLS on primary MX (amazon-smtp.amazon.com) (RFC 3207) 
openssl s_client -starttls smtp -connect amazon-smtp.amazon.com:25 -servername amazon-smtp.amazon.com </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

Search Certificate Transparency logs (RFC 6962) 
curl -s 'https://crt.sh/?q=%25.amazon.com&output=json' | python3 -c "import json,sys; [print(e['name_value']) for e in json.load(sys.stdin)]" | sort -u | head -20
Check security.txt (RFC 9116) 
curl -sL https://amazon.com/.well-known/security.txt | head -20

AI Surface

Check for llms.txt 
curl -sI https://amazon.com/llms.txt | head -5
Check robots.txt for AI crawler rules 
curl -s https://amazon.com/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'

Infrastructure Intelligence

ASN lookup for 98.82.161.185 (Team Cymru) 
dig +short 185.161.82.98.origin.asn.cymru.com TXT
ASN lookup for 98.87.170.71 (Team Cymru) 
dig +short 71.170.87.98.origin.asn.cymru.com TXT
Running Multi-Source Intelligence Audit

amazon.com

0s
DNS records — Cloudflare, Google, Quad9, OpenDNS, DNS4EU
Email auth — SPF, DMARC, DKIM selectors
DNSSEC chain of trust & DANE/TLSA
Certificate Transparency & subdomain discovery
SMTP transport & STARTTLS verification
MTA-STS, TLS-RPT, BIMI, CAA
Registrar & infrastructure analysis
Intelligence Classification & Interpretation

Every result includes terminal commands you can run to independently verify the underlying data. No proprietary magic.