How KillBot screens traffic before the destination loads.
A visit reaches your Protected Page or Smart Link. KillBot checks network, IP, ASN, browser, repeat activity, and route rules, then applies the right outcome before recording the result in your Traffic Log.
Follow the request from click to logged outcome.
Every visit follows the same path: the route receives the request, KillBot evaluates signals, the configured policy decides the outcome, and Traffic Log records the result.
From a paid ad, search, link, or campaign source.
Reason, signals, and outcome recorded in your Traffic Log.
Visitor reaches the route
The click lands on a Smart Link or directly on a Protected Page.
Signals are evaluated
IP intelligence, ASN context, browser signals, category matches, and route rules are checked together.
Decision is applied
The visitor is allowed, redirected, blocked, or rate-limited based on your configuration.
Traffic Log records the result
Teams review IP, country, ASN, category, reason, and final outcome later.
Choose the right route for the traffic path.
Protected Pages
Use when the visit lands directly on your real website or landing page.
- Landing pages
- Signup pages
- Lead forms
- Payment-intent pages
- Sensitive routes
Smart Links
Use when traffic should be screened before the final destination opens.
- Campaign links
- Redirect domains
- Tracker links
- Affiliate flows
- Paid traffic tests
What KillBot checks before choosing an outcome.
IP reputation
Bad IP coverage, threat feeds, proxy ranges, and datacenter ranges.
ASN and network context
Provider, hosting profile, suspicious infrastructure, and crawler markers.
Category match
Proxy, VPN, datacenter, Tor, crawler, threat feed, and custom blocklist categories.
Route policy
Country rules, referrer rules, schedule windows, redirect target, and selected mode.
Repeat activity
Repeat visitors, cross-site patterns, and repeated requests in short windows.
Browser behavior
When JS is installed, browser-side behavior can add extra confidence.
How the final action is chosen.
The visitor reaches the real page because the request matched the safe path for the page or link.
Risky traffic is sent to the configured safe URL instead of the sensitive destination.
High-risk traffic is denied when block mode is enabled for the account and route.
Repeated or excessive activity is slowed down when abuse thresholds are reached.
Redirect-first rollout
Start with redirect mode for broad risky categories. Use the Traffic Log to confirm the pattern before moving to stricter blocking.
What Traffic Log records after the decision.
Traffic Log closes the loop. It shows where the request came from, what was matched, what action was taken, and which route handled the visit.
| Field | Why it matters |
|---|---|
| IP and country | Confirms where the request came from and whether geography matches policy. |
| ASN / ISP / organization | Shows whether traffic came from suspicious hosting, proxy, VPN, or infrastructure-heavy networks. |
| Category and reason | Explains why KillBot classified the visit into a risk bucket. |
| Source route | Shows which Protected Page or Smart Link handled the request. |
| Decision outcome | Shows whether the visitor was allowed, redirected, blocked, or rate-limited. |
Questions teams ask before rollout.
What does KillBot check before making a decision?
KillBot checks IP intelligence, ASN context, browser and crawler signals, repeat activity, and the page or link rules configured for that route.
Should I start with blocking?
Usually no. Start broad risky categories in redirect mode, review the Traffic Log, then tighten rules after the pattern is clear.
When should I use Smart Links instead of Protected Pages?
Use Smart Links when traffic reaches a routing, tracking, or redirect domain before the real destination. Use Protected Pages when visitors land directly on your real page.
Start with one route and prove the decision path.
Create one Protected Page or Smart Link, review the first decisions, then expand protection across campaigns.