What does a VPN hide from your internet provider?
Which sites you open. Without a VPN, your provider carries every packet you send, and two parts of each visit can be read on the way.
The first is the name lookup. Before your browser can open a site, it asks a resolver for the site's address. RFC 1035, the 1987 standard that defines these lookups, sends them as plain messages to port 53. Unless your device has been set up to encrypt its lookups, your provider can read each name as it goes by.
The second is the hello. A secure connection opens with a first message from your browser, and that message names the site you want. The field is called the server name. RFC 6066, the 2011 standard that defines it, added it so that one server can host many sites and still answer with the right certificate. The message is sent before any encryption is agreed, so the name in it can be read.
After those two steps the page itself is encrypted, as long as its address starts with https. So without a VPN your provider cannot read the page. It still knows which site you opened, when you opened it and how much data moved.
With a VPN on, the lookup and the hello both travel inside the tunnel. Your provider is left with a stream of encrypted packets going to one address.
| What your provider can read | Without a VPN | With a VPN on |
|---|---|---|
| The names of the sites you look up | Yes, unless your device encrypts its lookups | No |
| The site named in the secure hello | Yes | No |
| The address of each site you connect to | Yes | No. Only the address of the VPN server |
| The pages you read on a site that uses https | No | No |
| The pages you read on a site without https | Yes | No |
| How much data you move, and when | Yes | Yes |
| That you are using a VPN | Does not apply | Yes |
What did our test show?
On 15 November 2026 we connected a test device to our New York server over WireGuard and loaded one page from a public test site. While it loaded, a packet capture recorded two views. View A sat between the device and the server, where an internet provider sits. View B sat between the server and the site.
packets held the site's name. All 32 were UDP, between one pair of addresses, on one port.
packets held the site's name in readable form: the secure hello, 1,368 bytes long.
Here is everything an observer in view A could learn. One address exchanged 32 UDP packets with one other address, on one port, carrying 11,456 bytes in all. The first two packets were the handshake, at 148 and 92 bytes. The other 30 carried data. We searched every one of them for the site's name, and it was in none. Not one name lookup left the device outside the tunnel.
| What was measured | View A, the provider's side | View B, the site's side |
|---|---|---|
| Packets recorded | 32 | 27 |
| Kind of traffic | UDP, on one port | TCP, on port 443 |
| Who the packets ran between | The device and the VPN server | The VPN server and the site |
| Packets that showed the device's own address | All 32 | 0 |
| Packets that held the site's name | 0 | 1 |
| Name lookups sent outside the tunnel | 0 | Does not apply |
| Sizes | 148 and 92 bytes for the handshake, then 30 data packets of 96 to 1,452 bytes | The hello that named the site was 1,368 bytes |
How the test was run, and its limits
The test device ran in a separate network space on the server itself, with its own key and its own tunnel. The packets in view A are the packets a provider would carry, recorded before they left the machine. A capture from a home connection is the next test, and this guide will be updated when it is done.
One page load is a small sample. It shows what the packets hold. It does not measure speed, and it does not show how every site behaves.
What does a VPN hide from the sites you open?
Your address. In view B, every one of the 27 packets on the site's side ran between the server's exit address and the site. The device's own address was in none of them. To the site, the visitor was the VPN server.
That matters because an address is more than a number. A site can turn it into a city and the name of your provider, and it can use it to link today's visit to yesterday's. Behind a VPN, the city is the server's, and the address is shared by everyone using that server.
What the site still sees is everything you hand it yourself:
- An account you sign in to. The site knows it is you because you told it.
- Cookies. RFC 6265, the standard for cookies, has the browser send a site's cookies back with each request to that site. The route the request took plays no part.
- The details your browser gives out. Its name and version, your screen size, your language and your time zone. Together they can be distinctive.
- Anything you type, post, upload or buy.
What can the VPN itself see?
This is the part that is easy to skip. A VPN does not remove the point where your traffic can be read. It moves that point from your provider to the VPN.
View B shows it. On the far side of the server the traffic is ordinary internet traffic again, and 1 of the 27 packets held the site's name in readable form. Whoever runs the server, and the network the server sits in, is placed to read that name, the same way your provider was before.
What they cannot read is the page. HTTPS runs between your browser and the site, through the tunnel and out the other side, so the content stays encrypted the whole way.
So the real question about any VPN is what it does at that point. Two things decide it:
- What it writes down. A server has to hold your address while you are connected. It does not have to keep it afterwards, and it does not have to keep a list of where you went.
- Whether it knows who you are. If the account is an email address and a card, a record of connections is a record about a named person. If the account is a random number, it is a record about a number.
This guide is written by a VPN, so here is our own answer to both. Veto writes nothing down about your traffic, and its account is a 15 digit number with no email behind it. The privacy policy lists every item that is kept and how each line was checked.
Does a VPN hide that you are using a VPN?
No. In view A the provider's side showed a steady exchange of UDP packets with one address on one port. That pattern does not say which sites were opened. It does say that a tunnel is running.
WireGuard's own documentation is direct about this. It says the protocol “does not focus on obfuscation”. Disguising the tunnel is a separate job, done by extra layers that some services add on top.
Sites can often tell as well. The addresses of VPN servers are shared by many people and become known over time, and some sites block them or ask for extra checks. A VPN makes you one of a crowd behind an address. It does not make that address look like a home connection.
Does a VPN hide your search history and your location?
Search history lives in three places, and a VPN reaches only one of them.
- On the way. With a VPN on, your provider sees neither the search site nor the search. Even without one, the words of a search are encrypted by https. Only the name of the search site showed.
- At the search engine. If you are signed in, the search is saved to your account, VPN or not.
- On your device. Your browser keeps its own history. A VPN does not touch it.
Location has two sources. The one a VPN changes is your address: a site that guesses your location from it will see the city of the server. The one it does not change is the device. A phone app that has location permission reads the position from the phone itself, and that reading does not depend on your address.
What does a VPN not hide?
Put together, this is the list of what stays visible with a VPN on, who sees it and why.
| What stays visible | Who sees it | Why |
|---|---|---|
| An account you are signed in to | The site | You told it who you are |
| Cookies already in your browser | The site that set them | The browser sends them back with each request |
| The details of your browser | The site | The browser hands them over by itself |
| A phone's own location | Apps with location permission | It comes from the device, not from your address |
| That a VPN is in use | Your provider, and often the site | A tunnel has a recognisable pattern, and server addresses become known |
| How much data you move, and when | Your provider | Packets can be counted even when they cannot be read |
| The name of each site you open | The VPN | The tunnel ends at its server |
| A payment made with your own card | The seller and the bank | The card carries your name |
| Malware already on your device | Whoever controls it | It reads your traffic before the tunnel does |
What happens when the tunnel drops?
A tunnel can drop. A phone changes networks, or a laptop wakes from sleep. If the device then sends its traffic the normal way, everything in the first table can be read by your provider again, and sites see your own address, until the tunnel is back. Often you would not notice.
The first guard is a kill switch, a setting that blocks all traffic while the tunnel is down. The second is keeping name lookups inside the tunnel, so they cannot reach your provider by a side door. In our test the count of lookups outside the tunnel was 0.
The Veto app for Windows has both, on the free plan and on Pro, and its kill switch is always on. With any VPN, check that the kill switch is switched on before you rely on it.
What a VPN hides, in three lines
- From your provider: which sites you open and what you do there. Not that you use a VPN, and not how much data you move.
- From the sites: your address and the city it points to. Not your account, your cookies or your browser.
- From the VPN: nothing about where your traffic goes. That is why what a VPN keeps, and what it knows about you, matters more than anything else it offers.
Questions people ask about what a VPN hides
Does a VPN hide your IP address?
Yes, from the sites and apps you use. They see the address of the VPN server. In our test, none of the 27 packets on the site's side carried the device's own address. Your internet provider and the VPN itself still see your real address.
Can my internet provider see that I use a VPN?
Yes. It sees encrypted packets going to one address, and that pattern is recognisable. It cannot see which sites you open through the tunnel. In our test, 32 packets crossed the provider's side and none held the site's name.
Does a VPN hide what I search for?
From your internet provider, yes. From the search engine, no. If you are signed in, the search is saved to your account whatever route it took. Your browser's own history is not changed by a VPN either.
Can the VPN company see the sites I open?
It is placed to. The tunnel ends at the VPN's server, and in our test the site's name was readable in 1 of the 27 packets that left it. The content of an https page stays encrypted. What matters is whether the VPN writes any of it down.
Does a VPN hide my location on a phone?
Partly. Sites that guess your location from your address will see the city of the VPN server. An app that has location permission reads your position from the phone itself, and a VPN does not change that.
Does a VPN make me anonymous?
No. It hides your address from sites and your browsing from your provider. It does not hide an account you sign in to, cookies, the details of your browser or a card payment, and the VPN itself is placed to see where your traffic goes.
Is a VPN the same as private browsing?
No. Private browsing stops your own browser from saving history and cookies on your device. It does nothing to the route your traffic takes, so your provider and the sites see the same as before. A VPN changes the route and leaves the browser alone.
Does a VPN hide my browsing on a work or school network?
The network sees what a home provider would see: a tunnel to one address, and no site names. A device that the employer or school manages is a different matter, because software on the device can see what you do before it enters the tunnel.