User Rating 0.0 ★★★★★

Total Usage 1 times

Category Network Utilities

Target Address / CIDR

Supports IPv4, IPv6, and CIDR Notation (e.g. /24)

Address Identity Unknown

---

--- • ---

Network & Routing (CIDR)

Network Address ---

Broadcast Address ---

Netmask ---

Wildcard Mask ---

Usable Hosts ---

IP Class (Hist.) ---

IANA Registry & Compliance

Allocation Block Checking...

Designation ---

RFC Reference ---

Regional Registry (RIR) ---

Bitwise Visualization & Translation

Network Bits Host Bits

---

Integer (Decimal) ---

Hexadecimal ---

Reverse DNS (PTR) ---

IPv6 Expanded/Compressed ---

Is this tool helpful?

Your feedback helps us improve.

★ ★ ★ ★ ★

About

In network engineering, ambiguity is the enemy of security. This tool provides a deterministic, RFC-compliant analysis of IPv4 and IPv6 addresses. Unlike basic geolocation lookups, this system dissects the packet-level structure of an IP address, revealing its binary composition, subnet allocation, and routing status.

We solve the specific problem of Contextual Identification. Knowing an IP is "10.0.0.1" is insufficient; knowing it is a Class A Private Network address (RFC 1918) with a specific binary bitmask allows engineers to configure firewalls and routing tables correctly. Errors in identifying Link-Local, Carrier-Grade NAT, or Documentation ranges often lead to routing loops or security breaches. This tool integrates the full IANA Special-Purpose Registry to flag reserved blocks instantly.

Formulas

The core of IP analysis relies on bitwise logic. For an IPv4 address IP and a subnet mask Mask, the Network Address is calculated using the bitwise AND operator:

Network = IP ∧ Mask

The Broadcast Address is derived by inverting the mask (NOT operator) and applying a bitwise OR with the Network Address:

Broadcast = Network ∨ (¬Mask)

To convert an IPv4 address to its 32-bit Integer representation (used in database storage), we sum the octets shifted by powers of 8 (where O represents an octet):

Integer = (O₁ << 24) + (O₂ << 16) + (O₃ << 8) + O₄

Reference Data

CIDR Block	Designation	RFC Standard	Usage Context	Routing Scope
0.0.0.0/8	Current Network	RFC 1122	Source address for hosts on this network	Local
10.0.0.0/8	Private-Use	RFC 1918	Internal Enterprise Networks	Private
100.64.0.0/10	Shared Address (CGN)	RFC 6598	ISP Carrier-Grade NAT	Private
127.0.0.0/8	Loopback	RFC 1122	Host self-communication	Host
169.254.0.0/16	Link Local	RFC 3927	Auto-configuration (APIPA)	Link
172.16.0.0/12	Private-Use	RFC 1918	Internal Networks (Class B)	Private
192.0.0.0/24	IETF Protocol	RFC 6890	Special IETF assignments	Varied
192.0.2.0/24	TEST-NET-1	RFC 5737	Documentation & Examples	Nowhere
192.168.0.0/16	Private-Use	RFC 1918	SOHO Networks (Class C)	Private
198.18.0.0/15	Benchmarking	RFC 2544	Inter-device benchmark testing	Private
224.0.0.0/4	Multicast	RFC 1112	One-to-Many communication	Global/Local
240.0.0.0/4	Reserved	RFC 1112	Future Use (Class E)	Reserved
::1/128	IPv6 Loopback	RFC 4291	Host self-communication	Host
fe80::/10	IPv6 Link-Local	RFC 4291	Single link communication	Link
fc00::/7	Unique Local (ULA)	RFC 4193	Local IPv6 Intranets	Private

Frequently Asked Questions

Private IPs (RFC 1918) are used for local networks and are routable within an organization but not on the internet. Link-Local IPs (169.254.x.x or fe80::) are only valid on the specific physical network segment (link) they are assigned to. Routers explicitly do not forward Link-Local traffic, whereas Private IPs can be routed internally across subnets.

A Wildcard Mask is the bitwise inverse of a Subnet Mask. It is heavily used in Cisco IOS and other firewall configurations (ACLs) to define which parts of an IP address must match. For example, a subnet mask of 255.255.255.0 corresponds to a wildcard mask of 0.0.0.255.

IPv6 addresses are 128-bit, often containing long strings of zeros. Rules allow: 1) Removing leading zeros in each 16-bit block (hextet). 2) Replacing the longest consecutive group of zero blocks with a double colon (::). This can only be done once per address to maintain uniqueness.

Bogon space includes IP blocks that are not yet allocated by IANA/RIRs or are reserved for special use. Seeing traffic from a Bogon IP on a public interface usually indicates spoofing (DDoS attacks) or severe misconfiguration, as these addresses should not be routable on the public internet.

Yes. A /32 network has 1 IP (used for loopbacks or single-host routes). A /31 network technically has 2 IPs and no broadcast/network address; it is often used for Point-to-Point links to conserve address space (RFC 3021).