Skip to main content

Security Toolbox

CMS Detection

Identify which CMS a website is using from public signals — name, evidence, version when it is exposed, and a confidence rating.

Warning: Authorised use only. Use this tool for authorised security-assessment recon only. You must have permission to test the target.

Install

Python 3.10 or newer. requests and beautifulsoup4 install with the package.

pip install lupaxa-cms-detection
cms-detection --help

CLI

cms-detection https://example.com
cms-detection https://example.com --active
cms-detection urls.txt --format json --output results.json
python -m lupaxa.cms_detection --version

Default mode uses the homepage plus a few well-known public files for CMS that already scored on that page. --active adds broader path probes, and when the homepage has no signal it also walks the catalogue's confirm files. A path is never a hit from HTTP 200 alone.

If the URL has no scheme, the tool tries https:// first and falls back to http:// only when TLS or connect fails.

Pass one URL, or a file of URLs with one URL per line. When the argument is an existing file, it is read as a list. Otherwise it is treated as a URL.

CLI Flags

Flag Default Description
--active off Run broader path probes after default confirm files
--format, -f text Output format: text, json, or csv
--output, -o stdout Write results to this file
--workers, -w 10 Thread-pool size for a file of URLs
--delay 0 Seconds to wait before each request
--retries 2 Retry count for failed fetches
--verbose off Append evidence notes to text lines
--version — Print the package version and exit

--output writes the chosen format to a file. Results stay off stdout.

A text line looks like {url} => {cms} {version} ({confidence}). --verbose appends a short evidence note. JSON is a list of result objects. CSV columns are url, cms, version, confidence, evidence, candidates, and error.

Network and HTTP failures set error on that result and the batch continues. An invalid URL or empty input exits non-zero. Unknown CMS is a successful result: cms is empty and error is empty. A failed write of the output file is reported after the scan, and the CLI exits non-zero.

Library

from lupaxa.cms_detection import detect, detect_many

result = detect("https://example.com", active=False)
print(result.cms, result.version, result.confidence)

results = detect_many(
    ["https://example.com", "https://example.org"],
    workers=10,
    active=False,
)

detect takes one target. Keyword-only arguments are active, delay, retries, and timeout. detect_many runs those detects independently, keeps input order, and adds workers.

Network and HTTP failures do not raise. They become result.error with cms set to None. An invalid URL or empty input raises CmsDetectionError.

Results

DetectResult is a frozen dataclass.

Field Type Meaning
url str Final URL after redirects, or the input if fetch failed
cms str | None Best match name, or None if unknown
version str | None Public version string, or None
confidence str | None high, medium, or low when cms is set
evidence tuple[Evidence, ...] Hits from the run, including candidate hits
candidates tuple[str, ...] Other CMS that scored, excluding cms
error str Fetch or parse failure, or ""

Evidence fields are kind (meta_generator, header, cookie, script, path), value (what was seen), and cms (which signature it supported).

Confidence Rules

Each matching signal adds points. Those points pick the winner and are not shown in the CLI.

Signal Points Strength
meta_generator substring match 3 strong
Listed response header name present 3 strong
Matching confirm_paths or active_paths probe 2 path
Cookie name prefix in Set-Cookie 1 weak
Script src host or path substring 1 weak
Confidence Rule
high Two or more independent passive kinds, or one strong passive plus a matching path
medium One strong passive, or two weak passives
low Path evidence only, or a single weak passive

cms is the highest total. Other names with a score greater than zero go in candidates. Ties break on more distinct evidence kinds, then a version being present, then alphabetical name.

A path probe counts when the status is allowed and a required snippet appears in the body or headers.

Development

make init
make python-install-dev
make python-check
The Lupaxa Project Footer

Metadata

Release files for lupaxa-cms-detection 0.1.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for lupaxa-cms-detection 0.1.5
File Size Uploaded
lupaxa_cms_detection-0.1.5.tar.gz 12.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for lupaxa-cms-detection 0.1.5
File Interpreter ABI Platform
lupaxa_cms_detection-0.1.5-py3-none-any.whl Python 3 none any Details

Total release size: 27.8 kB

Release files / lupaxa_cms_detection-0.1.5.tar.gz

Download URL lupaxa_cms_detection-0.1.5.tar.gz
Size 12.3 kB
Tags Source
SHA-256 checksum
How to use checksums
e8b6939e02f62e24966e5ce459b9f96e2803e6798e41dd058d99fbdf4d60b858
BLAKE2b-256 checksum
How to use checksums
227ec7f543d5081c28e635af18fc6737740e408e1553021257f1d620834e12ce
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 7, 2026.

Transparency log

Release files / lupaxa_cms_detection-0.1.5-py3-none-any.whl

Download URL lupaxa_cms_detection-0.1.5-py3-none-any.whl
Size 15.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c10dbe248b9570e305e833b45da7e41e7525d664fb69db8462766311038bb7ce
BLAKE2b-256 checksum
How to use checksums
4573c57d85cdcb93cbd053926d6357c5001c137ceecd2539da0d7f504084a5b6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 7, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.5 This release

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page