recent traces · 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 Pandalytics/2.0 (+https://domainsbot.com/network-crawler-pandalytics-kdc68dhsbd/).
| Timestamp | User Agent | Assets |
|---|---|---|
| 2026-08-15 04:44:13.246 UTC | Pandalytics/2.0 (+https://domainsbot.com/network-crawler-pandalytics-kdc68dhsbd/) |
0 |
no JS— | ||
By user agent
Running counts across all 7591 homepage requests (1 distinct agents). Click one to set the filter above.
| User Agent | Requests | JS ran |
|---|---|---|
Pandalytics/2.0 (+https://domainsbot.com/network-crawler-pandalytics-kdc68dhsbd/) |
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 Pandalytics/2.0 (+https://domainsbot.com/network-crawler-pandalytics-kdc68dhsbd/).
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-08-15 04:44:12.776 UTC | /robots.txt | Pandalytics/2.0 (+https://domainsbot.com/network-crawler-pandalytics-kdc68dhsbd/) | 6Xsdnow4 (+470ms) |