Identity
97
B
mailfence.com
Posture Score: 89/100
Scanned May 9, 2026 at 4:38 AM UTC
Score History
Attack Surface
70
Reputation
100
Identity Findings
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 (~7182s) differs significantly from the authoritative zone (~86400s).
💡 Align NS record TTLs between the parent zone delegation and the authoritative zone.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (50 bytes)
SPF record is within safe DNS packet size limits.
DKIM records are valid
DKIM records found and validated for selectors: k1
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
DKIM key strength indicates modern key management
All DKIM keys use RSA-2048+ or Ed25519, consistent with current best practices.
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).
MX records are valid
All MX records are properly configured.
2 MX records with 2 unique IPs
Multiple MX records provide mail delivery redundancy.
MTA-STS and TLS-RPT are properly configured
MTA-STS policy is enforced and TLS reporting is configured.
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.
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.
STARTTLS downgrade resistance is adequate
STARTTLS is supported with modern TLS and protected by MTA-STS and/or DANE.
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.
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/TLSA configured for smtp1.mailfence.com
TLSA records found and TLS certificate is available for verification.
DANE/TLSA configured for smtp2.mailfence.com
TLSA records found and TLS certificate is available for verification.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open mail ports on smtp1.mailfence.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: 2026050210, Refresh: 3600s, Retry: 600s, Expire: 1209600s, Min TTL: 7200s
Authorized certificate authorities
CAA records restrict certificate issuance to: letsencrypt.org
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.
Non-responsive IP for ns1.mailfence.com: 212.3.242.68
The subdomain ns1.mailfence.com resolves to 212.3.242.68 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 212.3.242.68 is operational or remove the DNS record for ns1.mailfence.com.
Non-responsive IP for ns2.mailfence.com: 217.182.28.163
The subdomain ns2.mailfence.com resolves to 217.182.28.163 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 217.182.28.163 is operational or remove the DNS record for ns2.mailfence.com.
DNS ANY query returns 20 record(s)
The DNS server responds to ANY queries with 20 record(s), creating significant DNS amplification risk.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
Software/version information in TXT record
A TXT record contains a software identifier or version string: "212.3.242".
💡 Review TXT records and remove unnecessary software version information.
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 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.
14 subdomain(s) discovered for mailfence.com
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
129 certificate(s) found in CT logs
Certificate Transparency logs contain 129 certificate(s) for mailfence.com and its subdomains. Each certificate reveals subdomain names.
NSEC3 authenticated denial of existence
The domain uses NSEC3 with 10 iteration(s) and salt 'F7A16A705CA684D8'.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
HSTS enabled with preload on mailfence.com
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
security.txt present
Found security.txt at https://mailfence.com/.well-known/security.txt.
TLS certificate valid for 66 days
Certificate for mailfence.com expires on 2026-07-14.
Certificate issued by R12
The certificate for mailfence.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for mailfence.com uses an acceptable signature algorithm.
RSA key: 4096 bits
The certificate for mailfence.com uses an adequate RSA key of 4096 bits.
SCTs present in certificate
The certificate for mailfence.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on mailfence.com.
Domain valid for 2763 days
Domain mailfence.com expires on 2033-12-01.
Domain transfer and delete locks enabled
Domain mailfence.com has clientTransferProhibited and clientDeleteProhibited locks.
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 (smtp1.mailfence.com) uses TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 including Forward Secrecy.
SMTP banner matches infrastructure identity
The SMTP banner (smtp2.mailfence.com) aligns with the MX hostname (smtp2.mailfence.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.
Could not connect to webmail.mailfence.com
HTTPS request to https://webmail.mailfence.com failed or timed out.
WHOIS registration data
Registrar: GoDaddy.com, LLC | Created: 2012-12-01 | Expires: 2033-12-01 | Updated: 2025-12-18
WHOIS privacy protection enabled
Domain mailfence.com has WHOIS privacy/redaction enabled.
Typosquat detected: malfence.com (has MX!), mailfece.com (has MX!), malifence.com (has MX!), maifence.com
4 registered lookalike domain(s) that could be used for phishing against your brand. 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: smtp1.mailfence.com
PTR record proves mail server legitimacy
MX: smtp1.mailfence.com
Mail server at 212.3.242.78
→
PTR Record
Reverse DNS: smtp1.mailfence.com
Mail Server Identity: smtp2.mailfence.com
PTR record proves mail server legitimacy
MX: smtp2.mailfence.com
Mail server at 212.3.242.79
→
PTR Record
Reverse DNS: smtp2.mailfence.com
Mail Server Reputation: smtp1.mailfence.com
RBL check ensures server is not blacklisted
MX: smtp1.mailfence.com
Mail server at 212.3.242.78
→
RBL Status
Not blacklisted
Mail Server Reputation: smtp2.mailfence.com
RBL check ensures server is not blacklisted
MX: smtp2.mailfence.com
Mail server at 212.3.242.79
→
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: enforce
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC policy: reject
→
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/mailfence.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan mailfence.com Again