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 Googlebot.
| Timestamp | User Agent | Assets |
|---|---|---|
| 2026-06-22 13:15:02.178 UTC | Googlebot | 0 |
no JS— | ||
| 2026-06-22 13:06:35.049 UTC | Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.7778.96 Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html) | 17 |
no JSCSSJSmoduleimgfaviconprefetchog-imgtwitter-imgiframe@import | ||
By user agent
Running counts across the last 200 homepage requests (69 distinct agents). Click one to set the filter above.
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 Googlebot.
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.
| Path | Requests | Distinct UAs |
|---|---|---|
| /robots.txt | 12 | 2 |
| /favicon.ico | 1 | 1 |
Requests (13 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.