Verify your domain.
Sign in and add a hostname you control. Publish the supplied DNS TXT record and keep it in place for ownership renewal.
PLATFORM / SITE OBSERVABILITYYour domain.
Your domain.
A clearer picture.
Verify ownership, connect a server-side observer, and see the requests reported by your integration. Start with visibility. Choose protection deliberately.
⌁SITE WORKSPACE
01 / OWNER ACCESSA clearer view
A clearer view
starts here.
Sign in with your provisioned owner key to connect a verified domain and inspect observation events.
01 / CONNECT YOUR DOMAIN
Put your site in view.
Start with a hostname you control. Ownership is verified with a DNS TXT record.
⌘
ONE-TIME INGEST KEY
Save it before you continue.
Store this key in a server-side environment variable. You cannot retrieve it again after dismissing this panel. Rotating it invalidates the previous key.
◎
A domain. A clear starting point.
Add your first site above. We’ll provide the DNS record and a private key for server-side observation.
SERVER-SIDE INTEGRATION
Observe at the source.
Use the integration in your server environment. Keep the ingest key out of browser bundles, client-side code, and public repositories.
OBSERVE FIRST.
Domain verification confirms control of a DNS record. Observation events are reports from your integration, not proof of an attack. Observation mode does not block or reroute requests. Protection policies are explicit and opt-in.
RESOURCES / INTEGRATION SETUPThree deliberate steps.
Three deliberate steps.
One clear starting point.
Connect your server.
Use the private ingest key in a server environment. The workspace provides the Node integration; a Worker adapter is also available through the integration API.
Observe before acting.
Inspect reported requests and labelled self-tests. Protection policies are configured explicitly through the owner API.