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 What10Bot/2.0 (+https://what10.com/bot).

clear
TimestampUser AgentAssets
2026-08-04 09:25:13.956 UTC
What10Bot/2.0 (+https://what10.com/bot)
0
no JS

By user agent

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

User AgentRequestsJS ran
What10Bot/2.0 (+https://what10.com/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 What10Bot/2.0 (+https://what10.com/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
/sitemap.xml 1 1
/robots.txt 1 1

Requests (2 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-08-04 09:25:11.384 UTC /sitemap.xml What10Bot/2.0 (+https://what10.com/bot)
2026-08-04 09:25:11.146 UTC /robots.txt What10Bot/2.0 (+https://what10.com/bot)

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