See every traffic decision, not just a final score.
Traffic Log gives operators a visible record of how KillBot handled each visit, including visitor context, matched category, reason, route source, and final outcome.
- Review allowed, redirected, blocked, and rate-limited visits
- See IP, country, ASN, network, category, and reason
- Understand whether a Protected Page or Smart Link handled the request
- Tune routing rules from real visit evidence
| Time | Visitor | Source / Category | Decision |
|---|---|---|---|
| 10:24 |
73.162.0.42
US · Comcast
|
Protected Page · No match
Clean route
|
Allowed |
| 10:18 |
35.178.123.114
GB · FireHOL Proxy
|
Smart Link · Proxy
Proxy feed match
|
Redirected |
| 10:05 |
17.241.208.161
US · Apple
|
Protected Page · Search bot
Bot category
|
Blocked |
| 09:52 |
185.213.155.247
DE · Datacenter
|
Smart Link · Datacenter
Hosting provider
|
Redirected |
| 09:41 |
187.45.0.18
BR · Mobile ISP
|
Protected Page · Repeat visit
Repeat threshold
|
Rate-limited |
What one logged decision shows.
Every line in the log is a full account of one visit — enough context to explain the outcome to a teammate, a client, or a support reviewer.
- IP address
- 35.178.123.114
- Country
- United Kingdom (GB)
- ASN / Organization
- AS16509 · Amazon AWS
- Source route
- Protected Page · /summer-offer
- Category
- Proxy · FireHOL feed
- Reason
- Matched proxy feed; redirect-first mode active
- Decision
- Redirected
- Destination outcome
- example.com/safe
- Time
- 2026-05-27 10:18:42 UTC
What the log records.
| Field | Why it matters |
|---|---|
| IP and country | Confirms where the request came from and whether geography matches page policy. |
| ASN / ISP / organization | Helps identify hosting, datacenter, proxy, VPN, and suspicious infrastructure. |
| Category and reason | Explains why the request matched a risk bucket. |
| Route source | Shows whether a Protected Page or Smart Link handled the visit. |
| Decision | Shows whether the visit was allowed, redirected, blocked, or rate-limited. |
| Destination outcome | Confirms where the visitor was sent. |
How teams use Traffic Log operationally.
Verify rollout
Confirm the first live requests after adding a Protected Page or Smart Link.
Tune policies
Adjust country, referrer, schedule, and repeat-visit rules based on real outcomes.
Explain decisions
Give operators, clients, or support teams a clear reason for each outcome.
Compare routes
See whether the page layer or link layer is producing the cleaner decision path.
Traffic Log connects the product.
Protected Pages
Page-level decisions land here when a Protected Page handles a visit.
Explore Protected PagesSmart Links
Link-level decisions land here when a Smart Link handles a click.
Explore Smart LinksPricing
Plan controls retention window and monthly check usage.
View pricingTraffic Log guide
Use the public docs guide to review log fields, retention, and rollout proof in more detail.
Read guideRetention follows the plan.
Traffic Log retention depends on the active plan. The pricing page shows the included history window per plan, and the workspace dashboard warns operators before usage or retention limits affect review.
Common questions.
What does Traffic Log show?
Traffic Log shows every visit handled by KillBot — IP, country, ASN, source route, matched category, reason, decision, and destination outcome.
Are allowed visits logged too?
Yes. Allowed visits land in the log alongside redirected, blocked, and rate-limited ones so the team can see the full traffic picture, not just the risky tail.
Can I see why a visit was redirected or blocked?
Every entry shows the matched category, the signal that triggered it, and the route that handled the visit. The reason is plain enough to explain to a teammate or client.
Does Traffic Log work for Protected Pages and Smart Links?
Yes. Both route types feed into the same log with a "Source" column so operators can compare page-level and link-level decisions side by side.
How long are logs stored?
Retention is set by the active plan and visible on the pricing page. The dashboard surfaces both the retention window and the monthly check usage.
Use the log to prove the route before you scale.
Add one Protected Page or Smart Link, run risky traffic in redirect mode, and let Traffic Log show the pattern before you widen the rules.