Edge APIChecking
Awaiting health response
Live edge diagnostics
Your search network.
In clear view.
Inspect the registry. Run an exact-title diagnostic. See which providers answered, and what their results actually contain.
— tracked connectors
— implemented adapters
Standard TorBox tier
Strict match or no result
System truth
Coverage at a glance
Registry counts describe capability. The answering-source count only changes after a real diagnostic search.
Source registry—
tracked connectors
Implemented—
search adapters, not live claims
Last diagnostic—
run a search for live proof
ProtectionChecking
bounded edge proxy
Live query lab
Test the whole search path
Runs through the public Manager proxy using your real Standard-tier configuration. Nothing here invents source coverage.
Stress tests
Ready when you are
Your evidence appears here
Start with a title you knowRun a diagnostic above to compare providers, candidate links, and discovery records.
Source registry
Every source, with evidence.
Configured is not the same as answered. Inspect individual checks, their query and timing, and any reported failure.
Loading all source adapters…
Status model: “Implemented” means code exists. “On demand” means it runs only when a relevant search needs it. “Answered” means it returned at least one result in the most recent test.
This browser
Recent diagnostics
Your completed tests will appear here.
Protected route
Manager → edge → sources
Browser→Manager proxy→Builder worker→Source lanes
Body limits, provider budgets, circuit breaking, and VPS failover stay enforced across the route.