Find your router's IP address

One command per platform

Platform	Command or path	What to read
Windows	ipconfig	The Default Gateway line under your active adapter
Windows (PowerShell)	Get-NetRoute -DestinationPrefix 0.0.0.0/0 | Select-Object NextHop	NextHop
macOS	route -n get default	The gateway line
macOS	netstat -nr | grep default	Second column of the default row
Linux	ip route show default	The address after via
Linux	nmcli -g IP4.GATEWAY device show	The printed value
iOS / iPadOS	Settings, Wi-Fi, (i), IPV4 ADDRESS	Router
Android	Settings, Wi-Fi network details	Gateway
ChromeOS	Settings, Network, your Wi-Fi, Network	Gateway

macOS also exposes it in the GUI: System Settings, Wi-Fi, Details…, then the TCP/IP tab, Router row.

What the output looks like

Windows:

   IPv4 Address. . . . . . . . . . . : 192.168.1.47
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1

macOS:

$ route -n get default
   route to: default
destination: default
       mask: default
    gateway: 192.168.1.1
  interface: en0

Linux:

$ ip route show default
default via 192.168.1.1 dev enp3s0 proto dhcp src 192.168.1.24 metric 100

The pattern is the same everywhere. Your device holds a host address, and the gateway is one address in the same subnet, usually the first or last usable one.

Why the gateway is nearly always .1 or .254

There is no rule requiring it. It is a convention: vendors take the first usable host address in the subnet, or the last, and start the DHCP pool above or below it. That produces the four addresses people search for most, each of which has its own page here.

Address	Typical vendors
192.168.1.1	ASUS, Linksys, Netgear, Zyxel, Verizon Fios
192.168.0.1	D-Link, TP-Link, many cable gateways
10.0.0.1	Comcast Xfinity gateways, many business networks
192.168.1.254	BT, Technicolor, Arris, AT&T gateways

Read your own gateway rather than trying these in turn. A guess that lands on another subnet just times out.

Opening the admin page

Type the address straight into the URL bar on a device connected to that network. If nothing loads:

• Add the scheme. Modern browsers assume HTTPS and many routers only serve HTTP on the LAN. Try http://192.168.1.1 explicitly.
• Check you are on the right network. A guest SSID with client isolation, or a VPN capturing all routes, will both block the admin page. Disconnect the VPN and try again.
• Use a wired port if Wi-Fi fails. Some routers restrict administration to the LAN ports.
• Look at the label. The sticker on the underside or back of the router prints the admin address or hostname, the Wi-Fi name, and the initial credentials for that unit. Vendor hostnames such as routerlogin.net, tplinkwifi.net, or bthomehub.home resolve only on the local network.

Change the factory password on first login. Vendors ship per-unit credentials on the label now, but older units used one password across the whole model line, and those lists are public.

Only sign in to a router you own or administer. Accessing someone else’s equipment without permission is a criminal offence in most countries, including under the Computer Fraud and Abuse Act in the United States and the Computer Misuse Act in the United Kingdom.

When the gateway is not the router you expect

Two gateways in the output. A VPN client installs its own default route. Whichever route has the lower metric wins. Disconnect the VPN to see the real LAN gateway.

The gateway is a mesh node. Systems like Eero, Deco, Google Nest Wifi, and Orbi keep the gateway on the primary unit and manage everything through an app. Satellites do not serve an admin page.

The gateway is another router. If your router’s WAN address is itself in RFC 1918 space, there is a second router upstream and you are double-NATed. Port forwards need a rule on both devices, or the upstream one set to bridge mode.

The gateway is 100.64.x.x on the WAN side. That is carrier-grade NAT under RFC 6598. Your ISP is sharing one public address among subscribers. Compare your router’s WAN address with the address shown on this site to confirm.

No gateway at all. The interface has no route out. On a 169.254.x.x address, DHCP failed entirely, as described in RFC 3927.

Related

Your gateway address is private, from the ranges reserved by RFC 1918. It is not the address websites see. The public vs private guide covers the difference, and /report shows the public side of your connection.