WHAT IS THIS SITE BUILT WITH?

Paste any public URL and get a BuiltWith-style rundown of the technology behind it — CMS, frameworks, analytics, ad networks, CDNs, servers and more — detected from the page markup, HTTP response headers and cookies.

Enter a public URL like example.com or https://example.com. Our server fetches the page and its response headers — nothing is stored. Or try an example.

Paste a URL above and the detected technology appears here

Analyzed:

0
Technologies detected
0
Categories
—
Server

Detected technologies

A green dot marks a strong signal (an HTTP header, cookie or generator meta tag); a grey dot means the match came from the page markup.

Response headers

Header Value

Copy the summary

A plain-text recap of everything detected on the page.

How the detection works

Response headers

The strongest signals: Server, X-Powered-By, Via, CDN and cache headers, and cookie names.

Page markup

Script and stylesheet URLs, the generator meta tag and framework-specific attributes.

Cookies

Cookie names like wordpress_*, PHPSESSID or _shopify_* give away the backend.

Frequently asked questions

It is a best-effort fingerprint, not a guarantee. Headers, cookies and generator tags are reliable; markup matches can produce false positives or miss heavily minified or custom stacks. Use it as a starting point, then confirm by viewing the page source.

Some sites strip identifying headers, ship one monolithic bundle, or block automated requests. Single-page apps also render their content in the browser, so the raw HTML may contain very little to fingerprint.

No. Only public HTTP/HTTPS pages can be analyzed. Localhost, internal hostnames and private network IP ranges are blocked for security.

Privacy: the URL you enter is fetched by our server so it can read the page and its headers; the content is never stored. Set-Cookie values are used only for detection and are never shown or saved.

Related tools

Check how the site you just fingerprinted presents itself when its links are shared.

Load that page into an editable copy and try the wording changes you have in mind.

Percent-encode a messy URL before you paste it into a form, a query string or a bug report.