Identity
70
C
fbi.gov
Posture Score: 75/100
Scanned May 8, 2026 at 8:18 AM UTC
Attack Surface
63
Reputation
92
Identity Findings
Overly broad CIDR range: 153.31.0.0/16
The /16 CIDR block authorizes a very large IP range to send email as this domain.
💡 Narrow the IP range to only the specific servers that send email.
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.fbi.gov
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.fbi.gov/.well-known/mta-sts.txt
STARTTLS without MTA-STS or DANE protection
STARTTLS alone is vulnerable to downgrade attacks. Neither MTA-STS nor DANE is configured to enforce encryption.
💡 Deploy MTA-STS and/or DANE to protect against STARTTLS stripping attacks.
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@fbi.gov").
ARC support not detected
No evidence of ARC (Authenticated Received Chain) support on MX servers. Forwarded messages may lose authentication.
💡 Consider enabling ARC signing on your mail servers to preserve authentication through forwarding.
No CAA iodef tag configured
No iodef tag is present in the CAA records. CA policy violation reports will not be sent.
💡 Add an iodef CAA record. Example: 0 iodef "mailto:security@example.com"
Very low TTL on MX records: 95s
2 MX records have a TTL of 95s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on A records: 120s
2 A records have a TTL of 120s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on AAAA records: 60s
2 AAAA records have a TTL of 60s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
MX records are valid
All MX records are properly configured.
SMTP security checks passed
No open relay, VRFY/EXPN, or banner disclosure issues detected.
SMTP RFC 5321 compliance checks passed
The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.
IPv6 readiness is good
IPv6 records are present and properly configured.
NS delegation is properly configured
All nameservers are responsive, consistent, and properly secured.
DNS responses are consistent across all nameservers
All authoritative nameservers return consistent answers with proper AA flags.
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.
DMARC alignment: adkim=r, aspf=r
DKIM alignment is relaxed, SPF alignment is relaxed.
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.
Deprecated DMARCbis tags found: pct
The DMARC record contains tags deprecated in DMARCbis: pct. Consider removing these for forward compatibility.
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.
No DANE/TLSA records found
DANE is not configured for any MX server. This is optional but provides strong certificate binding.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open mail ports on mx-east.fbi.gov
Detected open mail-related ports: 25
RFC 8058 one-click unsubscribe assessment
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
MX IP network diversity
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 1415240977, Refresh: 600s, Retry: 1800s, Expire: 1209600s, Min TTL: 1800s
Authorized certificate authorities
CAA records restrict certificate issuance to: amazon.com, digicert.com, entrust.net, letsencrypt.org, pki.goog, sectigo.com
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.
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.
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.
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.
DNS ANY query returns 46 record(s)
The DNS server responds to ANY queries with 46 record(s), creating significant DNS amplification risk.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
Domain enumerability: low
The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.
No internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
6 subdomain(s) discovered for fbi.gov
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
0 certificate(s) found in CT logs
Certificate Transparency logs contain 0 certificate(s) for fbi.gov and its subdomains. Each certificate reveals subdomain names.
NSEC3 authenticated denial of existence
The domain uses NSEC3 with 1 iteration(s) and salt '0CA0F4943641889C'.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
Missing domain locks: clientTransferProhibited, clientDeleteProhibited
Domain fbi.gov is missing protective locks: clientTransferProhibited, clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
HSTS enabled with preload on fbi.gov
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
HSTS enabled with preload on webmail.fbi.gov
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
security.txt present
Found security.txt at https://fbi.gov/.well-known/security.txt.
TLS certificate valid for 83 days
Certificate for fbi.gov expires on 2026-07-30.
Certificate issued by WE1
The certificate for fbi.gov is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha256
The certificate for fbi.gov uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for fbi.gov uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for fbi.gov contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on fbi.gov.
Domain valid for 105 days
Domain fbi.gov expires on 2026-08-21.
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.
Abuse contact lookup failed
Could not query abuse contact information.
PhishTank — API key required
PhishTank phishing database check requires an API key.
Sender Score — API key required
Sender Score reputation check requires an API key.
Cisco Talos — API key required
Cisco Talos IP reputation check requires an API key.
WHOIS registration data
Registrar: get.gov | Created: 1997-10-02 | Expires: 2026-08-21 | Updated: 2025-08-26
WHOIS privacy protection enabled
Domain fbi.gov has WHOIS privacy/redaction enabled.
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: reject
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: reject
⚠️ 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: mx-east.fbi.gov
PTR record proves mail server legitimacy
MX: mx-east.fbi.gov
Mail server at 153.31.119.142
→
PTR Record
Reverse DNS: mx-east-ic.fbi.gov
Mail Server Identity: mx-west.fbi.gov
PTR record proves mail server legitimacy
MX: mx-west.fbi.gov
Mail server at 153.31.192.142
→
PTR Record
Reverse DNS: mx-west-ic.fbi.gov
Mail Server Reputation: mx-east.fbi.gov
RBL check ensures server is not blacklisted
MX: mx-east.fbi.gov
Mail server at 153.31.119.142
→
RBL Status
Not blacklisted
Mail Server Reputation: mx-west.fbi.gov
RBL check ensures server is not blacklisted
MX: mx-west.fbi.gov
Mail server at 153.31.192.142
→
RBL Status
Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
Mail servers support TLS encryption
→
MTA-STS Policy
MTA-STS not configured
⚠️ MTA-STS policy is missing. Even with TLS support, you lack the enforcement layer that prevents attackers from stripping encryption (downgrade attacks).
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC policy: reject
→
BIMI Record
BIMI not configured
⚠️ BIMI record is missing. Even with DMARC enforcement, you need to configure BIMI to display your brand logo in supported email clients.
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
Mail servers support TLS encryption
→
TLS-RPT Reporting
TLS-RPT not configured
⚠️ TLS-RPT is not configured. Without TLS reporting, you have no visibility into TLS connection failures that may be impacting email delivery.
Security Checks
MX Records
✓
SPF Record
✓
DKIM Record
✗
DMARC Policy
✓
BIMI Record
✗
CAA Records
✓
DNSSEC
✓
MTA-STS
✗
TLS-RPT
✗
Embed Badge
Display your domain's security grade on your website or README:
<img src="https://scan.ractermx.com/badge/fbi.gov.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan fbi.gov Again