ua-tracer by Paul Kinlan

recent traces · ua-tracer

ua-tracer

what does a user agent actually fetch, follow & run?

All recent homepage requests, newest first. This page does not mint a new trace (unlike /), so you can browse the log without adding noise.

Recent homepage requests

Filter by user agent and the matching requests appear right below. Showing requests whose user agent contains PurityBot/1.0 (+https://puri.li/bot).

clear
TimestampUser AgentAssets
2026-07-15 13:01:59.531 UTC
PurityBot/1.0 (+https://puri.li/bot)
0
no JS

By user agent

Running counts across all 4024 homepage requests (1 distinct agents). Click one to set the filter above.

User AgentRequestsJS ran
PurityBot/1.0 (+https://puri.li/bot)
1 0

Unsolicited / well-known requests

Paths a user agent fetched on its own that ua-tracer never links to: robots.txt, sitemap.xml, /.well-known/*, llms.txt, the root favicon, and similar. Reveals what an agent probes on its own initiative.

Filtered to user agent PurityBot/1.0 (+https://puri.li/bot). clear filters

By path

Each unsolicited path with its request count and how many distinct user agents hit it. Click a path to see the individual requests; click a user agent below to reverse-look-up everything that UA did.

PathRequestsDistinct UAs
/robots.txt 1 1

Requests (1 shown)

The Related trace column links a probe to a homepage trace from the same user agent and IP within 30 minutes (the same crawler that fetched a well-known file usually also loaded /). The offset shows how long before/after the probe that trace was minted.

TimestampPathUser Agent (click for reverse lookup)Related trace
2026-07-15 12:22:22.799 UTC /robots.txt PurityBot/1.0 (+https://puri.li/bot)

← back to the live tracer (mints a new trace)