Skip to main content
0%

What Your ISP Can See When You Use a VPN

10 min readUpdated

What Your Internet Provider Sees When Using a VPN

When a VPN works correctly, your internet service provider (ISP) sees the connection to the VPN server, its timing and the amount of data transferred. Forwarding those packets does not give the ISP the contents of the protected tunnel. This applies to traffic actually routed through the tunnel. The VPN operator and the website you open are separate participants with different access to data.

Sources were checked on October 27, 2026. This explains how the connection works; we have not tested leaks or the observations of a particular ISP.

Connection testHow fast is your internet right now?
Test your internet?Press to start — takes 30 seconds and up to 50 MB of data
—mspingmax—avg—min——Mbpsdownloadmax—avg—min——Mbpsuploadmax—avg—min—
Jitter—Ping under load—
Last speed test
MetricResultmaxavgmin
Ping—ms———
Download—Mbps———
Upload—Mbps———

What your ISP sees without a VPN: browsing history

Without a VPN, your ISP carries connections to internet resources and can observe network information available on its part of the path. This does not mean reading your browser's history file: visibility depends on HTTPS, DNS, other forms of encryption and the observer's position.

What Your ISP Sees by Default

  • Network metadata: connection IP addresses, ports, timing, data volume and available transport information.
  • DNS: a plain, unencrypted query may be visible along the path even when sent to a third-party DNS server. Choosing another server does not encrypt the query. DoH and DoT protect transmission to the chosen resolver, which you still trust with your queries.
  • Access information: your subscriber account, assigned address and connection settings. A MAC address operates on the local link; do not assume that an ISP automatically sees the MAC address of every laptop behind a home router.

What can be observed depends on the connection setup. Having these observations does not by itself prove that an exact history of actions has been reconstructed. See also how websites track you without cookies.

DNS risks are discussed in RFC 9076, and local addressing in Cisco's ARP guide.

What HTTPS Hides — and What It Does Not

With correctly functioning HTTPS, HTTP request and response contents are protected between the browser and website: URL paths and parameters, pages, forms, transferred files and cookies. The website itself receives the data intended for it.

A network intermediary can observe IP addresses, connection timing and data volume. Whether a domain name is visible depends in part on DNS and the TLS handshake. Unencrypted HTTP does not give its contents this protection along the network path. The distinction is described in Mozilla's HTTPS guide.

Without ECH, the server name may be visible in SNI during the TLS handshake. Encrypted ClientHello encrypts part of the handshake, including the inner server name, when supported and used for that connection. This does not remove the connection's IP address.

An IP address alone does not automatically identify an exact website, and HTTPS does not prove that ECH is working. Consider browser, DNS and server settings together; do not treat ECH as a universal replacement for a VPN. Examples of domain names are youtube.com and example.com. ECH conditions are described in Cloudflare's documentation.

How ISPs Can Profile Your Behavior

Distinguish three kinds of information: connection timing and volume, inferences about activity from network characteristics, and subscriber account data. These can be correlated, but similar traffic does not prove the use of a particular app or a specific action.

To understand your ISP's data handling, check its policy: what it collects, the purposes of use and the recipients. Do not infer actual profiling solely from the technical ability to observe packets.

In October 2021, the FTC published findings based on information from six internet service providers and related advertising entities. Practices identified included combining data across products and using activity information for advertising. This was a historical study of particular US companies, not an audit of your current ISP or evidence that any HTTPS content can be read. This account uses the FTC's press release about the report.

Rules on retention, access restrictions and disclosure depend on the country, operator and circumstances of a request. Check these three questions against the applicable documents; this article does not establish one retention period or obligation for all countries.

Network packet analysis does not by itself remove correctly functioning TLS encryption. A managed environment may use separate TLS inspection with a certificate trusted by the device and a compatible app. This changes the trust arrangement; an ordinary home ISP does not gain that access merely by forwarding packets. Change work certificates and settings only with your administrator. Conditions and limitations of such inspection are described in Cloudflare's documentation.

Basic Information Available to the Provider

  • Information about your subscriber connection and the address it uses to reach the VPN.
  • The VPN server's address, connection times and durations.
  • The amount of data transferred and the flow's timing characteristics.
  • Available ports and transport characteristics. These may support an inference about the connection type; a port number alone does not confirm a particular VPN protocol.

This visibility concerns the path between your connection and the server. The VPN status shown in an app does not by itself verify the routes used by every program. Content and metadata are discussed in EFF's explanation of encryption.

