To see your router's IP address, use the command prompt (Windows), Terminal (macOS/Linux), or access your router's web interface through a browser. The default gateway-typically 192.168.1.1 or 192.168.0.1-is the device managing your home network.
The router IP address is the gateway between your devices and the internet. It's assigned by your ISP or set manually during setup. Most home networks use private IP ranges: 192.168.x.x, 10.0.x.x, or 172.16.x.x. These addresses aren't visible on the public internet.
On most routers, the default login page is accessible via the gateway IP. If you can't reach it, try common defaults like 192.168.1.1, 192.168.0.1, or 10.0.0.1. Some ISPs assign unique IPs-like EE's 192.168.1.254 for certain modems-so check your provider's documentation.
On Windows, open Command Prompt and run ipconfig. Look under "Wireless LAN adapter" or "Ethernet adapter" for "Default Gateway." The value listed is your router's IP. For example:
Default Gateway . . . . . . . . . : 192.168.1.1
On macOS or Linux, open Terminal and run netstat -nr | grep default. The output shows the default route-the router's IP. On macOS, you can also use route get 8.8.8.8 to find the gateway.
These tools work because your computer stores routing tables. The default gateway is the first hop for traffic leaving your local network. This method is fast, accurate, and doesn't require logging into the router.
Open a browser and enter the gateway IP. If it's 192.168.1.1, type http://192.168.1.1 in the address bar. You'll be prompted for a username and password. Default credentials are often "admin/admin" or "admin/password."
If the page fails to load, ensure your device is connected to the correct network. A wired connection reduces errors. If you're on Wi-Fi, disconnect and reconnect to confirm the network assignment.
Some routers hide the IP in settings. Go through to "Network" or "Status" and look for "Gateway," "Router Address," or "Default Gateway." On TP-Link models, this appears under "Advanced" → "System Tools."
Many users assume their router IP is 192.168.1.1 without checking. But some ISPs change the default. EE routers, for example, use 192.168.1.254. Entering the wrong IP causes a "page not found" error.
Another mistake: confusing the router IP with the public IP. Your public IP is visible on sites like whatismyip.com. That's the address seen by websites-not your internal gateway. The router IP is private and used only within your home network.
When troubleshooting, verify the IP is static. Changing IPs can change after reboot. Check your router's DHCP settings. If the gateway changes frequently, assign a static IP to your computer or use a reservation in the router's DHCP settings.
Different brands use different defaults. Knowing the model helps avoid guesswork.
| Brand | Default IP | Common Login |
|---|---|---|
| Netgear | 192.168.1.1 | admin / password |
| TP-Link | 192.168.0.1 | admin / admin |
| ASUS | 192.168.1.1 | admin / blank |
| Comcast/Xfinity | 192.168.1.1 | admin / password |
| EE (UK) | 192.168.1.254 | admin / admin |
Always check the label on the router. The IP and login details are printed on the back or side. If missing, search the model number online. According to the FCC database, many modem-router combos have factory-set IPs documented in firmware specifications.
I once spent 45 minutes trying to log into a Netgear router using 192.168.1.1. Nothing loaded. After switching to 192.168.0.1-found on the device's label-I accessed the dashboard in seconds. The lesson: don't assume. Verify.
For advanced users, the arp -a command reveals all devices on the network, including the router. This shows MAC addresses and IP assignments. It's useful when multiple gateways exist-common in multi-router setups.
Changing the default router IP improves security. A custom IP like 192.168.10.1 makes it harder for attackers to guess the address. Disable remote management and enable WPA3 encryption.
Never share your router IP publicly. It's not sensitive like passwords, but exposing it allows unauthorized access attempts. Use a firewall and monitor logs for failed login attempts.
For those managing multiple networks, tools like nmap scan for active devices. Run nmap -sn 192.168.1.0/24 to list all hosts. The router usually responds first.
If you're setting up port forwarding or configuring a server, knowing the router IP is essential. Without it, services won't be reachable from outside your home network.