192.168.1.1 is a private IPv4 address drawn from the 192.168.0.0/16 range that RFC 1918 sets aside for internal use. That block carries a 255.255.0.0 netmask and holds 65,536 addresses, none of which are routed across the public internet. Because the space is unallocated, it has no registrant, no operator and no location attached to it: the same address is in use simultaneously on millions of unrelated networks, and nothing about it identifies whose network you are on. Any question about 192.168.1.1 is a question about your own local network rather than about a host somewhere on the internet.
Within that block, 192.168.1.1 sits in the 192.168.1.0/24 subnet, whose usable host range runs from 192.168.1.1 to 192.168.1.254, with 192.168.1.255 reserved as the broadcast address. It occupies position one, the first usable address in the subnet, and that first slot is the conventional place to put a gateway. The other addresses in the same subnet are commonly handed out by DHCP to laptops, phones, printers and cameras, which is why 192.168.1.1 answers with an administration page while its neighbours usually belong to client devices.
The 192.168.0.0/16 block is the one most people meet, because nearly every home router, mobile hotspot and small office access point ships a default gateway inside it. Vendors documented as shipping this particular address include TP-Link on the Archer C7, TL-WR841N and Archer AX models, Linksys on the WRT54G and EA series, ASUS on the RT-AC68U and RT-AX series, Zyxel on its Keenetic and VMG series, and TRENDnet on the TEW series. Most people reading this are trying to do one of three things: open the admin page when the browser refuses to load it, get past a login screen that rejects every password tried, or work out whether 192.168.1.1 is even the gateway on the network they are connected to.
To open the admin panel, type 192.168.1.1 into your browser's address bar. If the page does not load, this is probably not the gateway address on your network — see the checks below. http://192.168.1.1
8 default username and password pairs have been reported for devices answering on 192.168.1.1, ordered by how often each one is seen.
| Username / Password | Percentage |
|---|---|
| admin / admin | 57% |
| none / admin | 19% |
| admin / password | 8% |
| admin / 1234 | 5% |
| none / none | 5% |
| none / 1234 | 3% |
| admin / none | 2% |
| guest / guest | 2% |
Among the credential pairs reported for devices answering on 192.168.1.1, admin/admin dominates at about 57 percent of reports. A blank username with the password admin accounts for roughly 10 percent, admin/password for 8 percent and admin/1234 for 5 percent, the last matching Zyxel's documented default on its Keenetic and VMG lines, while TP-Link, Linksys, ASUS and TRENDnet all document admin/admin. Smaller shares record none or an empty field on one or both sides, and guest/guest at 2 percent.
These are reported defaults, not a reading of your device. Units supplied by an internet provider frequently carry a unique password printed on the label, and any router configured previously will hold whatever was set then. Check the sticker first.
| Vendor | Models | Username / Password |
|---|---|---|
| TP-Link | Archer C7, TL-WR841N, Archer AX series | admin / admin |
| Linksys | WRT54G, EA series | admin / admin |
| ASUS | RT-AC68U, RT-AX series | admin / admin |
| Zyxel | Keenetic, VMG series | admin / 1234 |
| TRENDnet | TEW series | admin / admin |
If no password works, a factory reset is the fallback. TP-Link, Zyxel and TRENDnet units commonly use a recessed pinhole reset that needs a straightened paperclip, while Linksys and ASUS models commonly expose a physical reset button. In either case the device should be powered on and the control held for roughly ten to thirty seconds until the status lights cycle, then left alone to reboot for a minute or two.
A reset is not free. It clears the Wi-Fi network name and passphrase, so every wireless device has to be rejoined, and it discards port forwards, static DHCP reservations, parental controls, custom DNS and any PPPoE or VLAN settings the connection depends on. Export or photograph the configuration first if the admin page is still reachable.
Reset method by vendor:
Type 192.168.1.1 into your browser's address bar and press Enter. Type it by hand rather than accepting an autocomplete suggestion, which often fills in a different address you visited before.
If the browser reports that it cannot reach 192.168.1.1, this is not the gateway address on your network. On Windows run ipconfig /all and read the Default Gateway line; on macOS open System Settings, Network, Details, TCP/IP; on Linux run ip route and read the address after "default via".
If the login page loads but rejects your credentials, and you have never changed them, use the defaults printed on the device's label. If they have been changed and nobody knows the new password, a factory reset is the only way back in.
Type http://192.168.1.1 into the address bar rather than a search box, since a bare 192.168.1.1 is often treated as a search term. Confirm you are joined to the router's own network rather than a guest SSID, a phone hotspot or a VPN tunnel, all of which route traffic away from the local gateway. Then try a private window to rule out a stale cached redirect.
Many networks use a different first-hop address. On Windows, run ipconfig /all and read the Default Gateway line for the active adapter. On Linux, run ip route and take the address after "default via". On macOS, open System Settings, then Network, then Details for the active interface, and read the Router field under TCP/IP. Use whatever that reports, even if it is not 192.168.1.1.
A visible login page proves the device is reachable, so the problem lies with the credentials rather than the network. Work through the documented defaults in order instead of repeating one pair, and leave the username field genuinely empty where a blank entry is listed. Watch for caps lock and for a keyboard layout that swaps characters. Many firmwares lock out further attempts for several minutes after a handful of failures, so pause between rounds.
Older firmware on this address commonly serves plain HTTP on port 80, and forcing https://192.168.1.1 produces a connection reset. Newer firmware often does the opposite, redirecting to HTTPS with a self-signed certificate that browsers flag as unsafe; that warning is expected on a local device and can be accepted. If both fail, try an explicit port such as 192.168.1.1:8080 before concluding the device is dead.
Because this is the most common default, adding a second router or placing a modem-router behind an existing one often puts two devices on 192.168.1.1 at once. You will reach only the nearer one, and traffic meant for the other fails silently. Move the inner device to a different subnet, such as 192.168.2.0/24, so each gateway holds a unique address.
192.168.l.1 with a lowercase L, 192.168.11 with a missing dot, 192.168.1.1.1 with an extra octet and 192,168,1,1 with commas are all invalid as addresses, so the browser sends them to a search engine instead. Retype the four numbers separated by full stops, with no www prefix, no trailing path and no protocol other than http or https.
192.168.1.1 is often mistyped. These all refer to the same address:
l92.l68.l.l, 192.168..1.1, 192 168 1 1, 192.168.1.1..
The most common slip is typing a lower-case letter L in place of the digit 1, or the letter O in place of a zero.
The 192.168.1.0/24 subnet runs from 192.168.1.1 to 192.168.1.254, with 192.168.1.255 reserved as the broadcast address. These are the addresses in it we hold router login details for.
255 addresses in this subnet have a page; the most looked-up are listed here.
~$ curl https://www.proxydocker.com/api/v2/free/8.8.8.8
{
"ipAddress": "8.8.8.8",
"countryCode": "US",
"countryName": "United States",
"stateProv": "California",
"city": "Mountain View"
}The free API is limited to 500 daily requests and returns city-level location data only. For larger volumes or more data such as latitude/longitude, ISP details and proxy detection, see our commercial offers.
Copyright © 2026 Proxydocker.com, all rights reserved. · Privacy policy · Affiliate program