STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

pink.rs

pink.rs's public homepage, certificate and DNS checked against 31 practices and compared with 3,856 News & Media sites.

Readiness index
38/100

News & Media median 68

Ahead of
<1%

of measured News & Media sites

Practices observed
10/31

0 of 31 could not be measured

Popularity band
Top 5K

Chrome UX Report top-sites list

Measured 2026-10-23 12:09:44 UTC from one location. How we measure

Readiness by lane

Green: pink.rs. Thin bar: News & Media peer median.

Enable

44/100

Peers 89

Harden

23/100

Peers 56

Accelerate

53/100

Peers 68

Recover

100/100

Peers 11

Priority fixes for pink.rs

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

  1. Priority 1 · Harden

    HTTP requests move to HTTPS

    Observed: A request to http://pink.rs/ was not redirected to HTTPS.

    Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.

    What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.

    96% of News & Media peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.

  2. Priority 2 · Enable

    robots.txt published

    Observed: No robots.txt file was returned at the site root.

    What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.

    98% of News & Media 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.

    87% of News & Media peers do this.

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

    35% of News & Media peers do this.

What pink.rs already does well

Practices fewer than half of News & Media peers use.

  • Nameservers spread across providersNameservers spread across more than one operator.11% of peers

What we saw

Homepage checked
https://pink.rs/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Sectigo, 198-day validity, expiring 2026-12-31
DNS operators
2 self-run or other nameserver domains
DMARC policy
p=none
Homepage HTML
160 KB, gzip
Images on homepage
91 (png 59, svg 2, gif 2, jpg 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

Own pink.rs?

Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.

Live status for this site: Status Is Down: pink.rs. This profile covers configuration only.

Compare with other News & Media sites