Skip to main content
Contact

What is this website built with? How to check it

To find what a website is built with, look in four places: a detector tool, the page's markup, its response headers, and its copies in the Web Archive. Each shows part of the answer, and none shows all of it.

The question matters most when you are about to hand the site to someone. The stack is the part of a project that outlives the people who built it. Someone has to keep it updated, host it and hire for it.

Four places to look

WhereWhat it showsWhat it misses
A detector tool such as BuiltWith or WappalyzerThe content system, the framework, analytics and other services it recognisesAnything it has no pattern for; it can guess wrong
The page's markup (view source)Theme and plugin folders, generator tags, script namesAnything rendered on the server and hidden from the page
The response headersThe server and sometimes the language versionOften removed or rewritten by a host or a CDN
The Web ArchiveSaved markup, assets and sometimes original response metadata, for a date in the pastParts the archive did not keep, such as some images and scripts

A detector is the fastest start. The markup and headers are the evidence. The archive is how you check what a site ran on years ago, which is what a supplier's case study claims.

One case study, traced to its evidence

Every case study on our site lists the stack the project ran on. We check stack claims against the available evidence and record anything still unresolved. The evidence is our own code, the project's repository, the live site's headers and markup, or the Web Archive.

On TwinsUK, a capture of the research site from 3 January 2019 shows the WordPress version in its markup and PHP 5.6 on Apache in its headers. The same capture shows our own theme folder and the plugins behind the forms and the members' access. Each of those became a line in the list.

The evidence: a Web Archive capture of the TwinsUK research site, 3 January 2019. The markup shows the WordPress version, our theme folder and the plugins behind forms and members' access; the headers show PHP 5.6 on Apache. The stack list: WordPress, our own theme, PHP on Apache, form and access plugins.
From one dated capture to the stack list on the case study.

On Discovery World Trekking, the repositories name the framework, the libraries and the content system. The hosting came from the live site's headers in October 2026. An archive capture from 2020 shows the site on Apache, before the rebuild. We list the stack checked in October 2026, and the record keeps the history.

What stays off

A service in our repositories whose place on the live site we could not confirm is not on the Discovery World Trekking list. The page record notes it and why. A list that guesses is worse than a short one, because a reader cannot tell which line is the guess.

Four questions about a supplier's stack claims

  1. Where does each item on the list come from? Code, repository, headers or archive.
  2. Which version did the project run, and when?
  3. What did you leave off because you could not confirm it? A careful supplier has an answer.
  4. Can I see it myself? A live address or an archive date lets you check without them.

The tools that answer "what is this website built with" read the outside of a site. A supplier's case study should be able to show you the inside.

Related work

Running a site on a stack someone has to look after?

Tell us what it runs on, or the address, and we will tell you what we find and what keeping it current would take.

Tell us what it runs on