Skip to main content
DNS Tool
Executive's DNS Intelligence Brief
Generated 10 Feb 2026, 06:19 UTC
Duration 5.6s
Integrity 2456e8b08d5fffb6e09bd6e35a470a2e0246f242eb04eb82ee9389aadc4c79e44d61d986ad32d8fe41386ee38259fb2aef89b451c9e26ff79c135f9c063f9c40
Subject Domain
whitehouse.gov

Executive's DNS Intelligence Brief

Board-level domain security assessment — whitehouse.gov

10 Feb 2026, 06:19 UTC · 5.6s · SHA-3-512: 2456✱✱✱✱ Verify
Engineer
Golden-fixture baseline domain. This domain is part of the golden-fixture corpus: its recorded scan snapshot is the tool's regression baseline. A scan of it reproducing the snapshot is the baseline returning its own value — expected agreement, not independent validation.
DNS Security & Trust Posture
Risk Level: Secure
5 protocols configured, 3 not configured
Email Spoofing
Protected
Brand Impersonation
Protected
DNS Tampering
Protected
Certificate Control
Open
What Requires Attention
No urgent actions detected. Domain security posture is well-maintained.
The BIG Questions
Can this domain be impersonated by email? Not Assessed
Can DNS itself be tampered with? Not Assessed
Can this brand be convincingly faked? Not Assessed
Is mail transport encryption enforced? Not Assessed
Is certificate issuance controlled? Not Assessed
Domain Overview
Registrar get.gov (Registrant: REDACTED FOR PRIVACY)
Email Provider Unknown
Web Hosting Unknown
DNS Hosting Cloudflare

Technical Findings

Email Authentication
SPF (Sender Policy) Configured
DMARC (Policy) Configured Policy: reject
DKIM (Signatures) Configured
Mail Posture Not determined
Mail Transport Security
MTA-STS Partial
DANE / TLSA Hosted Provider No MX records available — DANE check skipped
TLS-RPT (Reporting) Not Configured
Mail Transport Not assessed
DNS Security
DNSSEC Signed & Validated
DNSSEC fully configured and validated - AD flag confirmed by resolver
NS Delegation Healthy
Brand & Certificate Controls
BIMI (Brand Logo) Configured VMC Verified
CAA (Certificate) Open Any certificate authority may issue certificates
Priority Actions 3 total Achievable: SECURE
Medium Add CAA records

Publish CAA DNS records to restrict which Certificate Authorities can issue TLS certificates for your domain. Specify your preferred CA (e.g., letsencrypt.org, digicert.com).

yourdomain.com CAA 0 issue "letsencrypt.org"
Medium Deploy MTA-STS policy

Publish an MTA-STS DNS record and host a policy file at https://mta-sts.yourdomain.com/.well-known/mta-sts.txt. This tells senders to require TLS when delivering mail to your domain.

_mta-sts.yourdomain.com TXT "v=STSv1; id=20240101"
Low Configure TLS-RPT reporting

TLS-RPT (TLS Reporting) sends you reports about TLS connection failures when other servers try to deliver mail to your domain. Helps diagnose MTA-STS and STARTTLS issues.

_smtp._tls.yourdomain.com TXT "v=TLSRPTv1; rua=mailto:tls-reports@yourdomain.com"
Appendix — Additional Resources

Full technical details including raw DNS records, DKIM public keys, IP/ASN mappings, resolver consensus evidence, and verification commands are available in the Engineer's DNS Intelligence Report.

View Engineer's DNS Intelligence Report

Verify Report Integrity SHA-3-512 Has this report been tampered with? Verify below

Tamper-evident fingerprint binding this analysis to its data, domain, timestamp, and tool version.

2456e8b08d5fffb6e09bd6e35a470a2e0246f242eb04eb82ee9389aadc4c79e44d61d986ad32d8fe41386ee38259fb2aef89b451c9e26ff79c135f9c063f9c40
12 RFCs evaluated · DNS state at 10 Feb 2026, 06:19 UTC