tool · one of 34 free, no counter

WordPress

Q: Why is a renamed directory not enough on its own?

Because /assets/plugins/select2/ is how every admin template lays out its vendor scripts. A renamed directory needs a second marker beside it - a generator tag, a wp-includes path, a block class - before anything is reported.

Is this WordPress, and what is it running?

The usual way to enumerate a WordPress install is to request paths and see what comes back, which is a scan of somebody else’s server rather than a reading of their page. This fetches nothing: it reads the asset URLs the document already contains, and every claim it makes is traceable to a file the browser has already loaded.

Reach it Press ⌘ + K on any tab and type wordpress. Ctrl + K on Windows and Linux

Whether this is WordPress, which theme draws it and what loads with it

reads asset URLs already in the document

requests nothing - never a guessed path

sends nothing

content directory discovered, never assumed

versions the first asset’s answer, and null is an answer

not WordPress an answer, and a headless install looks the same

plan free

Add LoupeKit

TWO BUILDS 9 browsers

Chrome from the Chrome Web Store Firefox from addons.mozilla.org Edge from Microsoft Edge Add-ons Brave takes the Chrome build Opera takes the Chrome build 4 more the Chrome build

in the panel · free, no counter

section#about

What this actually is

whether a page is wordpress, its theme, and every plugin loading an asset

Qualifying a site before a project, checking what a client’s install is running, or working out which plugin is responsible for a script you are looking at.

section#asked

Asked about this tool

4 of them

Why does it not check /wp-content/plugins/ directly?

Because requesting guessed paths is scanning somebody’s server, and this product reads the page in front of you. Everything reported comes from a file the browser already fetched because the page asked for it.

It found nothing on a site I know is WordPress. Why?

A headless install serves a front end that looks like anything else, and a hardened one renames its content directory. Both are reported as "no evidence" rather than as "not WordPress".

Why is a renamed directory not enough on its own?

Because /assets/plugins/select2/ is how every admin template lays out its vendor scripts. A renamed directory needs a second marker beside it - a generator tag, a wp-includes path, a block class - before anything is reported.

Is a detected REST API a problem?

It is stated, not graded. Whether an open REST API matters depends on the site, and this reading has not earned that opinion.

how to use wordpress

Open WordPress on the site you are qualifying.
It reads the asset URLs the document already carries, and fetches nothing at all.
Read the theme and the plugins, each beside the URL that proved it.
Treat anything unproven as absent - every row here is traceable to a marker in the page.

written about at length

builds 5 min What a page tells you about how it was built The six kinds of evidence a page leaves about its own stack, which of them can be trusted, and how each one is faked.

Add LoupeKit

TWO BUILDS 9 browsers

Chrome from the Chrome Web Store Firefox from addons.mozilla.org Edge from Microsoft Edge Add-ons Brave takes the Chrome build Opera takes the Chrome build 4 more the Chrome build

70 of these · no host permissions · three free audits