Enabling system-wide DNS over HTTPS in Windows 11 can do more than tighten privacy: it can make everyday browsing feel faster, especially when the machine’s bottleneck is DNS resolution rather than raw bandwidth. The key distinction is that browser-only DoH protects only one app, while Windows’ own DNS client can be configured to encrypt lookups for the whole operating system, including apps that never touch your browser at all. Microsoft’s documentation confirms that Windows 11 supports DNS encryption using DoH, and that the DNS client can be managed at the OS level rather than inside a single browser
DNS is one of those invisible internet systems that users rarely think about until it becomes the problem. Every time you visit a site, the computer has to translate a readable domain name into an IP address before the connection can begin. If those lookups are slow, the page can feel sluggish even when the connection itself is fine. If they are unencrypted, they can also expose browsing habits to intermediaries on the network path.
That is why DNS over HTTPS matters. Microsoft explains that traditional DNS uses unencrypted traffic, while DoH wraps DNS messages inside HTTPS so they travel with confidentiality and integrity protections. In practical terms, that means fewer plain-text queries that an ISP, hotspot operator, or local network observer can inspect. It does not make you invisible online, but it closes a very common leak.
The article’s core insight is that browser-level privacy settings are not the same thing as operating-system privacy settings. A browser may encrypt its own DNS requests, but Windows itself still has a DNS client service handling resolution for the OS, and apps such as Teams or Slack may use their own networking logic. Microsoft’s documentation and command-line tools reflect that broader system architecture, which is why changing one browser setting alone is often incomplete
This is also why the “it felt faster” part is believable. If the resolver you were previously using had poor latency, overloaded infrastructure, or a route that was suboptimal for your region, switching to a faster encrypted resolver can shave off enough lookup time to make cold-cache browsing feel more responsive. That improvement is usually subtle, but on a new installation it can be obvious because the browser cache is empty and every first visit needs fresh name resolution.
The wider context is that Windows 11 has become increasingly willing to expose these network settings to users, even if the UI still hides them behind a few clicks. Microsoft now documents DNS encryption in Windows 11 and Windows Server, while the newer Windows command tooling also includes DNS encryption management. In other words, what used to be a niche privacy tweak is increasingly treated as a normal part of endpoint configuration
That matters because privacy is only as strong as the weakest resolver path. If one app is encrypted and another is not, your network still leaks useful metadata. Microsoft’s own DNS client documentation makes clear that Windows has native support for managing DNS encryption at the OS level, which is the meaningful boundary when your goal is system-wide coverage rather than browser-only protection
The practical consequence is that browser privacy tools can create a false sense of completeness. They are still worthwhile, but they are not the same as encrypting the whole machine’s DNS traffic. If the goal is to reduce the amount of plain-text metadata leaving the device, OS-level DoH is the stronger answer.
A second issue is consistency. Different apps behave differently. Some use the system DNS client, some ship their own networking stacks, and some can bypass the expected path entirely. That is why a one-app solution is useful but limited, especially on a machine that acts as a general-purpose work device.
Once you open the connection details for Wi-Fi or Ethernet, the DNS assignment section lets you enter resolvers manually and choose the encryption mode. Microsoft describes options that let Windows automatically use a template when the resolver is on Microsoft’s known DoH list, or accept a manual DoH template if your chosen provider is not on that list. That distinction is important because it determines how flexible the setup is for custom or self-hosted resolvers
The manual template mode is the more powerful option. It lets you specify a DoH URL directly, which matters if you rely on a resolver that Microsoft has not cataloged or if you run your own encrypted DNS service. That flexibility is what turns DoH from a convenience feature into an infrastructure choice.
There is also a subtle trust implication here. If you pick a resolver from Microsoft’s list, you get convenience. If you manually define the template, you get control. The second path usually takes more effort, but it also gives advanced users a better match for their own privacy and policy goals.
Cloudflare, Google Public DNS, NextDNS, and Quad9 each occupy a different point on that trade-off curve. Cloudflare’s 1.1.1.1 resolver says it does not log personal information and retains limited resolver data for 25 hours. Google Public DNS says it uses temporary logs with IP and query data for 24–48 hours and maintains anonymized permanent logs for aggregate analysis. NextDNS says it discards query data immediately unless the user opts into logging features. Quad9 emphasizes that it does not maintain a user database and does not log IP addresses in the way conventional services do
This is also where user assumptions can be misleading. Many people think encrypted DNS means nobody can see anything. In reality, the resolver can still see queries, and policies differ on how long it keeps that data and how it can use it. A good resolver reduces exposure, but it does not eliminate it.
For enterprise users, the resolver can also become a policy engine. Filtering malware domains, blocking trackers, or enforcing family-safe policies can all happen at the DNS layer. That is one reason NextDNS and Quad9 appeal to different audiences despite both being positioned as privacy-conscious services.
A few milliseconds may sound trivial, but DNS happens constantly. When lookups are faster, the effect compounds across pages, tabs, and background requests. That makes the case for a resolver that is both private and geographically close enough to your network path.
The important takeaway is simple: the best resolver is local to your reality, not just good on paper. Choosing by reputation alone is convenient, but choosing by measurement usually produces better day-to-day results.
That matches the reported experience: a more responsive first-page load, smaller DNS lookup times, and a cleaner result when DNS leak testing was repeated. The performance uplift may be modest in absolute numbers, but on a new Windows install it can be enough to feel like the system stopped dragging its feet.
This is why the author’s “it got faster and more private” claim makes sense together. A fast encrypted resolver reduces one layer of waiting while also reducing the number of readable DNS queries on the wire. Those are two separate benefits, but they reinforce each other in everyday use.
It is also worth noting that browser caches can hide the effect. If you keep revisiting the same sites, the difference may be less obvious. Fresh boots, newly installed systems, and first visits are where you are most likely to notice it.
There is also an important distinction between DNS privacy and full traffic privacy. DNS hides what domains you ask about, but the server you connect to may still be visible through other signals, unless the browser and site support additional protections. The article’s mention of Encrypted Client Hello in Chrome and Firefox reflects that layered model, where one protection closes one leak and another closes a separate one.
Still, foundations matter. If your ISP cannot easily see every domain lookup, it has less visibility into your behavior. If you then combine that with browser protections like HTTPS-First or ECH where available, you narrow the amount of browsing metadata that leaks by default.
That is why the article’s conclusion is stronger than it might first appear. The setting does not make Windows “private” in some absolute sense. It makes the machine less observable in one of the most common and overlooked ways.
The security value is practical, not theoretical. Fewer plain-text queries mean less opportunity for passive collection, less leakage on hostile networks, and more consistency when switching between apps. The machine behaves more like a unit rather than a collection of separate privacy islands.
Running a leak test after setup helps prove whether the machine is actually using encrypted DNS. It also reveals whether any app is bypassing the expected path. Microsoft’s documentation makes it clear that Windows supports DNS encryption, but support is not the same thing as confirmation on your exact machine and network
A good post-change checklist includes flushing old DNS cache entries so stale plain-text resolutions are not reused. It also includes checking whether a VPN is interfering with your DNS path, because a VPN can sometimes override or duplicate DNS handling. These complications are normal, which is why verification belongs in the process.
For enterprise environments, the picture is more complicated. DoH can improve confidentiality on untrusted networks, but it can also interfere with DNS-based filtering, logging, and policy enforcement if administrators are not prepared for it. That makes rollout a governance issue as much as a technical one.
It is also a good example of a small setting with outsized impact. People often focus on browser choice or VPN subscriptions, but DNS is one of the easiest places to make a measurable difference. For a normal user, that is a compelling return on a few minutes of setup.
That tension is why the feature matters strategically. It nudges Windows toward a more encrypted default state while leaving room for policy-managed exceptions. In modern endpoint management, that balance is often the difference between a security control users accept and one they disable.
Microsoft’s own documentation shows that the platform now has the plumbing for encrypted DNS at the client level, with support for known providers, manual templates, and command-line management. That means the feature is not experimental fluff; it is part of the operating system’s evolving network model. The challenge is discovery, not capability.
The deeper lesson is that privacy features often become easier to sell when they have a side effect users can feel. People may not immediately care about DNS metadata, but they do care about websites opening faster and the machine feeling cleaner. That makes DoH one of the better examples of a security feature that actually earns its keep.
It also demonstrates why system-level fixes beat piecemeal tweaks. A browser setting may help one lane of traffic, but the OS setting changes the behavior of the entire device. That is the more durable approach, and in Windows 11 it is increasingly the one Microsoft is quietly supporting.
What will matter next is how well Microsoft balances convenience, control, and enterprise policy. If the company continues to make encrypted DNS easier to discover, easier to verify, and easier to manage across consumer and business editions, the feature could become one of those quiet Windows improvements people stop noticing only because it starts working exactly the way it should.
Source: MakeUseOf I turned on one Windows 11 setting and my browsing got faster and more private
Background
DNS is one of those invisible internet systems that users rarely think about until it becomes the problem. Every time you visit a site, the computer has to translate a readable domain name into an IP address before the connection can begin. If those lookups are slow, the page can feel sluggish even when the connection itself is fine. If they are unencrypted, they can also expose browsing habits to intermediaries on the network path.That is why DNS over HTTPS matters. Microsoft explains that traditional DNS uses unencrypted traffic, while DoH wraps DNS messages inside HTTPS so they travel with confidentiality and integrity protections. In practical terms, that means fewer plain-text queries that an ISP, hotspot operator, or local network observer can inspect. It does not make you invisible online, but it closes a very common leak.
The article’s core insight is that browser-level privacy settings are not the same thing as operating-system privacy settings. A browser may encrypt its own DNS requests, but Windows itself still has a DNS client service handling resolution for the OS, and apps such as Teams or Slack may use their own networking logic. Microsoft’s documentation and command-line tools reflect that broader system architecture, which is why changing one browser setting alone is often incomplete
This is also why the “it felt faster” part is believable. If the resolver you were previously using had poor latency, overloaded infrastructure, or a route that was suboptimal for your region, switching to a faster encrypted resolver can shave off enough lookup time to make cold-cache browsing feel more responsive. That improvement is usually subtle, but on a new installation it can be obvious because the browser cache is empty and every first visit needs fresh name resolution.
The wider context is that Windows 11 has become increasingly willing to expose these network settings to users, even if the UI still hides them behind a few clicks. Microsoft now documents DNS encryption in Windows 11 and Windows Server, while the newer Windows command tooling also includes DNS encryption management. In other words, what used to be a niche privacy tweak is increasingly treated as a normal part of endpoint configuration
Why Browser-Level DoH Was Not Enough
Browser-level DNS encryption is easy to misunderstand because it feels comprehensive when it is actually partial. If you turn on DoH in Brave, Firefox, or Chrome, the browser can hide its own DNS queries, but the operating system still has plenty of other reasons to resolve names. Windows Update, background services, native apps, and even some enterprise tools may continue using the system resolver path.That matters because privacy is only as strong as the weakest resolver path. If one app is encrypted and another is not, your network still leaks useful metadata. Microsoft’s own DNS client documentation makes clear that Windows has native support for managing DNS encryption at the OS level, which is the meaningful boundary when your goal is system-wide coverage rather than browser-only protection
The DNS Client Layer
The Windows DNS client sits below the browser and above the network. That means it can affect far more than web traffic, because the system itself depends on name resolution for many services. When users only tweak browser settings, they often assume the whole machine is protected, but that is simply not how Windows networking is structured.The practical consequence is that browser privacy tools can create a false sense of completeness. They are still worthwhile, but they are not the same as encrypting the whole machine’s DNS traffic. If the goal is to reduce the amount of plain-text metadata leaving the device, OS-level DoH is the stronger answer.
A second issue is consistency. Different apps behave differently. Some use the system DNS client, some ship their own networking stacks, and some can bypass the expected path entirely. That is why a one-app solution is useful but limited, especially on a machine that acts as a general-purpose work device.
- Browser DoH helps only inside that browser.
- Windows system DoH covers OS-level DNS resolution.
- Some apps may still implement separate DNS behavior.
- Privacy gains depend on the whole stack, not one toggle.
How Windows 11’s Hidden DoH Setting Works
Windows 11 does support system-wide DoH, but the setting is not front-and-center in the way a casual user might expect. Microsoft places it in the network adapter’s DNS assignment area, where you can switch from automatic DNS to manual DNS and then choose whether the device should use encrypted resolution. That design suggests Microsoft wants the feature available without forcing every user to think about it day oneOnce you open the connection details for Wi-Fi or Ethernet, the DNS assignment section lets you enter resolvers manually and choose the encryption mode. Microsoft describes options that let Windows automatically use a template when the resolver is on Microsoft’s known DoH list, or accept a manual DoH template if your chosen provider is not on that list. That distinction is important because it determines how flexible the setup is for custom or self-hosted resolvers
Automatic vs. Manual Templates
The automatic template mode is the simpler option. It works when Windows already knows the resolver and its DoH endpoint, so setup is quick and relatively foolproof. For mainstream providers, that will often be enough.The manual template mode is the more powerful option. It lets you specify a DoH URL directly, which matters if you rely on a resolver that Microsoft has not cataloged or if you run your own encrypted DNS service. That flexibility is what turns DoH from a convenience feature into an infrastructure choice.
There is also a subtle trust implication here. If you pick a resolver from Microsoft’s list, you get convenience. If you manually define the template, you get control. The second path usually takes more effort, but it also gives advanced users a better match for their own privacy and policy goals.
- Automatic templates are easier to configure.
- Manual templates support custom or self-hosted resolvers.
- The setting applies beyond the browser.
- Ethernet and Wi-Fi follow the same basic workflow.
Why Resolver Choice Changes the Outcome
Not all DNS resolvers are equal, and the article gets this right. Resolver location, logging policy, filtering features, and raw latency can vary dramatically. A resolver that is privacy-friendly but geographically distant may feel slower than a less private one that happens to have excellent routing in your region. That is why “fastest” and “best” are not always the same thing.Cloudflare, Google Public DNS, NextDNS, and Quad9 each occupy a different point on that trade-off curve. Cloudflare’s 1.1.1.1 resolver says it does not log personal information and retains limited resolver data for 25 hours. Google Public DNS says it uses temporary logs with IP and query data for 24–48 hours and maintains anonymized permanent logs for aggregate analysis. NextDNS says it discards query data immediately unless the user opts into logging features. Quad9 emphasizes that it does not maintain a user database and does not log IP addresses in the way conventional services do
Privacy Policy Isn’t a Footnote
Resolver choice is not just about speed tests. It is about deciding which party sits closest to your browsing metadata. If you care about privacy, the resolver’s logging model matters because it sees every domain your device asks for before the connection begins.This is also where user assumptions can be misleading. Many people think encrypted DNS means nobody can see anything. In reality, the resolver can still see queries, and policies differ on how long it keeps that data and how it can use it. A good resolver reduces exposure, but it does not eliminate it.
For enterprise users, the resolver can also become a policy engine. Filtering malware domains, blocking trackers, or enforcing family-safe policies can all happen at the DNS layer. That is one reason NextDNS and Quad9 appeal to different audiences despite both being positioned as privacy-conscious services.
Speed Depends on Geography
Latency is not universal. A resolver that benchmarks well in North America may be merely average in Southeast Asia or South America. That is why tools like DNS Benchmark can be helpful: they measure performance where you are, not where the resolver’s marketing team lives.A few milliseconds may sound trivial, but DNS happens constantly. When lookups are faster, the effect compounds across pages, tabs, and background requests. That makes the case for a resolver that is both private and geographically close enough to your network path.
The important takeaway is simple: the best resolver is local to your reality, not just good on paper. Choosing by reputation alone is convenient, but choosing by measurement usually produces better day-to-day results.
- Cloudflare usually favors balanced speed and privacy.
- Google prioritizes service scale and limited retention.
- NextDNS adds configurable filtering.
- Quad9 focuses on malware protection and non-logging posture.
What Actually Improved in Browsing
The biggest user-facing improvement from system-wide DoH is not a dramatic benchmark spike. It is the elimination of little delays that make a machine feel less crisp. Cold-cache page loads tend to be the most sensitive, because the browser cannot reuse old name resolutions and has to ask the resolver again.That matches the reported experience: a more responsive first-page load, smaller DNS lookup times, and a cleaner result when DNS leak testing was repeated. The performance uplift may be modest in absolute numbers, but on a new Windows install it can be enough to feel like the system stopped dragging its feet.
Small Gains, Big Perception
People often underestimate how much perceived speed comes from the first few steps of a network request. A page can be technically fast once the connection is made, yet still feel slow if the browser pauses before it gets there. DNS is one of the first places that delay shows up.This is why the author’s “it got faster and more private” claim makes sense together. A fast encrypted resolver reduces one layer of waiting while also reducing the number of readable DNS queries on the wire. Those are two separate benefits, but they reinforce each other in everyday use.
It is also worth noting that browser caches can hide the effect. If you keep revisiting the same sites, the difference may be less obvious. Fresh boots, newly installed systems, and first visits are where you are most likely to notice it.
- Faster cold-cache loads are the clearest upside.
- DNS timing improvements can be small but noticeable.
- Leak tests help confirm whether encryption is actually active.
- Repeated visits may hide the performance gain.
Privacy Gains Beyond the Browser
The privacy benefit of OS-level DoH is broader than many users realize. If the operating system resolves domains through encrypted channels, the ISP or network observer loses one of the easiest ways to infer what the machine is doing. That does not hide your traffic completely, but it meaningfully reduces passive metadata exposureThere is also an important distinction between DNS privacy and full traffic privacy. DNS hides what domains you ask about, but the server you connect to may still be visible through other signals, unless the browser and site support additional protections. The article’s mention of Encrypted Client Hello in Chrome and Firefox reflects that layered model, where one protection closes one leak and another closes a separate one.
DNS Privacy vs. Site Privacy
DNS encryption protects the lookup stage. It does not automatically conceal the destination from every other layer in the stack. That means DoH is best understood as a foundation, not a complete anonymity tool.Still, foundations matter. If your ISP cannot easily see every domain lookup, it has less visibility into your behavior. If you then combine that with browser protections like HTTPS-First or ECH where available, you narrow the amount of browsing metadata that leaks by default.
That is why the article’s conclusion is stronger than it might first appear. The setting does not make Windows “private” in some absolute sense. It makes the machine less observable in one of the most common and overlooked ways.
System Coverage Matters
A browser-only setting can be bypassed simply by using another app. System-wide DoH narrows that gap by protecting more of the device, not just one browser profile. That is especially relevant for people who use multiple apps for communication, collaboration, and content access.The security value is practical, not theoretical. Fewer plain-text queries mean less opportunity for passive collection, less leakage on hostile networks, and more consistency when switching between apps. The machine behaves more like a unit rather than a collection of separate privacy islands.
- ISP visibility into domain lookups is reduced.
- Browser protections can stack with OS protections.
- DoH is strong for metadata reduction, not anonymity.
- App coverage is the main reason system-wide setup matters.
Why Verification Steps Are Worth It
The article rightly emphasizes verification, because privacy settings are easy to misconfigure and hard to inspect by eye. A user can flip a toggle and assume success, while some apps continue to talk in plain text. That is exactly the kind of false confidence that causes avoidable exposure.Running a leak test after setup helps prove whether the machine is actually using encrypted DNS. It also reveals whether any app is bypassing the expected path. Microsoft’s documentation makes it clear that Windows supports DNS encryption, but support is not the same thing as confirmation on your exact machine and network
What to Check After Enabling DoH
The article’s workflow is sensible because it treats privacy as something you validate, not just enable. You should not assume the setting worked because the UI shows it as on. You should confirm the traffic path and then fix anything that still leaks.A good post-change checklist includes flushing old DNS cache entries so stale plain-text resolutions are not reused. It also includes checking whether a VPN is interfering with your DNS path, because a VPN can sometimes override or duplicate DNS handling. These complications are normal, which is why verification belongs in the process.
- Enable system-wide DoH on the active network adapter.
- Confirm the resolver choice matches your speed and privacy goals.
- Flush the DNS cache so stale entries do not linger.
- Run a DNS leak test to verify encrypted resolution.
- Check VPN behavior if a tunnel is active.
Enterprise and Consumer Impact
For consumers, the appeal is straightforward: fewer people can see which domains your machine queries, and the browser feels more responsive if the resolver is fast. That is easy to understand, easy to deploy, and valuable on home Wi-Fi or public networks. It also aligns with the growing expectation that privacy should be built into the operating system, not bolted on afterward.For enterprise environments, the picture is more complicated. DoH can improve confidentiality on untrusted networks, but it can also interfere with DNS-based filtering, logging, and policy enforcement if administrators are not prepared for it. That makes rollout a governance issue as much as a technical one.
Consumer Value
Consumers are the most obvious beneficiaries because they generally want simple protections that do not require infrastructure planning. A system-wide encrypted resolver is a relatively low-friction upgrade that improves privacy and may improve perceived speed at the same time.It is also a good example of a small setting with outsized impact. People often focus on browser choice or VPN subscriptions, but DNS is one of the easiest places to make a measurable difference. For a normal user, that is a compelling return on a few minutes of setup.
Enterprise Value
Enterprises can benefit too, but only if they know what they are trying to preserve. If the organization wants privacy on public Wi-Fi while still enforcing internal policies elsewhere, DoH can be part of a broader security posture. If the organization relies heavily on DNS inspection or custom filtering, then the rollout needs more care.That tension is why the feature matters strategically. It nudges Windows toward a more encrypted default state while leaving room for policy-managed exceptions. In modern endpoint management, that balance is often the difference between a security control users accept and one they disable.
- Consumers gain simple, system-wide privacy.
- Enterprises gain a configurable control point.
- Policy visibility may need redesign.
- DNS-based security tools may need adjustment.
The Bigger Windows 11 Lesson
This is not really a story about one toggle. It is a story about how much of modern computing is still governed by invisible defaults. Windows 11 can look polished on the surface while still making network decisions that surprise users, especially when those decisions live below the browser and outside the usual privacy menus.Microsoft’s own documentation shows that the platform now has the plumbing for encrypted DNS at the client level, with support for known providers, manual templates, and command-line management. That means the feature is not experimental fluff; it is part of the operating system’s evolving network model. The challenge is discovery, not capability.
Why This Feels Like a Hidden Win
Users love settings that are both protective and performance-positive because they do not feel like a compromise. When one switch can improve privacy and make browsing feel a bit snappier, it is easier to justify the time spent on setup. That is especially true on a fresh Windows 11 install, where every annoyance stands out.The deeper lesson is that privacy features often become easier to sell when they have a side effect users can feel. People may not immediately care about DNS metadata, but they do care about websites opening faster and the machine feeling cleaner. That makes DoH one of the better examples of a security feature that actually earns its keep.
It also demonstrates why system-level fixes beat piecemeal tweaks. A browser setting may help one lane of traffic, but the OS setting changes the behavior of the entire device. That is the more durable approach, and in Windows 11 it is increasingly the one Microsoft is quietly supporting.
Strengths and Opportunities
The biggest strength of system-wide DoH on Windows 11 is that it delivers two benefits from the same configuration: reduced DNS exposure and better-looking responsiveness on slow or inefficient resolver paths. It is also a low-effort improvement that can be applied without replacing browsers, changing ISPs, or buying new hardware.- System-wide coverage protects more than one browser.
- Encrypted queries reduce plain-text DNS exposure.
- Better resolver selection can improve perceived speed.
- Manual templates support advanced and self-hosted setups.
- Built-in Windows support means fewer third-party dependencies.
- Flexible privacy policy choices let users pick the right resolver.
- Testing and verification make the improvement measurable.
Risks and Concerns
The main risk is assuming that DoH solves more than it actually does. It improves DNS privacy, but it does not hide all browsing activity, and it does not guarantee that every app will obey the same resolver path. Users can also choose a resolver with privacy claims that do not match their expectations or network needs.- False confidence if users stop at the toggle.
- Resolver trust trade-offs still matter.
- App-specific DNS behavior can bypass the system path.
- VPN conflicts can complicate or override DNS handling.
- Performance varies by region, so one benchmark is not universal.
- Enterprise policy conflicts may arise with DNS filtering tools.
- Misconfigured templates can break resolution or weaken privacy.
Looking Ahead
System-wide DoH is part of a broader shift in Windows toward making network security a default capability rather than an expert-only feature. The more Windows moves in that direction, the more users will expect privacy controls to live at the OS level and work across apps, not just inside browsers. That expectation is healthy, because it pushes the platform toward more consistent behavior.What will matter next is how well Microsoft balances convenience, control, and enterprise policy. If the company continues to make encrypted DNS easier to discover, easier to verify, and easier to manage across consumer and business editions, the feature could become one of those quiet Windows improvements people stop noticing only because it starts working exactly the way it should.
- Better UI discovery for the DNS setting
- Stronger resolver visibility inside Windows
- Clearer guidance for enterprises
- More visible verification tools
- Tighter integration with modern privacy features
- Fewer conflicts with VPNs and security software
Source: MakeUseOf I turned on one Windows 11 setting and my browsing got faster and more private
Last edited:
