How to find what technology a website uses
Quick answer: paste the domain into a free technology checker such as TechLookup.app, which scans the site and lists its CMS, framework, analytics and hosting. To confirm a result by hand, open the page source and search for telltale paths like wp-content or cdn.shopify.com, then read the HTTP headers.
That covers most sites in under a minute. The rest of this guide is about the awkward cases: what each method can see, where it goes blind, and how to tell a real result from a leftover script.
Pick a method by what you need
| You want to know | Use | Time |
|---|---|---|
| The whole stack of one site | Online lookup | Under 1 min |
| The stack of every site you browse | Browser extension | One install |
| Whether one specific tool is really there | Page source | 2 min |
| The server, CDN or email provider | Headers and DNS | 5 min |
| A list of every site using a technology | A technology index | Minutes |
Method 1: Use an online lookup
Enter the domain in a website technology checker. TechLookup.app, BuiltWith and Netcraft all work this way: their servers fetch the site and match what comes back against known fingerprints, so you install nothing.
On TechLookup.app you get 3 lookups a day without an account and 5 with a free one. The report shows what was found and how sure we are of each item, with the matched text behind a detection.
What goes wrong: the scan may hit a bot check instead of the site. You then see the protection service and little else. A short report on a big site usually means this, not a simple stack. Try the extension instead, because it reads the page your own browser loaded.
If you already suspect a platform, the WordPress detector, Shopify detector and CMS detector answer that one question directly.
Method 2: Install a browser extension
An extension checks each page as you browse. Wappalyzer and WhatRuns are the best-known, and TechLookup.app has one for Chrome and Firefox.
It sees something a server-side lookup can miss: pages behind a login, and scripts that only load after you've interacted with the page. If you check a lot of competitors or prospects, this is the method you'll end up using most.
What goes wrong: an ad blocker stops scripts from loading, so analytics and ad tools can vanish from the result. If a tool you expected is missing, turn the blocker off for that site and reload.
Method 3: Read the page source
Right-click the page and choose View Page Source (Ctrl+U, or Cmd+Option+U on a Mac). Then press Ctrl+F and search for these strings.
| Search for | It points to |
|---|---|
wp-content | WordPress |
woocommerce | WooCommerce, on WordPress |
cdn.shopify.com | Shopify |
<meta name="generator" | Often names the CMS and version |
/_next/static/ | Next.js |
__NUXT__ | Nuxt |
ng-version | Angular |
googletagmanager.com | Google Tag Manager |
Use View Page Source, not Inspect, when you want to know what the server sent. Inspect shows the page after scripts have changed it, which is the right place to look for tools injected by a tag manager.
What goes wrong: finding a string doesn't prove the tool is in use. Sites that migrate from WordPress to something else can keep old wp-content image links for years. A framework bundled into a third-party widget can also look like the site's own. So look for more than one signal before you quote a result, especially in a sales email.
Method 4: Check the headers and DNS
Open DevTools (F12), go to the Network tab, reload and click the first request. Or run this in a terminal:
curl -sI https://example.comLook at server, x-powered-by and set-cookie. A cf-ray header means Cloudflare is in front. A PHPSESSID cookie means PHP, and _shopify_s means Shopify.
DNS shows what the page can't:
dig +short NS example.com
dig +short MX example.comThe NS records name the DNS host, and the MX records name the email provider. An MX value ending in google.com means Google Workspace, and outlook.com means Microsoft 365.
What goes wrong: the CDN hides the origin. A site behind Cloudflare reports server: cloudflare, which tells you nothing about the host underneath.
What no method can show you
Every outside check has the same limit: it only sees what the site sends to visitors. A database, a back-office tool or a server language that leaves no trace stays invisible.
Static sites are the hardest case. In our own accuracy test on 31 October 2026, TechLookup.app found every platform across 87 Shopify, WordPress, WooCommerce and Ghost sites, but only 52% of static site generators across 35 sites, because Jekyll often leaves nothing in the finished page. That's a small sample. Still, it shows the pattern: store and CMS results are the ones to trust, and "no generator found" doesn't mean none was used.
Our scanner also reads only the home page, so a checkout or help centre on another platform won't appear. To check one, look up that subdomain separately.
FAQ
Can I see what a website is built with for free?
Yes. Online lookups, browser extensions, page source and DNS checks are all free for single sites. You pay when you want bulk data, such as long lists of sites, filters or CSV exports.
How do I know if a website uses WordPress or Shopify?
Search the page source for wp-content for WordPress, or cdn.shopify.com for Shopify. The WordPress detector and Shopify detector run those checks and more for you.
Why do two tools give different results?
They use different fingerprints and they fetch the page at different times, from different places. One may also get a bot check where the other doesn't. If they disagree, check the page source yourself.
Can I find every website using a technology?
Not by hand. You need an index built from scanning many sites. Start with TechLookup.app's technology pages, which show usage counts and the top sites for each technology.