Netlify
Netlify providers hosting and server-less backend services for web applications and static websites.
What detecting Netlify tells you about a site
Netlify is a frontend hosting and deployment platform for static sites and JAMstack apps, and it is readily detectable from headers — an X-Nf-Request-Id or Server: Netlify response line, plus a *.netlify.app hostname before a custom domain. Detecting it tells you the front end is built from a static or pre-rendered output deployed via git-push, the hallmark of the modern JAMstack workflow. It skews toward marketing sites, docs, blogs and SPA front ends where the backend is a set of APIs or serverless functions rather than a monolithic server.
Netlify in a real-world stack
When you find Netlify, it rarely travels alone. Hosts output from Next.js, Astro, Hugo, Gatsby and similar; pairs with Netlify Functions/Edge and a headless CMS or API backend.
About
Netlify providers hosting and server-less backend services for web applications and static websites.
Categories: PaaS, CDN
Quick facts
Detection methodology for PaaS
Platform-as-a-Service offerings show up as response headers and deployment domains. Heroku's `Server: Cowboy` plus `*.herokuapp.com`; Render's `*.onrender.com`; Fly.io's `*.fly.dev`. We pair the host detection with framework signals so you can tell what's running on the platform — a Heroku dyno serving Rails looks very different from a Heroku dyno serving Node, even though both fit the same hosting fingerprint.
How we detect Netlify
Sourcemap Explorer carries 3 fingerprint signals for Netlify, spread across 2 channels — response header and url pattern. The exact patterns are listed below, and you can replay each one in Chrome DevTools to confirm a match by hand.
Each signal alone is rarely conclusive — Sourcemap Explorer cross-references all of them and weights by confidence. You can reproduce any of these checks yourself in Chrome DevTools.
Server-side fingerprint: the response header reveals the technology behind the page. Visible in DevTools → Network → response headers.
Server: ^Netlify
X-NF-Request-ID:
The page URL itself follows a known pattern (vanity slugs, embeds, hosting URLs).
^https?://[^/]+\.netlify\.(?:com|app)/
FAQ
How do I check if a website is using Netlify?
Open the page in Chrome, click the Sourcemap Explorer toolbar icon, and read the Stack tab. Netlify's specific fingerprints here are response header and url pattern, and the popup flags Netlify whenever any combination of them is found. The same checks can be reproduced manually in DevTools — see the "How we detect" section above.
What Netlify version can Sourcemap Explorer detect?
Netlify ships as a hosted paas rather than a bundled npm package, so version-specific detection isn't always possible. Where the platform leaks a version in response headers (`X-Powered-By`, `Server`, generator meta tags) we surface it; otherwise we report presence only.
How much does Netlify cost?
Netlify's pricing model is documented as: freemium, low, recurring, poa. Detection is independent of the pricing tier — Sourcemap Explorer flags the technology by its fingerprints, regardless of which paid plan a site is on. See the official site for the current pricing page.
Where can I read more about Netlify?
Official site: https://www.netlify.com/. For Sourcemap Explorer's detection guide, see the deep-dive link below or the related guides in the cross-link section.
Keep reading on Sourcemap Explorer
Practical guides
Alternative tools
Detected by Sourcemap Explorer
Open the popup on any page running Netlifyand you'll see the exact version pulled from the bundled package.json when sourcemaps are exposed.