wolframalpha.com

Readiness by lane

Green: wolframalpha.com. Thin bar: Data & Analytics peer median.

Priority fixes for wolframalpha.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.

   34% of Data & Analytics 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 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

   63% of Data & Analytics peers do this.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

3. Priority 3 · Enable

   Canonical URL declared

   Observed: The homepage did not declare a canonical URL.

   What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

   65% of Data & Analytics peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

4. Priority 4 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   37% of Data & Analytics peers do this.

   Guide: CDN Guide for Website Owners

What wolframalpha.com already does well

Practices fewer than half of Data & Analytics peers use.

• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.38% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.49% of peers

What we saw

Homepage checked

https://www.wolframalpha.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

GoDaddy, 365-day validity, expiring 2026-12-03

Platform or framework

Next.js

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=quarantine

Homepage HTML

177 KB, gzip

Images on homepage

2 (png 1, svg 1)

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 Data & Analytics sites

• asiakastieto.fi62
• botpower.ca62
• nperf.com63
• s-dri.com63
• statcounter.com63

Data & Analytics readiness benchmark