What is this website built with?

Enter any website and see the stack behind it: the CMS or framework, WordPress theme and plugins, ecommerce platform, hosting, CDN, DNS and email provider, analytics and payment tools. Each finding shows the evidence it's based on.

Try:

How it works

Every website gives away clues about how it was built. WordPress loads files from /wp-content/, Shopify serves from cdn.shopify.com, Laravel sets a laravel_session cookie, and hosts like WP Engine, Kinsta and Cloudflare add their own response headers. This tool loads the homepage the way a browser would, then checks the HTML, headers and cookies against a few hundred of those fingerprints.

It also looks up the domain's DNS: the name servers say who manages the DNS, the MX records say who handles email, and the server's reverse DNS often names the company running the machine. Put together, that's usually enough to say what a site runs on and where it lives, without logging in to anything.

What it can detect

CMS and site buildersWordPress, Drupal, Joomla, Ghost, Craft, Squarespace, Wix, Webflow, HubSpot, Framer and more.
Ecommerce platformsWooCommerce, Shopify, Magento, BigCommerce and PrestaShop, plus payment providers like Stripe, PayPal, Klarna and Clearpay.
FrameworksLaravel, Livewire, Inertia, Next.js, Nuxt, Gatsby, Astro, SvelteKit, Rails, Django and ASP.NET.
WordPress theme and pluginsThe active theme (and parent theme), its version and author, page builders, and every plugin the homepage loads, with versions where shown.
Hosting and CDNCloudflare, Fastly, CloudFront, Kinsta, WP Engine, SiteGround, Cloudways, Vercel, Netlify and the big cloud and UK hosts.
DNS, email and trackingWho runs the DNS and email (Google Workspace, Microsoft 365 and others), plus GA4, Google Tag Manager, ad pixels and chat widgets.

Why agencies use a website technology checker

Pitching and quoting. Before a call with a prospect, knowing whether their site is WordPress with forty plugins or a custom Laravel app changes the conversation and the price. You can see it in seconds instead of asking.

Taking over a site. When a client moves to you from another agency or freelancer, the first job is working out what you've inherited. The stack, theme, plugins, host and DNS provider are the starting point for the handover list, which is why this links straight into the website takeover checklist.

Competitor and market research. Seeing what similar businesses use (which ecommerce platform, which reviews widget, which analytics) is quick research for a proposal.

Things it can't see

It reads what the site sends to the public, so anything hidden behind a login, a firewall or a well-configured server won't show. Plenty of hosts strip identifying headers, many sites sit behind Cloudflare so the real host is masked, and plugins that only load on certain pages won't appear from the homepage. Treat it as a strong first read, then confirm with access to the hosting and admin when you have it.

Questions agencies ask

Enter the address above. The checker looks for the files, meta tags, headers and cookies each CMS leaves behind. WordPress, for example, loads files from /wp-content/ and often announces its version in a generator tag. If nothing matches, the site is either a custom build or deliberately hides its platform.

FOR AGENCIES

Inherited a site you'd rather not touch?

If the checker turns up a custom Laravel build, a WooCommerce shop with complicated logic, or a WordPress site held together by plugins, that's the work I take on for agencies: under your brand or alongside your team.

  • White-label, under your brand, or alongside your team
  • Laravel, WordPress, WooCommerce, integrations and tracking
  • Inherited and half-finished sites taken over and stabilised
  • UK based, straight to the developer, no account managers

Related free tools