How to check tech stack of a website?

Updated October 2026 · How we answer

Short answerYou can often spot a website's tech stack by viewing its page source, checking HTTP response headers, or using a detection extension or lookup service such as Wappalyzer or BuiltWith. Results are partial, so treat them as clues.

Look at the page itself

Right-click the page and choose View Page Source, or open developer tools and check the Network tab. Script file names, generator meta tags, and class names often reveal a framework or content system. Paths such as /wp-content/ usually point to WordPress.

  • Check the generator meta tag in the page head
  • Look for framework-specific script names and attributes
  • Inspect the Network tab for requests to third-party services
  • Look at cookie names for analytics or payment tools

Use detection tools

Browser extensions and web lookup services scan a page and match it against known signatures. They are quick and good for a first guess, but they can miss custom setups or misidentify a tool. Free tiers often have limits, so check current terms.

HTTP headers can also hint at the server, CDN, or hosting provider. A command such as curl -I lets you view these headers from a terminal. Headers are easy to hide, so the absence of a clue proves nothing.

Confirm what you find

Cross-check results from two sources before drawing conclusions. A website's public stack says little about its internal back end, which is usually invisible from the browser.

Be respectful when inspecting sites. Viewing public page source and network requests in your own browser is generally fine, but probing a site beyond normal visitor activity may violate its terms. Stick to what a regular browser session can show.

Common mistakes

  • Assuming the front-end framework reveals the whole back-end stack.
  • Relying on a single detection tool without verifying what it reports.
From our shopsSwiftCase: Curated phone cases that ship in 48 hours.