
A multi-hop VPN routes your traffic through two VPN servers instead of one, so your connection enters the first server and exits through the second. Checking that it works means verifying the exit IP, the DNS path, and the app behaviour, not just trusting the connected label.
Surfshark, which we recommend for readers in Pakistan and promote as 80% off for our users, includes a multi-hop feature called Dynamic MultiHop, and this checklist works with it and with any other provider that offers double VPN routing.
This guide is a practical test checklist, not a lab report. Every step tells you what to check, what result to expect, and what to record, so you can confirm the feature is working on your own device and give your provider’s support team useful evidence if it is not.
Read the whole checklist before you start, because the order matters. You need a baseline recorded with the VPN off, then a single-hop comparison, then the multi-hop test itself. Changing several settings at once makes the results impossible to interpret, so change one thing at a time.
The Short Answer: How to Test Multi-Hop VPN
Turn the VPN off and record your real public IP address, your internet provider’s name, and your DNS resolvers. Then connect with a normal single-hop server and record the new exit IP. Then enable multi-hop, connect to the same exit country, and check the IP again.
If multi-hop is working, the exit IP should match the second server’s location, not the first server’s, and not your real IP. The DNS resolvers should belong to the VPN provider, not your Pakistani internet provider, and the IP should stay the same when you refresh the check.
That exit-IP check is the core of the test, but it is not the whole test. You also need to check for DNS leaks, IPv6 leaks, and WebRTC leaks, and you need to confirm that the apps you actually use are routing through the tunnel. A browser test alone proves nothing about your other apps.
Finally, record everything: the servers you selected, the IP addresses you saw, the time of each test, and screenshots of the results. If something is wrong, that record is what support needs to help you, and if everything is right, it is your proof that the feature works.
What Multi-Hop VPN Is, and What It Is Not
Multi-hop, also called double VPN, sends your traffic through two VPN servers in sequence. Your device connects to the first server, which forwards the traffic to the second server, which then sends it to the website you are visiting. The website sees only the second server’s IP address.
The purpose is to separate knowledge: the first server knows your real IP address but not your destination, and the second server knows your destination but not your real IP address. Neither server alone can connect the two, which is a stronger privacy position than a single hop.
Multi-hop is not a speed feature. Routing through two servers adds latency and usually lowers throughput, because your traffic travels further and passes through an extra hop. If you need the fastest possible connection, a single hop is the better choice, and multi-hop is a trade of speed for privacy.
Multi-hop is also not the same as a VPN chain you build yourself with two different providers. Most providers’ multi-hop features use their own servers for both hops, and the pairings are fixed or chosen from a list. Building your own chain is possible with manual configuration, but it is outside the scope of this checklist.
Finally, multi-hop does not hide the fact that you are using a VPN, and it does not guarantee access to any particular service. A website that blocks VPN traffic will still see a VPN server’s IP address, whether it arrives after one hop or two.
Prerequisites and Safe Test Conditions
Before you test, confirm that your provider actually offers multi-hop and that your plan includes it. Surfshark offers Dynamic MultiHop on its apps, NordVPN offers Double VPN, Proton VPN offers Secure Core, and IVPN offers multi-hop connections. Some providers restrict the feature to certain apps or plans, so check the provider’s own documentation first.
Use the provider’s official app for the test. Third-party clients and manual configurations can behave differently, and a failed test in a third-party client may say nothing about the provider’s own feature. Install the latest version of the official app before you begin.
Test on a stable network. A weak Wi-Fi signal or a mobile connection that keeps switching between towers will produce inconsistent results that look like VPN problems. Connect to a reliable Wi-Fi network, close bandwidth-heavy apps, and avoid testing during a download or a video call.
Use the same device, browser, and test pages for every step. Different browsers handle WebRTC and DNS differently, so switching browsers halfway through the test makes the results incomparable. Pick one browser and stay with it.
Turn off any other tool that changes your traffic before you start. That includes other VPN apps, browser VPN extensions, privacy relays, and system-wide proxies. If two tools are active at once, you cannot tell which one produced the result you are looking at.
Step 1: Record Your Baseline With the VPN Off
Disconnect the VPN completely and close the app if you can, so no tunnel is active. Open your browser and visit an IP lookup page, then note the public IP address, the country and city it reports, and the name of your internet provider. This is your real baseline.
Run a DNS leak test as well, and note which resolvers appear. With the VPN off, the resolvers should belong to your Pakistani internet provider or to the public DNS service you have configured. Write these down, because every later result is compared against this baseline.
Check whether your connection has IPv6. Some IP lookup pages show both an IPv4 and an IPv6 address, while others show only IPv4. If your baseline has no IPv6, then seeing no IPv6 later is inconclusive rather than proof of protection, and you should not treat it as a pass.
Run a WebRTC leak test in the same browser and note the addresses it reports. WebRTC is a browser feature used by voice and video calls, and it can reveal your real IP address even when the VPN is working. Recording the baseline tells you what a leak looks like before you test for one.
Take a screenshot of each baseline result, or write the details in a note with the time. The baseline is the reference point for the whole checklist, and without it, a later result that matches your real IP is only a suspicion, not a confirmed leak.
Step 2: Connect a Single Hop and Compare
Connect to a normal single-hop server in the country you plan to use as your multi-hop exit. Note the server you selected, then visit the same IP lookup page again and record the new public IP address, country, city, and provider name.
The IP address should be completely different from your baseline, and the country should match the server you chose. Your Pakistani internet provider’s name should no longer appear. If any of those details still match the baseline, stop here and fix the single-hop connection before testing multi-hop.
Run the DNS leak test again. The resolvers should now belong to the VPN provider or to servers in the exit country, not to your local provider. If your local provider’s resolvers still appear, your DNS queries are leaking outside the tunnel, and multi-hop will not fix that on its own.
Check the WebRTC test again. The addresses it reports should now be the VPN’s addresses, not your real ones. If your real IP still appears, your browser is leaking through WebRTC, and you should disable WebRTC or use a browser that handles it better before continuing.
This single-hop step matters because it isolates the problem. If single-hop works and multi-hop does not, the fault is in the multi-hop feature. If single-hop already fails, the fault is in the basic connection, and testing multi-hop would only confuse the diagnosis.
Step 3: Enable Multi-Hop and Connect
Open the provider’s app and find the multi-hop setting. In Surfshark, it is called Dynamic MultiHop, and you choose an entry location and an exit location. In NordVPN, it is called Double VPN, and you choose from a list of server pairs. In Proton VPN, it is called Secure Core, and you choose an entry country and an exit country.
Choose the same exit country you used in the single-hop step, so the two results are directly comparable. Choose an entry country that is different from the exit country, because using the same country for both hops tells you less about whether the second hop is actually in use.
Connect and wait for the app to report a successful connection. Note the entry and exit servers the app shows, if it shows them. Some apps display both hops clearly, while others show only the exit, and that difference matters for how much you can verify from the app alone.
Do not change any other setting at the same time. Keep the same protocol, the same kill switch state, and the same network as the single-hop step. If you change the protocol and enable multi-hop together, and the result changes, you will not know which change caused it.

