Detect XOOPS
PluginView detects XOOPS, a CMS, by evaluating meta tags, javascript globals on publicly reachable pages. Illustrative public indicators associated with XOOPS include generator: XOOPS, xoops. Full fingerprint rules remain proprietary; this page summarizes the signal classes and example indicators used for identification.
Detection looks at meta tags, javascript globals across 2 fingerprint rules among the site's public responses.
Websites using XOOPS
Loading website list…
Signal classes
PluginView evaluates public page signals in these classes when identifying XOOPS. Individual fingerprint rule bodies are proprietary and are not published.
- Meta tags
- JavaScript globals
Example public indicators for XOOPS
Illustrative indicators derived from public catalog metadata for XOOPS. A live scan may match additional proprietary rules beyond these examples.
- generator: XOOPS
- xoops
What a detection means
- Establishes
- One or more public signals on the scanned page matched a known XOOPS signature (2 rules) at the time of the scan.
- Does not establish
- A sitewide install of XOOPS, an active vendor contract, exclusive use, or that XOOPS is still in place today.
How to check a site for XOOPS
- 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest XOOPS signals.
- 2. PluginView reads only public responses (meta tags, javascript globals) and scores them against the XOOPS signature set (2 rules).
- 3. Review the confidence score and text explanation for XOOPS on the results page.
Commonly implies
A confirmed XOOPS match also implies these technologies are present.
FAQ: detecting XOOPS
- Can PluginView detect XOOPS without logging in?
- Yes. PluginView only reads publicly accessible responses when checking for XOOPS — typically meta tags, javascript globals. It does not bypass authentication or paywalls.
- What category is XOOPS?
- XOOPS is classified under CMS in the PluginView directory.
- How many fingerprint rules cover XOOPS?
- This reference currently tracks 2 fingerprint rules across meta tags, javascript globals. Individual rule bodies are proprietary and are not published.
- What public signals suggest a site uses XOOPS?
- Illustrative public indicators for XOOPS include generator: XOOPS; xoops. A live scan may match additional proprietary rules beyond these examples.
