A comprehensive VPN leak test needs to compare traffic routes, DNS behavior, and browser network interfaces while a VPN is enabled. This site does not probe WebRTC, DNS resolvers, or other interfaces, so it cannot certify that a VPN has no leaks.
A basic address comparison
Compare the public address shown by this site before and after connecting your VPN. The connection dashboard reports the address visible to this server; on localhost, that may be the XAMPP server’s egress address rather than the browser’s VPN route.
Limits and safer testing
An address change is only one signal and does not establish that every app uses the tunnel. Follow your VPN provider’s instructions for platform-specific DNS and routing checks, understand what those tests collect, and avoid entering account credentials into third-party test pages.