What the VPN Hides

For traffic inside a correctly protected tunnel, simply forwarding packets does not give your ISP the contents. This can include website requests, files and messages routed through the VPN. Excluded traffic and DNS outside the tunnel must be considered separately. An example of route inclusion and exclusion rules appears in Cloudflare's documentation.

When a connection exits through a VPN, the website sees the server's exit IP address. However, an account, cookies, a browser fingerprint and location access you have granted can link activity to you. A VPN does not delete browser or account history.

The VPN operator gains access to some connection information after traffic leaves the tunnel. Correctly functioning HTTPS continues to protect content between the browser and website: removing the VPN layer does not by itself decrypt HTTPS.

VPN Limitations

A VPN does not make you anonymous. Your ISP sees a connection to the server's address and may recognize VPN characteristics. Websites retain their ways of recognizing an account or browser.

A no-logs policy describes the VPN operator's stated data retention, not the absence of a technical ability to observe connections. Check which logs are excluded, which account data remains and the conditions for handling it. A no-logs label is not an independent audit. Trust is discussed in EFF's guide to choosing a VPN.

See also the comparison of VPN vs Proxy and the risks of free VPNs.

How Providers Can Indirectly Assess Activity

Transfer timing and volume, connection frequency and available network characteristics can support inferences about activity. Accuracy depends on the observations and analysis method; data volume alone cannot reliably identify a page, video or app.

Do not confuse such an inference with reading a plain DNS query or obtaining a service's log. The possibility of correlating several sources does not mean that every ISP has those sources or has reconstructed a complete history.

How to Check Your Privacy Limits

How to Read a No-Logs Policy

Read what data the operator collects, what it stores, for how long and to whom it may disclose it. If it cites an independent audit, check the date, scope and available report. An audit of a particular system at a particular time does not establish every property of each future release.

Pay Attention to Encryption and Protocols

Check compatibility between the client, server and supplied configuration. WireGuard transmits encrypted IP packets over UDP. For VLESS, consider transport protection and settings: current Project X documentation describes external protection and optional VLESS Encryption. The VLESS name alone does not confirm the complete set of protections for a particular connection.

Do not disable encryption or certificate verification for presumed compatibility. Follow the documentation for your release: WireGuard and Project X on VLESS.

How to Assess a Free VPN

Assess free and paid services with the same questions: who operates them, how access is funded, what data is processed and what limits apply. A zero price does not by itself prove data sales; payment does not guarantee privacy. If the terms are unclear, clarify them before sending sensitive data.

What You Can Control

  1. Check HTTPS in the browser you use and do not bypass certificate warnings. Keep the browser and operating system updated.
  2. If you use a VPN, check the client documentation for the apps, addresses and DNS included in the tunnel. An excluded route cannot be treated as protected by that VPN. Agree on work settings with your administrator.
  3. Check DNS settings against the browser, operating system and VPN client documentation. If choosing DoH or DoT, find out who the resolver is, how it handles queries and whether it can fall back to unencrypted DNS. Do not change settings blindly: their interaction depends on the client.
  4. Check where you use the same account and which identifiers you send. A VPN exit IP does not prevent recognition through an account, cookies or location access you have granted. Do not remove necessary sign-in methods because of this article.

These checks help explain settings but do not constitute a leak audit. On a public network, HTTPS still protects its part of the path; a VPN does not fix a phishing page or a compromised device. Encrypted DNS is described in the RFCs for DNS over HTTPS and DNS over TLS.

What to Check Before Trusting a VPN

Decide which information you want to protect from which observer. Then check the route used by the relevant app, connection protection and the VPN operator's data handling terms. Keep HTTPS and account protection: a VPN adds a separate encrypted section of the path and transfers some trust to another operator.

FAQ

Can my ISP see the websites I visit through a VPN?

For traffic inside a correctly protected tunnel, your ISP sees the connection to the VPN server rather than the ordinary website requests inside it. DNS and connections outside the tunnel must be assessed separately; VPN status does not prove that every app is routed through it.

What can the VPN owner see?

The VPN operator can observe some connection information after traffic leaves the tunnel. Correctly functioning HTTPS separately protects content between the browser and website; a no-logs policy describes retention and does not remove technical visibility.

Does a VPN hide my IP address?

A website sees the VPN exit IP if that connection passes through it. Your ISP still knows your subscriber connection, and accounts, cookies and other means of recognition remain.

Author: — Cybersecurity specialist, VPNON