GitHub Pages Detector
Paste any URL and instantly see whether the site is built with GitHub Pages — with the matched evidence.
We do not store the URL you audit. Want the full audit (performance / images / SEO / accessibility + real-browser speed test)? → run the full audit
Why check this
Confirm the platform first: Hosting & CDN decides what can be changed and whether it is worth it.
What this is
GitHub Pages hosts static sites for docs, project home pages and personal sites. Confirming `x-github-request-id` or `server: GitHub.com` shows whether custom domains, HTTPS and build sources are configured correctly. Custom domains and HTTPS settings matter as much as the static files themselves.
How to tell from a public page
- [GitHub Pages] Response headers include `x-github-request-id`.
- [GitHub Pages] The `server` header names GitHub.com.
- [GitHub Pages] Default hosts follow a `github.io` shape.
- [GitHub Pages] Publish workflows leave Actions build traces when public.
How to read the result
Confirm when platform headers reproduce; a repository badge does not qualify. Absence can mean Cloudflare or similar proxies in front. Documentation sample headers occasionally leak into blog posts. After a hit, check whether large assets should move to an external CDN.
What to do next
Compress static assets, self-host fonts, and verify the generator — often Jekyll — via Jekyll detector. Combined vitals return via run the full performance / images / SEO / accessibility audit on the home page. Prefer compressed assets before renting a heavier host.
Related detectors
FAQ
How is GitHub Pages detected?
From structural signatures in the public HTML and response headers (domains, paths, attributes, scripts). Every verdict lists how many times each pattern matched — nothing is guessed.
Can the result be wrong?
If only a bare brand keyword matches without structural evidence, we label it \u201clikely\u201d instead of \u201cconfirmed\u201d — we would rather under-report than cry wolf.
Do you save the URLs I check?
No. The audit runs inside the request and the URL you paste is not written to storage. There are no third-party tracking scripts on the page either, so no log of who checked what exists. Copy the result yourself if you want a record.
Can a website hide what it is built with?
Partly, but rarely completely. The HTML sent to your browser, the response headers, script paths and asset structure have to be exposed to work, so there is always something readable. Server-side code, build config and private APIs stay invisible. That is why this tool reports the evidence it found rather than claiming a full picture. No match does not mean the technology is absent.
Optimization help is available
Tell me your URL and what you want fixed — you get a clear scope, price and timeline.
To：[email protected] | Cc：[email protected]
