Moderators see the white page. Buyers see the offer.
Moderators, crawlers and off-target traffic are routed to a safe white page; verified real users reach your money page. Routing is driven by a 3-layer antibot plus the targeting-rules engine, and SSL is issued automatically for every domain.
How cloaking works on TDS
Set the white page and the offer
Create a template and define two destinations per link: the safe white page (one of 50+ templates or your own) and the money page with click macros.
The antibot evaluates every visitor
A 3-layer pipeline scores each click: rule filter (IP/UA lists, referer allowlist) → ~40-signal fingerprint engine → ensemble scorer. Thresholds: ≥ 0.7 is a bot, ≥ 0.5 gets a CAPTCHA, below 0.5 passes.
Bots and off-target traffic get the white page
Bots, crawlers and traffic that fails your targeting rules (geo, device, ISP, referer) are routed to the white page. A double-meta redirect defers the real jump so first-touch crawlers only ever see the safe page.
Verified users reach the offer
Visitors who pass the antibot and your rules are redirected to your offer. SSL is issued automatically per domain — no manual certificates.
Why it matters
- 50+ white-page templates ready to use
- auto-SSL on any domain — no manual certificates
- Routing driven by a 3-layer antibot (~40 signals, 0.5 / 0.7 thresholds)
- Target by geo, device, ISP and referer, plus double-meta against crawlers
FAQ
How does it decide who sees the white page?
Do I need my own server for cloaking?
Can I use my own white pages?
Open an account.
Decide in three days.
Full access to the Standard plan. No card required. Setup help on Telegram in 15 minutes.