Can my ISP see my browsing history? Yes, every site
There are two popular beliefs about internet providers, and both are wrong. One says your ISP reads everything, down to what you type into a search box. The other says the HTTPS padlock made your ISP blind. The truth sits in between, and knowing exactly where tells you which fixes are worth your time.
Short answer: yes, your ISP can see every website you visit, even on HTTPS. It sees each domain, when you connected, for how long, and how much data moved. It cannot see the specific pages, your searches, or what you type on encrypted sites. Encrypted DNS narrows what leaks, and a VPN or Tor hides the sites themselves.
What your ISP can and cannot see
Picture every web request as an envelope. HTTPS seals the letter inside. The address on the outside has to stay readable so the network can deliver it.
Hidden from your ISP on HTTPS sites: the full page address after the domain, your search terms, form entries, passwords, messages, and the content of the page.
Visible to your ISP: the domain you connected to, the time, how long you stayed, how often you come back, and roughly how much data you exchanged.
So your ISP does not know which article you read on a health site. It knows you visited that health site at 11:40pm, for twenty minutes, every Tuesday. That pattern is often more revealing than the article.
The three places the site name leaks
Most guides stop at "HTTPS hides content but not the domain." The useful part is where the domain leaks, because each leak has a different fix.
- DNS lookups. Before loading a site, your device asks a DNS server to turn the name into an address. By default that question goes to your ISP's DNS server, unencrypted. It is a live list of every domain you visit.
- The SNI field in the TLS handshake. The first message of an HTTPS connection names the site you want, in a field called Server Name Indication, and it has traditionally been sent in plain text. A newer standard, Encrypted Client Hello (ECH), hides it. Current Chrome and Firefox support ECH, and Cloudflare turns it on by default for sites on its free plan, but many sites still do not offer it.
- The destination IP address. Packets have to go somewhere. On a big shared host the IP may cover thousands of sites, while on a dedicated server it points straight at one.
What your ISP sees at each layer of protection
| Your setup | Site names | Specific pages and content | What your ISP still sees |
|---|---|---|---|
| Plain HTTP (rare now) | Visible | Visible | Everything |
| HTTPS, default DNS | Visible via DNS, SNI, and IP | Hidden | Every domain, times, data volumes |
| HTTPS + encrypted DNS | Visible via SNI and IP | Hidden | Most domains, through the handshake |
| HTTPS + encrypted DNS + ECH | Mostly hidden, IP may still point to the site | Hidden | Destination IPs, times, volumes |
| VPN | Hidden | Hidden | That you use a VPN, when, and how much data |
| Tor Browser | Hidden | Hidden | That you use Tor, when, and how much data |
Test your own browser in one minute
You can check two of those leaks right now.
- Is your DNS encrypted? Visit one.one.one.one/help. If you use Cloudflare's resolver, it reports whether you are connected over DNS over HTTPS or DNS over TLS. Many other resolvers have a similar check page.
- Is your SNI encrypted? Visit crypto.cloudflare.com/cdn-cgi/trace and find the line that starts with
sni=. If it sayssni=plaintext, your browser just told your ISP the site name in the clear. If it sayssni=encrypted, ECH worked. If it still says plaintext, turn on encrypted DNS first. The browser fetches each site's ECH key through a DNS lookup, and Mozilla describes ECH as relying on DNS over HTTPS to get it. If the site you are testing has not enabled ECH, it will stay plaintext whatever you do.
Why your ISP keeps that record
Because it is valuable, and US law lets it. In 2016 the FCC adopted rules that would have required ISPs to get opt-in consent before using or selling sensitive data such as browsing history. Congress repealed them before they took effect: S.J.Res. 34 was signed on April 3, 2017.
In October 2021 the FTC published a staff report on six major ISPs covering about 98 percent of the mobile market. It found they had "access to all of their Internet traffic and real-time location data," combined personal, app-usage, and web-browsing data to target ads, and sorted some subscribers into sensitive categories such as race and sexual orientation, while "failing to offer consumers meaningful choices."
Location shows how far this goes. In April 2024 the FCC fined the largest US wireless carriers roughly $196 million combined for selling access to customers' real-time location data: about $57 million for AT&T, $47 million for Verizon, $80 million for T-Mobile, and $12 million for Sprint, as Krebs on Security detailed. In June 2026 the Supreme Court sided with the FCC against AT&T and Verizon.
How long do ISPs keep browsing history?
In the US there is no general law requiring ISPs to keep a record of the sites you visit, and none requiring them to delete it, so it varies by company and is set out, loosely, in each privacy policy. Other countries mandate it. In the UK, the Investigatory Powers Act 2016 lets the government require providers to retain "internet connection records" for up to 12 months.
How to stop your ISP from seeing your browsing history
Work through these in order. Each closes a different leak.
- Stay on HTTPS. Nearly every major site uses it, and current browsers upgrade to it automatically where they can. It already hides pages and content from your ISP. It does not hide domains.
- Turn on encrypted DNS. In Chrome, Edge, and Firefox, look for "Secure DNS" or "DNS over HTTPS" in the privacy or security settings and pick a resolver you trust. On Android, use the "Private DNS" setting. On iPhone, encrypted DNS needs a configuration profile or an app. This removes the plain-text list of lookups your ISP was receiving. Then run the SNI test above to see whether ECH is kicking in.
- Use a VPN when you want the site names hidden too. A VPN wraps everything in one encrypted tunnel to the VPN's server, so your ISP sees only that you are connected to a VPN and how much data moves. The catch: the VPN company is now the one in a position to see where you go. That makes the operator the whole question, and it is why a sketchy free VPN can be worse than none (here is how to tell them apart).
- Use Tor Browser for the highest bar. Tor routes traffic through several relays so no single one knows both who you are and where you are going. It is slower, and some sites block it, but it hides your destinations from your ISP without asking you to trust one operator.
None of these hide you from the website itself. Once you arrive, the site sees your visit, and its trackers see what they are built to see.
A VPN built to have nothing to hand over
If you move your trust from your ISP to a VPN, move it to one that is designed not to keep what your ISP was keeping. Secria VPN keeps no activity logs: we do not record browsing, DNS queries, or traffic contents. While a session is live we hold the account and device it belongs to, the server in use, and the time it started, and that record goes when the session ends. DNS is resolved on our own servers rather than handed to a third-party resolver, servers keep their state in RAM, and every WireGuard tunnel carries an ML-KEM-1024 post-quantum key, which matters because your ISP is exactly the kind of party that can store encrypted traffic today and try to decrypt it later. It is $7.99 a month on its own or included with Pro.
FAQ
Can my ISP see my browsing history if I use a VPN? No. With a VPN on, your ISP sees that you are connected to a VPN server, when, and how much data moves, but not the sites you visit. If the VPN leaks DNS, some site names can still slip through, so test for leaks.
Can my ISP see my Google searches? Not the search terms. Google uses HTTPS, so your ISP sees that you connected to google.com, not what you searched for. The sites you click on afterward are visible as separate domains.
Can my ISP see my history in incognito mode? Yes. Incognito only stops your browser from saving history on your device. The connections leave your machine exactly as before. Our guide to what incognito mode actually hides covers the rest.
Does deleting my browser history stop my ISP from seeing it? No. Clearing history deletes the copy on your device. Your ISP's record was made on its network when the connection happened, and your browser settings cannot reach it.
Can my ISP see my history on mobile data? Yes. On cellular, your mobile carrier is your ISP and sees the same domain-level information. The FCC's 2024 fines show carriers also hold something more sensitive: where you physically are.
Secria fact-checks every post against primary sources. Spotted something wrong or out of date? Email hq@secria.me and we will correct it.