STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

comss.ru

comss.ru's public homepage, certificate and DNS checked against 31 practices and compared with 231 Programming & Software sites.

Readiness index
54/100

Programming & Software median 68

Ahead of
16%

of measured Programming & Software sites

Practices observed
15/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

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

Readiness by lane

Green: comss.ru. Thin bar: Programming & Software peer median.

Enable

79/100

Peers 81

Harden

54/100

Peers 59

Accelerate

33/100

Peers 65

Recover

0/100

Peers 7

Priority fixes for comss.ru

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

  1. Priority 1 · Accelerate

    HTTP/2 negotiated

    Observed: The TLS handshake selected http/1.1 instead of HTTP/2.

    Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.

    What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

    92% of Programming & Software peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

  2. Priority 2 · Harden

    HSTS kept for at least a year

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

    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 Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

    40% of Programming & Software peers do this.

  3. Priority 3 · Accelerate

    Static files cached for 30 days or more

    Observed: A same-site stylesheet or script was cacheable for no max-age, 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.

    On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.

    50% of Programming & Software peers do this.

  4. Priority 4 · Harden

    DMARC policy enforces quarantine or reject

    Observed: The DMARC policy for comss.ru was p=none, which asks receivers to take no action on failing mail.

    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.

    45% of Programming & Software peers do this.

What comss.ru already does well

Practices fewer than half of Programming & Software peers use.

  • DNSSEC signedDNSSEC delegation (DS record) present.12% of peers
  • CAA records limit who can issue certificatesCAA limits issuance to comodoca.com, digicert.com, globalsign.com and others.23% of peers

What we saw

Homepage checked
https://www.comss.ru/
Homepage response
HTTP 200
TLS
TLSv1.3, http/1.1
Certificate
Let's Encrypt, 89-day validity, expiring 2027-01-13
DNS operators
Cloudflare
DMARC policy
p=none
Homepage HTML
49 KB, gzip
Images on homepage
49 (png 27, jpg 3, svg 2)

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 15

  • 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
  • DNSSEC signed
  • HTML compressed
  • No render-blocking scripts in <head>
  • robots.txt published
  • XML sitemap discoverable
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Social preview image set
  • At most one redirect to the homepage

Own comss.ru?

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: comss.ru. This profile covers configuration only.

Compare with other Programming & Software sites