1.1.1.1 Router Admin Login

1.1.1.1 is not your router. There is no login page at this address. If you typed 1.1.1.1 into your browser expecting a router admin panel, you reached Cloudflare’s public DNS resolver instead. This is one of the most common points of confusion in home networking. The address looks like a private gateway but is in fact a public IPv4 address — outside the RFC 1918 private ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) used by home routers. 1.1.1.1 is reachable from the internet because it is a public address operated as a globally distributed DNS anycast service. Your actual router admin panel is on your network’s default gateway — almost certainly an RFC 1918 private address like 192.168.1.1, 192.168.0.1, or 10.0.0.1.

Cloudflare launched 1.1.1.1 on April 1, 2018 as a free, fast, privacy-focused DNS resolver. It competes with Google’s 8.8.8.8 and Quad9’s 9.9.9.9 as an alternative to the DNS servers your ISP provides by default. Millions of devices worldwide are configured to use 1.1.1.1 for DNS resolution. Your router, however, has a completely different IP address.

What 1.1.1.1 Actually Does

DNS (Domain Name System) translates website names into IP addresses. When you type “google.com” into a browser, your device asks a DNS resolver to look up the corresponding IP address. The resolver returns the answer, and your browser connects to that IP address.

By default, your device uses whatever DNS server your ISP provides. These ISP DNS servers work but are not always the fastest or the most private. Cloudflare built 1.1.1.1 to offer an alternative with two priorities: speed and privacy.

DNS Resolver	Primary	Secondary	Operator
Cloudflare	1.1.1.1	1.0.0.1	Cloudflare
Google	8.8.8.8	8.8.4.4	Google
Quad9	9.9.9.9	149.112.112.112	Quad9
OpenDNS	208.67.222.222	208.67.220.220	Cisco

Cloudflare commits to not logging DNS queries in a way that identifies users and purges all logs within 24 hours. Independent auditors verify this commitment annually. Speed-wise, 1.1.1.1 consistently ranks among the fastest public DNS resolvers in independent benchmarks.

How to Find Your Actual Router

Your router admin panel is at your default gateway address, not at 1.1.1.1. Here is how to find your router IP address.

Windows. Open Command Prompt (Win+R, type cmd, Enter). Run ipconfig. The “Default Gateway” line shows your router’s address. It will be something like 192.168.1.1, 192.168.0.1, or 10.0.0.1.

macOS. Open System Settings, click Network, select Wi-Fi, click Details. The “Router” field displays your gateway.

iPhone/Android. Go to Wi-Fi settings and tap the connected network. The gateway or router address is listed in the connection details.

Type that gateway address into your browser to reach your router’s login page. That is where you change your Wi-Fi password, view connected devices, and manage network settings.

How to Use 1.1.1.1 as Your DNS Server

If you want to switch to Cloudflare DNS for faster or more private resolution, you have two options.

Configure it on your router. Log in to your router admin panel. Find the DNS settings section (usually under WAN or Internet settings). Replace the existing DNS addresses with 1.1.1.1 (primary) and 1.0.0.1 (secondary). Save and reboot the router. Every device on the network will now use Cloudflare DNS automatically.

Configure it on a single device. On Windows, go to Network Connections, right-click your adapter, select Properties, then Internet Protocol Version 4. Enter 1.1.1.1 and 1.0.0.1 as the DNS servers. On macOS, go to System Settings, Network, Wi-Fi, Details, DNS, and add the addresses.

Cloudflare also offers 1.1.1.1 with malware filtering (1.1.1.2) and adult content filtering (1.1.1.3) as variants for families.

The Buffalo Router Conflict

While 1.1.1.1 is primarily a DNS resolver, there is one notable exception. Some Buffalo routers sold in Japan were configured to use 1.1.1.1 as the default gateway address. Buffalo assigned this address to their routers years before Cloudflare claimed it for DNS services.

This creates a direct conflict. When a device on a Buffalo network tries to resolve DNS through 1.1.1.1, the query goes to the local router instead of Cloudflare. Conversely, if someone configures Cloudflare DNS on a Buffalo network, DNS queries bypass the router entirely and go to the internet, which may break local hostname resolution.

Buffalo has acknowledged this issue and released firmware updates for affected models that change the default gateway to a standard private address. If you own a Buffalo router and experience DNS problems, update the firmware or manually change the router’s LAN IP to a private address like 192.168.11.1 (Buffalo’s other common default).

Troubleshooting 1.1.1.1 Confusion

1. You typed 1.1.1.1 looking for a router login. Your router is at a different address. Run ipconfig on Windows or check Wi-Fi details on your phone to find the default gateway. That gateway address is your router.

2. 1.1.1.1 shows a Cloudflare page. This confirms the address is reaching Cloudflare’s DNS service, not a router. Your internet connection is working. Your router admin panel is at a private IP address like 192.168.1.1 or 192.168.0.1.

3. DNS is slow after configuring 1.1.1.1. Some ISPs intercept DNS traffic and redirect it to their own servers. Try enabling DNS over HTTPS (DoH) in your browser settings to bypass this interception. Firefox and Chrome both support DoH with Cloudflare.

4. Websites do not load after changing DNS. Double-check that you entered 1.1.1.1 and 1.0.0.1 correctly. If you accidentally removed the WAN or LAN gateway address instead of changing the DNS server, your internet connection will break. Restore the original settings and try again.

5. Buffalo router conflicts. If your Buffalo router uses 1.1.1.1 as the gateway, update the firmware. Alternatively, log in to the router’s admin panel and change the LAN IP address to 192.168.11.1 or another private address to eliminate the DNS conflict.

After confirming your DNS is configured correctly, run a broadband speed test from a wired client to verify your connection speed. DNS changes do not directly affect throughput — they only affect lookup latency (the time to resolve a hostname). If your speed is 30%+ below your ISP plan, the bottleneck is somewhere other than DNS. The full pillar context lives in the router brand directory, IP address directory, and find router IP guide.