BlankTrail Proxy Documentation
BlankTrail Proxy is a local proxy that gives your automation, scraping and testing tools an authentic browser network identity. This documentation covers installation, the dashboard, the system tray and the full local API.
What is BlankTrail Proxy?
BlankTrail Proxy runs on your own machine or server and sits between your tool and the internet. Point any application that supports an HTTP or SOCKS5 proxy at a BlankTrail Proxy port, and every request leaves with a coherent, real-browser fingerprint — no changes to your scripts required.
It works with browser-automation frameworks (Playwright, Puppeteer, Selenium), scrapers and parsers, plain HTTP clients, and anti-detect browsers. Each proxy port carries its own identity and its own upstream, so you can run many independent workers side by side.
- Authentic browser TLS and HTTP/2 identities, applied per port.
- Per-port upstream proxies and multi-hop chains (SOCKS5, HTTP, OpenVPN, VLESS).
- A built-in dashboard, a system-tray launcher, and a full local API.
- Optional response caching to cut pay-per-GB proxy bills.
- DNS / IPv6 leak-guard that checks an egress before a port goes live.
Key concepts
A few terms appear throughout this documentation and across the dashboard:
| Term | Meaning |
|---|---|
| Proxy port | A local TCP port (SOCKS5 or HTTP) you point your tool at. Each port is configured independently. |
| Profile / Identity | The browser identity a port presents — browser family, version and operating system. You can randomize it, pick from the database, or capture a real one. |
| Upstream | An external proxy your traffic exits through after BlankTrail Proxy. Optional — leave it empty to go direct. |
| Chain / First hop | An optional extra proxy or tunnel placed before the upstream, so you can compose multi-hop routes. |
| Gateway | A saved OpenVPN or VLESS profile that a port (or a chain) can route through. |
| Preset | A saved port configuration you can re-apply later, organized into folders. |
| Domain routing rule | A rule that routes specific domains through a different upstream or applies different settings. |
| Port pool | A pool of ports opened from a proxy list for large-scale, concurrent work — a fit for scrapers, parsers, posters and similar automation. |
| Term | Meaning |
|---|---|
| TLS interception (MITM) | The ordinary mode of a port: the connection is opened with our root certificate, so the chosen fingerprint can be sent outward and the content can be cached, logged and handed to the challenge solver. |
| TLS pass-through | The port does not open the connection: the CLIENT'S OWN fingerprint goes out. Fingerprint spoofing, the cache, the request log and Challenge Breaker then do not work — there is nothing to read. The checkbox is in the open-port dialog; switching it on by accident loses exactly what the port was opened for. |
| Interception (TUN) | A way to steer a program's or the whole machine's traffic into a port through the system, when there is nowhere to point the application at a proxy. It relies on a separate privileged service and works on Windows. |
| A license seat (device) | The license is bound to a device and has a limited number of seats. Reinstalling the system or cloning a virtual machine counts as a NEW device: the seat is freed in the account. |
Quick start
- Install BlankTrail Proxy and let it install its root certificate (see Installation).
- Open the dashboard at http://127.0.0.1:8891 and activate your license.
- Click + Open Port, choose a quick-start preset (Browser or HTTP client), and open a port.
- Point your tool at the port — for example socks5://127.0.0.1:20134.
- Send a request and confirm your traffic exits with the expected identity.
Where to go next
- Installation — install on Windows or Linux and activate your license.
- Dashboard — a guided tour of every tab and dialog, with screenshots.
- Connecting your apps — proxy settings and code examples for common tools.
- API reference — automate ports, profiles and everything else over HTTP.