Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BCrawlabilityrobots.txt present, no sitemapREVIEW
A sitemap helps search engines discover and index your pages more efficiently.
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.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
############################################
# 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/
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations79 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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
BCDN & DeliveryCloudflare (BYPASS)REVIEW
A+DNS Records2 A records, 13 ms lookupPASS
| A | 104.18.39.209, 172.64.148.47 |
| AAAA | 2a06:98c1:310d::ac40:942f, 2606:4700:4408::6812:27d1 |
| CNAME | — |
| NS | dayana.ns.cloudflare.com, quincy.ns.cloudflare.com |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
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'.
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)
ARedirect Chain1 redirect(s), 458 ms totalPASS
https://www.deepl.com
229 ms · HTTP/1.1
https://www.deepl.com/en
229 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.deepl.com | 301 | 229 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.deepl.com/en | 200 | 229 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (2 ms)PASS
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: www
HTTP → HTTPS
Consistent
A+Domain Intelligencedeepl.com — via Key-Systems GmbH, 16 years, 2 months oldPASS
248 days
April 22, 2027
79 days
Issued by Google Trust Services
16 years, 2 months
Registered April 22, 2010
Not enabled
Protects against DNS spoofing
Unknown
2a06:98c1:3108::ac40:9786
Key-Systems GmbH
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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