Bot Protection

Protected by
Passive signal score
0.86 · passes at 0.60
Browser challenge
solved in the browser
Response token
xrsp1. · single use · 2 min

A checkbox in front of your forms. Nothing in front of your customers.

Bots should work harder. Customers should not.

The cost of a captcha is paid by humans

Most checks treat every visitor the same: squint at a picture, prove yourself, try again. Xuda Bot Protection starts with a checkbox and a small challenge the visitor's browser solves in the background. If the connection looks human, that is the end of it. Only when it looks automated does anyone see an image challenge, and only after that does an AI get involved.

No captcha vendor

It is built in-house. There is no captcha vendor behind it and no account to open somewhere else. By default your visitors' details are not sent to a third-party scorer. An optional Cloudflare check can be switched on for a setup.

01What a check decides

Nobody sees a puzzle until they have earned one.

Level 0 is the checkbox, the passive signals and a proof-of-work puzzle the browser has to solve. Level 1 is a 9-tile image challenge. Level 2 is an AI risk verdict and, if that verdict is borderline, one generated question. Each level only exists because the one before it failed.

Passed18,402

Checkbox, signals and proof of work

L0 · where almost everyone stops

The visitor clicks once. Server side, what is known about the connection becomes a score and the browser has to have solved the challenge. A pass that arrives faster than the minimum age is not accepted.

Clear it and there is no puzzle, no grid of buses, no second attempt. That is the whole experience for most people.

  • The score starts high and only goes down when something looks automated.
  • A connection from a hosting network or Tor is asked for more work.
  • The session token behind the widget lives 15 minutes.
Challenged2,941

A 9-tile image challenge

L1 · only after level 0 fails

One target shape, nine tiles, at least two of them correct. The grid is generated on the spot from seven shapes in many colors, with rotation, scale and noise, and it is graded against a hash of the correct tiles rather than a stored answer.

Nothing is fetched from a third party and nothing is scraped from your users.

  • Refresh gives a new grid; Verify submits the selection.
  • Each issued challenge is good for two minutes.
  • No photographs, no street signs, no vendor library.
Blocked1,106

An AI risk check, then one question

L2 · the last step before a block

The collected evidence goes to a structured risk verdict: a score, a verdict of human, bot or borderline, and a reason. A clear human passes, a clear bot is blocked, and a borderline visitor gets exactly one generated question to answer.

A borderline visitor gets one generated common-sense question with a hashed expected answer.

  • The verdict has to score at least 0.7 to pass at this level.
  • The generated question is good for three minutes and is asked once.
  • If the scorer cannot be reached the visitor is treated as borderline, not failed.

02The escalation ladder

One check, two places to put it.

A widget for the forms and pages you host yourself, and an origin-side gate for anything running on Xuda. Same ladder, same keys, same dashboard.

Server-side signals, not trusted scripts
The server scores what it knows about the connection: the network it comes from, whether it is a hosting range or Tor, how fast requests arrive, and signs that a browser is automated. Signals can only lower the score, never raise it.
The browser does work before it is believed
Every visitor runs a small proof-of-work challenge in the browser, with a hidden check that it ran in a real page. It is cheap once and expensive at bot volume, and it is harder for hosting networks and Tor.
Single-use, short-lived pass tokens
A pass is a signed token that lives two minutes and is burned the first time your server verifies it. Replay the same token and the answer is timeout-or-duplicate, in every region.
Drop-in for code you already wrote
The verification call takes a secret and a response and answers with success, score, level_reached, hostname, challenge_ts and error-codes. Existing backend code usually only needs its URL changed.
Origin-side enforcement, no extra edge
Armed targets are enforced by the Xuda router itself. A cleared visitor carries an httpOnly, secure, SameSite=Lax cookie for the clearance window, so the interstitial is a one-time event, not a toll booth.
Flood control and a silent honeypot
60 verification attempts a minute per visitor IP and site key, 600 a minute per site key. A decoy field that gets filled fails the visitor with a deliberately uninformative reason, so the bot learns nothing from the rejection.

03Getting it live

Four moves from nothing to protected.

Bot Protection sits in the MODULES group of your account menu. Nothing runs until you create a setup, and Free is a real plan.

Name it. Pick how it shows. Paste the code.

Each setup has its own site key and secret key. The site key is public and goes in the embed code. The secret key stays on your server and is what verifies a pass. Each setup lists the domains it may run on, and the check refuses any other host.

  1. Choose a tier. Open Bot Protection and pick from the four-card ladder. Free is an activation, not an assumption: press Activate and you owe nothing. Paid tiers state the money in plain words before you confirm, and add one line to the invoice you already get.

  2. Create a setup. Press New setup, name it, list the domains it may run on, and choose how it shows: Checkbox, Invisible or Full page. The setup gets its own site key and secret key, and the embed code to paste.

  3. Paste the snippet, verify on your server. Copy the embed code into your page. Then post the secret and the response token from the form to the verification endpoint and read success, score and level_reached back.

  4. Protect what you host with Xuda. A deployment that Xuda hosts can be armed with its Under attack switch. The origin starts enforcing within one 30 second refresh, and disarming is the same switch.

  • Choose how it shows: a checkbox in your form, a check that runs in the background, or a full page cover.

  • Rotate the secret whenever you like. The dialog warns you that the old one stops working everywhere it is used.

  • Each setup reports a Refused count for hosts that were not on its list, with a button to allow one.

