STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

git-scm.com

git-scm.com's public homepage, certificate and DNS checked against 31 practices and compared with 231 Programming & Software sites.

Readiness index
40/100

Programming & Software median 68

Ahead of
3%

of measured Programming & Software sites

Practices observed
10/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 11:42:31 UTC from one location. How we measure

Readiness by lane

Green: git-scm.com. Thin bar: Programming & Software peer median.

Enable

38/100

Peers 81

Harden

43/100

Peers 59

Accelerate

38/100

Peers 65

Recover

0/100

Peers 7

Priority fixes for git-scm.com

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.

    91% of Programming & Software peers do this. Limit: Only the standard location was requested, once, at the time of the check.

  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 4 hours, 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 · 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.

    69% of Programming & Software peers do this.

What we saw

Homepage checked
https://git-scm.com/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Google Trust Services, 90-day validity, expiring 2026-12-18
CDN or edge
Cloudflare, Fastly
Platform or framework
Hugo
DNS operators
Cloudflare
Homepage HTML
6 KB, gzip
Images on homepage
10 (svg 7, png 3)

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 git-scm.com?

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: git-scm.com. This profile covers configuration only.

Compare with other Programming & Software sites