Skip to content
https://deepl.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Singapore, Singapore
301 Moved Permanently
Checks
9
5 PASS 4 REVIEW
B
Redirect Chain
2 redirect(s), 795 ms total
REVIEW
2 redirect(s), 795 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Redirect overhead: 795 ms total
Got: 795 ms

https://deepl.com

279 ms · HTTP/1.1

301

https://www.deepl.com/

226 ms · HTTP/1.1

301

https://www.deepl.com/en

289 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://deepl.com301279 msHTTP/1.1cloudflare
2https://www.deepl.com/301226 msHTTP/1.1cloudflare
3https://www.deepl.com/en200289 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1678 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 1678 B Sitemaps referenced 0 User-agents AdsBot-Google-Mobile, Ads-Naver, Y!J-BRY, Y!J-BRZ, Googlebot, Yeti, Y!J-WSC, AdsBot-Google, AdIdxBot, Mediapartners-Google, Bingbot, Y!J-ASR, Slurp, * Blocking No — crawling allowed
############################################
# Last full revision: 2025-07-23
############################################

##### Ads & Monetization #####
User-agent: AdsBot-Google
User-agent: AdsBot-Google-Mobile
User-agent: AdIdxBot
User-agent: Mediapartners-Google
User-agent: Ads-Naver
User-agent: Y!J-BRY
User-agent: Y!J-BRZ
# Full access for ads quality assessment & UTM tracking
Allow: /
# API legacy docs exclusion
Disallow: /*docs-api-legacy$
Disallow: /*docs-api-legacy/
# Cloudflare paths
Disallow: /cdn-cgi/bm/cv/
Disallow: /cdn-cgi/challenge-platform/
Disallow: /cdn-cgi/images/trace/
Disallow: /cdn-cgi/rum
Disallow: /cdn-cgi/scripts/
Disallow: /cdn-cgi/styles/
Disallow: /cdn-cgi/zaraz/

##### Organic #####
User-agent: Googlebot
User-agent: Bingbot
User-agent: Yeti
User-agent: Y!J-ASR
User-agent: Y!J-WSC
User-agent: Slurp
# Block campaign paths & UTM parameters
Disallow: */translator/c/
Disallow: /*utm_campaign=*
Disallow: /*utm_source=linguee*
# API legacy docs exclusion
Disallow: /*docs-api-legacy$
Disallow: /*docs-api-legacy/
# Cloudflare paths
Disallow: /cdn-cgi/bm/cv/
Disallow: /cdn-cgi/challenge-platform/
Disallow: /cdn-cgi/images/trace/
Disallow: /cdn-cgi/rum
Disallow: /cdn-cgi/scripts/
Disallow: /cdn-cgi/styles/
Disallow: /cdn-cgi/zaraz/

##### Everone else #####
User-agent: *
# Explicit access for campaign paths
Allow: */translator/c/
# API legacy docs exclusion
Disallow: /*docs-api-legacy$
Disallow: /*docs-api-legacy/
# Cloudflare paths
Disallow: /cdn-cgi/bm/cv/
Disallow: /cdn-cgi/challenge-platform/
Disallow: /cdn-cgi/images/trace/
Disallow: /cdn-cgi/rum
Disallow: /cdn-cgi/scripts/
Disallow: /cdn-cgi/styles/
Disallow: /cdn-cgi/zaraz/
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
B
CDN & Delivery
Cloudflare (BYPASS)
REVIEW
Cloudflare (BYPASS)
Info::
Site is served via Cloudflare CDN (edge: SIN)
Got: cf-ray: 9ed4fceda928ce17-SIN
Info::
CDN cache status: BYPASS
CDN Detected: Cloudflare
Provider Cloudflare Cache Status BYPASS Evidence cf-ray: 9ed4fceda928ce17-SIN
A+
DNS Records
2 A records, 14 ms lookup
PASS
2 A records, 14 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.36.122, 172.64.151.134
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a06:98c1:3108::ac40:9786, 2606:4700:440b::6812:247a
Info::
2 nameserver(s) configured
Got: michelle.ns.cloudflare.com, walt.ns.cloudflare.com
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 14 ms
Got: 14 ms
A104.18.36.122, 172.64.151.134
AAAA2a06:98c1:3108::ac40:9786, 2606:4700:440b::6812:247a
CNAME—
NSmichelle.ns.cloudflare.com, walt.ns.cloudflare.com
MX
0 smtp.google.com
TXT
MS=ms94938537
anny-verification=b9344e56-9ca1-402b-92e0-d52d4617a353
anthropic-domain-verification-07m7v0=6dGSR1Sz4Pg3xqDBILdsy6FZz
asv=2d27d0ec5b30971dc86859b146205c42
atlassian-domain-verification=G8PDXrPIvyPXuHUYcsdIJDTlpt82slyPnDIZfjins1Z7S2Hvra...
atlassian-sending-domain-verification=e7c9c60e-940c-4236-91b0-3290a1eb3769
cursor-domain-verification-dfadpg=SKzDd4NJxJEWO9JXBpz331IWk
elevenlabs=V_T6sqvcSLcl_KkymzcMgb_ksppzXnFG64me7P9H734
globalsign-domain-verification=sNBl_4fpTdJqJane0PKxdAeWK19VGXmM30hnEORT7q
google-site-verification=8OCSOnLXxintKp6DkZ5fUCTmvNzYFkx9Q_B9gy6LWhI
google-site-verification=N8tNJ1tbGuCuNPNtuBe0PUrHrGxJuiM69hsO28JRrNo
google-site-verification=aN5nHyBfylJ0XADm3qGTWqoV811B7O88AsSQ95l-A_4
google-site-verification=gLwobG7JbfW-Gpoaza41x-z7ntsVOAtLbuLPh12Yevc
google-site-verification=v4W2clGovoFOxvbMWRJn7B4yJcJr-vv9WI0DBQrJ9R4
jetbrains-domain-verification=2yxysrlegfjiy27vu06ni03dd
openai-domain-verification=dv-TMEbUJIVfqY7VdZiCsdWHyOb
reachdesk-verification=Mq12nOjsdbw9vRJMaIpVJnC3oK1CHIE43KujzB4kDK10V25aR1GDe4Dmk...
speechmatics-domain-verification-4h1v3d=1QcApFskilS9M5PSKYFzVgMOG
stripe-verification=277BB3C70938ABB4370AFD712918CF0EEDC7EC1A7FFDCCC3DA215EB034BC...
SPF v=spf1 include:mail.zendesk.com include:amazonses.com include:_spf.salesforce.co...
wework-site-verification=lU60dLWVxcErDMka
zoom-domain-verification=ZOOM_verify_a2dbc6bdd780461dbd0c85d1146e952d
CAALookup not available with standard resolver
Resolved in 14 ms

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.

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2a06:98c1:3108::ac40:9786, 2606:4700:440b::6812:247a
Got: 1 ms connect
IPv6 Ready
AAAA Records 2a06:98c1:3108::ac40:9786, 2606:4700:440b::6812:247a Connection Reachable (1 ms)
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.deepl.com/
200https://deepl.com/

Preferred variant: non-www

HTTP → HTTPS

301http://deepl.com/ → https://deepl.com/

Consistent

A+
Domain Intelligence
deepl.com — via Key-Systems GmbH, 16 years, 2 months old
PASS
deepl.com — via Key-Systems GmbH, 16 years, 2 months old
Info::
Domain registered until Apr 22, 2027 (1 years remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Key-Systems GmbH
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Domain expiry

283 days

April 22, 2027

SSL certificate

39 days

Issued by Google Trust Services

Domain age

16 years, 2 months

Registered April 22, 2010

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a06:98c1:3108::ac40:9786

Registrar

Key-Systems GmbH

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Key-Systems GmbH
Created April 22, 2010 (16 years, 2 months ago)
Expires April 22, 2027 (1 years)
Last Updated March 22, 2026
Name Servers michelle.ns.cloudflare.com, walt.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2a06:98c1:3108::ac40:9786
Data source: rdap (0.6s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A
HTTP Probe Timing
Total 480 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
3 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
6 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
480 ms
Total Time Total request time from DNS lookup through full response.
480 ms

Connection waterfall

DNS Lookup 3 ms TCP Connect 1 ms TLS Handshake 6 ms Server Processing 470 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