WordPress Tools / Tools

WordPress Tools

Find visible plugin and theme references on public WordPress websites.

Choose your task

2 tools in this workspace

Open a tool to see its inputs and get a result.

All tools ↗

Check public WordPress plugin and theme references

WordPress pages often load scripts, stylesheets, and images from plugin or theme folders. These public asset paths can help you understand how a page was built. FyrePress provides two tools for checking those references without installing software or signing in to the target website. Use them as a starting point when researching a design, reviewing your own pages, or investigating an unfamiliar asset.

Choose the right tool

The WordPress Plugin Finder looks for plugin folder references in the HTML returned by a public page. Results include the visible asset URLs behind each match. The readable label comes from the folder name, which may have been customized; it is not a verified product identity.

The WordPress Theme Detector looks for theme asset references. It also attempts to read up to three same-host theme stylesheets for available theme names, authors, versions, and parent theme details. Assets hosted on an external CDN can appear as evidence, but their stylesheets are not fetched for those extra details.

How to check a website

  1. Open the relevant tool and enter a public HTTP or HTTPS page URL. No WordPress username, password, or installation access is needed.
  2. Run the check and review the plugin or theme folder references returned for that page.
  3. Open View public evidence to inspect the asset URLs supporting a result. Treat each match as evidence to investigate.
  4. Try another relevant public page if needed. A contact page may load different plugin assets from a shop, article, or homepage.

Understand what a result means

A reference to /wp-content/plugins/contact-form/, for example, indicates that the returned page includes an asset path with that plugin folder. It does not prove the plugin is active across the website. Cached HTML and old asset references can remain after a component has changed.

Theme results can include both parent and child theme folders. Public stylesheet headers may be stale, so a reported name or version is not a guarantee of the currently active theme. Confirm findings in the WordPress administration area when you own or manage the site.

Why some components do not appear

These checks read returned HTML; they do not log in, run the target website's JavaScript, or search for hidden files. Plugins used only in administration, or components with no assets on the checked page, may be absent. Renamed directories, combined files, CDN rewriting, and bot protection can also limit detection. No results does not establish that a site is not using WordPress.

Privacy, access, and request limits

The entered URL is sent to FyrePress, and our server requests the public page. Theme detection may also request the same-host stylesheets described above. Use public URLs without private tokens or sensitive query parameters. Private addresses and nonstandard website ports are unsupported. Checks are limited to ten per ten minutes per client.

A blocked, slow, or unreachable page can prevent a result. These tools do not provide a complete component inventory, vulnerability scan, or security certification. Read the Privacy Policy for data handling, the Disclaimer for output limitations, or contact us with a reproducible detection problem.