Skip to main content
DNS Tool
Engineer's DNS Intelligence Report
Generated 19 Apr 2026, 15:43 UTC
Duration 19.0s
Version v26.46.21
Integrity ac08e3bb3a83154352f012ab40fd3ed3289c7070b3da40d5dc8b6cb3cd770c326d394dd7484da8f081a464c898ec30823aeac46e1e7010bec73b28bc991c1076
Subject Domain
spacex.com

Engineer's DNS Intelligence Report

spacex.com
19 Apr 2026, 15:43 UTC · 19.0s ·v26.46.21 · SHA-3-512: ac08✱✱✱✱ Verify ·Cross-Referenced
Executive Topology
Recon Mode Snapshot Re-analyze New Domain
Footprint Proofpoint 8 SaaS Services
DNS Security & Trust Posture
Risk Level: Low Risk
4 protocols configured, 4 not configured, 1 unavailable on provider Why we go beyond letter grades
Resolver agreement is inconsistent for some protocols, limiting confidence. Data currency and system maturity are adequate.
Accuracy 63% Currency 73/100 Maturity consistent
Limiting factor: Resolver agreement is low for this scan — some protocols returned inconsistent results across resolvers
Currentness Excellent TTL Compliance Excellent Completeness Degraded Source Credibility Excellent TTL Relevance Stale
ICuAE Details
DNS data shows some aging or gaps — consider re-scanning for critical decisions
Enterprise Traffic Engineering Detected DNS-based Global Server Load Balancing (GSLB)

This domain uses short TTLs across 4 record types (A record at 30s), consistent with DNS-based traffic management (GSLB). Enterprises operating large anycast networks intentionally use short TTLs to enable rapid failover, geographic steering, and load distribution. This is a deliberate infrastructure choice, not a misconfiguration. RFC 1035 §3.2.1 permits any TTL value the zone administrator selects. The findings below reflect deviation from typical values for reference, not necessarily actionable recommendations for this class of infrastructure.

The following DNS record TTLs deviate from typical values. For domains using DNS-based traffic management, short TTLs are expected and intentional.

