← Back to Scanner

nsa.gov

Name: nsa.gov Email Security Posture Assessment
Creator: RacterMX

Posture Score: 74/100

Scanned May 23, 2026 at 11:44 PM UTC

Identity

Attack Surface

Reputation

Identity Findings

No MX records found

The domain has no MX records and cannot receive email.

💡 Publish MX records pointing to your mail server(s).

critical

No DKIM records found

No DKIM records were found for any common selector. Email may not be authenticated.

💡 Configure DKIM signing and publish the public key at <selector>._domainkey.nsa.gov

high

No MTA-STS record found

Without MTA-STS, mail transport encryption cannot be enforced and is vulnerable to downgrade attacks.

💡 Publish a _mta-sts TXT record and host a policy file at https://mta-sts.nsa.gov/.well-known/mta-sts.txt

medium

SOA MNAME is not authoritative

The primary nameserver (MNAME) 'w000-dsid-u05.nsa.gov' does not return authoritative answers.

💡 Update the MNAME field to point to an authoritative nameserver for this zone.

medium

No CAA records found

No CAA records are configured. Any certificate authority can issue certificates for this domain.

💡 Add CAA records to restrict certificate issuance. Example: 0 issue "letsencrypt.org"

medium

No TLS-RPT record found

Without TLS-RPT, you will not receive reports about TLS negotiation failures.

💡 Publish a _smtp._tls TXT record (e.g. "v=TLSRPTv1; rua=mailto:tls-reports@nsa.gov").

low

ARC check skipped — no MX records

Cannot assess ARC support without MX records.

low

SPF record is valid

The SPF record is properly configured with valid syntax and within lookup limits.

pass

SPF record length OK (141 bytes)

SPF record is within safe DNS packet size limits.

pass

DKIM cryptographic configuration is compliant

No RFC 8301 compliance issues detected in DKIM key configuration.

pass

All external report destinations authorized

External DMARC report destinations have valid authorization records per RFC 7489 §7.1.

pass

Subdomains protected (sp=reject)

DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.

pass

Meets bulk sender authentication requirements

Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.

pass

IPv6 readiness is good

IPv6 records are present and properly configured.

pass

NS delegation is properly configured

All nameservers are responsive, consistent, and properly secured.

pass

DNS responses are consistent across all nameservers

All authoritative nameservers return consistent answers with proper AA flags.

pass

DNS TTL values follow best practices

All critical DNS record TTLs are within recommended ranges.

pass

DKIM2 not detected

No DKIM key record with v=2 was found across common selectors. DKIM2 is an emerging standard and not yet widely deployed.

informational

DMARC alignment: adkim=r, aspf=r

DKIM alignment is relaxed, SPF alignment is relaxed.

informational

DMARC failure reporting: fo=1

Failure reports generated when any authentication mechanism fails.

informational

DMARCbis np tag absent

The DMARC record does not include the np (non-existent subdomain policy) tag. Consider adding np=reject to protect non-existent subdomains under DMARCbis.

informational

Deprecated DMARCbis tags found: pct, rf

The DMARC record contains tags deprecated in DMARCbis: pct, rf. Consider removing these for forward compatibility.

informational

DMARCbis psd tag absent

The DMARC record does not include the psd (public suffix domain) indicator. Consider adding psd=n to explicitly identify this as an organizational domain.

informational

REQUIRETLS not advertised

The primary MX does not advertise REQUIRETLS (RFC 8689). This is an emerging standard — MTA-STS and DANE provide adequate TLS enforcement for most deployments.

informational

DANE check skipped — no MX records

Cannot check DANE/TLSA without MX records.

informational

No BIMI record found

BIMI is not configured. Your brand logo will not display in supporting email clients.

informational

Open relay check skipped — no MX records

Cannot test for open relay without MX records.

informational

SMTP compliance check skipped — no MX records

Cannot test SMTP compliance without MX records.

informational

Port exposure check skipped — no MX records

Cannot scan ports without MX records.

informational

