Identity
56
D
thehartford.com
Posture Score: 66/100
Scanned May 17, 2026 at 10:42 PM UTC
Attack Surface
58
Reputation
83
Identity Findings
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.
Weak DKIM RSA key (~1296 bits) for selector 'smtp'
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.
MX hostname does not resolve: ms46086885.msv1.invalid
The MX hostname has no A or AAAA records.
💡 Ensure the MX hostname resolves to a valid IP address.
MX hostname does not resolve: ms29530564.msv1.invalid
The MX hostname has no A or AAAA records.
💡 Ensure the MX hostname resolves to a valid IP address.
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.thehartford.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 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@thehartford.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: 113s
8 NS records have a TTL of 113s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on DMARC record: 90s
The DMARC record has a TTL of 90s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (56 bytes)
SPF record is within safe DNS packet size limits.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
All external report destinations authorized
External DMARC report destinations have valid authorization records per RFC 7489 §7.1.
Subdomains protected (sp=reject)
DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
BIMI record is valid
BIMI is properly configured with a valid logo and DMARC enforcement.
Meets bulk sender authentication requirements
Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.
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.
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.
DMARC failure reporting: fo=1
Failure reports generated when any authentication mechanism fails.
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.
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.
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.
Open mail ports on mx0a-001bde01.pphosted.com
Detected open mail-related ports: 25
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
DKIM signing is configured. RFC 8058 compliance depends on List-Unsubscribe and List-Unsubscribe-Post headers being included in outbound messages and DKIM signatures.
MX IP network diversity
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 2026051402, Refresh: 1800s, Retry: 900s, Expire: 604800s, Min TTL: 120s
Authorized certificate authorities
CAA records restrict certificate issuance to: identrust.com, digicert.com
Attack Surface Findings
Dangling MX: ms46086885.msv1.invalid does not resolve
The MX record points to ms46086885.msv1.invalid which has no A record. This may indicate a decommissioned mail provider (Unknown). Attackers can potentially re-register this hostname to hijack inbound mail.
💡 Remove the stale MX record pointing to ms46086885.msv1.invalid or update it to your current mail provider.
Dangling MX: ms29530564.msv1.invalid does not resolve
The MX record points to ms29530564.msv1.invalid which has no A record. This may indicate a decommissioned mail provider (Unknown). Attackers can potentially re-register this hostname to hijack inbound mail.
💡 Remove the stale MX record pointing to ms29530564.msv1.invalid or update it to your current mail provider.
DNS ANY query returns 88 record(s)
The DNS server responds to ANY queries with 88 record(s), creating significant DNS amplification risk.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
Domain enumerability: medium
The domain has moderate enumerability. CT logs and DNS records reveal significant information about the domain structure.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
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.
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.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
11 subdomain(s) discovered for thehartford.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 thehartford.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
Listed on bl.mailspike.net
148.163.139.63 (mx0b-001bde01.pphosted.com) is listed on blacklist bl.mailspike.net (response: 127.0.0.11).
💡 Visit the bl.mailspike.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
HSTS enabled but missing preload directive on thehartford.com
Strict-Transport-Security: max-age=0; includeSubDomains
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
Missing security.txt
No security.txt found at https://thehartford.com/.well-known/security.txt.
💡 Create a /.well-known/security.txt file per RFC 9116 with Contact, Expires, and optionally Encryption and Policy fields.
TLS certificate valid for 88 days
Certificate for thehartford.com expires on 2026-08-14.
Certificate issued by TrustID Server CA O1
The certificate for thehartford.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for thehartford.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for thehartford.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for thehartford.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on thehartford.com.
No disposable email provider MX records
MX records for thehartford.com do not match known disposable email provider patterns.
No wildcard MX records
No wildcard MX records detected for thehartford.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
DMARC reporting destinations look legitimate
DMARC rua/ruf addresses do not point to known URL shortener services.
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
Strong TLS configuration on primary MX
Primary MX (mx0b-001bde01.pphosted.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner from hosted mail provider
The MX (mx0b-001bde01.pphosted.com) is a hosted mail service. Banner alignment is managed by the provider and not actionable by the domain owner.
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 contacts found for MX IPs
Abuse contact information retrieved via abusix.org DNS lookup.
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 webmail.thehartford.com
HTTPS request to https://webmail.thehartford.com failed or timed out.
WHOIS lookup failed
Could not retrieve WHOIS data for thehartford.com.
Could not determine domain age
WHOIS creation date could not be parsed for thehartford.com.
Bulletproof Hosting Detection — API key required
Checking IPs against known bulletproof hosting providers requires a threat intelligence API key.
Threat Intelligence Feeds — API key required
Checking domain against threat intelligence feeds requires API keys (e.g., VirusTotal, AbuseIPDB).
Typosquat detected: hehartford.com (has MX!), tehartford.com (has MX!), thhartford.com (has MX!), thehrtford.com (has MX!), thehatford.com (has MX!)
17 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 17. 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 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: mx0a-001bde01.pphosted.com
PTR record proves mail server legitimacy
MX: mx0a-001bde01.pphosted.com
Mail server at 148.163.135.63
→
PTR Record
Reverse DNS: mx0a-001bde01.pphosted.com
Mail Server Identity: mx0b-001bde01.pphosted.com
PTR record proves mail server legitimacy
MX: mx0b-001bde01.pphosted.com
Mail server at 148.163.139.63
→
PTR Record
Reverse DNS: mx0b-001bde01.pphosted.com
Mail Server Identity: ms46086885.msv1.invalid
PTR record proves mail server legitimacy
MX: ms46086885.msv1.invalid
Mail server at ms46086885.msv1.invalid
→
PTR Record
No PTR record
⚠️ Mail server ms46086885.msv1.invalid (ms46086885.msv1.invalid) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: ms29530564.msv1.invalid
PTR record proves mail server legitimacy
MX: ms29530564.msv1.invalid
Mail server at ms29530564.msv1.invalid
→
PTR Record
No PTR record
⚠️ Mail server ms29530564.msv1.invalid (ms29530564.msv1.invalid) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Reputation: mx0a-001bde01.pphosted.com
RBL check ensures server is not blacklisted
MX: mx0a-001bde01.pphosted.com
Mail server at 148.163.135.63
→
RBL Status
Not blacklisted
Mail Server Reputation: mx0b-001bde01.pphosted.com
RBL check ensures server is not blacklisted
MX: mx0b-001bde01.pphosted.com
Mail server at 148.163.139.63
→
RBL Status
Not blacklisted
Mail Server Reputation: ms46086885.msv1.invalid
RBL check ensures server is not blacklisted
MX: ms46086885.msv1.invalid
Mail server at ms46086885.msv1.invalid
→
RBL Status
Not blacklisted
Mail Server Reputation: ms29530564.msv1.invalid
RBL check ensures server is not blacklisted
MX: ms29530564.msv1.invalid
Mail server at ms29530564.msv1.invalid
→
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
Brand logo configured
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/thehartford.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan thehartford.com Again