Record Type Observed TTL Typical TTL Severity Context
AAAA 30s 1 hour (3600s) high AAAA TTL is below typical — observed 30s, typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
TXT 1s 1 hour (3600s) high TXT TTL is below typical — observed 1s, typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
SOA 6 hours (21600s) 1 hour (3600s) high SOA TTL is above typical — observed 6 hours (21600s), typical value is 1 hour (3600s). Long TTLs reduce DNS query volume but slow propagation when records change. Consider 3600 seconds for a balance of performance and flexibility per NIST SP 800-53 SI-7 relevance guidance.
NS 21252s 1 day (86400s) medium NS TTL is below typical — observed 21252s, typical value is 1 day (86400s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 86400 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
MX 30s 1 hour (3600s) high MX TTL is below typical — observed 30s, typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
A 30s 1 hour (3600s) high A TTL is below typical — observed 30s, typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.

Big Picture Questions

  • This domain runs short TTLs across multiple record types. Does it operate a global anycast network where DNS-based traffic steering justifies the query volume?
  • Are the short TTLs enabling active failover, geographic routing, or load distribution — or are they leftover from a migration that was never reverted?
  • Enterprise-grade DNS infrastructure (sub-5ms authoritative response times, globally distributed nameservers) absorbs short-TTL query volume. Would your authoritative DNS handle the same load?
Tune TTL for spacex.com
Reference: NIST SP 800-53 SI-7 (Information Integrity) · RFC 8767 (Serve Stale) · RFC 1035 §3.2.1 (TTL semantics) DNS provider detected: Google Cloud DNS — provider-specific RFC compliance notes are shown inline above where applicable.
Primary NS ns-cloud-b1.googledomains.com
Serial 1
Admin cloud-dns-hostmaster.google.com
Provider Google Cloud DNS
Timer Value RFC 1912 Range
Refresh21600s1,200–43,200s (20 min – 12 hrs)
Retry3600sFraction of Refresh
Expire259200s1,209,600–2,419,200s (14–28 days)
Minimum (Neg. Cache)300s300–86,400s (5 min – 1 day)
Expire: SOA Expire is 3 days (259200s). RFC 1912 §2.2 recommends 1,209,600–2,419,200 seconds (14–28 days). If the primary nameserver becomes unreachable, secondary nameservers will stop serving this zone after only 3 days (259200s).
RFC 1912 §2.2
Suggested Scanner Configuration High Confidence
Based on 12 historical scans of this domain
Parameter Current Suggested Severity Rationale
timeout_seconds 5s 8s low Average scan duration is 31.0s, suggesting DNS responses are slow for this domain. Increasing timeout from 5s to 8s prevents premature resolution failures.
RFC 8767
Suggestions require explicit approval before applying. No automatic changes will be made.
Email Spoofing
Protected
Brand Impersonation
Not Setup
DNS Tampering
Unsigned
Certificate Control
Configured
Configured
SPF (hard fail), DMARC (reject), DKIM, CAA
Not Configured
MTA-STS, TLS-RPT, BIMI, DNSSEC
Unavailable on Provider
DANE
Priority Actions 4 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
Low Add BIMI Record

Your domain has DMARC reject — you qualify for BIMI, which displays your brand logo in receiving email clients that support it (Gmail, Apple Mail, Yahoo).

BIMI displays your verified brand logo next to your emails in supporting mail clients.
TypeTXT
Hostdefault._bimi.spacex.com (BIMI default record)
Valuev=BIMI1; l=https://spacex.com/brand/logo.svg
RFC 9495
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.spacex.com (SMTP TLS reporting record)
Valuev=TLSRPTv1; rua=mailto:tls-reports@spacex.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.spacex.com (MTA-STS policy record)
Valuev=STSv1; id=spacex.com
RFC 8461
Open Remediation Workspace — Copy-Paste Ready Records
Registrar (RDAP) OBSERVED LIVE
Network Solutions, LLC
Where domain was purchased
Email Service Provider INFERRED
Proofpoint
Strongly Protected
Web Hosting
Unknown
Where website is hosted
DNS Hosting OBSERVED
Google Domains
Where DNS records are edited
Email Security Methodology Can this domain be impersonated by email? No SPF and DMARC reject policy enforced

SPF Record RFC 7208 §4 Consistent

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

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

v=spf1 include:spf-a.spacex.com include:spf-b.spacex.com include:icpbounce.com include:shops.shopify.com include:_spf.qemailserver.com include:spf.mandrillapp.com include:spf.protection.office365.us include:spf-003ea501.gpphosted.com -all
RFC 7489: -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 is set to reject — enforcement is strong. However, some receivers may still reject messages on SPF hard fail before DKIM alignment is checked. Switching to ~all + p=reject would provide the same enforcement with full DMARC compatibility.

DMARC Policy RFC 7489 §6.3 Consistent

Are spoofed emails rejected or quarantined? Yes — reject policy
Success p=reject

DMARC policy reject (100%) - excellent protection

v=DMARC1; p=reject; fo=1; rua=mailto:dmarc_rua@emaildefense.proofpoint.com,mailto:re+9db8aed802f8@inbound.dmarcdigests.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com; aspf=r
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
RFC 7489 Conformant — DMARC record conforms to RFC 7489 §6.3 with full enforcement.
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 Consistent

Are outbound emails cryptographically signed? Yes — verified
Found 2048-bit

Found DKIM for 5 selector(s) with strong keys (2048-bit)

Mail routed through Proofpoint (security gateway) — DKIM signed by Microsoft 365 (sending platform). This is a standard enterprise architecture.
dkim._domainkey 2048-bit Adequate
v=DKIM1;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxecr9/3r7D1u7Vu66MnwOufy92SKntxT/zdVHxe+e7GgzJrEapsqAo6AfhIUeup54j+QAk8XM4Fq0aZJjttah7K4tShMBZRivt37fVpKJqVtMtZbifsvwh0NW+QG6M4+NqY/yK1gSkFVEswm/SPVuhozIgqVgBUhTE9Kgj13IJqkRlpf47AKxOewTzIxU8mo1IS12MwYMcG4PT6Q3VfLWuVe1CXQWYRPZuwAxo87+3ZW2J2DeAKnjlshgpM6INHz16AaXPkQtzdOufKCNYfYivY+ZmI2OyEzd7QnSdxwSxUovNzzHAuqq4gcX0QlVkjusXtybvyFxDXOlHpdfB3K/wIDAQAB
mandrill._domainkey MailChimp (Mandrill) 2048-bit Adequate
v=DKIM1;k=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB;
s1._domainkey SendGrid 2048-bit Adequate
k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4F+2fyJ7kSX9HIe3RWencxKyZpuPutqrzjDs8Cui5Pk60oFXIorzbsRY0e71Y91ohgnHQUwZpYv2bVZivfgTuCoJFBg6ipzaysHWrA3v6VY8cpjAMa2hSsLByLbNGygL6/IWqeZkdgW00pVStWA1C/gPsDHAx34ikZnvErQLj5yHKM6QMsY91qqXLgRo500jjQiJFrk7R+EgUueYJuRLveq6wZOiEoZxudU5vpftShccEvoBanokfaouzkxxHNtlG1RycF5Eq1M1ugndt9Tg4WcLu2jnYL/He3+VSkWDPDAXslUQwH3xAqcEw4yYQLzdiq1RM0y+JTGUabLKv9R6tQIDAQAB
s2._domainkey SendGrid 2048-bit Adequate
k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC8Y3RHXGz9CRYswzGv7yfuX1m8FaJwZI8avo8MTlt9O5GcZLg8dz63pmKd0AyHgehV3mJ1ZWTUpcp6tvMLwWz3DQd2c4RDCzuLA1csCpjI0ufRBqSEPm0oq8ao3Uv99UesSwd/VjaUeEhoLtkxWY1wYTiGH5Y/FFZyOO//6m3k7wIDAQAB
selector1._domainkey Microsoft 365 2048-bit Adequate
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3+nfB+q7C3RQ4z+NU/88e8vwP9qvOecl/c+T50gtyr3dAZm9Y64ds9dHuDUFAx+GwHGjNM6xP3wd0f2U3SuGjXkF+drceCdCE/SXUrihmWdqpAXU1rjAutOnZvznN4ak7MGEXV+/G2pMo5jgROgRr9NBAH3z85RPkO1+W5jvlYK/l+GoB9JDExlXrphfgNf+TUSBwCZPq3oJxmtb00SQ6ufx7prPLiBMxzEJAm5Wrq2kebaAsfKDKaPrLg01RKDiTVRuetT6+hd437cegmPHdgU1/qdZRZy4joP/qtz+E2QpNp7Jou8pqSD4qn/Fbu7azufFBfXstnkxPR0vF9tQfQIDAQAB;
RFC 6376 Conformant — DKIM keys and signatures conform to RFC 6376 §3.6 (Internet Standard).
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 Consistent

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 Consistent

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? Yes — all authorized
Success

All 2 external reporting domains properly authorized

External Domain Authorization Auth Record
emaildefense.proofpoint.com Authorized v=DMARC1;
inbound.dmarcdigests.com Authorized v=DMARC1;
DANE / TLSA Consistent Recon Methodology Can mail servers establish identity without a public CA? No
RFC 7672 §3 RFC 6698 §2 Not Available

DANE not available — Proofpoint does not support inbound DANE/TLSA on its MX infrastructure

DANE not deployable on Proofpoint

Proofpoint is a security gateway with shared MX infrastructure. It does not publish per-customer TLSA records.

Recommended alternative: MTA-STS

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. Since Proofpoint does not support inbound DANE, deploy MTA-STS (RFC 8461) to enforce TLS and protect against downgrade attacks.

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? Possible DMARC reject policy blocks email spoofing (RFC 7489 §6.3) and CAA restricts certificate issuance (RFC 8659 §4), but no BIMI brand verification — lookalike domains display identically in inboxes without visual proof of authenticity

BIMI BIMI Spec Consistent Warning

Is the brand identity verified and displayed in inboxes? No

No BIMI record found

CAA RFC 8659 §4 Consistent Success

Does this domain restrict who can issue TLS certificates? Yes

CAA configured - only Amazon, DigiCert, Let's Encrypt, GlobalSign can issue certificates

Authorized CAs: Amazon DigiCert Let's Encrypt GlobalSign
0 issue "amazon.com"
0 issue "digicert.com"
0 issue "letsencrypt.org"
0 issue "globalsign.com"
Since September 2025, all public CAs must verify domain control from multiple geographic locations (Multi-Perspective Issuance Corroboration, CA/B Forum Ballot SC-067). CAA records are now checked from multiple network perspectives before certificate issuance.
Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? Partial RFC 9116

security.txt found with issues

Contact

mailto:security@spacex.com

Expires

Missing (required by RFC 9116 §2.5.5)

Encryption

https://www.spacex.com/.well-known/publickey.txt
Hiring
Source: https://spacex.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 significant AI surface findings

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? No directives
No robots.txt found
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
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.
Sources scanned (6)
  • https://spacex.com/
  • https://spacex.com/environment.js
  • https://spacex.com/runtime.a38bd32aaabb03e4.js
  • https://spacex.com/polyfills.08b6611321d68f0c.js
  • https://spacex.com/vendor.ca6bf32c26e75d4a.js
  • https://spacex.com/main.9dd4195f58d5d129.js
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.

DNS Server Security Hardened

No DNS server misconfigurations found on ns-cloud-b3.googledomains.com — Nmap NSE probes for zone transfer (AXFR), open recursion (RFC 5358), nameserver identity disclosure, and DNS cache snooping.

Check Result Detail
Zone Transfer (AXFR) Denied Test inconclusive
Open Recursion Disabled Test inconclusive
Nameserver Identity Hidden Test inconclusive
Cache Snooping Protected Test inconclusive

Tested nameservers: ns-cloud-b3.googledomains.com, ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b4.googledomains.com

Delegation Consistency 1 Issue

Delegation consistency: 1 issue(s) found — Parent/child NS delegation alignment: DS↔DNSKEY, glue records, TTL drift, SOA serial sync.

Findings:
  • Could not retrieve NS TTL from parent zone

DS ↔ DNSKEY Alignment Aligned

Glue Record Completeness Complete

NameserverIn-BailiwickIPv4 GlueIPv6 GlueStatus
ns-cloud-b1.googledomains.com No N/A N/A OK
ns-cloud-b2.googledomains.com No N/A N/A OK
ns-cloud-b3.googledomains.com No N/A N/A OK
ns-cloud-b4.googledomains.com No N/A N/A OK

NS TTL Comparison Drift

Child TTL: 21600s Drift: 0s

SOA Serial Consistency Consistent

ns-cloud-b1.googledomains.com: 1
ns-cloud-b2.googledomains.com: 1
ns-cloud-b3.googledomains.com: 1
ns-cloud-b4.googledomains.com: 1
Nameserver Fleet Matrix Healthy

Analyzed 4 nameserver(s) for spacex.com — Per-nameserver reachability, ASN diversity, SOA serial sync, and lame delegation checks.

Nameserver IPv4 IPv6 ASN / Operator UDP TCP AA SOA Serial
ns-cloud-b1.googledomains.com 216.239.32.107 2001:4860:4802:32::6b AS15169
Google LLC 		1
ns-cloud-b4.googledomains.com 216.239.38.107 2001:4860:4802:38::6b AS15169
Google LLC 		1
ns-cloud-b3.googledomains.com 216.239.36.107 2001:4860:4802:36::6b AS15169
Google LLC 		1
ns-cloud-b2.googledomains.com 216.239.34.107 2001:4860:4802:34::6b AS15169
Google LLC 		1
Unique ASNs
1
Unique Operators
1
Unique /24 Prefixes
4
Diversity Score
Fair

1 ASN(s), 4 /24 prefix(es) — consider adding diversity

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

All 2 server(s) verified: encrypted transport confirmed via direct SMTP probe and DNS policy

Policy Assessment Primary
  • Proofpoint enforces TLS on managed mail transport
Telemetry
TLS-RPT not configured — domain has no visibility into TLS delivery failures from real senders
Live Probe Supplementary
MX Host STARTTLS TLS Version Cipher Certificate
mxa-003ea501.gslb.gpphosted.com TLSv1.2 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Valid
Expires: 2026-12-10 (235 days)
Issuer: Sectigo Limited
mxb-003ea501.gslb.gpphosted.com TLSv1.2 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Valid
Expires: 2026-12-10 (235 days)
Issuer: Sectigo Limited
Multi-Vantage Probe Results
Unanimous: TLS verified 2 probes, 1 responded
US-East (Boston) observed
All servers support TLS
France - EU skipped
Infrastructure Intelligence Who hosts this domain and what services power it? Direct

ASN / Network Success

Resolved 1 unique ASN(s) across 4 IP address(es)

ASNNameCountry
AS13335 Cloudflare, Inc. US
IPv4 Mappings:
104.18.26.217 → AS13335 (104.18.16.0/20)
104.18.27.217 → AS13335 (104.18.16.0/20)
IPv6 Mappings:
2606:4700::6812:1ad9 → AS13335 (2606:4700::/44)
2606:4700::6812:1bd9 → AS13335 (2606:4700::/44)

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
Microsoft 365 MS=ms70688094
Adobe adobe-idp-site-verification=97fe9cbe45f7936353e717f88486fcad77d04e2cc65312bbf40d...
Apple apple-domain-verification=CU99PbnQj7UXnmWi
Atlassian atlassian-domain-verification=ppDBYYiz7xEIHo3t4qYTnznDkQkbtHi1WeWw9eyuRwqsdDXQHS...
Canva canva-site-verification=UxpT4tgSgT1xAINsHsHGKg
Cisco Umbrella cisco-ci-domain-verification=236aab1dcf7007f2b6c9e8f16e541b4dadc3be19ca2f88c034d...
Google Workspace google-site-verification=HEGwcQwzYMM_y6dwOMoyKNtRi1Fnq4ogrhx9G8aJ5FU
Stripe stripe-verification=1C2B00FD0AF495B8CCC0CB8F533A38544C0199B7A83F306D3D0F63F45AAE...
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 Consistent Unsigned

DNSSEC not configured - DNS responses are unsigned

Enterprise DNS Context: DNSSEC is the only standardized, DNS-verifiable mechanism that cryptographically authenticates responses between authoritative servers and resolvers (RFC 4033 §2, RFC 4035). Without it, DNS responses are technically vulnerable to in-transit tampering. Enterprise operators may employ compensating controls (anycast, DDoS mitigation, private peering, TSIG) — however, these do not provide DNS-layer data authentication to third-party resolvers and are not verifiable via DNS alone.
Visibility: DNS-only — network-layer compensating controls cannot be observed or verified through DNS queries. This assessment reflects what is provable from the DNS evidence available.

NS Delegation Verified

4 nameserver(s) configured

Nameservers: ns-cloud-b1.googledomains.com ns-cloud-b2.googledomains.com ns-cloud-b3.googledomains.com ns-cloud-b4.googledomains.com
Managed DNS
All 4 nameservers hosted by Google Domains. Managed DNS provides reliable resolution with provider-maintained infrastructure.
DNS provider(s): Google Domains
Multi-Resolver Verification Recon: Discrepancy detected - Some resolvers returned different results (1 difference found)
Resolver Differences:
TXT: OpenDNS returned different results: [DirectFedAuthUrl=https://auth.spacex.com MS=ms70688094 apple-domain-verification=CU99PbnQj7UXnmWi autodesk-domain-verification=jOFrO72SJC9U9y0WfVv3 canva-site-verification=UxpT4tgSgT1xAINsHsHGKg fadv-verification-3a01b9945b7b4369a5d19e95d33bb880 smartsheet-gov-site-validation=5cZs1XJeR9JG8Q9MWZRln5PJ_RLjXjhj zqgtz1gl80bvk19hn02dy51gz592fhpf]
This may indicate DNS propagation in progress or geo-based DNS routing.
Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

104.18.26.217
104.18.27.217
Where the domain points for web traffic

AAAAIPv6 Address

2606:4700::6812:1ad9
2606:4700::6812:1bd9
IPv6 ready

MXMail Servers

5 mxa-003ea501.gslb.gpphosted.com.
5 mxb-003ea501.gslb.gpphosted.com.
Priority + mail server for email delivery
Proofpoint

SRVServices

_sip._tls: 100 1 443 sipdir.online.gov.skypeforbusiness.us.
_sipfederationtls._tcp: 100 1 5061 sipfed.online.gov.skypeforbusiness.us.
SIP, XMPP, or other service endpoints
Web: Reachable (2 IPv4, 2 IPv6) Mail: 2 servers Services: 2 endpoints
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 232 subdomains discovered
How did we find these?
CT logs unavailable 232 current 0 expired 14 CNAMEs Source: Certificate Transparency + DNS Intelligence
Subdomains discovered via CT logs (RFC 6962), DNS probing of common service names, and CNAME chain traversal.
Subdomain Source Status Provider / CNAME Certificates First Seen Issuer(s)
3sljjue.spacex.com CT Log Current — 1 2026-02-19T04:31:59Z
activesync.spacex.com CT Log Current — — — —
adfs.spacex.com CT Log Current spacexadfs.usgovtrafficmanager.net 1 2025-10-08T00:00:00Z
admin.dev.spacex.com CT Log Current — — — —
admin.spacex.com CT Log Current — — — —
api-rideshare.spacex.com CT Log Current — 2 2026-02-15T09:32:49Z
api.spacex.com CT Log Current — 4 2026-01-22T11:22:07Z
api.staging.spacex.com CT Log Current — 4 2026-01-19T20:02:16Z
api.weather.spacex.com CT Log Current teleport.spacex.com 3 2026-02-02T19:50:16Z
as274-gw-216.spacex.com CT Log Current — 1 2025-10-22T00:00:00Z
as274-sbc-teams.spacex.com CT Log Current — 1 2025-05-13T00:00:00Z
as4.spacex.com CT Log Current — — — —
atlas.corp.spacex.com CT Log Current — — — —
auth.spacex.com CT Log Current — 6 2026-02-11T22:00:28Z
autodiscover.spacex.com CT Log Current — 2 2025-05-07T00:00:00Z
belbcvw.spacex.com CT Log Current — — — —
borgcust.spacex.com CT Log Current — 2 2025-04-24T00:00:00Z
bower.corp.spacex.com CT Log Current — — — —
callmgr1.spacex.com CT Log Current — — — —
ch-dlp-pov.spacex.com CT Log Current — 2 2026-01-22T15:47:24Z
cheeseshop.corp.spacex.com CT Log Current — — — —
cob5goj.spacex.com CT Log Current — — — —
confluence-test.spacex.com CT Log Current — — — —
connect-corp-wired.spacex.com CT Log Current — 1 2025-05-07T00:00:00Z
connect-corp-wireless.spacex.com CT Log Current — 1 2025-05-07T00:00:00Z
connect-east.spacex.com CT Log Current — 1 2025-05-07T00:00:00Z
connect-west.spacex.com CT Log Current — 1 2025-05-07T00:00:00Z
connect.spacex.com CT Log Current — 1 2025-05-07T00:00:00Z
connect2.spacex.com CT Log Current — — — —
content.spacex.com CT Log Current — 4 2026-01-22T11:21:56Z
content.staging.spacex.com CT Log Current content.staging.spacex.com.cdn.cloudflare.net 4 2026-01-19T20:01:47Z
crl.spacex.com CT Log Current — — — —
cuma.spacex.com CT Log Current — — — —
customer.spacex.com CT Log Current — — — —
customereprocs.spacex.com CT Log Current — — — —
customervpn.spacex.com CT Log Current — — — —
dev.spacex.com CT Log Current — — — —
devicetest.spacex.com CT Log Current — — — —
dgjira.customer.spacex.com CT Log Current — — — —
dialin.spacex.com CT Log Current — — — —
djiratest.customer.spacex.com CT Log Current — — — —
ews.spacex.com CT Log Current — — — —
files.mail.spacex.com CT Log Current — 1 2025-09-09T00:00:00Z
finance.spacex.com CT Log Current — 3 2026-02-02T19:50:16Z
frontline.spacex.com CT Log Current — — — —
gauntlet-staging.spacex.com CT Log Current — 1 2026-01-10T00:00:00Z
gauntlet.spacex.com CT Log Current — 1 2026-01-08T00:00:00Z
geoevent.spacex.com CT Log Current — 2 2025-03-28T00:00:00Z
globalwarpdrive.spacex.com CT Log Current ugazwinarcp3afdapp01-arcqbxhwffcad8fy.z01.azurefd.us 2 2025-11-10T00:00:00Z
hanko-staging.spacex.com CT Log Current — 1 2026-01-09T00:00:00Z
hanko.spacex.com CT Log Current — 1 2026-01-09T00:00:00Z
heartofgold.spacex.com CT Log Current — 1 2025-09-16T00:00:00Z
heartofgold2.spacex.com CT Log Current — — — —
hermes.spacex.com CT Log Current — — — —
hr.spacex.com CT Log Current — — — —
ht-patchman.corp.spacex.com CT Log Current — — — —
ht-vm-jamf-prod1.spacex.com CT Log Current — — — —
ht-vm-jamf-prod2.spacex.com CT Log Current — — — —
htpwp1exot001.spacex.com CT Log Current — 1 2025-05-07T00:00:00Z
htpwp1exot002.spacex.com CT Log Current — 1 2025-05-07T00:00:00Z
hx.spacex.com CT Log Current — — — —
hyperion.corp.spacex.com CT Log Current — — — —
hyperspace.spacex.com CT Log Current — — — —
ingress.spacex.com CT Log Current — — — —
insidex.spacex.com CT Log Current teleport.spacex.com 3 2026-02-02T19:50:16Z
intune-ndes-test.spacex.com CT Log Current — — — —
iss-sim.spacex.com CT Log Current — 2 2026-01-27T05:35:00Z
ivpn.spacex.com CT Log Current — — — —
ivpn2.spacex.com CT Log Current — — — —
ivpn3.spacex.com CT Log Current — — — —
jamf.spacex.com CT Log Current — 1 2025-04-17T00:00:00Z
jira-test.spacex.com CT Log Current — — — —
jira.spacex.com CT Log Current — 2 2025-11-10T00:00:00Z
la600-egw.spacex.com CT Log Current — — — —
la600-sbc-teams.spacex.com CT Log Current — 1 2025-11-17T00:00:00Z
la600-vpn.spacex.com CT Log Current — — — —
la600adfs.spacex.com CT Log Current — — — —
la600auth.spacex.com CT Log Current — — — —
la600mail.spacex.com CT Log Current — 1 2025-09-09T00:00:00Z
la600send.spacex.com CT Log Current — — — —
la624-sbc-teams.spacex.com CT Log Current — 1 2025-09-23T00:00:00Z
la624-vpn.spacex.com CT Log Current — — — —
la624adfs.spacex.com CT Log Current — — — —
la624auth.spacex.com CT Log Current — — — —
la624mail.spacex.com CT Log Current — 1 2025-09-09T00:00:00Z
launch.spacex.com CT Log Current — 4 2026-01-22T11:22:07Z
launch.staging.spacex.com CT Log Current — 4 2026-01-19T20:02:16Z
legacy.spacex.com CT Log Current — — — —
live-training.spacex.com CT Log Current — 4 2026-02-02T19:50:16Z
ljngird.spacex.com CT Log Current — — — —
lync.spacex.com CT Log Current — — — —
lync2013.spacex.com CT Log Current — — — —
lyncadmin.spacex.com CT Log Current — — — —
lyncav.spacex.com CT Log Current — — — —
lyncdiscover.spacex.com CT Log Current — — — —
lyncdiscoverinternal.spacex.com CT Log Current — — — —
mail.spacex.com CT Log Current — 1 2025-09-09T00:00:00Z
mail1.spacex.com CT Log Current — — — —
mc1divar.spacex.com CT Log Current — — — —
mc1ns25.spacex.com CT Log Current — — — —
mconnect-east.spacex.com CT Log Current — 1 2025-06-03T00:00:00Z
mconnect-west.spacex.com CT Log Current — 1 2025-06-03T00:00:00Z
mconnect.spacex.com CT Log Current — 1 2025-06-03T00:00:00Z
meet.spacex.com CT Log Current — — — —
mercury.spacex.com CT Log Current — — — —
metrics.nether.spacex.com CT Log Current — 1 2026-03-07T01:13:55Z
mfatest.spacex.com CT Log Current — — — —
missionlinks-staging.spacex.com CT Log Current — — — —
mta1.spacex.com CT Log Current — — — —
mta2.spacex.com CT Log Current — — — —
mta3.spacex.com CT Log Current — — — —
mta4.spacex.com CT Log Current — — — —
mta5.spacex.com CT Log Current — — — —
mx1.spacex.com CT Log Current — 1 2026-03-03T00:00:00Z
mx2.spacex.com CT Log Current — 1 2026-03-03T00:00:00Z
mx3.spacex.com CT Log Current — 1 2026-03-03T00:00:00Z
mx4.spacex.com CT Log Current — 1 2026-03-03T00:00:00Z
mx5.spacex.com CT Log Current — 1 2026-03-03T00:00:00Z
mx6.spacex.com CT Log Current — 1 2026-03-03T00:00:00Z
netflow.spacex.com CT Log Current — — — —
nether.spacex.com CT Log Current — 8 2026-02-02T18:29:56Z
niujlvmc.spacex.com CT Log Current — 1 2026-03-16T15:41:57Z
ns1.spacex.com CT Log Current — — — —
nsfw.spacex.com CT Log Current — — — —
o1.ptr6968.spacex.com CT Log Current — — — —
oa.spacex.com CT Log Current — — — —
oab.spacex.com CT Log Current — — — —
odyssey-east.spacex.com CT Log Current — 1 2025-05-07T00:00:00Z
odyssey-west.spacex.com CT Log Current — 1 2025-05-07T00:00:00Z
odyssey.spacex.com CT Log Current — 1 2025-05-07T00:00:00Z
online-training.spacex.com CT Log Current — 4 2026-02-02T19:50:16Z
oob.spacex.com CT Log Current — 2 2025-04-24T00:00:00Z
oob2.spacex.com CT Log Current — — — —
oos.spacex.com CT Log Current — — — —
operations.spacex.com CT Log Current operations-spacex.azurefd.us 4 2026-01-22T11:22:17Z
operations.staging.spacex.com CT Log Current — 4 2026-01-19T20:02:44Z
ops-staging.spacex.com CT Log Current — 2 2025-05-16T00:00:00Z
ops.spacex.com CT Log Current — 1 2026-01-10T00:00:00Z
otto-result-stg.spacex.com CT Log Current otto-result-stg-spacexgcchigh.msappproxy.us 2 2025-05-16T00:00:00Z
otto-results.spacex.com CT Log Current — 3 2025-05-16T00:00:00Z
owa.spacex.com CT Log Current — — — —
patches.spacex.com CT Log Current — 3 2026-03-02T12:17:16Z
paw.spacex.com CT Log Current — — — —
perappvpn.spacex.com CT Log Current — — — —
portal.spacex.com CT Log Current — — — —
preview.spacex.com CT Log Current — — — —
ra.spacex.com CT Log Current — — — —
range-staging.spacex.com CT Log Current — 1 2026-01-08T00:00:00Z
range.spacex.com CT Log Current — 1 2026-01-08T00:00:00Z
returns.spacex.com CT Log Current — — — —
rideshare.spacex.com CT Log Current — 2 2026-02-15T09:32:49Z
s3.corp.spacex.com CT Log Current — — — —
safetynet.spacex.com CT Log Current — 3 2026-02-02T19:50:16Z
schematics-staging.spacex.com CT Log Current — 1 2026-01-09T00:00:00Z
schematics.spacex.com CT Log Current ugazwinarcp3afdapp01-arcqbxhwffcad8fy.z01.azurefd.us 1 2026-01-09T00:00:00Z
secure-files.spacex.com CT Log Current — 3 2026-02-02T18:39:34Z
send.spacex.com CT Log Current — — — —
sentry.corp.spacex.com CT Log Current — — — —
shop.spacex.com CT Log Current shops.myshopify.com 4 2026-01-31T09:04:07Z
shopify-shim.spacex.com CT Log Current — 1 2025-08-17T00:00:00Z
sip.spacex.com CT Log Current — — — —
skype.spacex.com CT Log Current — — — —
softwareinterview.spacex.com CT Log Current — — — —
sp.spacex.com CT Log Current — — — —
spaceport-beta.spacex.com CT Log Current — — — —
spacexstash.customer.spacex.com CT Log Current — 3 2025-05-05T00:00:00Z
spok-beta-gcp.spacex.com CT Log Current — 1 2025-12-16T00:00:00Z
spok-gcp.spacex.com CT Log Current — 1 2025-12-18T00:00:00Z
staging.spacex.com CT Log Current — 4 2026-01-19T20:01:39Z
starbase.spacex.com CT Log Current — 4 2026-01-22T11:22:27Z
starbase.staging.spacex.com CT Log Current — 4 2026-01-19T20:03:01Z
stargate.spacex.com CT Log Current — 1 2025-10-05T00:00:00Z
stargate2.spacex.com CT Log Current — 1 2025-05-20T00:00:00Z
starlink-returns-staging.spacex.com CT Log Current — 1 2026-01-09T00:00:00Z
starlink-returns.spacex.com CT Log Current — 1 2026-01-09T00:00:00Z
starshipthegame.spacex.com CT Log Current — 4 2026-01-22T11:22:35Z
starshipthegame.staging.spacex.com CT Log Current — 3 2026-01-19T20:03:20Z
stfo.spacex.com CT Log Current — — — —
supplierexchange.spacex.com CT Log Current — — — —
supplierportal.spacex.com CT Log Current — 7 2026-02-02T18:29:56Z
supplierxchange.spacex.com CT Log Current — — — —
survey.spacex.com CT Log Current — — — —
svnext.spacex.com CT Log Current — — — —
syrinx.spacex.com CT Log Current — — — —
tax-payments-staging.spacex.com CT Log Current — 1 2026-01-09T00:00:00Z
tax-payments.spacex.com CT Log Current — 1 2026-02-02T00:00:00Z
tech-test.spacex.com CT Log Current — 3 2026-02-27T20:38:36Z
telemetron.mars.spacex.com CT Log Current — 3 2026-02-02T19:50:16Z
teleport.spacex.com CT Log Current — 10 2026-01-20T12:42:23Z
test.spacex.com CT Log Current — — — —
tricaster.spacex.com CT Log Current — — — —
tyche.spacex.com CT Log Current — — — —
vault.operations.spacex.com CT Log Current vault-operations-spacex.azurefd.us 4 2026-01-22T11:22:17Z
vault.operations.staging.spacex.com CT Log Current — 4 2026-01-19T20:02:44Z
videoingest.spacex.com CT Log Current — — — —
voyager.spacex.com CT Log Current teleport.spacex.com 2 2026-02-18T01:50:33Z
vpn-test.spacex.com CT Log Current — — — —
vpn.spacex.com CT Log Current — — — —
vpn1.spacex.com CT Log Current — — — —
vpn2.spacex.com CT Log Current — — — —
vpna.spacex.com CT Log Current — — — —
vpnb.spacex.com CT Log Current — — — —
vpntest.spacex.com CT Log Current — — — —
wac.spacex.com CT Log Current — — — —
warpdrive-customer.spacex.com CT Log Current — 1 2026-03-04T00:00:00Z
warpdrive.spacex.com CT Log Current — 2 2026-02-27T21:26:38Z
weather.spacex.com CT Log Current — 4 2026-01-10T00:00:00Z
webconf.spacex.com CT Log Current — — — —
www.adfs.spacex.com CT Log Current — — — —
www.auth.spacex.com CT Log Current — — — —
www.bower.corp.spacex.com CT Log Current — — — —
www.connect.spacex.com CT Log Current — — — —
www.connect2.spacex.com CT Log Current — — — —
www.dev.spacex.com CT Log Current — — — —
www.ht-patchman.corp.spacex.com CT Log Current — — — —
www.hyperion.corp.spacex.com CT Log Current — — — —
www.hyperspace.spacex.com CT Log Current — — — —
www.jamf.spacex.com CT Log Current — 1 2025-04-17T00:00:00Z
www.la600-egw.spacex.com CT Log Current — — — —
www.la600-sbc-teams.spacex.com CT Log Current — — — —
www.mconnect.spacex.com CT Log Current — 1 2025-06-03T00:00:00Z
www.mfatest.spacex.com CT Log Current — — — —
www.send.spacex.com CT Log Current — — — —
www.sentry.corp.spacex.com CT Log Current — — — —
www.spaceport-beta.spacex.com CT Log Current — — — —
www.spacex.com CT Log Current www.spacex.com.cdn.cloudflare.net 4 2026-01-22T11:21:45Z
www.spok-beta-gcp.spacex.com CT Log Current — 1 2025-12-16T00:00:00Z
www.spok-gcp.spacex.com CT Log Current — 1 2025-12-18T00:00:00Z
www.staging.spacex.com CT Log Current www.staging.spacex.com.cdn.cloudflare.net 4 2026-01-19T20:01:39Z
www.stargate.spacex.com CT Log Current — 1 2025-10-05T00:00:00Z
www.supplierportal.spacex.com CT Log Current — — — —
www2.spacex.com CT Log Current ec2-35-168-45-209.compute-1.amazonaws.com 1 2025-05-13T00:00:00Z
Export 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 2 / 2 records
104.18.26.217
104.18.27.217
104.18.27.217
104.18.26.217
AAAA Synchronized 2 / 2 records
2606:4700::6812:1ad9
2606:4700::6812:1ad9
2606:4700::6812:1bd9
2606:4700::6812:1bd9
CAA RFC 8659 §4 Synchronized 4 / 4 records
0 issue "digicert.com"
0 issue "globalsign.com"
0 issue "amazon.com"
0 issue "amazon.com"
0 issue "letsencrypt.org"
0 issue "digicert.com"
0 issue "globalsign.com"
0 issue "letsencrypt.org"
DMARC _dmarc.spacex.com RFC 7489 §6.3 Synchronized 1 / 1 records
v=DMARC1; p=reject; fo=1; rua=mailto:dmarc_rua@emaildefense.proofpoint.com,mailto:re+9db8aed802f8@inbound.dmarcdigests.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com; aspf=r
v=DMARC1; p=reject; fo=1; rua=mailto:dmarc_rua@emaildefense.proofpoint.com,mailto:re+9db8aed802f8@inbound.dmarcdigests.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com; aspf=r
MX RFC 5321 Synchronized 2 / 2 records
5 mxa-003ea501.gslb.gpphosted.com.
5 mxb-003ea501.gslb.gpphosted.com.
5 mxb-003ea501.gslb.gpphosted.com.
5 mxa-003ea501.gslb.gpphosted.com.
NS RFC 1035 Synchronized 4 / 4 records
ns-cloud-b1.googledomains.com.
ns-cloud-b1.googledomains.com.
ns-cloud-b2.googledomains.com.
ns-cloud-b4.googledomains.com.
ns-cloud-b3.googledomains.com.
ns-cloud-b2.googledomains.com.
ns-cloud-b4.googledomains.com.
ns-cloud-b3.googledomains.com.
SOA RFC 1035 Synchronized 1 / 1 records
ns-cloud-b1.googledomains.com. cloud-dns-hostmaster.google.com. 1 21600 3600 259200 300
ns-cloud-b1.googledomains.com. cloud-dns-hostmaster.google.com. 1 21600 3600 259200 300
TXT RFC 7208 §4 Propagating 18 / 4 records
6QDSR1iPUpF8QnDs/ERveO9hf/xVc75idTlfMNcmvbhPz95AJK5wyNWMiOfz40Ko58TqC/IFofEdm12xINJKOA==
cisco-ci-domain-verification=236aab1dcf7007f2b6c9e8f16e541b4dadc3be19ca2f88c034dc75531327cad8
7WDkmgY8hyFOAp9T8d5mA6w5Bf5DVOq8Y5BNaQmQ+iy/OY1lxkTpt1AAs/o44cx5dmxeXGVl0ba5T2abaxRuQg==
google-site-verification=HEGwcQwzYMM_y6dwOMoyKNtRi1Fnq4ogrhx9G8aJ5FU
DirectFedAuthUrl=https://auth.spacex.com
adobe-idp-site-verification=97fe9cbe45f7936353e717f88486fcad77d04e2cc65312bbf40da31883227465
MS=ms70688094
atlassian-domain-verification=ppDBYYiz7xEIHo3t4qYTnznDkQkbtHi1WeWw9eyuRwqsdDXQHSDnaQyzPVXfOE/g
adobe-idp-site-verification=97fe9cbe45f7936353e717f88486fcad77d04e2cc65312bbf40da31883227465
—
apple-domain-verification=CU99PbnQj7UXnmWi
—
atlassian-domain-verification=ppDBYYiz7xEIHo3t4qYTnznDkQkbtHi1WeWw9eyuRwqsdDXQHSDnaQyzPVXfOE/g
—
autodesk-domain-verification=jOFrO72SJC9U9y0WfVv3
—
canva-site-verification=UxpT4tgSgT1xAINsHsHGKg
—
cisco-ci-domain-verification=236aab1dcf7007f2b6c9e8f16e541b4dadc3be19ca2f88c034dc75531327cad8
—
fadv-verification-3a01b9945b7b4369a5d19e95d33bb880
—
google-site-verification=HEGwcQwzYMM_y6dwOMoyKNtRi1Fnq4ogrhx9G8aJ5FU
—
pexip-ms-tenant-domain-verification=dc4dccf7-f034-4180-822d-4da377309371
—
smartsheet-gov-site-validation=5cZs1XJeR9JG8Q9MWZRln5PJ_RLjXjhj
—
stripe-verification=1C2B00FD0AF495B8CCC0CB8F533A38544C0199B7A83F306D3D0F63F45AAEC793
—
stripe-verification=1E214CE588837E638F2D46AB2A2790B0A51F74D94E1DA8BA6758E32F1D7457BD
—
v=spf1 include:spf-a.spacex.com include:spf-b.spacex.com include:icpbounce.com include:shops.shopify.com include:_spf.qemailserver.com include:spf.mandrillapp.com include:spf.protection.office365.us include:spf-003ea501.gpphosted.com -all
—
zqgtz1gl80bvk19hn02dy51gz592fhpf
—
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.

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.

ac08e3bb3a83154352f012ab40fd3ed3289c7070b3da40d5dc8b6cb3cd770c326d394dd7484da8f081a464c898ec30823aeac46e1e7010bec73b28bc991c1076
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 19 Apr 2026, 15:43 UTC.
Download Raw Intelligence Download Checksum (.sha3) Cross-Reference Verification

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-spacex.com.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-spacex.com.json
Python 3 (cross-platform) 
python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-spacex.com.json','rb').read()).hexdigest())"
sha3sum (coreutils 9+) 
sha3sum -a 512 dns-intelligence-spacex.com.json
Compare the output against the .sha3 file or the checksum API at /api/analysis/14188/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 spacex.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 spacex.com A
Query AAAA records (IPv6) RFC 1035 
dig +noall +answer spacex.com AAAA
Query MX records (mail servers) RFC 1035 
dig +noall +answer spacex.com MX
Query NS records (nameservers) RFC 1035 
dig +noall +answer spacex.com NS
Query TXT records RFC 1035 
dig +noall +answer spacex.com TXT

Email Authentication

Check SPF record RFC 7208 
dig +short spacex.com TXT | grep -i spf
Check DMARC policy RFC 7489 
dig +short _dmarc.spacex.com TXT
Check DKIM key for selector 'dkim' RFC 6376 
dig +short dkim._domainkey.spacex.com TXT
Check DKIM key for selector 'mandrill' RFC 6376 
dig +short mandrill._domainkey.spacex.com TXT
Check DKIM key for selector 's1' RFC 6376 
dig +short s1._domainkey.spacex.com TXT
Check DKIM key for selector 's2' RFC 6376 
dig +short s2._domainkey.spacex.com TXT
Check DKIM key for selector 'selector1' RFC 6376 
dig +short selector1._domainkey.spacex.com TXT

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

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

Domain Security

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

Infrastructure Intelligence

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

Transport Security

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

Infrastructure Intelligence

Search Certificate Transparency logs RFC 6962 
curl -s 'https://crt.sh/?q=%25.spacex.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://spacex.com/.well-known/security.txt | head -20

AI Surface

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

Infrastructure Intelligence

ASN lookup for 104.18.26.217 (Team Cymru) 
dig +short 217.26.18.104.origin.asn.cymru.com TXT
ASN lookup for 104.18.27.217 (Team Cymru) 
dig +short 217.27.18.104.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 consistent · 9/9 Evaluated
How confident are these results? Each protocol is independently verified against RFC standards. No self-awarded badges.
SPF
Consistent 15107 runs
DKIM
Consistent 14884 runs
DMARC
Consistent 15088 runs
DANE/TLSA
Consistent 14866 runs
DNSSEC
Consistent 15065 runs
BIMI
Consistent 14881 runs
MTA-STS
Consistent 14902 runs
TLS-RPT
Consistent 14917 runs
CAA
Consistent 14914 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 spacex.com A
Query AAAA records (IPv6) (RFC 1035) 
dig +noall +answer spacex.com AAAA
Query MX records (mail servers) (RFC 1035) 
dig +noall +answer spacex.com MX
Query NS records (nameservers) (RFC 1035) 
dig +noall +answer spacex.com NS
Query TXT records (RFC 1035) 
dig +noall +answer spacex.com TXT

Email Authentication

Check SPF record (RFC 7208) 
dig +short spacex.com TXT | grep -i spf
Check DMARC policy (RFC 7489) 
dig +short _dmarc.spacex.com TXT
Check DKIM key for selector 'dkim' (RFC 6376) 
dig +short dkim._domainkey.spacex.com TXT
Check DKIM key for selector 'mandrill' (RFC 6376) 
dig +short mandrill._domainkey.spacex.com TXT
Check DKIM key for selector 's1' (RFC 6376) 
dig +short s1._domainkey.spacex.com TXT
Check DKIM key for selector 's2' (RFC 6376) 
dig +short s2._domainkey.spacex.com TXT
Check DKIM key for selector 'selector1' (RFC 6376) 
dig +short selector1._domainkey.spacex.com TXT

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

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

Domain Security

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

Infrastructure Intelligence

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

Transport Security

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

Infrastructure Intelligence

Search Certificate Transparency logs (RFC 6962) 
curl -s 'https://crt.sh/?q=%25.spacex.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://spacex.com/.well-known/security.txt | head -20

AI Surface

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

Infrastructure Intelligence

ASN lookup for 104.18.26.217 (Team Cymru) 
dig +short 217.26.18.104.origin.asn.cymru.com TXT
ASN lookup for 104.18.27.217 (Team Cymru) 
dig +short 217.27.18.104.origin.asn.cymru.com TXT

0s

Running Real-Time Scan Telemetry

Most scans complete in less than one minute. Some may take longer.

Markers represent known resolver locations. Anycast routing selects the nearest node — exact routing is internal to each provider.

Pipeline nodes reflect live data as each analysis phase completes.

Telemetry Log 0 polls