Welcome, Guest!

Cyber Cafe?

WP Theme Detector

WordPress Theme Detector – Find Any Website's WordPress Theme
Fast, Non-Intrusive Public WordPress Inspector

WordPress Theme Detector

Discover Which WordPress Theme Any Website Is Using

Privacy Notice: Only publicly accessible front-end pages are analyzed. Submitted URLs are never published.

Loading...
Connecting to website...
Performing SSRF-safe DNS verification and analyzing public markup...
Your Recently Scanned Websites (Local Browser Storage)

Detection Report

Public inspection results

WordPress Status

—
Website URL
—
Website Title
—
HTTP Status
—
Scan Timestamp
—
Verified Signals:

Active Theme Information

Child Theme Active

Theme Name
—
Theme Directory Slug
—
Theme Version
—
Theme Author
—
Author URL
—
Theme Homepage
—
Stylesheet URL
—
Description
—
Open Theme Homepage

Parent Theme Identified

Parent Theme Name
—
Template Slug
—
Version / Author
—
Parent Homepage
—

Theme Preview

Detected WordPress Theme Screenshot Preview

Public screenshot.png preview

Detected Plugins

0 Found
Transparency Notice: Plugin detection is partial and based strictly on publicly exposed front-end asset directories (/wp-content/plugins/). It does not prove that every listed plugin is active.

Website Technologies

Publicly verifiable server headers and front-end technology signatures. Unexposed headers are never fabricated.

Web Server —
PHP Version —
CDN Provider —
WordPress Version —
Page Builder Indicators —
WooCommerce Indicators —
Caching Indicators —

How Our WordPress Theme Detector Works

Our engine uses a multi-step, non-intrusive inspection pipeline to identify WordPress themes and plugins accurately without fabricating data.

1

Core WordPress Verification

We inspect public HTML meta tags, REST API discovery links (api.w.org), /wp-content/ and /wp-includes/ asset paths, and HTTP headers to verify whether the site is powered by WordPress.

2

Stylesheet Header & Parent Resolution

Once a theme directory is located, we fetch its public style.css file to extract the official Theme Name, Version, Author, and Template header—automatically resolving parent themes when a child theme is active.

3

Plugin & Stack Fingerprinting

Finally, we scan front-end scripts, stylesheets, and response headers to catalog publicly exposed /wp-content/plugins/ slugs, page builders, WooCommerce footprints, CDNs, and caching layers.

Frequently Asked Questions

Everything you need to know about detecting WordPress themes, child templates, and plugins.

A WordPress Theme Detector is an online analysis tool that inspects the publicly accessible HTML, CSS stylesheets, and HTTP headers of a website to determine whether it runs on WordPress and which WordPress theme and plugins are publicly referenced in its front-end source code.

Enter the website URL into the WPCodeQuill WordPress Theme Detector input field above and click "Detect Theme". Our engine fetches the public webpage, locates references to /wp-content/themes/, and parses the standard WordPress header comments inside the active style.css file.

Yes, provided the website leaves its theme directory and style.css header publicly accessible. Whether a theme is free from the WordPress.org repository or a commercial theme from ThemeForest, Elegant Themes, or an independent studio, its metadata can be identified whenever standard WordPress stylesheet headers are intact.

Yes. When a website uses the Divi theme or the Divi Builder plugin without hiding its asset paths, our detector identifies the Divi stylesheet (/wp-content/themes/Divi/style.css), parent template references, and Divi Builder DOM markers.

Our tool identifies plugins that expose public front-end assets—such as CSS files, JavaScript bundles, or HTML generator comments—under /wp-content/plugins/. Because back-end-only plugins do not output front-end markup, plugin detection is always partial and does not guarantee that every listed plugin is actively executing on every page.

Yes, the WPCodeQuill WordPress Theme Detector is 100% free to use with no account registration required.

Some websites cannot be detected because they are not built with WordPress, use a headless WordPress architecture, rewrite or obfuscate /wp-content/ paths via security plugins, strip CSS header comments during minification, or block automated HTTP requests using a firewall (WAF) or CAPTCHA challenge.

No. WPCodeQuill strictly inspects publicly accessible front-end resources (the public HTML document and public CSS/REST headers) just like a standard web browser. It never attempts to bypass authentication, WAF rules, or access private server files.

Yes. When a WordPress site uses a child theme whose style.css file includes the standard "Template:" header pointing to the parent theme folder, our engine detects both the active child theme and fetches the parent theme metadata.

By default, we do not store your scanned URLs in any public list. You can optionally enable local browser scan history using the toggle below the search bar, which stores your recent scans privately inside your own browser's localStorage and can be cleared at any time.
Copied to clipboard!
© 2026 WPCodeQuill. All rights reserved. WordPress® is a registered trademark of the WordPress Foundation.