Enforcement & takedowns
Dispatching takedowns across email, API, and headless channels — and the honesty guardrails that keep 'submitted' true.
How a case becomes a real, submitted takedown — and how the platform refuses to fake one.
Video uploads in progress
Tutorial recordings are still uploading and transcoding, so the players below are placeholders for now. The outlines are final — videos will appear here automatically once processing completes.
Dispatching your first takedown
4:15From a triaged case to a dispatched submission, and how the channel is resolved from the provider.
The XARF abuse email channel
3:50Generate and send a XARF report to a registrar or host — with dry-run and sandbox modes for safe demos.
The API channel (CleanDNS)
4:05Submitting through a provider API, storing the provider reference, and mapping its status honestly.
Headless portals and the CAPTCHA park
4:40The sharpest guardrail — a portal that hits a CAPTCHA parks in needs_human and never reports a false 'submitted'.
Idempotency and status re-checks
3:30Why re-dispatching the same takedown won't double-submit, and how re-checks advance submitted toward actioned.
Verification and resurrection
3:55Confirming a target is actually down, scheduling re-checks, and catching a threat that comes back.
The auto-enforce hand-off and approval gate
4:10When triage hands a case to enforcement automatically — and the default-deny gate that blocks it without approval.