Skip to main content
DNS Tool
Executive's DNS Intelligence Brief
Generated 10 Feb 2026, 03:04 UTC
Duration 22.6s
Version v26.10.88
Integrity da30ebf5d50b005aee251bc8dff3ba52dea3065eb9412f11174897d5e5fd5839aab5e2df9b356866bd5dbc1fc3b93a14dc39416a16d4549133268eba997772ff
Subject Domain
usa.gov

Executive's DNS Intelligence Brief

Board-level domain security assessment — usa.gov

10 Feb 2026, 03:04 UTC · 22.6s · SHA-3-512: da30✱✱✱✱ Verify
Engineer
DNS Security & Trust Posture
Risk Level: SECURE
2 protocols configured, 5 not configured
Email Spoofing
Protected
Brand Impersonation
Not Set Up
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 Standard

Technical Findings

Email Authentication
SPF (Sender Policy) Configured
DMARC (Policy) Configured Policy: reject
DKIM (Signatures) Not Detected
Mail Posture Email: Ambiguous
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) Not Configured
CAA (Certificate) Open Any certificate authority may issue certificates
Priority Actions 5 total Achievable: SECURE
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 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"
Low Add TLS-RPT reporting

Publish a TLS-RPT DNS record to receive reports about TLS delivery failures to your domain.

_smtp._tls.yourdomain.com TXT "v=TLSRPTv1; rua=mailto:tls-reports@yourdomain.com"
Low Configure BIMI brand logo

Publish a BIMI DNS record pointing to your brand logo (SVG Tiny PS format). For full support in Gmail, you will also need a Verified Mark Certificate (VMC).

default._bimi.yourdomain.com TXT "v=BIMI1; l=https://yourdomain.com/logo.svg"
Low Deploy DANE/TLSA for mail transport

Since DNSSEC is already active, you can add TLSA records for your MX hosts to enable DANE. This cryptographically pins TLS certificates for mail delivery.

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.

da30ebf5d50b005aee251bc8dff3ba52dea3065eb9412f11174897d5e5fd5839aab5e2df9b356866bd5dbc1fc3b93a14dc39416a16d4549133268eba997772ff
12 RFCs evaluated · DNS state at 10 Feb 2026, 03:04 UTC