What Is 192.168.1.1? A Complete Guide to Private IPs, Gateways, and RFC 1918

1. Public IP vs. Private IP — One Diagram Explains It All

Here's what a typical home network looks like:

Internet ← (Public IP, unique) → ISP → your router's WAN port
                                ↓
          Router LAN port (192.168.1.1 = gateway)
                                ↓
            +---------------+---------------+
            ↓               ↓               ↓
      Phone 192.168.1.5   TV .6         PC .10
      (all private IPs, visible only inside your home)

• Public IP — globally unique; this is the address exposed when you visit external websites (assigned by your ISP)
• Private IP / Internal IP — valid only within the local subnet; every household's 192.168.1.1 doesn't conflict because these IPs never reach the public internet
• NAT — the "translation" performed by the router: when a device on the LAN accesses the internet, the router rewrites the request from 192.168.1.5 to go out using the public IP, then translates the reply back

Want to know yourPublic IP? Just open the cleanip.io homepageand you'll see it right away. What you see isn't 192.168.x.x, but the real address assigned by your ISP.

2. The Three RFC 1918 Private IP Ranges — Full Spectrum

In 1996, the IETF standard RFC 1918 designated three IPv4 ranges exclusively for private use. They are never routed to the public internet, and anyone can use them in their own network without authorization.

3. Default Login IPs for Popular Router Brands

Home routers ship with these default addresses out of the box. If it's been changed, check the sticker on the bottom of the router (look for "Default IP" or "Admin URL"), or check the "gateway IP" from your computer's command line.

How to Find Your Router's IP Address

• Windows: Press Win+R → type cmd → type ipconfig → look for "Default Gateway"
• macOS: System Settings → Network → Details → TCP/IP → Router
• Linux: In a terminal, run ip route | grep default
• iOS: Settings → Wi-Fi → tap the ⓘ next to your current Wi-Fi name → Router
• Android: Settings → Wi-Fi → long-press the current Wi-Fi → Modify network → Advanced → Show gateway

4. CGNAT — What's That 100.64.x.x Address You Got?

IPv4 addresses ran out. All 4.3 billion IPv4 addresses worldwide were fully allocated by 2019. To keep bringing new users online, ISPs deployed CGNAT (Carrier-Grade NAT), and RFC 6598 defines a range reserved specifically for carrier-internal use:

If the IP your home WAN port gets is 100.x.x.xthen you're behind CGNAT — you don't have a real public IPv4 address. This means:

• Port forwarding / NAT traversal won't work (remote access to game consoles or NAS becomes a hassle)
• Multiple users share a single real public IP, which risk-control systems may flag as suspicious
• You can call your broadband provider and request a "public IP" (usually free; supported by China Mobile / China Unicom / China Telecom)

How to check if you're behind CGNAT? Log into your router and check whether the WAN IP is 100.64.x.x; then visit the cleanip.io homepageto see your real egress IP — if the router's WAN IP doesn't match the exit IP you see, there's at least one layer of CGNAT in between.

Another use case:Tailscale and Cloudflare WARP also use 100.64/10 by default to assign IPs to virtual network nodes.

5. 169.254.x.x — Seeing This Means Your Network Is Broken

169.254.0.0/16 is the Link-local Address (RFC 3927). When a device boots, it requests an IP from a DHCP server. If the request fails(router is off, cable unplugged, DHCP service down), the operating system automatically assigns itself a 169.254.x.x address so it can at least talk to other failed devices on the local segment.

On Windows this is called APIPA (Automatic Private IP Addressing). Actually seeing this address = your network isn't connected. Don't fiddle with settings — restart your router or check the cable first.

6. 127.0.0.1 — Always You

127.0.0.0/8 is entirely reserved as Loopback (RFC 1122), but in practice only 127.0.0.1 is actually used — its alias is localhost.

• Visiting http://127.0.0.1:3000 = accessing port 3000 on your own machine
• Every running computer, phone, or server has this address, and it never conflicts
• It's the same on Windows / Mac / Linux / iOS / Android
• Essential for developers — used whenever you spin up a local service for debugging

The IPv6 equivalent is ::1.

7. Other Special IPs You May Have Encountered

7.1 0.0.0.0 — "All Addresses"

This isn't a specific IP — it's a placeholder. Its meaning differs depending on context:

• A server binding to 0.0.0.0 = listening on ports across all network interfaces(vs. listening only on 127.0.0.1 / 192.168.1.5)
• In a routing table, 0.0.0.0/0 = default route (used when nothing else matches)
• When a client makes a DHCP request, the source IP is 0.0.0.0 (because it hasn't obtained an IP yet)

7.2 255.255.255.255 — Limited Broadcast

Before obtaining an IP, a DHCP client broadcasts to this address asking "who can give me an IP?" Every device on the local subnet receives it.

7.3 Documentation Example IPs (TEST-NET-1/2/3)

RFC 5737 reserves three ranges specifically for documentation and teaching examples, which are never routable:

• 192.0.2.0/24 — TEST-NET-1
• 198.51.100.0/24 — TEST-NET-2
• 203.0.113.0/24 — TEST-NET-3

If you see these IPs in an RFC, tutorial, or course, the author is just using them as an example — don't actually try to ping them.

7.4 224.x.x.x Multicast

224.0.0.0/4 is a one-to-many multicastaddress range. One host sends data and multiple hosts can receive it simultaneously (vs. ordinary one-to-one unicast). Common uses: LAN device discovery (mDNS/Bonjour uses 224.0.0.251) and routing protocols (OSPF uses 224.0.0.5).

8. IPv6 Has Private Ranges Too

The IPv6 equivalents:

Note: IPv6 has no concept of NAT translating a private IP to a public one — every device gets a globally unique IPv6 address directly.

9. Why Doesn't cleanip.io Return Results for These IPs?

You may have noticed that searching directly for 192.168.1.1doesn't return the usual IP intelligence (location / ASN / type). That's because these IPs are bogon(locally reserved, never routed globally), so no GeoIP or WHOIS database has real information for them — hundreds of millions of routers worldwide use 192.168.1.1 simultaneously, and there's no concept of "which country" it belongs to.

That's why we built this knowledge card specifically for these IPs — far friendlier than just showing "no results."