Website readiness profile · Snapshot 23 October 2026

github.com

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

Readiness index: 86/100
Ahead of: 96%
Practices observed: 23/28
Popularity band: Top 1K

Measured 2026-10-23 11:25:16 UTC from one location. How we measure

Readiness by lane

Green: github.com. Thin bar: Programming & Software peer median.

Enable

71/100

Peers 81

Harden

95/100

Peers 59

Accelerate

88/100

Peers 65

Recover

100/100

Peers 7

Priority fixes for github.com

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

Priority 1 · Enable
XML sitemap discoverable
Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.
Why it matters: A sitemap helps search engines find new and updated pages, especially on large or frequently updated sites.
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. Limit: Only the standard location was requested, once, at the time of the check.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 2 · Accelerate
HTTP/3 advertised
Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.
What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.
40% of Programming & Software peers do this.
Guide: CDN Guide for Website Owners
Priority 3 · Enable
Structured data present
Observed: The homepage had no JSON-LD structured data.
What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.
52% of Programming & Software peers do this.
Guide: Structured Data Basics for Website Owners
Priority 4 · Enable
Reachable over IPv6
Observed: No IPv6 (AAAA) address was published for github.com.
What to do: Enable IPv6 at your CDN or host and publish the AAAA record it provides.
62% of Programming & Software peers do this.
Guide: How to Evaluate Web Hosting Performance

What github.com already does well

Practices fewer than half of Programming & Software peers use.

Nameservers spread across providersNameservers spread across Amazon Route 53 and NS1.7% of peers
security.txt publishedsecurity.txt with a contact found.15% of peers
CAA records limit who can issue certificatesCAA limits issuance to digicert.com, globalsign.com, letsencrypt.org and others.23% of peers

What we saw

Homepage checked: https://github.com/
Homepage response: HTTP 200
TLS: TLSv1.3, HTTP/2
Certificate: Sectigo, 89-day validity, expiring 2026-11-29
CDN or edge: GitHub Pages
DNS operators: Amazon Route 53, NS1
HSTS: max-age 365 days, includeSubDomains, preload
DMARC policy: p=quarantine
Homepage HTML: 567 KB, gzip
Images on homepage: 25 (webp 16, svg 6, 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.

Amazon Route 53 (dns operator)NS1 (dns operator)Sectigo (certificate authority)Service guide: AWS (Amazon Web Services)

All 31 checks

Select a gap for the method and fix. How each check works

Not observed 5

Observed 23

HSTS kept for at least a year
TLS 1.3 negotiated
Certificate has more than 14 days left
Certificate lifetime of 100 days or less
CAA records limit who can issue certificates
security.txt published
DMARC policy enforces quarantine or reject
X-Content-Type-Options: nosniff
Framing restricted
Content Security Policy present
Referrer-Policy set
HTTP/2 negotiated
HTML compressed
Modern image formats in use
Offscreen images lazy-loaded
No render-blocking scripts in <head>
Canonical URL declared
Meta description written
Mobile viewport configured
Social preview image set
Page language declared
At most one redirect to the homepage
Nameservers spread across providers

Not measured 3

HTTP requests move to HTTPS
Static files cached for 30 days or more
robots.txt published

Own github.com?

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

Re-check github.com now Add to owner workspace Request a correction or removal

Live status for this site: Status Is Down: github.com. This profile covers configuration only.

Compare with other Programming & Software sites

Programming & Software readiness benchmark