WebRTC gathers no ICE candidates (disabled/blocked)
br.webrtc_unavailable ·
What it catches
Camoufox disables WebRTC (fires); stock headless Firefox keeps it (does not). v0.74.1: category corrected artifact->ENVIRONMENT — the original premise ('a real browser never is [WebRTC-disabled]') is FALSE. Disabling WebRTC is a common, legitimate privacy/enterprise CONFIGURATION (Firefox media.peerconnection.enabled=false, uBlock Origin's 'prevent WebRTC IP leak', Brave's WebRTC policy, corporate policy), so a real privacy-conscious user trips it — it must only CORROBORATE (cap at suspicious), never convict, per the conviction-gate principle that a real browser must not be trippable into a bot label. A WebRTC-disabling anti-detect tool with OTHER convicting tells (camoufox-hardened: pointer_touch_incoherent; zendriver: chrome_runtime_missing) is still caught; a headful tool whose ONLY tell was this (camoufox-headful) correctly drops to suspicious rather than risk a privacy-user FP.
Signals it reads
browser.webrtc_unavailable
How it fires
present