← Back to Scanner

gsa.gov

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

Posture Score: 85/100

Scanned May 23, 2026 at 11:27 PM UTC

Identity

Attack Surface

Reputation

Identity Findings

Weak DKIM RSA key (~1296 bits) for selector 'google'

RSA keys shorter than 2048 bits are considered weak. Current key is approximately 1296 bits.

💡 Generate a new 2048-bit (or larger) RSA key pair and update the DKIM record.

high

Weak DKIM RSA key (~1296 bits) for selector 'mandrill'

RSA keys shorter than 2048 bits are considered weak. Current key is approximately 1296 bits.

💡 Generate a new 2048-bit (or larger) RSA key pair and update the DKIM record.

high

SPF record is valid

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

pass

SPF record length OK (103 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

DKIM key strength indicates modern key management

All DKIM keys use RSA-2048+ or Ed25519, consistent with current best practices.

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

MTA-STS and TLS-RPT are properly configured

MTA-STS policy is enforced and TLS reporting is configured.

pass

TLS-RPT report destinations are reachable

All TLS-RPT rua= URIs point to resolvable domains.

pass

ARC support likely available

MX server software appears to support ARC headers for authentication preservation.

pass

Meets bulk sender authentication requirements

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

pass

SMTP security checks passed

No open relay, VRFY/EXPN, or banner disclosure issues detected.

pass

SMTP RFC 5321 compliance checks passed

The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.

pass

IPv6 readiness is good

IPv6 records are present and properly configured.

pass

STARTTLS downgrade resistance is adequate

STARTTLS is supported with modern TLS and protected by MTA-STS and/or DANE.

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, ri

The DMARC record contains tags deprecated in DMARCbis: pct, ri. 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

Shared/free email hosting detected: aspmx.l.google.com

The MX record points to a known shared or free email hosting provider.

informational

Shared/free email hosting detected: alt1.aspmx.l.google.com

The MX record points to a known shared or free email hosting provider.

informational

Shared/free email hosting detected: alt2.aspmx.l.google.com

The MX record points to a known shared or free email hosting provider.

informational

Shared/free email hosting detected: alt3.aspmx.l.google.com

The MX record points to a known shared or free email hosting provider.

informational

Shared/free email hosting detected: alt4.aspmx.l.google.com

The MX record points to a known shared or free email hosting provider.

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

No DANE/TLSA records found

DANE is not configured for any MX server. This is optional but provides strong certificate binding.

informational

No BIMI record found

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

informational

Open mail ports on aspmx.l.google.com

Detected open mail-related ports: 25

informational

RFC 8058 one-click unsubscribe assessment

DKIM signing is configured. RFC 8058 compliance depends on List-Unsubscribe and List-Unsubscribe-Post headers being included in outbound messages and DKIM signatures.

informational

MX IP network diversity

MX IPs span 5 different /16 networks, providing good diversity.

informational

SOA record parameters

Serial: 797014024, Refresh: 3600s, Retry: 180s, Expire: 1209600s, Min TTL: 3600s

informational

Authorized certificate authorities

CAA records restrict certificate issuance to: amazon.com, globalsign.com, letsencrypt.org, comodoca.com, entrust.net, digicert.com, godaddy.com

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

DNS ANY query returns 65 record(s)

The DNS server responds to ANY queries with 65 record(s), creating significant DNS amplification risk.

💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.

medium

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 email autodiscovery endpoints detected

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

pass

16 subdomain(s) discovered for gsa.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 gsa.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 gsa.gov is missing protective locks: clientDeleteProhibited.

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

high

Not listed on any DNS blacklists

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

pass

HSTS enabled with preload on gsa.gov

Strict-Transport-Security: max-age=31536000; includeSubDomains; preload

pass

security.txt present

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

pass

TLS certificate valid for 87 days

Certificate for gsa.gov expires on 2026-08-19.

pass

Certificate issued by R13

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

pass

Signature algorithm: rsa-sha256

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

pass

RSA key: 4096 bits

The certificate for gsa.gov uses an adequate RSA key of 4096 bits.

pass

SCTs present in certificate

The certificate for gsa.gov contains Signed Certificate Timestamps.

pass

No weak ciphers detected

No known weak cipher suites detected on gsa.gov.

pass

Domain valid for 101 days

Domain gsa.gov expires on 2026-09-02.

pass

No disposable email provider MX records

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

pass

Domain is 10460 days old

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

pass

No wildcard MX records

No wildcard MX records detected for gsa.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 (aspmx.l.google.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.

pass

SMTP banner from hosted mail provider

The MX (aspmx.l.google.com) is a hosted mail service. Banner alignment is managed by the provider and not actionable by the domain owner.

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.gsa.gov

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

informational

WHOIS registration data

Registrar: get.gov | Created: 1997-10-02 | Expires: 2026-09-02 | Updated: 2025-11-06

informational

WHOIS privacy protection enabled

Domain gsa.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: ga.gov (has MX!), gsa.com (has MX!), gsa.net (has MX!), gsa.io (has MX!), sa.gov

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: 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: aspmx.l.google.com

PTR record proves mail server legitimacy

MX: aspmx.l.google.com Mail server at 74.125.193.27 → PTR Record Reverse DNS: ig-in-f27.1e100.net

Mail Server Identity: alt1.aspmx.l.google.com

PTR record proves mail server legitimacy

MX: alt1.aspmx.l.google.com Mail server at 173.194.76.26 → PTR Record Reverse DNS: ws-in-f26.1e100.net

Mail Server Identity: alt2.aspmx.l.google.com

PTR record proves mail server legitimacy

MX: alt2.aspmx.l.google.com Mail server at 142.250.102.27 → PTR Record Reverse DNS: rb-in-f27.1e100.net

Mail Server Identity: alt3.aspmx.l.google.com

PTR record proves mail server legitimacy

MX: alt3.aspmx.l.google.com Mail server at 192.178.213.27 → PTR Record Reverse DNS: yugrqzs-in-f27.1e100.net

Mail Server Identity: alt4.aspmx.l.google.com

PTR record proves mail server legitimacy

MX: alt4.aspmx.l.google.com Mail server at 142.251.127.27 → PTR Record Reverse DNS: lcfrai-in-f27.1e100.net

Mail Server Reputation: aspmx.l.google.com