TiloBox
Back to directory
curl-impersonate project preview

curl-impersonate

Special build of curl that can impersonate the four major browsers at the TLS handshake level.

LicenseMIT
GitHub stars7.5k
Last commit1 weeks ago
Tags6 topics
Tls FingerprintingHttp2CDeveloper ToolsCurlJa3 Fingerprint
Overview

Why consider curl-impersonate?

curl-impersonate is a special build of curl that impersonates Chrome, Firefox, Edge, and Safari at the TLS and HTTP/2 handshake layers. It matches TLS Client Hello ciphers and JA3/JA4 fingerprints to prevent anti-bot blocking.

Guided learning

Learn curl-impersonate by building

Practical setup notes, real use cases, and copy-ready examples in one focused guide.

1 min read 2 sections
In this guide2 sections

Overview of curl-impersonate

curl-impersonate mimics browser-specific TLS parameters (cipher suites, extensions, elliptic curves) to communicate transparently with protected endpoints.

Quickstart

bash
1# Run Chrome-impersonated curl
2curl_chrome116 https://tls.peet.ws/api/all

curl-impersonate is licensed under the permissive MIT License.

Related tools

More options with a similar category or technology profile.

curl-impersonate FAQs

curl-impersonate is listed as a Developer Tools tool on TiloBox. Review the overview, features, and official documentation on this page to decide whether it solves your specific workflow.

Start with the project's GitHub repository for supported installation and deployment instructions. Test the setup with representative data or a small project before rolling it out more widely.

curl-impersonate is listed under the MIT license. Read the complete license text and the project's notices before using, modifying, or distributing the software.

Production readiness depends on your requirements. Review maintenance activity, security practices, documentation, backup and upgrade procedures, and compatibility with your stack; then validate it in a non-production environment.

curl-impersonate is listed as an alternative to ZenRows. Compare the core workflow, deployment model, integrations, and licensing against your must-have requirements before switching.