diamond-rm.net

Readiness by lane

Green: diamond-rm.net. Thin bar: News & Media peer median.

Priority fixes for diamond-rm.net

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://diamond-rm.net/ 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.

   On WordPress: Set both WordPress Address and Site Address to https:// in Settings > General, then add the server or CDN redirect.

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

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Enable

   Mobile viewport configured

   Observed: The homepage had no viewport meta tag, so phones may render it zoomed out.

   What to do: Add <meta name="viewport" content="width=device-width, initial-scale=1"> and check the layout on small screens.

   98% of News & Media peers do this.

   Guide: Responsive Web Design Checklist for Real Devices

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.

   On WordPress: WordPress has generated a basic sitemap at /wp-sitemap.xml since 5.5; SEO plugins can replace it.

   87% of News & Media peers do this.

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

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.

   Guide: HTTPS and TLS Guide for Website Owners

What diamond-rm.net already does well

Practices fewer than half of News & Media peers use.

• X-Content-Type-Options: nosniffnosniff header present.42% of peers
• Framing restrictedFraming controls present.42% of peers
• Modern image formats in useWebP or AVIF images detected.44% of peers

What we saw

Homepage checked

https://diamond-rm.net/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-03-30

Platform or framework

WordPress

DNS operators

Xserver/Value-Domain DNS

DMARC policy

p=none

Homepage HTML

351 KB, br

Images on homepage

271 (jpg 334, png 132)

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 News & Media sites

• blabbermouth.net51
• botasot.info51
• dallasnews.com51
• diariodeburgos.es51
• dn.no51

News & Media readiness benchmark