Network

WebRTC Fingerprint

WebRTC capabilities and IP leakage checks. Detect peer connection support and potential network exposure signals.

Live signal

Analyzing your browser…0%
Creating peer connection
Gathering ICE candidates
Inspecting exposed network signals
Testing connection capabilities
Summarizing network observations

API integration

Send a complete collected fingerprint to the authenticated API endpoint.

fetch('https://api.creepjs.org/v1/fingerprint', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'X-API-Token': 'YOUR_API_TOKEN'
  },
  body: JSON.stringify(fingerprint)
});

What CreepJS reports

CreepJS runs the WebRTC Fingerprint collector in the current browser. It inspects the browser surface represented by this network signal and reports the observed value or availability state, collection timing, and any collector error. The live result is local browser evidence, not a population estimate.

How to interpret it

Use WebRTC Fingerprint as one observation alongside other signals. Different browsers, devices, settings, and permissions may return different values. An unsupported or blocked API may return no value. A single signal does not identify a person.

Limits

This reference makes no uniqueness, match-rate, or fraud-probability claim. Results can change after browser, operating-system, hardware, permission, privacy-setting, or driver changes. Treat unavailable data as unavailable, not as evidence of safety or risk.

Test the signal

Reviewed: 2026-07-28.

Compare related fingerprint signals

Move from this collector to the CreepJS signal index, live checker, API docs, and other high-value fingerprinting explainers.