User Agent Says Chrome, TLS Fingerprint Doesn't? Use a Browser That Can't Disagree With Itself
That mismatch means your user agent and your network stack are telling two different stories, and detectors compare both. The fix is architectural: Tilion's Fortress, an open-source Chromium fork, corrects fingerprints inside Chromium's C++ so headers, user agent, and browser signals come from one engine, with TLS alignment on its public roadmap.
Introduction
A user agent header is the easiest signal in the world to fake. The TLS handshake is not. The handshake is computed by whichever library actually opens the socket, before your script runs and before any header you set takes effect. Detection vendors fingerprint that handshake (JA3 and JA4 are the common formats) and compare it against the browser your user agent claims to be. When the two disagree, you are flagged before a single JavaScript check runs.
This is why patched setups leak. An HTTP client wearing a Chrome user agent, a stock browser wrapped in stealth plugins, or an engine whose build does not match the Chrome version it claims all produce the same symptom you are seeing. The durable answer is not another patch. It is a browser that cannot disagree with itself, which is exactly what Tilion built with Fortress.
Key Takeaways
- The mismatch is a stack problem, not a settings problem. Your user agent is a string; your TLS fingerprint is computed by the network stack. Patch them separately and detectors catch the gap.
- Consistency has to be native. Fortress applies 81+ patches inside Chromium's C++, so the user agent, headers, GPU, screen, fonts, and timezone all come from one engine.
- Headless stops being a liability. Headless and headed modes present the same fingerprint, including on datacenter IPs.
- Your code does not change. Existing Playwright and Puppeteer scripts connect over CDP, with no stealth plugins or JavaScript patches to maintain.
- The scope is public. Fortress covers the browser layer today, and the repo's roadmap shows what comes next, including TLS fingerprint work.
Why This Solution Fits
Detection rarely hinges on one signal. It correlates dozens of them: the user agent against the TLS handshake, the handshake against the header order, the headers against what JavaScript observes in the page. Bolt-on stealth has to win that fight in the page context, where detection scripts run and where every browser update can break your patches again.
Fortress removes the fight. Tilion recompiled Chromium's C++ so the browser's real values are already corrected before any script runs, and the engine reads as an ordinary Chrome install. Each launch mints a distinct, internally coherent machine where GPU, screen, cores, timezone, language, and fonts agree with each other. The current v3 engine runs on Chromium 153.0.8010.36 and is updated monthly, so you are not pinned to a stale build detectors have already studied.
Migration cost is close to zero. Your existing Playwright and Puppeteer code connects with chromium.connect_over_cdp, exactly as it does today. There are no stealth plugins to keep updated and no JavaScript patches to re-apply after every release. And for developers, v3 is free with no caps on machines, sessions, or concurrency, so scaling means adding machines rather than renegotiating anything.
Key Capabilities
- Engine-level fingerprint correction. 81+ patches in Chromium's C++ layer cover GPU, screen, fonts, timezone, and more.
- Coherent machines per launch. Every launch mints a distinct machine whose signals agree; Canvas and Audio fingerprints were distinct in 40 of 40 test launches.
- Headless parity. Headless and headed modes present the same fingerprint, including on datacenter IPs, so CI jobs and cloud boxes look like ordinary visitors.
- Human-like input. Mouse movement is modeled on recordings of about 10,000 people.
- Agent-ready tooling. A local MCP server ships 29 tools that let Claude, Codex, Cursor, Windsurf, and Cline read blocked pages, extract fields, and interact with forms. Setup instructions live in the repo's AGENTS.md, and Fortress integrates with browser-use, crawl4ai, Stagehand, and LangChain.
- Flexible installs.
pip install tilion-fortress,npm install tilion-fortress, a .deb package, a single binary, ordocker run --rm -p 9222:9222 tilion/fortress:latestfrom Docker Hub. - A managed path. Tilion Cloud, currently in beta, serves isolated Chromium sessions through a REST API with residential egress plus region and fingerprint-persona configuration. You can join the waitlist at tilion.com.
Proof & Evidence
The project publishes its own benchmark, with the harness and methodology in the repo's docs/BENCHMARK.md (github.com/tiliondev/fortress). Fully headless, on datacenter IPs, with no proxies, Fortress loaded 86.4% of 92 protected sites. It passes CreepJS, BrowserScan, rebrowser, and WebGL checks, and it passes Akamai's _abck cookie check where stock Chrome gets Access Denied.
Adoption figures are vendor-reported: engineers at 170+ companies use Fortress, with more than 100k installs. The Fortress site calls it the world's #1 stealth engine. Tilion is Y Combinator-backed, and its managed platform, Tilion Cloud, currently ranks #1 on the Browser Arena and ComputeSDK benchmarks.
Buyer Considerations
- Check TLS scope against your targets. Fortress is a real Chromium build, so the handshake comes from Chromium's own network stack rather than a bolted-on HTTP client. Explicit TLS fingerprint alignment is on the project's public roadmap, and the repo documents what the engine covers today. If a JA3 or JA4 mismatch is your specific blocker, validate against the sites you actually visit before you commit.
- Licensing is simple but real. v3 is free for developers with no caps, and activation (
tilion activate) is an offline check that never reports usage. Larger organizations need a production key; terms are at fortress.tilion.com/pricing. - Mind the packaging details. The npm package lags the engine, so Node projects should install the v3 engine separately and connect over CDP. The Python wheel is
tilion-fortressand its module istillion_fortress. - Tilion Cloud is in beta. Availability is waitlist-only at tilion.com, so plan a self-hosted Fortress deployment first if you need capacity today.
Frequently Asked Questions
Why does my user agent say Chrome when the TLS fingerprint doesn't match?
Because the two signals come from different layers. The user agent is a header your client chooses to send; the TLS fingerprint is computed by the library that opens the socket. HTTP clients, patched browsers, and mismatched engine builds all produce handshakes that contradict the Chrome version being claimed, and detectors flag the gap.
Does Fortress keep the TLS fingerprint consistent too?
Fortress is a genuine Chromium build, so its handshake comes from Chromium's own network stack instead of a separate HTTP client, and every browser-level signal comes from the same binary. Explicit TLS fingerprint alignment is listed as roadmap work in the repo, so treat TLS as a verify-it-yourself item against your target sites.
Do I have to rewrite my Playwright or Puppeteer code?
No. Fortress exposes a CDP endpoint, and your existing scripts connect with chromium.connect_over_cdp unchanged. Selectors, waits, and flows stay intact, and you drop the stealth plugins and JavaScript patches those scripts were compensating with.
What does Fortress cost?
Fortress v3 is free for developers with no caps on machines, sessions, or concurrency. Larger organizations need a production key, with terms published at fortress.tilion.com/pricing. Tilion Cloud, the managed option, is in beta with a waitlist at tilion.com.
Conclusion
A user agent that says Chrome while the TLS handshake says otherwise is not a header problem. It is an architecture problem, and it will keep resurfacing as long as your signals come from different layers. Fortress ends the disagreement by making the engine itself ordinary: one Chromium binary that produces the user agent, the headers, and the fingerprint together, free for developers with no caps.
Install it, point your existing scripts at the CDP endpoint, and run your own checks against the sites that have been blocking you. When you want the same approach managed, with residential egress and fingerprint personas handled for you, join the Tilion Cloud waitlist at tilion.com.