Command palette
Search pages and actions
Overview
The proxy fleet at a glance — health first, then where the capacity sits.
Is the fleet healthy?
proxies healthy
…
live edge ports
not answering
…
dead or stale
countries
…
distinct origins
free tier
…
fresh spiderproxies
Which exits fail p0f?
p0f usable now
…
healthy, current health check, matching measurement ≤6h
stored matches
…
includes old results and unavailable proxies
stored mismatches
…
0 ours
unknown · not a pass
…
missing target, unmeasured, ambiguous or unrecognized
Reading p0fTCP evidence, not browser identity
- Stored match ≠ usable
- Usable requires a healthy proxy, current health check, and a matching measurement no more than 6 hours old. Unknown is not a pass; zero mismatches alone is not a complete pass.
- Android and Linux
- Android uses a Linux TCP stack: a Linux-family measurement can match an Android target. It does not prove an Android device or browser.
- Apple exits
- macOS can describe an already-measured Apple exit. It does not mean a Linux exit can be configured to present macOS or iOS.
- Provider relays
- The provider may originate the SYN. An ambiguous result cannot distinguish the TCP family; a declared target cannot turn it into a measurement.
- TCP only
- p0f uses TCP fingerprint heuristics, not proof of the host OS or browser identity. Browser, TLS and WebRTC checks are separate.
| Declared target → measured TCP family | ||||
|---|---|---|---|---|
What is verifying and cleaning the fleet?
Loading the run log…
Proxies by pool
Where the fleet's capacity sits
No data in this window