Identity
0
F
unitedhealth.com
Posture Score: 50/100
Scanned May 8, 2026 at 10:44 PM UTC
Attack Surface
66
Reputation
85
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.unitedhealth.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@unitedhealth.com").
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.unitedhealth.com
No STARTTLS support on mail1.corpmailsvcs.com:25
The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on mail2.corpmailsvcs.com:25
The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on mail10.corpmailsvcs.com:25
The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on mail11.corpmailsvcs.com:25
The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on mail1.corpmailsvcs.com
The mail server does not support STARTTLS. All email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on mail2.corpmailsvcs.com
The mail server does not support STARTTLS. All email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on mail10.corpmailsvcs.com
The mail server does not support STARTTLS. All email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on mail11.corpmailsvcs.com
The mail server does not support STARTTLS. All email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
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.unitedhealth.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.
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"
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@unitedhealth.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.
Very low TTL on NS records: 214s
2 NS records have a TTL of 214s 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.
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.
Mail server port configuration is acceptable
No concerning port exposure detected.
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.
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.
Domain is IPv4-only
No AAAA records found for the domain, MX servers, or nameservers. The domain operates on IPv4 only.
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: 2029, Refresh: 300s, Retry: 30s, Expire: 604800s, Min TTL: 900s
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 19 record(s)
The DNS server responds to ANY queries with 19 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.
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.
0 subdomain(s) discovered for unitedhealth.com
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
30 certificate(s) found in CT logs
Certificate Transparency logs contain 30 certificate(s) for unitedhealth.com and its subdomains. Each certificate reveals subdomain names.
NSEC3 authenticated denial of existence
The domain uses NSEC3 with 10 iteration(s) and salt '0D4A1E61420B575E8B6D19FD970E'.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
Could not retrieve TLS certificate
Failed to connect to unitedhealth.com:443 or retrieve the peer certificate.
💡 Ensure the domain has a valid TLS certificate installed and port 443 is accessible.
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.
Could not connect to unitedhealth.com
HTTPS request to https://unitedhealth.com failed or timed out.
Could not connect to webmail.unitedhealth.com
HTTPS request to https://webmail.unitedhealth.com failed or timed out.
WHOIS lookup failed
Could not retrieve WHOIS data for unitedhealth.com.
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 missing
⚠️ 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 missing
→
DMARC Policy
DMARC policy missing
⚠️ 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: mail1.corpmailsvcs.com
PTR record proves mail server legitimacy
MX: mail1.corpmailsvcs.com
Mail server at 198.203.174.9
→
PTR Record
Reverse DNS: mail1.corpmailsvcs.com
Mail Server Identity: mail2.corpmailsvcs.com
PTR record proves mail server legitimacy
MX: mail2.corpmailsvcs.com
Mail server at 198.203.174.10
→
PTR Record
Reverse DNS: mail2.corpmailsvcs.com
Mail Server Identity: mail10.corpmailsvcs.com
PTR record proves mail server legitimacy
MX: mail10.corpmailsvcs.com
Mail server at 198.203.176.100
→
PTR Record
Reverse DNS: mail10.corpmailsvcs.com
Mail Server Identity: mail11.corpmailsvcs.com
PTR record proves mail server legitimacy
MX: mail11.corpmailsvcs.com
Mail server at 198.203.176.101
→
PTR Record
Reverse DNS: mail11.corpmailsvcs.com
Mail Server Reputation: mail1.corpmailsvcs.com
RBL check ensures server is not blacklisted
MX: mail1.corpmailsvcs.com
Mail server at 198.203.174.9
→
RBL Status
Not blacklisted
Mail Server Reputation: mail2.corpmailsvcs.com
RBL check ensures server is not blacklisted
MX: mail2.corpmailsvcs.com
Mail server at 198.203.174.10
→
RBL Status
Not blacklisted
Mail Server Reputation: mail10.corpmailsvcs.com
RBL check ensures server is not blacklisted
MX: mail10.corpmailsvcs.com
Mail server at 198.203.176.100
→
RBL Status
Not blacklisted
Mail Server Reputation: mail11.corpmailsvcs.com
RBL check ensures server is not blacklisted
MX: mail11.corpmailsvcs.com
Mail server at 198.203.176.101
→
RBL Status
Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
TLS not verified or unsupported
→
MTA-STS Policy
MTA-STS not configured
⚠️ TLS support could not be verified. MTA-STS requires TLS to enforce encrypted connections. Without TLS, MTA-STS cannot function.
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
BIMI not 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
TLS not verified or unsupported
→
TLS-RPT Reporting
TLS-RPT not configured
⚠️ TLS support could not be verified. TLS-RPT reports on TLS connection failures, but without TLS support, there's nothing to monitor. You need working TLS encryption before TLS-RPT can provide value.
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/unitedhealth.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan unitedhealth.com Again