STARTTLS downgrade check skipped — no MX records

Cannot test STARTTLS without MX records.

informational

RFC 8058 one-click unsubscribe assessment

No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.

informational

FCrDNS check skipped — no MX records

Cannot perform FCrDNS without MX records.

informational

SOA record parameters

Serial: 2025050657, Refresh: 3600s, Retry: 1080s, Expire: 2419200s, Min TTL: 900s

informational

Attack Surface Findings

Weak DNSSEC RSA key: 336 bits

The DNSKEY uses an RSA key of 336 bits, below the recommended 2048 bits.

💡 Generate a new DNSKEY with at least 2048-bit RSA or migrate to ECDSA/Ed25519.

high

Weak DNSSEC RSA key: 336 bits

The DNSKEY uses an RSA key of 336 bits, below the recommended 2048 bits.

💡 Generate a new DNSKEY with at least 2048-bit RSA or migrate to ECDSA/Ed25519.

high

Weak DNSSEC RSA key: 336 bits

The DNSKEY uses an RSA key of 336 bits, below the recommended 2048 bits.

💡 Generate a new DNSKEY with at least 2048-bit RSA or migrate to ECDSA/Ed25519.

high

Weak DNSSEC RSA key: 336 bits

The DNSKEY uses an RSA key of 336 bits, below the recommended 2048 bits.

💡 Generate a new DNSKEY with at least 2048-bit RSA or migrate to ECDSA/Ed25519.

high

Domain enumerability: low

The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.

low

All MX records resolve correctly

No dangling MX records detected — all MX hostnames resolve to valid IP addresses.

pass

Explicit MX records present

The domain has explicit MX records — no implicit A-record fallback delivery.

pass

No internal information leakage detected

No non-routable IP addresses or internal references were found in public DNS records.

pass

No excessive DNS information exposure detected

No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.

pass

No email autodiscovery endpoints detected

No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.

pass

3 subdomain(s) discovered for nsa.gov

Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.

informational

0 certificate(s) found in CT logs

Certificate Transparency logs contain 0 certificate(s) for nsa.gov and its subdomains. Each certificate reveals subdomain names.

informational

NSEC3 authenticated denial of existence

The domain uses NSEC3 with 0 iteration(s) and salt '-'.

informational

DNSSEC is enabled

DNSKEY and/or DS records are present, indicating DNSSEC is configured.

informational

Reputation Findings

Missing domain locks: clientDeleteProhibited

Domain nsa.gov is missing protective locks: clientDeleteProhibited.

💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.

high

HSTS enabled but missing preload directive on nsa.gov

Strict-Transport-Security: max-age=31536000

💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.

low

Not listed on any DNS blacklists

Domain and MX IPs checked against 55 DNSBLs — no listings found.

pass

security.txt present

Found security.txt at https://nsa.gov/.well-known/security.txt.

pass

TLS certificate valid for 66 days

Certificate for nsa.gov expires on 2026-07-29.

pass

Certificate issued by R13

The certificate for nsa.gov is issued by a third-party CA.

pass

Signature algorithm: rsa-sha256

The certificate for nsa.gov uses an acceptable signature algorithm.

pass

RSA key: 2048 bits

The certificate for nsa.gov uses an adequate RSA key of 2048 bits.

pass

SCTs present in certificate

The certificate for nsa.gov contains Signed Certificate Timestamps.

pass

No weak ciphers detected

No known weak cipher suites detected on nsa.gov.

pass

Domain valid for 87 days

Domain nsa.gov expires on 2026-08-19.

pass

No disposable email provider MX records

MX records for nsa.gov do not match known disposable email provider patterns.

pass

Domain is 10460 days old

Domain nsa.gov was registered 1997-10-02.

pass

No wildcard MX records

No wildcard MX records detected for nsa.gov.

pass

TLD has good reputation

The .gov TLD is not on known abuse watchlists.

pass

DMARC reporting destinations look legitimate

DMARC rua/ruf addresses do not point to known URL shortener services.

pass

