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 ApcosysBot/1.0 (+https://apcosys.net).
| Timestamp | User Agent | Assets |
|---|---|---|
| 2026-10-22 13:56:22.856 UTC | ApcosysBot/1.0 (+https://apcosys.net) |
1 |
no JSfavicon | ||
By user agent
Running counts across all 20496 homepage requests (1 distinct agents). Click one to set the filter above.
| User Agent | Requests | JS ran |
|---|---|---|
ApcosysBot/1.0 (+https://apcosys.net) |
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 path /security.txt to user agent ApcosysBot/1.0 (+https://apcosys.net).
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 | 2 | 1 |
| /security.txt | 1 | 1 |
| /.well-known/security.txt | 1 | 1 |
Requests (2 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-10-22 13:56:29.861 UTC | /security.txt | ApcosysBot/1.0 (+https://apcosys.net) | — |
| 2026-10-22 13:56:28.009 UTC | /.well-known/security.txt | ApcosysBot/1.0 (+https://apcosys.net) | — |