NexBrowser指纹浏览器-官方博客Blog
Proxy Connected but IP Mismatch on Detection Page: Identify Which Column First, Then Troubleshoot by Cause
An IP mismatch on a detection page doesn't necessarily mean the proxy isn't working; first identify whether the mismatch is in the main IP, WebRTC, IPv6, or geolocation label, then address gateway vs. exit confusion, dynamic rotation, UDP bypass, dual-stack direct connection, extension conflicts, and database differences, and finally re-verify the exit in the environment.
WebRTC Fingerprint Leak Prevention: mDNS Only Masks Local IPs; What Really Matters Is Whether STUN Goes Through the Proxy
mDNS only hides local IPs; to truly prevent WebRTC leaks, verify that STUN's UDP traffic follows the proxy and that the srflx public IP matches the HTTP egress IP.
