How to Check if an IP Address Is Private or Public

You’re troubleshooting a network issue, reading through firewall rules, or debugging why a service isn’t reachable, and you’re staring at an IP address trying to remember whether it falls in a private range, a loopback range, or is actually a routable public address. The private ranges defined in RFC 1918 (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) are common enough that many people have the 192.168.x.x range memorized, but the boundaries of the 172.16.0.0/12 block in particular trip people up, since it’s not simply “everything starting with 172.”

Beyond RFC 1918 private ranges, there’s also loopback (127.0.0.0/8), link-local (169.254.0.0/16), and other reserved ranges that come up regularly enough in network troubleshooting that misidentifying one can send you down the wrong debugging path entirely.

What checking private vs. public IP ranges actually involves

Determining whether an IPv4 address is private or public means checking it against the specific defined CIDR blocks for private (RFC 1918), loopback, link-local, and other reserved ranges — each with an exact numeric boundary, not just a memorable-looking prefix. The 172.16.0.0/12 range is the one most commonly gotten wrong, since it only covers 172.16.0.0 through 172.31.255.255, not every address starting with 172.

Why people get stuck here

• Assuming 172.x.x.x is entirely private. Only the 172.16.0.0 through 172.31.255.255 range is actually private — addresses like 172.32.0.0 and above, or 172.15.x.x, are public, and this specific boundary is easy to misremember.
• Confusing loopback with private ranges. 127.0.0.0/8 (loopback, most commonly seen as 127.0.0.1) is a genuinely separate reserved range from RFC 1918 private space, serving a different purpose (routing back to the local machine itself).
• Not recognizing link-local addresses. The 169.254.0.0/16 range shows up specifically when a device fails to get an IP address via DHCP and falls back to self-assigning one — recognizing this range immediately tells you something specific went wrong with automatic addressing.
• Manually checking address ranges against memorized boundaries. For anything beyond the most common 192.168.x.x range, manually verifying whether an address falls within the correct CIDR boundary is easy to get wrong without directly checking it.

What a good private IP range checker looks like

Checks against the complete set of relevant reserved ranges

Covering RFC 1918 private ranges, loopback, link-local, and other reserved blocks together — not just the most common 192.168.x.x range — makes the tool useful for the full range of addresses you might actually encounter.

Shows the matching CIDR block explicitly

Displaying the exact CIDR range an address falls into, not just a yes/no private answer, gives you the precise boundary information needed for firewall rules or subnet planning.

Explains the typical use of each range

Context on what each reserved range is typically used for (private LAN addressing, loopback, DHCP failure fallback) helps you interpret what finding an address in that range actually implies about a network situation.

Common mistakes to avoid

• Assuming any address starting with “172” is automatically private without checking the actual 172.16.0.0/12 boundary.
• Treating a link-local address (169.254.x.x) as a normal assigned address rather than recognizing it as a sign that DHCP addressing failed.
• Confusing loopback addresses with private network addresses, which serve different purposes despite both being non-publicly-routable.
• Debugging a connectivity issue without first confirming whether the IP in question is actually meant to be reachable from where you’re checking, given its range.
• Assuming IPv6 reserved ranges follow the same boundaries as IPv4 — they’re a completely separate addressing scheme with their own reserved range definitions.

How to do it with Private IP Range Checker

Online Tool Store’s Private IP Range Checker checks your address entirely in your browser.

1. Open the Private IP Range Checker tool.
2. Enter the IPv4 address you want to check.
3. See whether it falls into a private, loopback, link-local, or other reserved range.
4. Review the matching CIDR block and its typical use to inform your troubleshooting.

Frequently asked questions

What’s the exact range covered by 172.16.0.0/12?

It covers 172.16.0.0 through 172.31.255.255 — not every address starting with 172. Addresses like 172.15.x.x or 172.32.x.x and above fall outside this private range and are publicly routable.

Why would I see a 169.254.x.x address on my device?

This is the link-local range, self-assigned by a device when it fails to receive an address from a DHCP server — seeing this range on a device is usually a signal to check DHCP connectivity rather than a normal working network configuration.

Is 127.0.0.1 the only loopback address?

No — the entire 127.0.0.0/8 range is reserved for loopback, meaning any address in that block routes back to the local machine itself. 127.0.0.1 is simply the most commonly used address within that reserved range.

Final thought

Private and reserved IP ranges have exact numeric boundaries, not memorable-looking prefixes — check the actual range rather than relying on a rough recollection, especially for the commonly misremembered 172.16.0.0/12 block.

Try the free Private IP Range Checker tool