How Website Technology Detection Works
Oberon Atlas detects technologies by combining evidence from crawled pages, response metadata, scripts, asset paths and product catalogs. A single signal can be useful, but the strongest detections usually come from multiple independent clues.
What Oberon observes
The crawler collects public signals from pages and responses. It does not need access to private dashboards or admin systems.
HTML markup, meta tags, script URLs and stylesheet paths.
HTTP headers, redirect behavior, canonical URLs and security policies.
Runtime signals that appear when a page loads client-side scripts.
Known catalog fingerprints for products, plugins, platforms and infrastructure.
How signals become a technology match
Detected evidence is mapped to known technologies and categories. Oberon Atlas keeps the evidence close to the result so users can understand why a technology was detected.
Strong product-specific fingerprints increase confidence.
Repeated evidence across multiple pages is stronger than one isolated asset.
Category matches help group raw detections into business-friendly stack layers.
What detection does not prove
A detected technology means that public evidence for that technology was observed. It does not prove how the company licenses, configures or internally uses the tool.