Understand private and public IP addresses

Learn the reserved private ranges

IANA explains that private-use address blocks are reserved for local networks and should not appear as routable addresses on the public internet.

The current IANA special-purpose registry identifies 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16 as Private-Use space.

A private address is not automatically unsafe or misconfigured. It is the expected design for most home clients. The router normally uses network address translation so several devices can share upstream connectivity.

Find the active address, not every adapter

Microsoft documents that ipconfig without parameters displays IPv4 and IPv6 addresses, subnet mask and default gateway for adapters.

VPNs, virtual machines and disconnected adapters can add many entries. Find the adapter that is currently connected and confirm its Default Gateway. An address beginning 169.254 commonly indicates that Windows did not obtain normal IPv4 settings from DHCP.

1. 1

   Open Command Prompt and run ipconfig.

2. 2

   Locate the active Wi-Fi or Ethernet adapter.

3. 3

   Record its IPv4 address, subnet mask and Default Gateway.

4. 4

   Ignore disconnected and clearly virtual adapters for the first pass.

5. 5

   Check whether the address falls inside a private-use range or is a 169.254.x.x fallback address.

Interpret the public side carefully

A public-IP lookup usually shows the address presented by the router or provider, not a unique address assigned to the laptop. Some providers use carrier-grade translation, so even the router's WAN address may be private or shared upstream. Public addresses can also change after reconnects or lease changes.

Do not use a public IP as proof of a person's identity. It identifies an internet connection at a time and can be shared by households, VPN users, mobile networks or provider translation.

Use address patterns as evidence

A valid private address plus a reachable gateway shows that DHCP and the local path are at least partly working. A 169.254 address with no gateway suggests the client could not complete normal DHCP configuration. Duplicate-address warnings point to static configuration or multiple DHCP problems.

Keep automatic addressing unless the network owner has assigned a static plan. Randomly typing an address can create conflicts or place the device outside the correct subnet.

1. 1

   Compare the address before and during the problem.

2. 2

   Verify the gateway is in the expected local range.

3. 3

   Test the gateway before testing the internet.

4. 4

   Renew DHCP only after recording the original values.

5. 5

   Escalate duplicate or provider-facing address issues with timestamps and the router model.

Common mistakes to avoid

• Calling every non-public address invalid.
• Publishing a complete ipconfig /all output without redaction.
• Assigning a random static address to fix DHCP.
• Treating a public IP as a unique personal identity.