STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

discordstatus.com

discordstatus.com's public homepage, certificate and DNS checked against 31 practices and compared with 469 Business Tools sites.

Readiness index
67/100

Business Tools median 63

Ahead of
58%

of measured Business Tools sites

Practices observed
17/27

4 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 12:01:59 UTC from one location. How we measure

Readiness by lane

Green: discordstatus.com. Thin bar: Business Tools peer median.

Enable

67/100

Peers 75

Harden

63/100

Peers 57

Accelerate

79/100

Peers 60

Recover

n/a/100

Peers 6

Priority fixes for discordstatus.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: Strict-Transport-Security was sent with a max-age of 3 days, below the one-year benchmark.

    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 Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

    45% of Business Tools peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

  2. Priority 2 · Harden

    DMARC policy enforces quarantine or reject

    Observed: No DMARC record was found at _dmarc.discordstatus.com.

    What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

    50% of Business Tools peers do this.

  3. Priority 3 · 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.

    61% of Business Tools peers do this.

  4. Priority 4 · Accelerate

    No render-blocking scripts in <head>

    Observed: The homepage <head> loaded 2 external scripts 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.

    46% of Business Tools peers do this.

What discordstatus.com already does well

Practices fewer than half of Business Tools peers use.

  • security.txt publishedsecurity.txt with a contact found.9.4% of peers
  • CAA records limit who can issue certificatesCAA limits issuance to amazon.com, digicert.com, globalsign.com and others.16% of peers
  • Referrer-Policy setReferrer-Policy present.28% of peers

What we saw

Homepage checked
https://discordstatus.com/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Let's Encrypt, 89-day validity, expiring 2027-01-09
CDN or edge
Amazon CloudFront
HSTS
max-age 3 days
Homepage HTML
130 KB, br
Images on homepage
1 (png 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

Observed 17

  • HTTP requests move to HTTPS
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • Certificate lifetime of 100 days or less
  • CAA records limit who can issue certificates
  • security.txt published
  • X-Content-Type-Options: nosniff
  • Referrer-Policy set
  • HTTP/2 negotiated
  • HTTP/3 advertised
  • HTML compressed
  • robots.txt published
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Page language declared
  • At most one redirect to the homepage

Not measured 4

  • Static files cached for 30 days or more
  • Modern image formats in use
  • Offscreen images lazy-loaded
  • Nameservers spread across providers

Own discordstatus.com?

Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.

Live status for this site: Status Is Down: discordstatus.com. This profile covers configuration only.

Compare with other Business Tools sites