Skip to main content
DNS Tool
Executive's DNS Intelligence Brief
Generated 12 Feb 2026, 17:36 UTC
Version v26.12.28
Integrity 16aea5417ba5feb5dd102fd4b7876a62c6e937913a3c12eef5da26ab046ea0cf8a8566f3921f1b5c81ab40f9280eeb7c85901b390d6c61191c12b14633b62f53
Subject Domain
cia.gov

Executive's DNS Intelligence Brief

Board-level domain security assessment — cia.gov

12 Feb 2026, 17:36 UTC · SHA-3-512: 16ae✱✱✱✱ 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: Low Risk
5 protocols configured, 2 not configured
Email Spoofing
Protected
Brand Impersonation
Not Set Up
DNS Tampering
Protected
Certificate Control
Configured
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 Akamai
DNS Hosting Akamai Edge DNS

Technical Findings

Email Authentication
SPF (Sender Policy) Configured
DMARC (Policy) Configured Policy: quarantine
DKIM (Signatures) Configured
Mail Posture Email: Enforced
Mail Transport Security
MTA-STS Partial
DANE / TLSA Hosted Provider No DANE/TLSA records found (checked 2 MX hosts)
TLS-RPT (Reporting) Not Configured
Mail Transport Not Enforced Policy-assessed
DNS Security
DNSSEC Signed & Validated
DNSSEC fully configured and validated — AD (Authenticated Data) flag set by resolver 8.8.8.8 confirming cryptographic chain of trust from root to zone (RFC 4035 §3.2.3)
NS Delegation Healthy
Brand & Certificate Controls
BIMI (Brand Logo) Not Configured
CAA (Certificate) Configured
Priority Actions 5 total Achievable: Low Risk
Medium Deploy MTA-STS policy

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

_mta-sts.cia.gov TXT "v=STSv1; id=20240101"
Low Upgrade DMARC to reject policy

Your DMARC policy is quarantine — spoofed messages are flagged. Upgrading to p=reject blocks them entirely. Review aggregate reports to confirm legitimate senders are aligned.

_dmarc.cia.gov TXT "v=DMARC1; p=reject; rua=mailto:dmarc-reports@cia.gov"
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.cia.gov TXT "v=TLSRPTv1; rua=mailto:tls-reports@cia.gov"
Low Deploy DANE/TLSA for email transport

DNSSEC is already enabled — you can strengthen email transport security by publishing DANE TLSA records. DANE binds your mail server's TLS certificate to DNS, preventing man-in-the-middle attacks on SMTP connections.

_25._tcp.mail.cia.gov TLSA 3 1 1 <certificate_hash>
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.cia.gov TXT "v=BIMI1; l=https://cia.gov/logo.svg"
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.

16aea5417ba5feb5dd102fd4b7876a62c6e937913a3c12eef5da26ab046ea0cf8a8566f3921f1b5c81ab40f9280eeb7c85901b390d6c61191c12b14633b62f53
12 RFCs evaluated · DNS state at 12 Feb 2026, 17:36 UTC