deepl.com

Readiness by lane

Green: deepl.com. Thin bar: Web Tools peer median.

Priority fixes for deepl.com

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   Why it matters: A plain <script src> in the head stops the browser from showing anything until that file has downloaded and run.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   On Next.js: Use the next/script component with an appropriate loading strategy.

   69% of Web Tools peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

   Guide: Control Third-Party Scripts Before They Control Your Page

2. Priority 2 · Harden

   DNSSEC signed

   Observed: No DS record was found for deepl.com at its parent zone, so its DNS answers are not DNSSEC-signed.

   What to do: Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.

   On Cloudflare: Enable DNSSEC in DNS > Settings and add the DS record at the registrar.

   9.3% of Web Tools peers do this.

   Guide: Website Uptime Readiness: Prepare Before Traffic Arrives

3. Priority 3 · Recover

   Nameservers spread across providers

   Observed: All nameservers for deepl.com belong to Cloudflare.

   What to do: Treat this as an advanced step. Add a secondary DNS provider through zone transfers or a multi-provider setup, then test changes carefully, since both providers must stay in sync.

   On Cloudflare: Cloudflare supports zone transfers for primary or secondary DNS setups on eligible plans.

   6.1% of Web Tools peers do this.

   Guide: Website Uptime Readiness: Prepare Before Traffic Arrives

What deepl.com already does well

Practices fewer than half of Web Tools peers use.

• security.txt publishedsecurity.txt with a contact found.4.8% of peers
• CAA records limit who can issue certificatesCAA limits issuance to amazon.com, amazonaws.com, amazontrust.com and others.14% of peers
• Content Security Policy presentContent-Security-Policy present.15% of peers

What we saw

Homepage checked

https://www.deepl.com/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2026-12-20

CDN or edge

Cloudflare

Platform or framework

Next.js

DNS operators

Cloudflare

HSTS

max-age 730 days, includeSubDomains, preload

DMARC policy

p=reject

Homepage HTML

326 KB, br

Images on homepage

67 (svg 25, png 13, webp 2)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Web Tools sites

• astrologyfutureeye.com95
• firefox.com90
• grizzlysms.com91
• ingles.com91
• reverselookup.com90

Web Tools readiness benchmark