Skip to content
https://www.proton.me

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.proton.me/
200https://proton.me/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://www.proton.me/ https://www.proton.me/

Consistent

B
TLS Certificate Expiry & Recommendations
72 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

72
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A
DNS Records
1 A records, 76 ms lookup
PASS
1 A records, 76 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 185.70.42.45
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 76 ms
Got: 76 ms
A185.70.42.45
AAAA
CNAME
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 76 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A
Redirect Chain
1 redirect(s), 276 ms total
PASS
1 redirect(s), 276 ms total
Info::
Single redirect
Got: https://www.proton.me → https://proton.me/ (301)
Info::
WWW normalization redirect

https://www.proton.me

97 ms · HTTP/1.1

301

https://proton.me/

179 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.proton.me30197 msHTTP/1.1
2https://proton.me/200179 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 24 URLs
PASS
robots.txt present, sitemap with 24 URLs
Info::
robots.txt is present
Got: 181 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 24 entries
Info::
Sitemap index with 24 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 181 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wallet/explorer/
Allow: /wallet/explorer/$
Allow: /wallet/explorer/blocks/recent$
Allow: /wallet/explorer/tx/recent$
Sitemap: https://proton.me/sitemap.xml

A+
Domain Intelligence
proton.me — via MarkMonitor Inc., 15 years, 8 months old, hosted on PROTON, CH
PASS
proton.me — via MarkMonitor Inc., 15 years, 8 months old, hosted on PROTON, CH
Info::
Domain registered until Oct 10, 2026 (6 months remaining)
Info::
Registrar: MarkMonitor Inc.
Info::
Hosting: PROTON, CH
Got: AS62371
Domain expiry

90 days

October 10, 2026

SSL certificate

72 days

Issued by Let's Encrypt

Domain age

15 years, 8 months

Registered October 10, 2010

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

PROTON, CH

ASN AS62371

185.70.42.45

Registrar

MarkMonitor Inc.

Lock status unknown 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
Registrar MarkMonitor Inc.
Created October 10, 2010 (15 years, 8 months ago)
Expires October 10, 2026 (6 months)
Last Updated September 13, 2024
Name Servers ns1.proton.me, ns2.proton.me, ns3.proton.me
Registrant Proton AG
Hosting
IP Address 185.70.42.45
ASN AS62371 (PROTON, CH)
Provider PROTON, CH
Data source: whois (1.5s)
A+
HTTP Probe Timing
Total 173 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
74 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
31 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
38 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
173 ms
Total Time Total request time from DNS lookup through full response.
174 ms

Connection waterfall

DNS Lookup 74 ms TCP Connect 31 ms TLS Handshake 38 ms Server Processing 30 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback