Recon Report
cia.gov
Target Assessment
Target Hardness:
Hardened
5 defensive layers
|
2 attack surface gaps
Email Spoofability Can you spoof email from this domain?
> analyzing sender authorization policy...
SPF — Sender Policy Framework
SPF is configured — sender authorization restricts spoofing
RFC 7208 — Sender Policy Framework
SPF allows domain owners to specify which mail servers are authorized to send email on behalf of their domain. Without SPF, any server can forge the envelope sender.
> enumerating cryptographic selectors...
DKIM — DomainKeys Identified Mail
DKIM selectors reveal mail infrastructure
— signatures found
RFC 6376 — DomainKeys Identified Mail
DKIM provides cryptographic authentication of email messages. Selector names often reveal email providers (e.g., google, selector1 = Microsoft 365).
> evaluating enforcement policy...
DMARC — Domain-based Message Authentication
DMARC p=quarantine — authentication failures are sequestered, not rejected. Forensic telemetry is preserved (RFC 7489 §7). Some organizations maintain this posture as a deliberate monitoring strategy. See NIST SP 800-177
RFC 7489 — DMARC
DMARC ties SPF and DKIM together with a policy that tells receiving servers what to do with unauthenticated mail. p=none is monitoring only — attackers love it.
Transport Security Can you intercept email in transit?
> probing certificate pinning via DNSSEC chain...
DANE / TLSA
No DANE — TLS is opportunistic and can be downgraded
MTA-STS
MTA-STS not enforced — STARTTLS stripping possible
TLS-RPT
No TLS-RPT — TLS failures go unnoticed by the domain owner
RFC 8460 — SMTP TLS Reporting
TLS-RPT enables reporting of TLS negotiation failures. Without it, STARTTLS downgrade attacks leave no trace.
Brand & Certificate Security Can you fake this brand's identity?
BIMI
No BIMI — no verified brand logo in email clients. Visual impersonation is easy.
CAA — Certificate Authority Authorization
CAA restricts certificate issuance to authorized CAs. Attacker must compromise an approved CA or exploit issuance delay windows.
0 iodef "mailto:caanotices@uce.cia.gov"
0 issue "digicert.com"
RFC 8659 — CAA
CAA records specify which Certificate Authorities are authorized to issue certificates. Without CAA, an attacker could obtain a valid cert from any CA.
DNS Infrastructure Can you poison the DNS?
> validating cryptographic chain of trust...
DNSSEC
No DNSSEC — DNS responses can be spoofed or poisoned
RFC 4033–4035 — DNSSEC
DNSSEC adds cryptographic signatures to DNS responses, preventing cache poisoning and response forgery. Without DNSSEC, an attacker can forge DNS answers.
NS Delegation
0 nameservers detected
— single point of failure
Attack Surface Discovery What can you find from the outside?
Subdomain Discovery (Multi-Source)
0 subdomains discovered via CT logs + DNS probing + Nmap SAN extraction
| Subdomain |
|---|
map[cert_count:1 has_dns:false issuer:C=US, O=Amazon, OU=Server CA 1B, CN=Amazon not_after:2023-06-29T23:59:59 not_before:2022-05-31T00:00:00 subdomain:cloudbolt.cloud.cia.gov] |
map[cert_count:2 has_dns:false issuer:C=US, O=Amazon, CN=Amazon RSA 2048 M02 not_after:2023-07-27T23:59:59 not_before:2023-02-22T00:00:00 subdomain:cmp.cloud.cia.gov] |
map[cert_count:2 has_dns:true issuer:C=US, O="VeriSign, Inc.", OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)06, CN=VeriSign Class 3 Extended Validation SSL SGC CA not_after:2014-09-10T23:59:59 not_before:2012-12-11T00:00:00 subdomain:crypt.cia.gov] |
map[cert_count:1 has_dns:false issuer:C=US, O="VeriSign, Inc.", OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)09, CN=VeriSign Class 3 Secure Server CA - G2 not_after:2013-08-10T23:59:59 not_before:2010-08-12T00:00:00 subdomain:ddss.cia.gov] |
map[cert_count:1 has_dns:false issuer:C=US, O="VeriSign, Inc.", OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)09, CN=VeriSign Class 3 Secure Server CA - G2 not_after:2013-07-31T23:59:59 not_before:2010-08-11T00:00:00 subdomain:ddsstest.cia.gov] |
map[cert_count:14 has_dns:false issuer:C=US, O=DigiCert Inc, CN=DigiCert EV RSA CA G2 not_after:2025-04-25T23:59:59 not_before:2024-03-25T00:00:00 subdomain:mail1.cia.gov] |
map[cert_count:12 has_dns:false issuer:C=US, O=DigiCert Inc, CN=DigiCert EV RSA CA G2 not_after:2025-04-25T23:59:59 not_before:2024-03-25T00:00:00 subdomain:mail2.cia.gov] |
map[cert_count:5 has_dns:true issuer:C=US, O=DigiCert Inc, CN=DigiCert EV RSA CA G2 not_after:2026-03-29T23:59:59 not_before:2025-03-25T00:00:00 subdomain:mail3.cia.gov] |
map[cert_count:5 has_dns:true issuer:C=US, O=DigiCert Inc, CN=DigiCert EV RSA CA G2 not_after:2026-03-29T23:59:59 not_before:2025-03-25T00:00:00 subdomain:mail4.cia.gov] |
map[cert_count:8 has_dns:true issuer:C=US, ST=Arizona, L=Scottsdale, O="GoDaddy.com, Inc.", OU=http://certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2 not_after:2023-08-18T18:35:03 not_before:2022-08-18T19:50:45 subdomain:mivsp.cia.gov] |
map[cert_count:2 has_dns:false issuer:C=US, O=Let's Encrypt, CN=R3 not_after:2021-03-21T18:50:40 not_before:2020-12-21T18:50:40 subdomain:preview-16789456.cia.gov] |
map[cert_count:1 has_dns:true issuer:O=VeriSign Trust Network, OU="VeriSign, Inc.", OU=VeriSign International Server CA - Class 3, OU=www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD.(c)97 VeriSign not_after:2011-02-07T23:59:59 not_before:2008-04-02T00:00:00 subdomain:res.cia.gov] |
map[cert_count:55 cname:cia.gov.edgekey.net. has_dns:true issuer:C=US, O=DigiCert Inc, CN=DigiCert Global G3 TLS ECC SHA384 2020 CA1 not_after:2026-08-12T23:59:59 not_before:2025-08-13T00:00:00 subdomain:www.cia.gov] |
map[cert_count:7 has_dns:false issuer:C=US, ST=Arizona, L=Scottsdale, O="GoDaddy.com, Inc.", OU=http://certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2 not_after:2023-08-18T18:35:03 not_before:2022-08-18T19:50:45 subdomain:www.mivsp.cia.gov] |
SaaS Services (TXT Record Discovery)
No SaaS verification records found
Intelligence Metadata Can you verify this independently?
SHA-3-512 Integrity Hash
88cecd26f22563ba6041febb8ed2370ac3d2be054bc5c9a52f85d38d15731a872f42d25495ec538a29fa9af8a1f0a97e3d4cb0e4f3f630bfec22c3ab69cac9de
RFC References
12
Tool Version
v26.12.28