Skip to content

v0.1.0 — browser-exact TLS fingerprint

Choose a tag to compare

@North-web-dev North-web-dev released this 02 Jul 16:31
· 8 commits to main since this release

A drop-in Go *http.Client whose TLS ClientHello is byte-identical to a real browser (Chrome/Firefox/Safari/Edge/iOS) — survive JA3/JA4 fingerprinting without a headless browser, CGo, or curl.

client := impersonate.New(impersonate.Chrome)
resp, _ := client.Get("https://example.com")

Verified against tls.peet.ws — each profile's JA4 matches the real browser (Chrome t13d1516h2_8daaf6152771).

Scope: TLS (JA3/JA4) + default headers are browser-exact. HTTP/2 frame-level (Akamai) fingerprint is Go's stack for now — browser-exact h2 is the v0.2 roadmap, documented honestly.

Only deps: uTLS + x/net. MIT.