Prove it’s yours.
Verify domain ownership with a DNS TXT record. Keep existing traffic routing as it is.
Your real website has better things to do.
Give unwanted requests somewhere else to go.
Most security decisions end at allow or block. We’re building another destination: deliberate decoys that keep selected requests separate from what matters.
Explicit routes serve fictional content. The real origin stays out of that request.
Inspect the demonstration ↗Unique canary links record when they’re opened. A signal you can inspect, with its context intact.
Open the canary console ↗Verify your domain and connect server-side observations before changing traffic behaviour.
Connect a site ↗Start with a boundary you can understand. Synthetic content. Explicit routes. Observable events. Then build from evidence.
See what’s real today ↗Explore the idea in seconds. Choose a request and watch where an explicit routing policy sends it.
01 / SELECT REQUEST TYPE
GET /products Choose a request, then trace its destination.
Browser simulation · No network requests or detection claims. To inspect a service response, open the interactive demo.
Verify domain ownership with a DNS TXT record. Keep existing traffic routing as it is.
Use a private server-side key to report request observations. Keys never belong in the browser.
Review canary callbacks and request observations. A signal needs context before a conclusion.
This is a working development preview. See the capabilities that are available and the ones still ahead.