Identity
83
B
proton.me
Posture Score: 84/100
Scanned May 9, 2026 at 1:07 AM UTC
Attack Surface
70
Reputation
100
Identity Findings
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.proton.me
No DMARC aggregate report URI (rua=)
Without rua=, you will not receive aggregate reports about authentication results.
💡 Add rua=mailto:dmarc-reports@proton.me to your DMARC record.
BIMI record missing logo URL (l= tag)
The BIMI record does not specify a logo URL.
💡 Add l=https://example.com/logo.svg to the BIMI record.
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.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
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.
MTA-STS and TLS-RPT are properly configured
MTA-STS policy is enforced and TLS reporting is configured.
ARC support likely available
MX server software appears to support ARC headers for authentication preservation.
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.
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=s, aspf=s
DKIM alignment is strict, SPF alignment is strict.
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.
DANE/TLSA configured for mail.protonmail.ch
TLSA records found and TLS certificate is available for verification.
DANE/TLSA configured for mailsec.protonmail.ch
TLSA records found and TLS certificate is available for verification.
Open mail ports on mail.protonmail.ch
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
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
MX IP network diversity
MX IPs span 3 different /16 networks, providing good diversity.
SOA record parameters
Serial: 2026042425, Refresh: 1200s, Retry: 144s, Expire: 1814400s, Min TTL: 7200s
Authorized certificate authorities
CAA records restrict certificate issuance to: letsencrypt.org, sectigo.com
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.proton.me: 185.70.42.150
The subdomain ns1.proton.me resolves to 185.70.42.150 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 185.70.42.150 is operational or remove the DNS record for ns1.proton.me.
Non-responsive IP for ns2.proton.me: 176.119.200.150
The subdomain ns2.proton.me resolves to 176.119.200.150 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 176.119.200.150 is operational or remove the DNS record for ns2.proton.me.
DNS ANY query returns 44 record(s)
The DNS server responds to ANY queries with 44 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.
Mozilla Autoconfig endpoint detected
The Autoconfig endpoint at autoconfig.proton.me is publicly accessible and exposes mail server configuration details.
💡 Review the autoconfig XML to ensure it does not expose internal server names or sensitive configuration.
No internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
10 subdomain(s) discovered for proton.me
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 proton.me and its subdomains. Each certificate reveals subdomain names.
NSEC3 authenticated denial of existence
The domain uses NSEC3 with 0 iteration(s) and salt '-'.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
HSTS enabled with preload on proton.me
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
security.txt present
Found security.txt at https://proton.me/.well-known/security.txt.
TLS certificate valid for 41 days
Certificate for proton.me expires on 2026-06-19.
Certificate issued by R13
The certificate for proton.me is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for proton.me uses an acceptable signature algorithm.
RSA key: 4096 bits
The certificate for proton.me uses an adequate RSA key of 4096 bits.
SCTs present in certificate
The certificate for proton.me contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on proton.me.
Domain valid for 154 days
Domain proton.me expires on 2026-10-10.
Domain transfer and delete locks enabled
Domain proton.me has clientTransferProhibited and clientDeleteProhibited locks.
TLD has good reputation
The .me 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.
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.proton.me
HTTPS request to https://webmail.proton.me failed or timed out.
WHOIS registration data
Registrar: MarkMonitor Inc. | Created: 2010-10-10 | Expires: 2026-10-10 | Updated: 2024-09-13
WHOIS privacy protection enabled
Domain proton.me has WHOIS privacy/redaction enabled.
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: mail.protonmail.ch
PTR record proves mail server legitimacy
MX: mail.protonmail.ch
Mail server at 185.205.70.128
→
PTR Record
Reverse DNS: mail.protonmail.ch
Mail Server Identity: mailsec.protonmail.ch
PTR record proves mail server legitimacy
MX: mailsec.protonmail.ch
Mail server at 176.119.200.129
→
PTR Record
Reverse DNS: mailsec.protonmail.ch
Mail Server Reputation: mail.protonmail.ch
RBL check ensures server is not blacklisted
MX: mail.protonmail.ch
Mail server at 185.205.70.128
→
RBL Status
Not blacklisted
Mail Server Reputation: mailsec.protonmail.ch
RBL check ensures server is not blacklisted
MX: mailsec.protonmail.ch
Mail server at 176.119.200.129
→
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: quarantine
→
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 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/proton.me.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan proton.me Again