Identity
0
D
whitehouse.com
Posture Score: 62/100
Scanned May 10, 2026 at 5:01 AM UTC
Score History
Attack Surface
94
Reputation
92
Identity Findings
No SPF record found
The domain has no SPF record, allowing anyone to send email as this domain.
💡 Publish an SPF TXT record (e.g. "v=spf1 include:_spf.google.com -all").
No DMARC record found
The domain has no DMARC record, providing no policy for handling unauthenticated email.
💡 Publish a DMARC TXT record at _dmarc.whitehouse.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@whitehouse.com").
Invalid DKIM syntax for selector 'default'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'selector1'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'selector2'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'google'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'dkim'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'mail'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'k1'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 's1'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 's2'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'mandrill'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'amazonses'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'cm'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'smtp'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Does not meet bulk sender requirements
Google and Yahoo require all bulk senders to have SPF+DKIM, DMARC, and one-click unsubscribe. Issues: No DMARC record published (required since Feb 2024); SPF not published (recommended alongside DKIM)
💡 Publish SPF, DKIM, and DMARC records. Implement RFC 8058 one-click unsubscribe for marketing mail.
TLS certificate hostname mismatch on mail.whitehouse.com
Certificate subject '*.internetmailserver.net' does not match hostname 'mail.whitehouse.com'. SANs: *.internetmailserver.net, internetmailserver.net
💡 Obtain a TLS certificate that matches the mail server hostname.
NS delegation mismatch
The registrar-delegated nameservers do not match the zone NS records.
💡 Update either the registrar NS delegation or the zone NS records to match.
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.whitehouse.com/.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.
Single MX record — no redundancy
Only one MX record exists. If this mail server goes down, all inbound mail will bounce. Most production mail systems use 2+ MX records with different priorities.
💡 Add a secondary MX record with a higher priority number (e.g., priority 20) pointing to a backup mail server.
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@whitehouse.com").
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"
NS TTL mismatch between parent and authoritative zone
The NS record TTL in the parent zone (~7189s) differs significantly from the authoritative zone (~86400s).
💡 Align NS record TTLs between the parent zone delegation and the authoritative zone.
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.
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.
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.
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 mail.whitehouse.com
Detected open mail-related ports: 25, 110, 143, 465, 587, 993, 995
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: 2009010251, Refresh: 43200s, Retry: 3600s, Expire: 1209600s, Min TTL: 180s
Authorized certificate authorities
CAA records restrict certificate issuance to: letsencrypt.org
Attack Surface Findings
DNSSEC is not enabled
No DNSKEY or DS records were found. DNS responses are not cryptographically authenticated.
💡 Enable DNSSEC by generating DNSKEY records and publishing DS records at the registrar.
DNS ANY query returns 12 record(s)
The DNS server responds to ANY queries with 12 record(s). The low record count limits amplification risk, but ANY responses still aid reconnaissance.
💡 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 subdomain takeover risks detected
All checked subdomains have valid, responsive targets.
All MX records resolve correctly
No dangling MX records detected — all MX hostnames resolve to valid IP addresses.
Explicit MX records present
The domain has explicit MX records — no implicit A-record fallback delivery.
No internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
1 subdomain(s) discovered for whitehouse.com
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 whitehouse.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.whitehouse.com, resolving to 54.209.37.18. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Microsoft Autodiscover endpoint detected
The Autodiscover endpoint at autodiscover.whitehouse.com responded with HTTP 404.
Reputation Findings
Missing Strict-Transport-Security on whitehouse.com
The Strict-Transport-Security header is not set on https://whitehouse.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
Missing Strict-Transport-Security on webmail.whitehouse.com
The Strict-Transport-Security header is not set on https://webmail.whitehouse.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
security.txt present
Found security.txt at https://whitehouse.com/.well-known/security.txt.
TLS certificate valid for 79 days
Certificate for whitehouse.com expires on 2026-07-28.
Certificate issued by R13
The certificate for whitehouse.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for whitehouse.com uses an acceptable signature algorithm.
RSA key: 3072 bits
The certificate for whitehouse.com uses an adequate RSA key of 3072 bits.
SCTs present in certificate
The certificate for whitehouse.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on whitehouse.com.
Domain valid for 1107 days
Domain whitehouse.com expires on 2029-05-22.
Domain transfer and delete locks enabled
Domain whitehouse.com has clientTransferProhibited and clientDeleteProhibited locks.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
Strong TLS configuration on primary MX
Primary MX (mail.whitehouse.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner matches infrastructure identity
The SMTP banner (m03.internetmailserver.net) aligns with the MX hostname (mail.whitehouse.com).
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: Sea Wasp, LLC | Created: 1997-05-21 | Expires: 2029-05-22 | Updated: 2024-07-10
WHOIS privacy protection enabled
Domain whitehouse.com has WHOIS privacy/redaction enabled.
Typosquat detected: hitehouse.com (has MX!), whiethouse.com (has MX!), witehouse.com, whithouse.com, whitehose.com
8 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 8. Domains with MX records can send and receive email, making them high-risk phishing vectors.
Dependency Chains
DMARC Authentication Chain (SPF)
DMARC uses SPF to verify that emails come from authorized servers
SPF Record
SPF record missing
→
DMARC Policy
DMARC policy:
⚠️ SPF record is missing. DMARC relies on SPF to verify sender authorization. Without SPF, DMARC alignment will fail, reducing email deliverability and brand protection.
DMARC Authentication Chain (DKIM)
DMARC uses DKIM to verify that emails have not been tampered with
DKIM Signature
DKIM signature configured
→
DMARC Policy
DMARC policy:
Mail Server Identity: mail.whitehouse.com
PTR record proves mail server legitimacy
MX: mail.whitehouse.com
Mail server at 64.79.170.147
→
PTR Record
Reverse DNS: m03.internetmailserver.net
Mail Server Reputation: mail.whitehouse.com
RBL check ensures server is not blacklisted
MX: mail.whitehouse.com
Mail server at 64.79.170.147
→
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 not enforced (p=none or missing)
→
BIMI Record
Brand logo configured
⚠️ DMARC is not enforced. BIMI requires a DMARC policy of "quarantine" or "reject" to prove you have strong email authentication. Without enforcement, email clients will not display your logo.
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
Mail servers support TLS encryption
→
TLS-RPT Reporting
TLS failure reporting configured
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/whitehouse.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan whitehouse.com Again