Identity
55
F
mail.com
Posture Score: 45/100
Scanned May 30, 2026 at 4:29 AM UTC
Attack Surface
47
Reputation
32
Identity Findings
No MX records found
The domain has no MX records and cannot receive email.
💡 Publish MX records pointing to your mail server(s).
No NS records found
No nameserver records could be retrieved for this domain.
💡 Ensure NS records are properly configured at your registrar and in your zone file.
Cannot check DNS consistency — no NS records
No nameserver records could be retrieved for consistency checking.
💡 Ensure NS records are properly configured.
No DKIM records found
No DKIM records were found after probing 56 common selectors. The domain may use a custom selector not discoverable via external scan.
💡 Configure DKIM signing and publish the public key at <selector>._domainkey.mail.com
MTA-STS is in testing mode
The MTA-STS policy is in testing mode and not actively enforcing TLS.
💡 Switch mode to "enforce" once TLS is confirmed working for all MX hosts.
ARC check skipped — no MX records
Cannot assess ARC support without MX records.
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"
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (29 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.
No external DMARC report destinations
All DMARC report URIs point to the same domain — no external authorization needed.
Subdomains protected (sp=quarantine)
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).
TLS-RPT report destinations are reachable
All TLS-RPT rua= URIs point to resolvable domains.
Meets bulk sender authentication requirements
Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.
DNS TTL values follow best practices
All critical DNS record TTLs are within recommended ranges.
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.
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.
DANE check skipped — no MX records
Cannot check DANE/TLSA without MX records.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open relay check skipped — no MX records
Cannot test for open relay without MX records.
SMTP compliance check skipped — no MX records
Cannot test SMTP compliance without MX records.
Port exposure check skipped — no MX records
Cannot scan ports without MX records.
Domain is IPv4-only
No AAAA records found for the domain, MX servers, or nameservers. The domain operates on IPv4 only.
STARTTLS downgrade check skipped — no MX records
Cannot test STARTTLS without MX records.
RFC 8058 one-click unsubscribe assessment
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
FCrDNS check skipped — no MX records
Cannot perform FCrDNS without MX records.
SOA record parameters
Serial: 2013096257, Refresh: 14400s, Retry: 3600s, Expire: 605000s, Min TTL: 600s
Authorized certificate authorities
CAA records restrict certificate issuance to: sectigo.com, telesec.de, digicert.com, Digicert.com
Attack Surface Findings
Non-routable IPv4 in public DNS: ns1.mail.com → 127.0.0.1
The subdomain ns1.mail.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv6 in public DNS: ns1.mail.com → ::1
The subdomain ns1.mail.com resolves to non-routable IPv6 ::1, leaking internal network information.
💡 Remove non-routable IPv6 addresses from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: ns2.mail.com → 127.0.0.1
The subdomain ns2.mail.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv6 in public DNS: ns2.mail.com → ::1
The subdomain ns2.mail.com resolves to non-routable IPv6 ::1, leaking internal network information.
💡 Remove non-routable IPv6 addresses from public DNS or implement split-horizon DNS.
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 25 record(s)
The DNS server responds to ANY queries with 25 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.
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 email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
11 subdomain(s) discovered for mail.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 mail.com and its subdomains. Each certificate reveals subdomain names.
NSEC3 authenticated denial of existence
The domain uses NSEC3 with 27 iteration(s) and salt '539B51B24809A5F4'.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
Listed on dnsbl-2.uceprotect.net
74.208.5.20 (mx00.mail.com) is listed on blacklist dnsbl-2.uceprotect.net (response: 127.0.0.2).
💡 Visit the dnsbl-2.uceprotect.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl-3.uceprotect.net
74.208.5.20 (mx00.mail.com) is listed on blacklist dnsbl-3.uceprotect.net (response: 127.0.0.2).
💡 Visit the dnsbl-3.uceprotect.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl-2.uceprotect.net
74.208.5.22 (mx01.mail.com) is listed on blacklist dnsbl-2.uceprotect.net (response: 127.0.0.2).
💡 Visit the dnsbl-2.uceprotect.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl-3.uceprotect.net
74.208.5.22 (mx01.mail.com) is listed on blacklist dnsbl-3.uceprotect.net (response: 127.0.0.2).
💡 Visit the dnsbl-3.uceprotect.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Missing domain locks: clientDeleteProhibited
Domain mail.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
HSTS enabled with preload on mail.com
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
security.txt present
Found security.txt at https://mail.com/.well-known/security.txt.
TLS certificate valid for 137 days
Certificate for mail.com expires on 2026-10-14.
Certificate issued by Sectigo Public Server Authentication CA OV R36
The certificate for mail.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for mail.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for mail.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for mail.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on mail.com.
Domain valid for 298 days
Domain mail.com expires on 2027-03-25.
No disposable email provider MX records
MX records for mail.com do not match known disposable email provider patterns.
Domain is 10658 days old
Domain mail.com was registered 1997-03-24.
No wildcard MX records
No wildcard MX records detected for mail.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 (mx01.mail.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner matches infrastructure identity
The SMTP banner (mail.com) aligns with the MX hostname (mx00.mail.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 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.mail.com
HTTPS request to https://webmail.mail.com failed or timed out.
WHOIS registration data
Registrar: World4You Internet Services GmbH | Created: 1997-03-24 | Expires: 2027-03-25 | Updated: 2026-03-26
WHOIS privacy protection enabled
Domain mail.com has WHOIS privacy/redaction enabled.
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: mil.com (has MX!), mial.com (has MX!), mqil.com (has MX!), mwil.com (has MX!), msil.com (has MX!)
26 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 26. 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: quarantine
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: quarantine
⚠️ 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: mx00.mail.com
PTR record proves mail server legitimacy
MX: mx00.mail.com
Mail server at 74.208.5.20
→
PTR Record
Reverse DNS: mx00.mail.com
Mail Server Identity: mx01.mail.com
PTR record proves mail server legitimacy
MX: mx01.mail.com
Mail server at 74.208.5.22
→
PTR Record
Reverse DNS: mx01.mail.com
Mail Server Reputation: mx00.mail.com
RBL check ensures server is not blacklisted
MX: mx00.mail.com
Mail server at 74.208.5.20
→
RBL Status
Not blacklisted
Mail Server Reputation: mx01.mail.com
RBL check ensures server is not blacklisted
MX: mx01.mail.com
Mail server at 74.208.5.22
→
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
Mode: testing
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC policy: quarantine
→
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 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/mail.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan mail.com Again