What GitHub Pages is
GitHub Pages publishes static files directly from a repository, served through a CDN with automatic TLS for custom domains. It hosts no server-side code, so anything dynamic on a Pages site is running in the browser or calling a separate service.
How DNSTrace.dev detects it
Detection correlates independent public signals. A single match is reported as strong evidence; agreement between a response header and the announcing network is reported as confirmed.
x-github-request-id— Per-request identifier issued by GitHub's serving layer.server: GitHub.com— Present on Pages responses.CNAME targets under github.io— The standard custom-domain mapping for a user, organisation or project site.Published apex A records— GitHub documents four IPv4 addresses for apex domains, which is why an address match alone is weak evidence shared by every Pages site.
What a detection proves
The files were served by GitHub Pages.
What it does not prove
Which repository or account publishes the site, or whether a separate CDN sits in front. A proxy placed ahead of Pages can mask these headers entirely.
Common questions
Can GitHub Pages run server-side code?
No. Pages serves static files only. Any dynamic behaviour comes from client-side code or an external API.
Does an apex IP match prove GitHub Pages?
It is weak on its own because every apex Pages domain uses the same documented addresses. DNSTrace.dev wants a response header or a github.io target to confirm.
Compare with
NetlifyNetlify, Inc.
Frontend application platform
VercelVercel, Inc.
CDN, reverse proxy and WAF
CloudflareCloudflare, Inc.
Application platform
Fly.ioFly.io, Inc.
Check a domain
Run a full lookup to see the delivery layer, the detected application stack, live TLS and the announcing network side by side.