Step 4: Verify the Multi-Hop Exit IP
Visit the same IP lookup page again, in a fresh tab or after a full refresh, and record the public IP address, country, city, and provider name. Compare it with your single-hop result and your baseline.
If multi-hop is working, the exit IP should be different from your baseline and should report the exit country you chose. It should usually be different from the single-hop IP as well, because the exit server is a different machine, though some providers reuse the same exit server for both modes, so an identical IP is not automatic proof of failure.
Check a second IP lookup site as well. Two independent sources agreeing on the exit country is far stronger evidence than one, because a single checker can be wrong, and its geolocation database may be out of date.
Look at the provider name in the results. It should name the VPN provider’s hosting network or a data centre in the exit country, not your Pakistani internet provider and not the entry country’s network. If the provider name points to the entry country, the traffic may be exiting from the first hop instead of the second.
Refresh the check after a minute and confirm the result is stable. An exit IP that changes between refreshes, or that flips back to your real IP, suggests an unstable tunnel rather than a working multi-hop connection, and you should reconnect and repeat the test.
Step 5: Check DNS, IPv6, and WebRTC Again
Run the DNS leak test with multi-hop active. The resolvers should belong to the VPN provider, and your Pakistani provider’s resolvers should not appear. If they do, DNS is leaking, and you should check the app’s DNS settings and your system’s DNS configuration before blaming the multi-hop feature.
Check IPv6 if your baseline had it. With the VPN on, there should be no IPv6 address belonging to your real connection. If your real IPv6 address appears in the multi-hop test, IPv6 traffic is bypassing the tunnel, and you should disable IPv6 on the device or in the app if it offers that option.
Run the WebRTC test in the same browser. The addresses should be the VPN’s, not your real ones. A WebRTC leak with multi-hop active is usually a browser issue rather than a multi-hop issue, but it still means your real IP is visible to websites that use WebRTC, so fix it before relying on the connection.
Test one app beyond the browser. Open an app that shows your location or IP, such as a maps app or a streaming app, and check what it reports. A browser test proves the browser is routed correctly, but it says nothing about other apps, and split-tunnelling settings can send some apps outside the tunnel.
Record each of these results next to the exit-IP result, with the time. A complete multi-hop test has four parts, and passing only the exit-IP check while failing the DNS check is not a pass.
Expected Results: What a Working Multi-Hop Looks Like
A working multi-hop connection produces a consistent set of results. The exit IP belongs to the exit country, the provider name points to the VPN’s network, the DNS resolvers belong to the provider, no real IPv6 address appears, and the WebRTC test shows only VPN addresses.
The connection should also be stable. The exit IP should stay the same across several checks over a few minutes, the app should report a continuous connection, and ordinary browsing should work, though it may feel slower than a single hop. Slowness alone is not a failure, because two hops add latency by design.
You should also be able to see the two hops in the app, or at least the exit server. Some apps show the entry and exit clearly, while others show only the exit. If your app shows neither, you are relying entirely on the IP check, which is still valid evidence, but it is thinner than a confirmed pair.
Do not expect to see the entry server’s IP address in any public lookup. The entry server forwards your traffic to the exit server, and the website you visit only ever sees the exit. That is the design, and a test that looks for the entry IP in a public check is testing the wrong thing.
Unexpected Results: What Each Failure Means
If the exit IP still matches your baseline, the tunnel is not active at all, or the browser is bypassing it. Check that the app reports a connection, that the kill switch is not blocking everything, and that no split-tunnelling rule is sending the browser outside the tunnel. Reconnect and repeat the test.
If the exit IP matches the single-hop result exactly, multi-hop may not be active, or the provider may be using the same exit server for both modes. Check the app’s settings to confirm that multi-hop is actually enabled, and try a different entry and exit pair to see whether the result changes.
If the exit IP shows the entry country instead of the exit country, the traffic may be leaving through the first hop. This is the most specific multi-hop failure, and it is worth reporting to support with your recorded server pair and IP addresses, because it suggests a routing fault rather than a settings error.
If the exit IP is correct but DNS resolvers still point to your local provider, the leak is in DNS handling, not in multi-hop routing. Check the app’s DNS settings, your system’s DNS configuration, and whether any other app on the device is overriding DNS. A DNS leak does not mean multi-hop is broken, but it does mean the connection is not fully private.
If the connection drops repeatedly, or the exit IP changes between checks, the problem may be network stability rather than the VPN. Test on a different network, or at a different time of day, and try a different protocol, such as switching from WireGuard to OpenVPN, before concluding that multi-hop itself is at fault.
Surfshark Multi-Hop: What to Check Specifically
Surfshark is the provider we recommend for readers in Pakistan, and its multi-hop feature is called Dynamic MultiHop. It lets you choose an entry location and an exit location, and it is available in the provider’s apps on the main platforms. Check that your app version supports it before testing, because older versions may not.
When you test Surfshark’s multi-hop, choose an entry and exit pair that are far apart, such as Singapore as the entry and Germany as the exit. The IP check should then report Germany, not Singapore, and not Pakistan. A distant pair makes a routing error easier to spot than two neighbouring countries.
Surfshark’s app also includes a kill switch, CleanWeb ad and tracker blocking, and a choice of WireGuard or OpenVPN. Leave those settings unchanged during the test, so the result reflects multi-hop alone, and note which protocol you used, because support will ask.
Surfshark’s longer-term pricing is reported at around 2.49 dollars per month on introductory two-year plans. At an approximate rate of PKR 280 per US dollar as of November 2026, that is roughly PKR 700 per month, and the plan includes multi-hop at no extra cost, so there is no higher tier to unlock for this feature.
Surfshark — our recommended VPN for Pakistan
Multi-hop is included on every Surfshark plan, so you can test it without paying for a higher tier.
Multi-Hop VPN Test Results: How to Read Them Honestly
A single test result is a snapshot, not a verdict. Network conditions change, servers change, and geolocation databases change, so a result that looks odd once may be normal on a repeat test. Run each check at least twice before concluding that something is wrong.
Do not treat a speed test as a multi-hop test. A slower connection with multi-hop active is expected, because traffic passes through two servers, and a fast result does not prove the routing is correct. Speed and routing are separate questions, and only the IP, DNS, and leak checks answer the routing question.
Do not claim that a passing test proves the provider’s no-logs policy, or that the entry server cannot see your traffic. The checklist verifies routing, not the provider’s internal logging, and logging can only be assessed through audits, transparency reports, and the provider’s own documentation.
Similarly, do not claim that a passing test proves the second server is in the country it reports. Geolocation databases can be wrong, and some providers use virtual locations, where the server hardware sits in a nearby country while the IP address is registered to the exit country. The IP check proves the exit address, not the physical hardware location.
Label your results as what they are: a routing check on your device, on your network, at a specific time. That honesty makes the test useful, and it is the standard this guide applies to every claim in it.
Record Reproducible Evidence for Support
If your test finds a problem, support will need evidence they can reproduce, not a general complaint. Record the entry and exit servers you selected, the public IP addresses from each step, the DNS resolvers shown, and the exact time of each test, including your time zone.
Take screenshots of the IP lookup results, the DNS leak test, and the app’s connection screen showing the selected servers. A screenshot with a visible timestamp is stronger than a typed summary, because it removes any doubt about what you saw.
Note your device, operating system version, app version, and protocol. A multi-hop problem that appears on one app version and not another is a useful clue, and support will ask for these details before they can investigate.
Describe the steps you took in order, including the baseline and the single-hop comparison. Support teams diagnose routing faults by comparing the baseline, the single hop, and the multi-hop result, and a report that includes all three is far more useful than one that only shows the failure.
Send the report through the provider’s official support channel, and keep a copy for yourself. If the first answer does not resolve the issue, the same evidence supports a follow-up, and you will not need to repeat the whole test from scratch.

