Verify rollout
Confirm the first requests after a Protected Page or Smart Link goes live before scaling traffic.
DOCS
Traffic Log: see every traffic decision, reason, and outcome.
KillBot Traffic Log shows what happened to a visit, why it happened, and which route handled it. Use it to verify rollout, tune rules, and explain allowed, redirected, blocked, or rate-limited traffic.
IP and country
ASN and network
Category and reason
Final action
Route context
Demo record
Sample logged decision.
Use sample data on public pages so teams can see the record format without exposing private traffic evidence.
Redirected visit on Protected Page /summer-offer
Use sample/demo data only. Do not expose real customer data on public pages.
Sample data only
Protected Page
Redirected outcome
IP address
198.51.100.24
Country
United States
ASN
AS9009
Network
M247 Europe SRL
Category
Proxy / VPN
Reason
Known proxy range + repeat-risk match
Handled by
Protected Page /summer-offer
Outcome
Redirected to safe destination
Occurred at
2026-05-27 10:18:42 UTC
Use sample/demo data only. Do not expose real customer data on public pages.
Fields
What the log records.
Traffic decision logs matter because they keep VPN traffic filtering, datacenter traffic control, and click fraud prevention tied to a visible record instead of a hidden score.
| Field | Why it matters |
|---|---|
| IP and country | Confirms where the request came from and whether geography fits the page policy. |
| ASN / ISP / org | Helps identify datacenter, hosting, proxy, VPN, or suspicious network patterns. |
| Category and reason | Explains why KillBot classified the visit into a risk or traffic bucket. |
| Decision and outcome | Shows whether the visit was allowed, redirected, blocked, or rate-limited. |
| Route context | Shows which Protected Page or Smart Link handled the request. |
| Timestamp | Helps review rollout and investigate campaign periods. |
Trust and tuning
Why visible logs matter.
The Traffic Log keeps decision proof close to the route instead of hiding everything behind a generic bot score.
Tune policies
Adjust page, referrer, schedule, proxy, VPN, or datacenter handling after the live record proves the pattern.
Explain outcomes
Show teammates or clients why a visit was allowed, redirected, blocked, or rate-limited.
Billing context
Retention and plan limits.
Traffic Log retention follows the active plan. Public pricing should show each plan's included history window. The dashboard should warn users before monthly check limits are reached.
- Review the history window before long investigations or exports.
- Watch usage warnings so full checks do not pause unexpectedly.
- Use the log before and after rule changes to verify the impact on ad campaign traffic quality.
Get started
Use Traffic Log before scaling protection.
Create one route, review the first decisions, then widen the rules only after the log proves the pattern.