Crawler Fingerprint Analyzer

Comprehensive browser fingerprint analysis for crawler stealth validation

Label: unlabeled | Report ID: 294bbab1-61a6-484a-a942-704674e42968 | 2026-05-22T07:43:15.031Z
Tip: visit with ?label=chrome-real, ?label=brave-real, ?label=safari-real, ?label=our-stealth.
All saved reports | Diff two reports

Capturing raw signals…

Server-Side Analysis (HTTP Request)

✗
User-Agent string HTTP Headers
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
Matched automation pattern: /bot/i
✗
Accept-Language presence HTTP Headers
(missing)
Missing — headless browsers often omit Accept-Language
✗
Accept-Language quality weights HTTP Headers
(missing)
Missing Accept-Language
✓
Pragma header (automation artifact) HTTP Headers
(absent — correct)
No Pragma header — matches real browser behavior
!
Sec-CH-UA Client Hints HTTP Headers
(missing)
Missing (may be HTTP/1.1 or non-Chromium)
✓
Header order (Chrome reference) HTTP Headers
host, user-agent, accept, accept-encoding, x-forwarded-for, x-forwarded-host, x-forwarded-port, x-forwarded-proto, x-forwarded-server, x-real-ip
Header order matches known Chrome pattern
!
Accept header HTTP Headers
*/*
Does not include text/html
✓
Accept-Encoding HTTP Headers
gzip, br, zstd, deflate
Supports gzip + br — matches modern Chrome
!
Sec-Fetch-* headers HTTP Headers
site=, mode=, user=, dest=
Some Sec-Fetch headers missing — may indicate non-browser request
✓
Platform ↔ UA consistency HTTP Headers
Platform: (none), UA OS: unknown
Sec-CH-UA-Platform matches User-Agent OS
i
Connection header HTTP Headers
(missing)
Informational — HTTP/2 does not use Connection header
i
Client IP address Network
10.42.0.1
Check against datacenter IP ranges (AWS, GCP, Azure, Hetzner, OVH, DigitalOcean) — datacenter IPs are flagged by anti-bot systems
i
TLS fingerprint (JA3/JA4) TLS / HTTP/2
(not available — server running in HTTP mode or behind TLS-terminating proxy)
Start with HTTPS mode (node index.js --https) to capture TLS fingerprints, or deploy fingerproxy sidecar in K8s.
i
HTTP/2 fingerprint TLS / HTTP/2
Request protocol: HTTP/1.1
HTTP/2 SETTINGS/WINDOW_UPDATE/priority frames create a fingerprint. Use browserleaks.com/http2 to verify.
i
All request headers (raw order) Raw Data
Host: fingerprint.venus.miguvino.com User-Agent: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com) Accept: */* Accept-Encoding: gzip, br, zstd, deflate X-Forwarded-For: 10.42.0.1 X-Forwarded-Host: fingerprint.venus.miguvino.com X-Forwarded-Port: 443 X-Forwarded-Proto: https X-Forwarded-Server: traefik-c98fdf6fb-kksw5 X-Real-Ip: 10.42.0.1
Complete headers as received by the server, in original order

Client-Side Analysis (JavaScript Fingerprint)

Running client-side fingerprint checks...

External Test Sites

CreepJS (comprehensive) Rebrowser Bot Detector bot.incolumitas (30+ tests) DeviceAndBrowserInfo BrowserLeaks (all tests) BrowserLeaks TLS/JA3 BrowserLeaks HTTP/2 Pixelscan SannySoft Bot Test BrowserScan BrowserScan TLS/JA4 AmIUnique Cover Your Tracks (EFF)