How to Find My Router IP Address (All Devices)
This guide covers: How to Find My Router IP Address (All Devices).
Your router IP is usually the default gatewayon the local network. It is the address you use to open the router admin panel, and it is also the path your devices use when sending traffic out of the LAN. That sounds simple, but users often confuse the router IP with the public IP, the modem admin IP, or the computer's own private address. This guide shows how to find the gateway correctly on every major platform and explains what the number is actually for.
What the router IP actually is
On most home networks, the router IP is the local address your devices use as their next hop out of the network. In other words, it is the gateway for internet access and local routing decisions. That is why operating systems often label it as Default Gateway or Router rather than just "router IP."
The key point is that this is a local address. It is usually not the same as the public IP websites see. If you type the gateway address into the browser, you often reach the router admin page. If you type the public IP, you are interacting with the internet-facing side of the connection instead.
Common default router IPs
- 192.168.1.1 for many consumer routers and ISP devices
- 192.168.0.1 for many D-Link, TP-Link, and Netgear setups
- 10.0.0.1 on some ISP gateways and cable-router setups
- 192.168.1.254 on some ISP-provided equipment
- 192.168.8.1 on some mobile hotspots and Huawei devices
These are common defaults, not guarantees. The exact address may have been changed by the user, the ISP, or a mesh setup, which is why the better approach is to ask the operating system which gateway it is using.
How to find the router IP on each platform
Windows
ipconfigRead the Default Gateway line under the active adapter. For more Windows detail, see Find My IP on Windows.
Mac
netstat -nr | grep defaultThe IP beside default is the gateway. You can also Option-click the Wi-Fi icon or check System Settings.
iPhone
- Open Settings > Wi-Fi.
- Tap the info button next to the connected network.
- Read the Router field.
Android
- Open Wi-Fi or Internet settings.
- Open the connected network details.
- Read the Gateway or Router entry.
Linux
ip route | grep default
nmcli device show | grep IP4.GATEWAYRouter IP, public IP, and modem IP are different jobs
The router IP is the local gateway. The public IP is the internet-facing identity seen by websites. A modem admin IP, when present, is often just another management address on local equipment such as 192.168.100.1. These addresses are easy to confuse because they all appear in "network settings," but they solve different problems.
If you only want to know what outside services see, use the homepage checker. If you want to reach the router admin panel, use the gateway IP. If you want to compare the router's WAN status against outside visibility, check both.
Why finding the gateway matters in practice
- Router login. You need the gateway IP to open the admin interface.
- Wi-Fi password changes. Router admin access often starts with the gateway page.
- Port forwarding. You configure forwarding rules in the router panel reached via the local gateway.
- DNS and DHCP review. Local address assignment and DNS settings are often managed there.
- Connected-device checks. Many routers show active clients and leases in the admin UI.
- CGNAT diagnosis. Comparing gateway-side status with public IP visibility helps explain upstream translation issues.
When a default IP does not work in the browser
If 192.168.1.1 or another common address does not open the panel, that does not automatically mean the router is broken. The router may be using a different subnet, the gateway may have been changed, the device may be on guest Wi-Fi, or the admin interface may be disabled on that segment. In mesh and ISP-managed setups, the visible gateway can also belong to one device while admin control lives on another.
The best next step is to read the OS-reported gateway rather than keep guessing default values.
Gateway IP and router admin page are related, but not always identical
On many home networks the default gateway and the router admin page live on the same IP, so users start treating them as the same thing. In more complex setups, that can break down. Mesh systems, ISP-managed gateways, or modem/router combinations can separate the device doing the routing from the place where full administration happens.
So the gateway IP is still the right first answer, but if it does not expose the settings you expect, the network may be using a layered design rather than a single traditional home router.
Common mistakes and edge cases
- Using the public IP to try to reach the router locally. That is usually the wrong address for admin access.
- Assuming every router uses 192.168.1.1. Many do, but not all, and custom changes are common.
- Ignoring guest networks. Guest Wi-Fi may isolate clients from the router admin page.
- Confusing WAN status with LAN gateway. The router can display both, and they serve different roles.
- Forgetting mesh systems. In mesh networks, the gateway function and the admin app workflow may not look like traditional single-router setups.
- Overlooking CGNAT when checking reachability. Local gateway access says nothing by itself about direct public inbound access.
Useful IP Trackers tools after finding the router IP
- IP Address Lookup shows what the outside world sees as the public IP.
- Public vs Private IP helps clarify gateway scope versus public scope.
- Port Forwarding Not Working? CGNAT Checks matters if router changes are not producing outside reachability.
- DNS Lookup is useful when you are also reviewing router DNS settings.
- Router login guide goes deeper into credentials and admin-panel access.
Why this check matters before troubleshooting port forwarding
Users often skip straight to public-port tests without confirming the local gateway and device path first. But if you do not know which router is actually acting as the gateway, it becomes much harder to tell whether the real issue is double NAT, CGNAT, a wrong forwarding target, or the wrong admin interface entirely. Finding the router IP is the foundation step that makes those later checks meaningful.
Guest Wi-Fi and managed networks often hide the admin page on purpose
In homes this is usually only a small edge case, but in guest Wi-Fi, hotel, dorm, and some ISP-managed environments, the gateway address may exist without giving you normal admin access. The network is designed to route traffic for clients while keeping the control plane restricted. That is why "I found the router IP but can't log in" does not always mean you found the wrong address.
Why each operating system labels the router differently
One reason "find my router IP" feels harder than it should is that every OS uses different language for the exact same number. Windows says Default Gateway. macOS says Router. iOS says Router. Android sometimes shows Gateway, sometimes Router, depending on the manufacturer skin. Linux command-line tools call it the default route or simply default.
All of those labels refer to the same idea: the IP your device sends traffic to when the destination is not on the local subnet. If you keep that mental model, you can stop worrying about which screen uses which word. They are pointing at the same address, just with different vocabulary inherited from each platform's networking stack.
Router IP on guest Wi-Fi, captive portals, and public networks
Hotels, airports, cafes, dorms, and corporate guest Wi-Fi networks usually still expose a gateway IP, but you should treat it differently than your home gateway. The number you see in ipconfigor the Wi-Fi details page may belong to a captive-portal device, a guest VLAN gateway, or a tightly restricted segment. Reaching that IP in a browser will not give you router admin access, and it should not. You are a guest on someone else's network.
That is also why "I found a different IP than I expected" on public Wi-Fi is usually normal rather than a misconfiguration. Managed networks often segment client traffic so each room, table, or session sees its own slice of the address plan. The gateway address you read still works for outbound routing, but it does not unlock the network the way a home-router IP would.
Static gateway vs DHCP-assigned gateway
On most home networks, the gateway address is delivered to each device automatically via DHCP at the same time as the IP, subnet mask, and DNS servers. That is why your phone, laptop, and TV all magically agree on the same router IP without anyone configuring it.
On some advanced setups, you can override that and pin a static gateway directly on the device. That is rarely needed at home and often causes problems: if you set a static gateway and then change routers, the device keeps trying to send traffic to a router IP that no longer exists. For almost every home use case, DHCP-assigned gateway plus a DHCP reservation on the router gives the same predictability without the brittleness of a fully manual static configuration on the client.
Modem-router combo units add a second hidden management address
Many ISPs ship modem-router combo units (sometimes called gateways or residential gateways) that contain both a modem and a router in one box. These devices often expose two management addresses on different IP planes: the normal router gateway you see in ipconfig (typically 192.168.1.1 or 192.168.0.1), and a modem-side diagnostic page on a separate fixed address like 192.168.100.1. The modem page is reachable even when the router side has issues, which is why ISP support sometimes asks you to open it during troubleshooting.
If you only check the gateway your OS reports, you will miss the modem-side page entirely. That is fine for most home users, but if you are debugging signal levels, DOCSIS status, or upstream sync issues on cable, knowing the modem page exists at a fixed address is the difference between a 30-second check and a long call with the ISP.
Double NAT shows up as a router IP that does not feel right
Double NAT happens when you have a router behind another router — for example, your own Wi-Fi router plugged into the LAN port of an ISP gateway that is also routing. Each router runs its own DHCP, each one hands out private addresses on its own subnet, and traffic gets translated twice before reaching the internet.
The clue often shows up in the gateway IP. If your laptop's default gateway is something like 192.168.0.1 and your public IP check shows you are behind another 192.168.x.x block, you are double NATed. The fix is usually to put one of the routers (commonly the ISP gateway) into bridge or pass-through mode so only one device is doing NAT. Port forwarding, gaming, and direct connections are the workflows that break first under double NAT, which is why this is worth knowing even if your home browsing feels fine.
Reading the gateway when a VPN is active
A VPN can change what you see when you check the gateway, depending on the client and the routing policy. Many VPN clients (WireGuard, OpenVPN, IKEv2 on Windows, Tailscale, ZeroTier) add a virtual interface with its own gateway address used only for tunnel traffic. The original LAN gateway is still there, still handling local traffic and serving as the default route for anything outside the VPN's allowed-IPs list.
That is why ipconfig or ip route on a VPN device often shows two default routes with different metrics. The lower metric wins. If you only want the LAN router IP for admin access, look for the gateway tied to your Wi-Fi or Ethernet adapter, not the one tied to tun0, wg0, or a VPN-named adapter.
Frequently asked questions
Is the router IP the same as the public IP? Usually no. The router IP is the local gateway; the public IP is what the internet sees.
How do I find my router IP on Windows? Run ipconfig and read the Default Gateway line.
How do I find my router IP on iPhone? Open Wi-Fi settings and read the Router field in the connected network details.
Why doesn't 192.168.1.1 work? Your router may use a different subnet, the gateway may have been customized, or you may be on a guest or isolated network.
Can I use the router IP to check what websites see? No. For that, use a public IP checker instead.
What if my WAN status and public IP do not match? You may be behind CGNAT or another upstream translation layer.
Related reading: Computer IP vs Router IP, Find My IP on Windows, Public vs Private IP, and Port Forwarding and CGNAT
