Free tool

What is this site
actually built with?

A straight answer first — WordPress, Shopify, Laravel, .NET, Next.js — then the language on the server, then every other technology with a verdict on whether it is current, dated or should be retired. Read live from the page, not from a stored profile.

Free, no account needed. We fetch the page once and read the HTML — nothing is changed on your site.

What makes this different

Six things a logo list will not give you

Detecting technology is the easy half. Deciding what to do about it is the half that matters.

A verdict on every item

Current, dated or retire — with the reason and the replacement. Unsupported software is flagged as a security matter, not a style preference.

Read live, not from a database

The big profilers serve a stored profile that can be months out of date. We fetch the page when you press the button and report only what is in it.

Version and support status

Where the version is visible we read it and say whether that release still receives security updates — PHP, jQuery and WordPress especially.

Real page count

Taken from the sitemap and grouped by section, so you can see how big the site actually is and where its weight sits.

Third-party surface

Every external domain the page calls, counted. It is a performance number and a privacy number at the same time, and most tools bury it.

What is missing

No CDN, no compression, no analytics, thin security headers. A detector that only lists what is present misses half the story.

Straight answers

How to read the result

Three things worth understanding before you change anything.

1"Retire" is the only urgent one It means unsupported or no longer functional. Unpatched code is the most common way a small site gets compromised. Everything else can wait for your next round of work.
2Old is not the same as bad A ten-year-old library that still gets security patches and does its job is fine. We flag things that stopped being maintained, not things that stopped being fashionable.
3Do not rebuild because a tool said so Replacing a working stack is expensive and rarely pays for itself. Fix the unsupported pieces, drop what you are not using, and leave the rest. We will say the same thing if you ask us to quote.