3 free days after linking the Telegram bot · We help you move from Keitaro and Binom
Try
Bot protection

Bot protection with granular controls.

The antibot works as a chain: rules and lists (your own IP and UA white and black lists, allowed referrers) → network checks (data centers, proxies, TOR, IP reputation lists) → fingerprint and behavior (~40 signals) → an ensemble verdict with a final probability. You choose the filter level and where detected bots go — not a black box: every setting is in plain view.

Start free Compare with Keitaro

How the antibot works in TDS.SO

1

Rules and lists

Rules run first: your own IP and UA white and black lists, a list of allowed referrers, empty-UA and local-IP checks, ISP and hostname signatures. Filter levels 0–3 set the strictness, from basic checks to strict VPN, server and country signatures.

2

Network checks

Each click is checked on its network: datacenter orgs (AWS, Google Cloud, Azure, Linode), datacenter hostnames, TOR exit nodes, public, web and residential proxies, VPN with a timezone mismatch, and IP reputation lists.

3

Fingerprint and behavior

~40 signals across fingerprint and behavior: WebGL/canvas, software GPU markers (swiftshader/llvmpipe), fonts, audio, instant-post timing and mouse-trail jitter. navigator.webdriver and automation tools (Selenium, Puppeteer, Playwright) are hard signals — near-certain on their own.

4

Ensemble verdict and action

The ensemble combines the signals from every check into one probability. At 0.5 or more a CAPTCHA is shown; at 0.7 or more the traffic is treated as a bot and goes to the default page, while real users continue to the offer.

Why it matters

  • Configurable filter levels (0–3) plus your own IP and UA white and black lists
  • ~40 signals across IP, behavior, fingerprint and technical categories
  • webdriver and automation tools (Selenium, Puppeteer, Playwright) count as hard signals
  • Bots go to the default page — real users reach the offer
~40 signals
0–3 filter levels

Related modules

Traffic filtering → Real-time analytics →

FAQ

How is this different from a black-box antibot?
You set the filter level (0–3), the white and black lists and the bot action yourself, and the final-score thresholds — 0.5 and 0.7 — are documented openly.
How are bots actually decided?
Signals aggregate into a probability. At ≥ 0.5 a visitor gets a CAPTCHA challenge; at ≥ 0.7 they are treated as a bot and go to the default page; below that they pass through. In the model's score one weak signal (a VPN, Brave, an unusual config) does not decide the outcome — a verdict needs several anomalies to coincide. But if VPN blocking is on in your settings, such a visit goes straight to the default page.
Do I need my own server?
No tracker server to run: the antibot works in the TDS.SO cloud. For your own domains you only need a separate VPS with a lightweight proxy, and with ready domains from a seller you do not need one at all.

Open an account.
Decide in three days.

3 free days after linking the Telegram bot. We help with setup on Telegram.

Start free trial Message us on Telegram
Start free trial