rusprofile.ru

Readiness by lane

Green: rusprofile.ru. Thin bar: Data & Analytics peer median.

Priority fixes for rusprofile.ru

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

1. Priority 1 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

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

   Guide: HTTPS and TLS Guide for Website Owners

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.

   34% of Data & Analytics peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   Modern image formats in use

   Observed: The homepage had 23 images and none used WebP or AVIF.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   31% of Data & Analytics peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

4. Priority 4 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   51% of Data & Analytics peers do this.

   Guide: A Practical Website Health Check for Owners

What rusprofile.ru already does well

Practices fewer than half of Data & Analytics peers use.

• Content Security Policy presentContent-Security-Policy present.24% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.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.rusprofile.ru/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

GlobalSign, 199-day validity, expiring 2027-04-05

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=reject

Homepage HTML

133 KB, gzip

Images on homepage

23 (png 68, 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

Compare with other Data & Analytics sites

• abr.ge63
• deeplol.gg65
• flightstats.com64
• statsforspotify.com64
• ytultra.com65

Data & Analytics readiness benchmark