The test shows DNS leaks and your external IP. If you use the same ASN for DNS and connection - you have no leak, otherwise here might be a problem.
Please, before use make sure you have curl and ping installed.
- Download dnsleaktest.sh
curl https://raw.githubusercontent.com/macvk/dnsleaktest/master/dnsleaktest.sh -o dnsleaktest.sh
chmod +x dnsleaktest.sh
- Run dnsleaktest.sh
./dnsleaktest.sh
- Download dnsleaktest.py
curl https://raw.githubusercontent.com/macvk/dnsleaktest/master/dnsleaktest.py -o dnsleaktest.py
chmod +x dnsleaktest.py
- Run dnsleaktest.py
./dnsleaktest.py
- Download dnsleaktest.bat
powershell -command "& { (New-Object Net.WebClient).DownloadFile('https://raw.githubusercontent.com/macvk/dnsleaktest/master/dnsleaktest.bat', 'dnsleaktest.bat') }"
- Run dnsleaktest.bat
dnsleaktest.bat
You can use prebuilt executable binary for Linux, MacOs or Windows created by travis-ci.org:
- Download dnsleaktest v1.3
chmod +x dnsleaktest
- Run dnsleaktest
./dnsleaktest
-
Download dnsleaktest.exe v1.3
-
Run dnsleaktest.exe, open cmd then navigate to the exe file
dnsleaktest.exe
- Linux & macOS
GOOS=linux GOARCH=386 go build -o dnsleaktest dnsleaktest.go
- Windows
GOOS=windows GOARCH=386 go build -o dnsleaktest.exe dnsleaktest.go
Use host networking so the test sees the host's network stack and DNS configuration. This is important when the host uses a local DNS resolver such as systemd-resolved or NextDNS.
docker run --rm --network host python:alpine sh -c 'wget -q -O- https://raw.githubusercontent.com/macvk/dnsleaktest/master/dnsleaktest.py | python'
Docker Desktop runs containers in a virtual machine, so host networking does not provide the same view of the host's DNS configuration as it does on Linux. The following command tests the DNS configuration visible inside the container:
docker run --rm python:alpine sh -c 'wget -q -O- https://raw.githubusercontent.com/macvk/dnsleaktest/master/dnsleaktest.py | python'