A WebRTC leak and proxy detection are 2 different things. If IPFighter shows a WebRTC leak, it means your real IP could still be exposed through the browser, even if the proxy itself isn't being flagged. That's probably why the proxy status shows "no" while the leak is still reported. If Pixelscan also looks clean, the proxy is likely decent, but I'd still fix the WebRTC leak if you're using the setup for accounts where anonymity matters. Better to have both the proxy and browser fingerprint fully protected.