ovhcloud.com

Readiness by lane

Green: ovhcloud.com. Thin bar: Web Hosting & Infrastructure peer median.

Priority fixes for ovhcloud.com

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

   On Next.js: Add the header in the headers() option of next.config.js for all routes.

   53% of Web Hosting & Infrastructure peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 900 seconds, short of the 30-day benchmark.

   What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

   65% of Web Hosting & Infrastructure peers do this.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

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

   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.

   50% of Web Hosting & Infrastructure peers do this.

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

4. Priority 4 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   On Drupal: The Security Kit module includes CSP settings.

   50% of Web Hosting & Infrastructure peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What ovhcloud.com already does well

Practices fewer than half of Web Hosting & Infrastructure peers use.

• Nameservers spread across providersNameservers spread across more than one operator.18% of peers
• security.txt publishedsecurity.txt with a contact found.37% of peers

What we saw

Homepage checked

https://www.ovhcloud.com/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-30

Platform or framework

Drupal, Next.js, PrestaShop

DNS operators

OVHcloud DNS, plus 1 self-run or other nameserver domain

DMARC policy

p=quarantine

Homepage HTML

1,009 KB, br

Images on homepage

25 (png 43, webp 20, svg 9, jpg 3)

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 Hosting & Infrastructure sites

• ionos.de77
• ionos.es77
• netlify.com70
• pgyer.com57
• strato.de77

Web Hosting & Infrastructure readiness benchmark