sat.box

Readiness by lane

Green: sat.box. Thin bar: Uncategorized peer median.

Priority fixes for sat.box

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

1. Priority 1 · Enable

   robots.txt published

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

   Why it matters: robots.txt is where crawlers look first for crawl rules and sitemap locations. Without it, they assume everything is open.

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

   88% of Uncategorized peers do this. Limit: Only the standard location was requested, once, at the time of the check.

   Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes

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

   75% of Uncategorized peers do this.

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

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

   34% of Uncategorized peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.sat.box.

   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.

   39% of Uncategorized peers do this.

   Guide: A Practical Website Health Check for Owners

What sat.box already does well

Practices fewer than half of Uncategorized peers use.

• No render-blocking scripts in <head>Head scripts load without blocking.37% of peers

What we saw

Homepage checked

http://sat.box/

Homepage response

HTTP 200, after 3 redirects

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-11-24

CDN or edge

Amazon CloudFront

DNS operators

1 self-run or other nameserver domain

Homepage HTML

11 KB, gzip

Images on homepage

2 (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 Uncategorized sites

• astrosage.com47
• astrotheme.fr47
• lotteryextreme.com48
• mobiles24.co49
• vestirna.com49

Uncategorized readiness benchmark