Before you start
Use your normal trusted browser and the same reputable test page for both measurements. An IP or DNS test sees your test traffic: review its privacy information first. You never need to enter your subscription URL.
Write down the selected server, client mode and network type. These checks are observations, not a promise of anonymity, an audit or proof that every application is covered.
Your subscription URL is a credential. Anyone who receives it may be able to use your access. Keep it out of screenshots, public chats, browser searches and shared clipboard history. If exposed, ask Nimzo support to replace it.
Based on official client documentation. Controls and operating-system prompts can differ between versions.
Independent tools you can use
- test-ipv6.com — public IPv4/IPv6 and browser connectivity.
- DNSLeakTest — compare the DNS resolvers observed before and after connecting.
These are independent services, not Nimzo tools. They receive your test traffic and public network information when opened. No account or subscription URL is needed. A test result is an observation, not a security certificate.
Establish a disconnected baseline
Disconnect the client and confirm ordinary internet access works. Record the public IPv4 address shown by your chosen IP checker. If it reports an IPv6 address, record that separately. Keep these results private: public addresses can identify your network.
Use the same device, browser and network for the next comparison. A private browser window does not itself create a VPN connection.
Connect and compare public IP addresses
Connect to your intended server, wait for the client to settle, then reload the test in a fresh tab. Compare the actual addresses, not just a country label: location databases can be inaccurate.
If the IPv4 address remains your baseline, inspect the selected mode and routing rules. A system proxy may cover only compatible applications, while split routing can intentionally send some destinations directly. Test the particular app you need; browser results do not cover all device traffic.
Check the DNS resolution path
DNS translates names into addresses. Run a DNS test before and after connecting and compare the resolver names or network operators it reports. An unexpected ISP resolver is a reason to investigate the configured DNS and routing path, not a reason to declare the entire connection safe or broken from one label.
Browser encrypted DNS, operating-system DNS, cached answers and split routing can produce different results. Review the browser’s secure-DNS setting and the client’s DNS policy. Change one setting at a time and repeat; do not disable encrypted DNS blindly.
Compare IPv6 separately
A changed IPv4 address says nothing by itself about IPv6. If your baseline had public IPv6, check whether it is still visible after connecting. If it remains on your normal ISP route when you expected all traffic in the tunnel, review IPv6 handling with support.
If the test shows no IPv6, that only means the tested browser path did not expose a working public IPv6 connection at that moment. It does not establish how every app behaves or prove that IPv6 is disabled everywhere.
Source: Internet Society: IPv6 basics
Repeat under real conditions
Repeat after a Wi-Fi-to-mobile-data switch, sleep/wake or a server change. Open the apps you intend to use and check their behavior. A successful web test does not test background traffic, other protocols or behavior when a connection fails.
For a failure, note the time, network, operating system, client version, selected mode and redacted error. Send that summary privately to support. Never include the subscription URL or an unredacted QR code.
Troubleshooting
IP changes, but a site still fails
Check whether the site works with the connection off, then try another supplied server. A website can restrict addresses independently of your setup. A changed address does not promise access to any particular website or streaming service.
DNS results look unfamiliar
A resolver can belong to a hosting or DNS provider rather than the same organization as your exit IP. Compare your configured resolver with the observed result and ask support if it differs. Country labels and a simple “pass” badge are not enough to decide.
Results disagree across apps or tests
Check proxy versus tunnel mode, direct-route rules, browser DNS and IPv4 versus IPv6. Keep the test conditions consistent. If uncertain, avoid relying on the configuration for sensitive traffic until support has explained the route.
Need help with access or service rules? Read the Nimzo FAQ. P2P and torrents are not supported.
Need Nimzo access?
Get your subscription first, then return to the guide for your device.