Multi-Hop VPN Troubleshooting: Common Fixes
If multi-hop will not connect at all, switch to a different server pair. Some pairs are temporarily unavailable, and the app may not say so clearly. A pair with well-known locations, such as a European entry and a European exit, is a good first alternative.
If multi-hop connects but the exit IP is wrong, disconnect, switch protocol, and reconnect. A protocol change fixes routing faults more often than any other single step, because WireGuard and OpenVPN handle routing differently, and one may work where the other does not.
If the connection is very slow, try an entry server closer to Pakistan, such as Singapore or the United Arab Emirates, and an exit server in the region you actually need. The entry hop matters most for latency, because it is the first leg of the journey, and a nearby entry usually helps.
If a specific website fails with multi-hop but works with a single hop, the site may be blocking the exit server’s IP address, or the extra hop may be breaking a connection the site expects. Try a different exit country, and if the problem persists, use a single hop for that site and multi-hop for the rest.
If the app crashes or freezes when you enable multi-hop, update the app, restart the device, and try again. If the problem continues on the latest version, report it to support with your device and app version, because it is likely a bug rather than a configuration error.
Multi-Hop VPN Settings Check: Before Every Use
Multi-hop is not a set-and-forget feature. Server pairs change, app updates reset settings, and a setting that was correct last week may not be correct today. Run a short version of this checklist whenever you rely on multi-hop for something important.
Confirm that multi-hop is still enabled in the app, and that the entry and exit locations are the ones you intend. Some apps reset the feature when they update, and some switch back to a single hop when the chosen pair is unavailable.
Check the exit IP with one lookup before you start work. That single check takes less than a minute, and it catches the most common failure, which is a tunnel that silently fell back to a single hop or to no tunnel at all.
Confirm that the kill switch is on. Multi-hop adds a second server to the chain, and if either hop drops, the kill switch is what stops your traffic from leaking outside the tunnel. A multi-hop connection without a kill switch is less safe than a single hop with one.
Finally, remember that multi-hop is a privacy tool, not a guarantee. It improves the separation of knowledge between servers, but it does not make you anonymous, and it does not protect you from every form of tracking. Use it as one layer among several, not as a single solution.
Pakistan-Specific Considerations
Readers in Pakistan face two practical issues that guides written elsewhere rarely mention: payment friction and the PTA’s VPN registration framework. International card payments can fail on Pakistani cards, so confirm your payment method works before the subscription renews, and keep a note of the renewal date.
The Pakistan Telecommunication Authority operates a registration system for VPN use, and readers who use a VPN for work or business purposes should check the current PTA guidance for their situation. This guide does not give legal advice, but the regulatory position exists and it changes, so check the PTA’s own announcements rather than relying on old articles.
Internet quality in Pakistan also varies by provider and by time of day, so a multi-hop connection that works well for one reader may feel slower for another. Multi-hop adds a second server to the route, which makes it more sensitive to local network quality than a single hop, so test on your own connection at the times you actually use it.
Finally, remember that multi-hop does not change the price you pay for a VPN subscription. Providers bill in dollars or euros, and the rupee cost depends on the exchange rate and your bank’s international transaction charges. Our Surfshark pricing guide for Pakistan explains the full upfront and renewal costs in rupees, and our NordVPN pricing guide does the same for NordVPN.
Frequently Asked Questions
How Do I Test Multi-Hop VPN?
Record your real IP with the VPN off, then connect a single hop and record the new exit IP, then enable multi-hop with the same exit country and check the IP again. The exit should match the second server’s location, and DNS, IPv6, and WebRTC checks should show only the VPN’s addresses.
What Result Should I Expect?
You should expect an exit IP in the exit country you chose, DNS resolvers belonging to the VPN provider, no real IPv6 address, and no real address in the WebRTC test. The connection will usually be slower than a single hop, because traffic passes through two servers, and that is normal.
What Evidence Should I Send Support if the Result Differs?
Send the entry and exit servers you selected, the IP addresses from the baseline, single-hop, and multi-hop steps, the DNS resolvers shown, screenshots with timestamps, and your device, app version, and protocol. That record lets support reproduce the fault instead of guessing.
Does Multi-Hop VPN Slow My Connection?
Yes, usually. Routing through two servers adds latency and lowers throughput compared with a single hop, because your traffic travels further. The slowdown varies with the server pair and your network, so test with a nearby entry server if speed matters to you.
Can I See Both Multi-Hop Servers in the App?
It depends on the provider. Some apps show the entry and exit servers clearly, while others show only the exit. If your app shows neither, rely on the IP lookup and leak checks, which still verify the exit routing, even though they cannot confirm the entry server.
Is Multi-Hop VPN Worth It for Everyday Use?
For most everyday use, no. A single hop already hides your IP address and encrypts your traffic, and multi-hop trades speed for a stronger separation of knowledge between servers. It is worth it when privacy is the priority, and a single hop is the better choice when speed matters more.
Conclusion
Testing a multi-hop VPN is a short, repeatable process: record a baseline with the VPN off, compare a single hop, enable multi-hop with the same exit country, and verify the exit IP, DNS, IPv6, and WebRTC results. Each step isolates a different part of the connection, so a failure points to a specific cause rather than a vague problem.
Keep the limits of the test in mind. It verifies routing on your device at a specific time, not the provider’s logging, and not the physical location of the servers. Label the results honestly, repeat any odd result before concluding it is a fault, and record everything support would need if you have to report a problem.
For readers who want a multi-hop feature included on every plan without paying for a higher tier, the recommended option in this guide is the natural starting point. Enable it, run the checklist, and use the connection knowing exactly what your test did and did not prove.
Surfshark — our recommended VPN for Pakistan
If you want multi-hop included on every plan, Surfshark keeps the setup simple and consistent.



