Algoblocker · Enterprise Recovery · v1

Session recovery when the custom domain is 403

First enterprise solution on the Algoblocker plane. When a customer custom host (e.g. intrikata.com) returns browser-only HTTP 403 while cookieless probes still return 200 — regardless of whether Bot Fight Mode is enabled — recover here on a clean host, then land on a known-good app surface.

Intrikata console

OTP sign-in, then open the Worker console (not the blocked custom domain).

Recover console session Open safe console host

Intrikata docs

Recover docs session Open safe docs host

How it works

Separate host / cookie jar from the failing custom domain (class is browser-profile + host specific).
OTP runs against Intrikata APIs via a clean edge proxy.
Return URLs are rewritten off blocked custom hosts onto workers.dev / pages.dev.
Do not assume Bot Fight Mode — confirm in CF Security; residual may be WAF, routing, or stale site data.
Topology entry: https://topology.intrikata.com/recover.html

algoblocker-enterprise-recovery · edge 1 · trap #29