Skip to content
IPOK

What IP data does ping0.cc send? A dated client-side observation

In a 2026-06 browser Network-panel review, the ping0.cc front end used RTCPeerConnection / STUN and sent a request to /ip/peer containing an ICE-candidate address. The page also sent a /logv6/... request whose path contained both IPv6 and IPv4 parameters. Separate v4/v6 endpoints are themselves a normal dual-stack technique.

The observation establishes that the browser transmitted those parameters to the relevant endpoints at that time, which users of a proxy or VPN may wish to include in a privacy review. A client-side capture cannot establish server retention, retention period, later use, operator intent, or that the current implementation is unchanged.

To review current behavior, use the browser Network panel only with authorization and under the site's terms, inspect peer, logv6, and single-stack requests, and read the latest privacy policy. Treat what you observe at that time as the evidence.

IPOK's WebRTC test runs only on click: the browser contacts Google / Cloudflare public STUN, while ICE candidates are parsed locally and never sent to IPOK. IPOK builds no account profile and has no session replay or tracking cookie; limited operational logs, IP-based quotas, sessions, and caches are disclosed in the privacy policy.

Your public IP
Up to 8 sources cross-verifiedOpen methodologyFree · no loginNo account profile · retention disclosed

FAQ

Does this prove ping0.cc stores my real IP?

No. The 2026-06 client-side observation only establishes that requests containing ICE-candidate and IPv4/IPv6 parameters reached endpoints at that time. It does not prove server retention, duration, purpose, or current behavior.

How can I review current network behavior?

With authorization and under the site's terms, inspect the current page's peer, logv6, and single-stack requests in the browser Network panel and read its latest privacy policy. The implementation may have changed.

What is IPOK's corresponding privacy boundary?

IPOK offers the same checks. Its WebRTC test runs only on click and contacts public STUN; ICE candidates stay on-device and are not sent to IPOK. IPOK builds no account profile and has no session replay or tracking cookie; limited operational logs, IP-based quotas, sessions, and caches are disclosed in the privacy policy.

How do I reduce WebRTC exposure?

Review browser and network settings appropriate to your authorized setup, and use a test that clearly discloses its STUN and candidate data flow. A private/mDNS-only or no-public-candidate result is unknown, not proof of safety.

How does this page compare ping0 and IPOK?

It compares observable data flow and current disclosed implementation only: the 2026-06 ping0 client requests carried ICE and dual-stack parameters; IPOK runs WebRTC only on click, does not send ICE candidates to IPOK, and does not create an application-level v4/v6 pairing record. This does not establish the other site's server retention or intent.

Related checks

ipinfo.io alternative: not just geolocation — IP risk & purity too | IPOK
proxycheck.io alternative: proxy detection + multi-source cross-check, no key | IPOK