Skip to content
TheChatArchiveThe Chat Archive
Qwenqwen3-235b-a22b· Alibaba (Qwen)Hugging Face LMArena Human Preference 140K

what does the isp sees when you use a browser based vpn like a chrome extension? show me…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Mistralmistral-small-3.1-24b-instruct-2503’s answer.
  1. User

    what does the isp sees when you use a browser based vpn like a chrome extension? show me a realistic traffic packets example

  2. Qwen Assistant

    When using a browser-based VPN (like a Chrome extension), your Internet Service Provider (ISP) can observe the outer layer of network traffic, but not the inner encrypted content (e.g., websites visited, data exchanged). Here's a breakdown of what the ISP sees and a realistic packet example:


    What the ISP Sees

    1. Encrypted Tunnel Traffic:

      • The browser extension establishes a secure tunnel (e.g., HTTPS, TLS, or proprietary protocols) to the VPN provider’s server.
      • The ISP sees encrypted packets flowing between your device’s public IP and the VPN server’s IP (e.g., 198.51.100.1 → 203.0.113.45).
      • They cannot decrypt the payload (e.g., websites visited or data sent/received).
    2. Metadata:

      • Destination IP/Port: The ISP sees the IP address of the VPN server and the port used (e.g., TCP 443 for HTTPS).
      • Traffic Volume: The size and timing of packets may hint at activity (e.g., streaming vs. browsing).
      • DNS Requests: If the browser extension does not handle DNS securely (e.g., using DNS over HTTPS [DoH]), the ISP may still see DNS queries in plaintext.
    3. Potential Leaks:

      • WebRTC Leaks: Some browser-based "VPNs" fail to block WebRTC, exposing your real IP.
      • Split Tunneling: Non-browser traffic (e.g., apps, OS updates) bypasses the VPN, exposing it to the ISP.

    Realistic Traffic Packet Example

    Here’s a simplified view of packets as seen by the ISP when visiting https://example.com via a browser-based VPN:

    [Packet 1: TCP Handshake]
    Source IP: 198.51.100.1 (Your Public IP)
    Destination IP: 203.0.113.45 (VPN Server IP)
    Protocol: TCP
    Ports: 56789 (ephemeral) → 443 (HTTPS)
    Flags: SYN
    Length: 60 bytes
    
    [Packet 2: TLS ClientHello (Encrypted)]
    Source IP: 198.51.100.1
    Destination IP: 203.0.113.45
    Protocol: TLS 1.3
    Length: 512 bytes
    Payload: Encrypted (contains SNI: "example.com" in plaintext if SNI is not hidden)
    
    [Packet 3: Encrypted Application Data]
    Source IP: 203.0.113.45
    Destination IP: 198.51.100.1
    Protocol: TLS 1.3
    Length: 1400 bytes
    Payload: Encrypted (contains HTML content of "example.com")
    

    Key Observations

    1. Outer Layer:

      • The ISP sees encrypted traffic to the VPN server (203.0.113.45 on port 443).
      • They cannot decrypt the TLS payload, so the actual website (example.com) and content remain hidden if the tunnel is properly configured.
    2. SNI Exposure:

      • In the ClientHello, the Server Name Indication (SNI) field (e.g., example.com) is sent in plaintext unless the tunnel uses advanced techniques like ESNI/ECH (Encrypted Client Hello). Most browser extensions do not implement this.
    3. DNS Resolution:

      • If the browser extension uses the ISP’s DNS servers (instead of private DNS like Cloudflare 1.1.1.1), the ISP will see DNS queries for example.com.

    Common Weaknesses in Browser-Based VPNs

    WeaknessISP Visibility
    No DNS encryptionFull DNS queries (e.g., example.com)
    No WebRTC blockingReal IP address
    Split tunnelingNon-browser traffic (e.g., apps)
    Poor encryptionMetadata leaks (e.g., SNI)

    Example: Unprotected DNS Leak

    If the browser extension does not secure DNS:

    [DNS Query]
    Source IP: 198.51.100.1
    Destination IP: 203.0.113.44 (ISP DNS Server)
    Query: "example.com"
    

    The ISP now knows you’re visiting example.com.


    Takeaways

    • A browser-based "VPN" is often just a proxy and may not provide full privacy.
    • Use tools like ipleak.net to check for leaks.
    • For stronger privacy, pair a browser extension with a system-wide WireGuard/OpenVPN setup.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.