DeepScope

DeepScope

Navigation

DeepScope by Kaiju

Inspect the active website, review supported technology facts, and trace each result back to the evidence observed in your browser.

Need intelligence across a domain list?

Continue to the Kaiju platform.

Visit Kaiju

A free browser extension from Kaiju

See what a website is built with. Inspect the evidence behind every detection.

DeepScope observes the active website, resolves those observations into technology facts, and keeps the supporting evidence, coverage, and uncertainty close enough to review.

Local-first active-tab analysis. No broad host permissions. Results remain in extension storage.

example.com
DS

Technology detection

DeepScope

Analyze the visible tab locally and inspect the facts behind every result.

Observed
Refresh analysisStop observation
Facts observed148
Technologies12
CoverageComplete
Host: example.comEvidence: reviewableStorage: local

Detected technologies

Facts resolved from this page

snapshot

Each detection keeps the page observation and detector rule that supported it.

Web frameworkAstro

Evidence: 2 signals

  • script: /_astro/entry.js
  • meta generator = Astro v7
Edge deliveryBunny CDN

Evidence: 2 signals

  • response header: cdn-pullzone
  • resource host: assets.example.com
AnalyticsPlausible

Evidence: 1 signal

  • script src contains plausible.io/js/script.js

The result should be inspectable

Do not stop at “this site uses X.”

DeepScope is designed around the evidence behind the detection, not a decorative list of technology logos.

A technology label is only the conclusion

Without the page signal behind it, a detection is hard to verify, explain, or challenge.

Modern pages keep changing after load

Lazy-loaded scripts and resources can reveal facts after the first snapshot. DeepScope keeps watching while the popup is open.

Not observed is not the same as absent

DeepScope preserves coverage and uncertainty so a missing public signal does not become a confident claim about private systems.

From observation to explanation

The facts system keeps the path to each result intact.

DeepScope separates what the browser observed, which maintained definition matched it, and what the extension can safely conclude.

DeepScope observes

01

Capture browser-visible facts

Inspect DOM markers, metadata, resource URLs, selected headers, storage key names, JavaScript globals, and other bounded signals from the active page.

The fact system resolves

02

Apply maintained definitions

Normalize observations, evaluate detector rules, reconcile relationships, and preserve the facts that support each final technology result.

You review

03

See why the result exists

Open the detection, inspect its evidence, understand coverage and uncertainty, then use the grounded result in research, documentation, or AI-assisted work.

What becomes visible

Explore the public technology surface of one website.

DeepScope groups supported detections without pretending the public website reveals every private system behind the company.

01

Applications

Software and services

Frameworks, analytics, marketing, support, documentation, commerce, and developer tools visible on the page.

02

Foundation

Infrastructure

Observable hosting, CDN, DNS, security, delivery, data, and other public web-platform infrastructure.

03

Technical surfaces

AI and developer systems

Observable AI products, models, agent surfaces, APIs, developer platforms, and technical integrations.

04

Why it is supported

Evidence and coverage

Matched values, observation context, detector reasoning, collection status, and explicit unknown states.

How DeepScope works

From the active website to a reviewable technology record.

The workflow stays inside the browser: observe the selected page, resolve supported facts, and keep the explanation beside the result.

  1. 01

    Open the website you want to inspect

    Visit an HTTP or HTTPS page, then open DeepScope from the browser toolbar. Access is granted for that active tab after your action.

  2. 02

    Let DeepScope observe and resolve facts

    The extension captures bounded page observations, enriches the signals available to the browser, and evaluates maintained fact and detector definitions locally.

  3. 03

    Review the result and its evidence

    Inspect technologies by category, expand the evidence behind a detection, refresh the analysis, or keep watching as the page loads new resources.

Evidence is part of the interface

A detection should survive a reasonable challenge.

DeepScope keeps the path from observation to fact visible, so the result can be reviewed before it becomes research, documentation, outreach context, or input to another tool.

  • The page observation and matched value that supported the fact
  • The maintained detector definition and relationship path used to resolve it
  • Coverage, uncertainty, and whether the result changed during live observation
example.com
DS

Technology detection

DeepScope

Analyze the visible tab locally and inspect the facts behind every result.

Observed
Refresh analysisStop observation
Facts observed148
Technologies12
CoverageComplete
Host: example.comEvidence: reviewableStorage: local

Detected technologies

Facts resolved from this page

snapshot

Each detection keeps the page observation and detector rule that supported it.

Web frameworkAstro

Evidence: 2 signals

  • script: /_astro/entry.js
  • meta generator = Astro v7
Edge deliveryBunny CDN

Evidence: 2 signals

  • response header: cdn-pullzone
  • resource host: assets.example.com
AnalyticsPlausible

Evidence: 1 signal

  • script src contains plausible.io/js/script.js

Before you install

What DeepScope can see, what it stores, and what its results mean.

The extension should be as clear about its limits as it is about its detections.

What can DeepScope inspect?

DeepScope analyzes supported signals available to the browser on the active HTTP or HTTPS page. These can include DOM markers, metadata, resource URLs, selected headers, cookie and storage key names, JavaScript global names, and bounded evidence snippets.

Does DeepScope send page analysis to Kaiju?

The first release is local-first. Detector rules ship with the extension, and page analysis, evidence, replay summaries, and cached results remain in local extension storage unless you clear them or uninstall the extension.

Why does it need activeTab, scripting, storage, and offscreen?

activeTab grants temporary access after your action. scripting performs the packaged page observation. storage keeps normalized local results. offscreen provides a local execution surface for matcher work that should not block the popup or depend on the service worker staying alive.

Does a missing detection mean the company does not use that technology?

No. DeepScope reports what the selected public page supports. A technology can be private, hidden, used elsewhere, blocked from observation, or unsupported by the current definitions. Coverage and uncertainty remain part of the result.

Where does AI fit?

AI can explain, compare, summarize, or act on a DeepScope result. DeepScope provides the grounded observation and fact record so those later steps do not need to invent what the page exposed.

How is this different from the Kaiju platform?

DeepScope helps one person inspect one active website. Kaiju applies maintained observation and fact definitions across supplied domain lists, then supports review, enrichment, and export at workflow scale.

The website is already open

See what the active page actually exposes.

Open DeepScope, review the supported technology facts, and inspect the evidence behind the result without leaving your browser.