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 LinkedInBot/1.0 (compatible; Mozilla/5.0; Apache-HttpClient +http://www.linkedin.com).
| Timestamp | User Agent | Assets |
|---|---|---|
| 2026-07-03 04:21:48.195 UTC | LinkedInBot/1.0 (compatible; Mozilla/5.0; Apache-HttpClient +http://www.linkedin.com) |
2 |
no JSimgog-img | ||
By user agent
Running counts across all 1908 homepage requests (1 distinct agents). Click one to set the filter above.
| User Agent | Requests | JS ran |
|---|---|---|
| LinkedInBot/1.0 (compatible; Mozilla/5.0; Apache-HttpClient +http://ww… | 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 LinkedInBot/1.0 (compatible; Mozilla/5.0; Apache-HttpClient +http://www.linkedin.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.
| Path | Requests | Distinct 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.
| Timestamp | Path | User Agent (click for reverse lookup) | Related trace |
|---|---|---|---|
| 2026-07-03 04:21:49.161 UTC | /robots.txt | LinkedInBot/1.0 (compatible; Mozilla/5.0; Apache-HttpClient +http://www.linkedin.com) | — |