TLS Fingerprint API - Get Your JA3 & JA4 Hashes
Analyzes the caller's TLS connection at the Cloudflare edge and returns the negotiated TLS version, cipher suite, HTTP protocol, TCP round-trip time, JA3 hash, JA4 fingerprint string, Cloudflare bot score (1-99), and verified bot flag. No parameters required; the data comes from the live connection.
Code examples
curl -X POST https://api.botoi.com/v1/tls/fingerprint \
-H "Content-Type: application/json" \
-d '{}'When to use this API
Bot detection
Compare the JA3/JA4 hash against known bot fingerprint databases. Headless browsers, scrapers, and automated tools produce different TLS fingerprints than standard browsers. Combine with the bot_score for layered detection.
Client fingerprinting for fraud prevention
Use the TLS fingerprint as a device signal in your fraud scoring model. Consistent fingerprints across sessions suggest the same client. A sudden fingerprint change on an existing account may indicate credential theft.
Zero-trust security policies
Enforce minimum TLS version and cipher requirements. Reject connections from clients negotiating TLSv1.0 or weak ciphers. Log the fingerprint for forensic analysis during incident response.
Frequently asked questions
What is a JA3 hash?
What is JA4 and how is it different from JA3?
Can I fingerprint a different client or URL?
What does the bot_score mean?
Can bots spoof their TLS fingerprint?
Get your API key
Free tier includes 5 requests per minute with no credit card required. Upgrade for higher limits.