WebRTC Public IP & STUN NAT Candidate Inspector
STUN ProbeInspect WebRTC candidate gathering, discover public IPv4/IPv6 addresses, and diagnose STUN NAT traversal directly in your browser. Utilizing the native RTCPeerConnection API, this utility evaluates WebRTC connectivity, candidate types (host, srflx, relay), and potential IP leakage with zero server tracking.
WebRTC Public IP & STUN NAT Candidate Inspector
Inspect WebRTC ICE candidates, NAT traversal types, public IPv4/IPv6, and STUN server latency in real time.
Interactive WebRTC Public IP & STUN NAT Candidate Inspector Workspace
Discover your public IP address, assigned NAT reflexive port, and ICE candidate hierarchy (host, srflx, relay) directly in browser memory using native WebRTC RTCPeerConnection and public STUN relays.
How This Tool Works (100% Client-Side Engine)
The tool creates a local RTCPeerConnection configured with public STUN servers (stun:stun.l.google.com:19302). It generates an SDP offer via createOffer() and listens to onicecandidate events. When candidates arrive, the tool parses candidate strings to extract IP addresses, port numbers, transport protocols (UDP/TCP), and candidate types (host, srflx).
Step-by-Step Guide
Start WebRTC Candidate Gathering
Click Gather Candidates to initialize a local RTCPeerConnection session in your browser.
Inspect Gathered ICE Candidates
Review the live log of gathered candidates showing IP addresses, ports, protocols, and priority metrics.
Review Public IP & NAT Status
Inspect detected public IPv4/IPv6 addresses and verify whether your browser leaks local network IPs.
Why Use This Tool: Privacy & Performance
WebRTC (Web Real-Time Communication) powers browser-based video calling, voice chat, and peer-to-peer data transfers in apps like Google Meet, Discord, and Zoom. To establish peer connections across firewalls, WebRTC uses the Interactive Connectivity Establishment (ICE) protocol with Session Traversal Utilities for NAT (STUN) servers. However, misconfigured routers, symmetric NATs, or aggressive VPN tunnels can block WebRTC candidate gathering, causing dropped calls or silent "connecting..." loops. Furthermore, privacy advocates need to verify whether WebRTC is inadvertently leaking true local or public IP addresses past active VPN connections. ToolByte WebRTC & STUN NAT Inspector creates a temporary local RTCPeerConnection in your browser. It triggers ICE candidate gathering against public Google STUN servers, logs every gathered candidate (host, server reflexive, and relay), identifies NAT mapping types, and displays detected public IPv4 and IPv6 addresses in real time with complete confidentiality.
Common Use Cases & Workflows
Detecting WebRTC VPN IP Leaks
Verify whether your true ISP public IP address is exposed through WebRTC while an active VPN connection is running.
Troubleshooting Video Call & VoIP Failures
Diagnose whether restrictive enterprise firewalls are blocking UDP STUN packets needed for Google Meet or Discord calls.
Inspecting Local vs. Public ICE Candidates
Review local host candidates (private IP / mDNS) and server reflexive candidates (srflx) to understand NAT traversal.
Network Engineering & WebRTC Development
Audit ICE gathering timing and connection state transitions when building custom peer-to-peer web applications.
Technical Limitations & Operational Boundaries
Frequently Asked Questions
Recommended Utilities Complementary to WebRTC NAT & STUN
High-performance tools running 100% in local browser memory with zero server data retention.