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 Mozilla/5.0 (compatible; DemoBot/1.0; +https://example.com).
| Timestamp | User Agent | Assets |
|---|---|---|
| 2026-07-02 18:33:20.470 UTC | Mozilla/5.0 (compatible; DemoBot/1.0; +https://example.com) |
7 |
JS ranCSSJSimgcss-bgcss-font | ||
| 2026-07-02 13:49:02.699 UTC | Mozilla/5.0 (compatible; DemoBot/1.0; +https://example.com) |
4 |
JS ranCSSJScss-bg | ||
By user agent
Running counts across all 1401 homepage requests (1 distinct agents). Click one to set the filter above.
| User Agent | Requests | JS ran |
|---|---|---|
| Mozilla/5.0 (compatible; DemoBot/1.0; +https://example.com) | 2 | 2 |
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 Mozilla/5.0 (compatible; DemoBot/1.0; +https://example.com).
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.
No unsolicited paths fetched yet.
Requests (0 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.
No unsolicited probe requests match the current filter.