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 TLM-Audit-Scanner/1.0.
| Timestamp | User Agent | Assets |
|---|---|---|
| 2026-06-24 21:23:02.376 UTC | TLM-Audit-Scanner/1.0 | 0 |
no JS— | ||
| 2026-06-24 21:23:02.373 UTC | TLM-Audit-Scanner/1.0 | 0 |
no JS— | ||
| 2026-06-24 21:23:02.316 UTC | TLM-Audit-Scanner/1.0 | 0 |
no JS— | ||
| 2026-06-24 03:35:56.143 UTC | TLM-Audit-Scanner/1.0 | 0 |
no JS— | ||
| 2026-06-24 03:35:56.141 UTC | TLM-Audit-Scanner/1.0 | 0 |
no JS— | ||
| 2026-06-24 03:35:56.078 UTC | TLM-Audit-Scanner/1.0 | 0 |
no JS— | ||
By user agent
Running counts across the last 200 homepage requests (97 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 TLM-Audit-Scanner/1.0.
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 |
|---|---|---|
| /.well-known/stripe.txt | 4 | 1 |
| /.well-known/stripe/ | 4 | 1 |
| /.well-known/acme-challenge/* | 4 | 1 |
| /.well-known/* | 4 | 1 |
| /.well-known/acme-challenge/ | 4 | 1 |
Requests (20 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.