Cloudflare 1.1.1.1 vs Quad9 9.9.9.9: Was Speed the Reason?
Usually, switching from Cloudflare’s 1.1.1.1 DNS resolver to Quad9’s 9.9.9.9 is not mainly about raw speed: both are public DNS services, and either may feel faster depending on your network and location. People often make the change for Quad9’s malicious-domain blocking and security focus, or because they prefer its policies—not because it is universally quicker.
What the addresses do
1.1.1.1 and 9.9.9.9 are IPv4 addresses for recursive DNS resolvers. DNS, the Domain Name System, translates a name such as example.com into the address a device needs to contact a website. A recursive resolver finds or retrieves that information on your behalf, then returns it to your device.
Cloudflare operates the 1.1.1.1 public resolver, with a separate filtering option at 1.1.1.2 that blocks malware. Quad9 operates 9.9.9.9, which is the service’s security-oriented resolver and blocks domains associated with threats using threat intelligence feeds. Quad9 also provides other resolver addresses and configurations, including options that do not apply the same blocking; check its current setup guidance before choosing one.
These are DNS services, not general-purpose internet accelerators. They do not increase the capacity of your internet connection, change the speed of a remote server, or encrypt all of your browsing traffic. They can affect the time required to look up a domain and whether certain domains resolve.
Why someone might switch to Quad9
The most substantial reason is protection against known malicious domains. When a device asks a security-filtering resolver for a blocked domain, the resolver can refuse to return the ordinary destination address. This may help prevent accidental connections to some phishing, malware, or other threat-associated sites. It is one layer of protection, not a replacement for updated software, cautious link handling, or endpoint security.
Other motivations can include preferring Quad9’s stated privacy approach, wanting a resolver that filters threats by default at its standard address, or finding that it works more reliably through a particular internet provider. These are practical or policy choices. A switch might also happen after reading a recommendation or troubleshooting DNS failures, without any measured speed difference.
Cloudflare’s standard 1.1.1.1 resolver emphasizes privacy and performance, while its 1.1.1.2 option adds malware blocking. That distinction matters: comparing 9.9.9.9 with 1.1.1.1 is not the same as comparing two identically filtered configurations. Resolver features, privacy policies, and configuration details can change, so consult each provider’s current documentation for exact behavior.
What speed tests can—and cannot—show
DNS response time is only one small part of loading a page. After the lookup, the browser still has to connect to the site, negotiate a secure connection, download content, and run scripts. A resolver that answers a DNS query a few milliseconds earlier may make little noticeable difference, especially when the browser or operating system already has the answer cached.
Results also depend on where you are, how your internet provider routes DNS traffic, whether a resolver has a nearby service location, and how the test is conducted. A test that repeats queries for one domain may measure cached answers rather than the first lookup. A browser using its own secure DNS setting may bypass the resolver configured in the operating system, making a router-level change irrelevant to that browser.
For a fair comparison, use the same device and network, test at different times, and compare multiple uncached domain lookups if you have a suitable diagnostic tool. Treat small differences as variable rather than proof that one service is always faster. Also distinguish DNS lookup latency from a broadband speed test’s download and upload measurements; changing DNS should not be expected to improve those throughput figures.
How to choose and configure a resolver
Choose based on the trade-off you actually care about: threat filtering, privacy policy, compatibility, reliability, or measured latency on your own connection. If you value filtering, check whether the resolver you select blocks the kinds of domains you want blocked and whether that could interfere with legitimate services. If performance is the priority, compare it locally rather than relying on a universal ranking.
On many home networks, DNS addresses are set in the router, which can apply them to devices that use the router’s network settings. Alternatively, a computer or phone may allow DNS settings for a particular network. Exact menu names vary by operating system and router. Browsers can also offer a secure DNS setting of their own; when enabled, it may take precedence for browser lookups.
- Record the existing DNS settings before changing them, so you can restore the previous configuration.
- Enter the addresses in the correct primary and secondary fields. For Quad9, the standard IPv4 addresses commonly used are 9.9.9.9 and 149.112.112.112; for Cloudflare’s standard IPv4 resolver, they are 1.1.1.1 and 1.0.0.1.
- Check whether your device or router also has IPv6 DNS settings. Leaving a different resolver configured for IPv6 can produce mixed behavior.
- Reconnect or renew the network connection if necessary, then test several websites and apps. Restarting a device or clearing its DNS cache may help if it continues using old results.
Do not assume that setting a resolver on one device changes every device in the home, or that router settings override a browser’s separate DNS configuration. If you use a work, school, or managed network, its administrator may control DNS settings.
Common problems and limitations
A filtering resolver can block a domain that a user wants to visit, including a site flagged incorrectly or a service that depends on a blocked domain. If only one site fails after a switch, compare its behavior using the prior resolver or another network, and check the provider’s guidance for reporting or resolving a filtering issue. Do not infer that a site is malicious solely because it fails to load.
If many sites stop resolving, first check that the addresses were entered correctly and that the network connection itself works. A temporary resolver outage, router configuration error, captive portal, or conflicting IPv4 and IPv6 settings can also be responsible. Reverting to automatic DNS is a useful way to determine whether the change caused the problem. DNS choice does not make every connection private: websites can still see the IP address used to reach them, and DNS settings alone do not provide a VPN.
Frequently Asked Questions
Is Quad9 9.9.9.9 faster than Cloudflare 1.1.1.1?
There is no universally faster choice. The result varies with location, routing, caching, and the device’s DNS configuration. Compare them on the network and devices you actually use.
Why switch from 1.1.1.1 to 9.9.9.9 if speed was not the reason?
A common reason is Quad9’s threat-domain blocking at its standard resolver, along with a preference for its privacy approach or behavior. The right explanation depends on the person who made the switch.
Does changing DNS make downloads faster?
Usually it does not increase download throughput. DNS can affect how quickly a domain is looked up, but download speed depends on the connection, remote server, and other factors.
Does 9.9.9.9 block every dangerous website?
No. Its filtering is based on threat information and cannot identify every harmful or newly created domain. Treat it as one protective layer, not a guarantee of safety.
Can I use Quad9 on my router and Cloudflare in my browser?
It may be possible, because browsers can use a separately configured secure DNS resolver. That can mean browser lookups use a different service from other apps, so check the browser’s DNS setting if behavior differs.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.