04Server-side verification

Your backend already knows how to talk to this.

The verification endpoint takes a secret and a response token and answers in the same shape reCAPTCHA and Turnstile answer in. If you have written that code once, you have written it for this. Usually only the URL changes.

05Under attack, on demand

Put the check in front of the whole site.

A deployment you host with Xuda can be armed with its Under attack switch. Every uncleared visitor then gets a full-page "Checking your browser" screen before the site loads. Flip it off and they stop. Only Xuda-hosted targets can be protected today.

Enforced at your origin
The Xuda router keeps the armed list in memory and refreshes it every 30 seconds, so arming and disarming take effect within one refresh and there is no extra hop on the hot path.
One pass, then silence
A visitor who clears the check gets an httpOnly, secure, SameSite=Lax clearance cookie and browses normally for the rest of the window, 30 minutes by default.
Or one toggle on the app
A deployment's Quick Actions card carries "Bot Protection (Under Attack)". Flip it there and the same check goes up, with a challenges-served line underneath.

06When a blanket is too blunt

Rules in countries and paths.

Sometimes the answer is not harder for everyone, it is harder for one country or one path. Custom rules run at the edge in a fixed order, so you always know which rule won. They come with the Business plan.

  • Allow, challenge or block by country, chosen from the full ISO 3166-1 alpha-2 list.

  • Per-path rules such as /login or /checkout, each set to challenge, block or allow.

  • Always allow and always block lists that take IP addresses, CIDR ranges or country codes.

07One plan, no per-target fee

Four plans, counted in checks a month.

The plan counts the checks on your own forms and pages, so nothing here is charged per protected target; anything hosted with Xuda is unlimited and does not count. Free is an activation rather than a trial, and moving between paid plans reprices a single line instead of stacking a second charge.

Start here

Free

No card needed

The checkbox on your own forms, and the full-page check on anything you host with Xuda.

50,000checks a month on your own sites and forms
  • The "I'm not a robot" checkbox on any page you host yourself, as a script tag or an inline mount div.
  • The full-page check in front of a deployment you host with Xuda, armed with its Under attack switch.
  • Server-side verification through the siteverify endpoint, with no API key involved.
  • A setup for each form or site: its allowed domains, how it shows and its look are yours to set.

Starter

More checks, and the widget carries your name.

250,000checks a month on your own sites and forms

Everything in Free, plus

  • Your own brand on the widget, in place of Xuda's.

Pro

Room for a busy site.

1,000,000checks a month on your own sites and forms

Everything in Starter, plus

  • 20,000 AI calls a month, included in the plan.
Most complete

Business

The most checks, and the check aimed at one country, one path or one window.

5,000,000checks a month on your own sites and forms

Everything in Pro, plus

  • Allow or block by country, from the full ISO 3166-1 alpha-2 list.
  • Per-path rules, each set to challenge, block or allow.
  • Always allow and always block lists taking IP addresses, CIDR ranges or country codes.
  • Evaluated at the edge in a fixed order, so you know which rule won.
  • More than 5,000,000 checks a month? Talk to us.
AI calls a month
Free1,000
Starter5,000
Pro20,000
Business100,000
Anything hosted with Xuda
FreeUnlimited
StarterUnlimited
ProUnlimited
BusinessUnlimited
Your own brand on the widget
Free
Starter
Pro
Business
Custom rules
Free
Starter
Pro
Business
Path rules
Free
Starter
Pro
Business100 max
Entries per allow or block list
Free
Starter
Pro
Business200 max
Charged per protected target
FreeNever
StarterNever
ProNever
BusinessNever

Going over never stops the check and no form breaks: the AI step is skipped and the dashboard offers a bigger plan. Above Business, talk to us. Verifying a pass from your own backend needs no plan: the server-side verification endpoint is public and sits on Free.

08Bot protection vs the usual options

No vendor to sign up with. No visitors to hand over.

The realistic choices are a hosted captcha widget from a third party, a network-level block in front of your site, or a honeypot field you wrote yourself. Here is what each one actually gives you.

Xuda Bot ProtectionA third-party captcha widgetA network-level blockYour own honeypot field
Checkbox you can paste on your own forms
Full-page check in front of a whole hosted site
Escalates only when the signals look automatedVaries
Proof of work before the browser is believed16 bits by defaultVaries
Image challenge generated in process, no photo setVaries
AI risk verdict as the final stepVaries
Visitor signals scored by a third partyVariesVaries
Server-side verify in the siteverify shape
Single-use pass token, replay rejected2 minutesVaries
Per-visitor and per-site rate limiting includedVaries
Country and path rulesBusiness planVaries
Charged per protected targetVariesVaries

Common questions

The things worth asking first.

Stop the bots. Leave everyone else alone.

Turn on the checkbox for your own forms and pages, or arm the full-page check in front of anything you host with Xuda. Free tier, no card, no per-target fee, and no captcha vendor in the middle.