Private IP Checker
Private IP Checker recognizes 10/8, 172.16/12, 192.168/16, and 127/8 as private or reserved IPv4 ranges. It is a narrow local classifier, not a complete registry of special-purpose addresses, and it does not analyze IPv6, CGNAT, link-local, documentation, multicast, or broadcast ranges.
Runs locally — files stay on your deviceIs 172.20.4.8 private?
Yes. It falls inside 172.16.0.0 through 172.31.255.255.
RFC 1918 defines three private IPv4 blocks
Private-use IPv4 space comprises 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. This tool also groups the 127.0.0.0/8 loopback block into its private/reserved result.
How it works
The input is split into four decimal components. The first octets are compared with the common private blocks and loopback rule.
Key concepts
Private and loopback are not identical
The tool combines them in one result for convenience, but they serve different purposes.
Non-private does not guarantee public routability
Other reserved and special-use ranges exist.
When to use it
- Recognize familiar LAN addresses.
- Check whether a common IPv4 value is private.
- Explain why a local address is not globally routed.
When not to use it
- Do not use it as a complete special-use registry.
- Do not classify IPv6 with this page.
- Do not infer whether an address is safe or belongs to your network.
Worked examples
Ten network
- Input
10.42.0.7- Expected output
Private/reserved IPv4 range
All 10.x.x.x values match 10/8.
Middle private block
- Input
172.31.255.1- Expected output
Private/reserved IPv4 range
The second octet is within 16–31.
Outside the block
- Input
172.32.0.1- Expected output
Not a common private IPv4 range
172.32 is outside 172.16/12.
Common mistakes
Assuming every 172 address is private
Only second octets 16 through 31 match. Correction: Check the full 172.16/12 boundary.
Calling all non-private addresses public
Special-purpose ranges extend beyond these checks. Correction: Use a comprehensive address registry.
Treating private as trusted
Private network traffic can still be malicious. Correction: Apply authentication and authorization independently.
Best practices
- Parse the address strictly before classification.
- Use a maintained special-range library for security controls.
- Keep network location separate from trust.
Related operations and differences
CIDR to Range
Choose CIDR to Range when you need to calculate an IPv4 network and broadcast address.; use Private IP Checker specifically for private ip.
IP Address Validator
Choose IP Address Validator when you need to validate IPv4 or basic IPv6 syntax.; use Private IP Checker specifically for private ip.
cURL Command Builder
Choose cURL Command Builder when you need to build a basic cURL command from manual fields.; use Private IP Checker specifically for private ip.
DMARC Record Generator
Choose DMARC Record Generator when you need to generate a basic DMARC policy record.; use Private IP Checker specifically for private ip.
Fetch Request Builder
Choose Fetch Request Builder when you need to build a browser fetch request snippet.; use Private IP Checker specifically for private ip.
HTTP Header Formatter
Choose HTTP Header Formatter when you need to normalize spacing in pasted HTTP headers.; use Private IP Checker specifically for private ip.
Limitations and privacy
- Checks only four common IPv4 families, including loopback.
- No IPv6 or exhaustive IANA special-purpose classification.
- Does not verify ownership, route, interface, or reachability.
The entered network data is processed locally in this browser.
Frequently asked questions
Is 192.168.1.1 private?
Yes.
Is every 172.x.x.x address private?
No.
Does private mean secure?
No.
Does this check IPv6 private space?
No.