MX records point to stable infrastructure

No MX records point to known dynamic DNS service domains.

pass

Strong TLS configuration on primary MX

Primary MX (pri-jeemsg.eemsg.mail.mil) uses with cipher including Forward Secrecy.

pass

Google Safe Browsing DNS check — no flag detected

DNS-based Safe Browsing lookup returned no results. Full verification requires the Google Safe Browsing API key.

informational

Abuse contacts found for MX IPs

Abuse contact information retrieved via abusix.org DNS lookup.

informational

PhishTank — API key required

PhishTank phishing database check requires an API key.

informational

Sender Score — API key required

Sender Score reputation check requires an API key.

informational

Cisco Talos — API key required

Cisco Talos IP reputation check requires an API key.

informational

Could not connect to webmail.nsa.gov

HTTPS request to https://webmail.nsa.gov failed or timed out.

informational

WHOIS registration data

Registrar: get.gov | Created: 1997-10-02 | Expires: 2026-08-19 | Updated: 2025-08-24

informational

WHOIS privacy protection enabled

Domain nsa.gov has WHOIS privacy/redaction enabled.

informational

Bulletproof Hosting Detection — API key required

Checking IPs against known bulletproof hosting providers requires a threat intelligence API key.

informational

Threat Intelligence Feeds — API key required

Checking domain against threat intelligence feeds requires API keys (e.g., VirusTotal, AbuseIPDB).

informational

Typosquat detected: nea.gov (has MX!), nsa.com (has MX!), nsa.net (has MX!), nsa.io (has MX!), nsa.co (has MX!)

7 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 7. Domains with MX records can send and receive email, making them high-risk phishing vectors.

informational

Dependency Chains

DMARC Authentication Chain (SPF)

DMARC uses SPF to verify that emails come from authorized servers

SPF Record SPF record found and configured → DMARC Policy DMARC policy:

DMARC Authentication Chain (DKIM)

DMARC uses DKIM to verify that emails have not been tampered with

DKIM Signature DKIM signature missing → DMARC Policy DMARC policy:

⚠️ DKIM signature is missing. DMARC relies on DKIM to verify email integrity and prevent tampering. Without DKIM, DMARC alignment will fail for cryptographic verification.

Mail Server Identity: pri-jeemsg.eemsg.mail.mil

PTR record proves mail server legitimacy

MX: pri-jeemsg.eemsg.mail.mil Mail server at 156.112.250.0 → PTR Record Reverse DNS: pri-jeemsg.eemsg.mail.mil

Mail Server Identity: sec-jeemsg.eemsg.mail.mil

PTR record proves mail server legitimacy

MX: sec-jeemsg.eemsg.mail.mil Mail server at 156.112.250.5 → PTR Record Reverse DNS: sec-jeemsg.eemsg.mail.mil

Mail Server Identity: w455-emsm-u10.ncsc.mil

PTR record proves mail server legitimacy

MX: w455-emsm-u10.ncsc.mil Mail server at 214.80.121.17 → PTR Record Reverse DNS: w455-emsm-u10.ncsc.mil

Mail Server Identity: w455-emsm-u11.ncsc.mil

PTR record proves mail server legitimacy

MX: w455-emsm-u11.ncsc.mil Mail server at 214.80.121.18 → PTR Record Reverse DNS: w455-emsm-u11.ncsc.mil

Mail Server Identity: emsm-gh1-uea10.ncsc.mil

PTR record proves mail server legitimacy

MX: emsm-gh1-uea10.ncsc.mil Mail server at 214.29.60.2 → PTR Record Reverse DNS: emsm-gh1-uea10.ncsc.mil

Mail Server Identity: emsm-gh1-uea11.ncsc.mil

PTR record proves mail server legitimacy

MX: emsm-gh1-uea11.ncsc.mil Mail server at 214.29.60.3 → PTR Record Reverse DNS: emsm-gh1-uea11.ncsc.mil

Mail Server Reputation: pri-jeemsg.eemsg.mail.mil