Skip to main content
IPAddressLookup.in

IP Address Format Converter

Convert any IPv4 or IPv6 address into canonical RFC 5952 compressed form, full 128-bit expanded hexadecimal, unsigned decimal integer, hexadecimal literal, grouped and continuous binary, and reverse ARPA pointer notation.

Sample inputs:

Synchronized Address Representations · IPv4

49.44.0.1

Canonical Normalized Representation

49.44.0.1

Standard dotted-decimal

Zero-Padded Dotted-Decimal

049.044.000.001

3 digits per octet

Unsigned 32-Bit Decimal Integer

824967169

Network byte order (Big-Endian, RFC 1700): most significant octet transmitted first.

Hexadecimal Integer Literal

0x312C0001

8 hex nibbles in Big-Endian network byte order

Grouped Binary Representation

00110001.00101100.00000000.00000001

4 groups of 8 bits

Continuous Bitstream

00110001001011000000000000000001

32 contiguous bits

Reverse DNS Zone Pointer (ARPA)

1.0.44.49.in-addr.arpa

in-addr.arpa reversed octets

IPv4-Mapped IPv6 Address (RFC 4291)

::ffff:49.44.0.1 (or ::ffff:312c:1)

Used by dual-stack sockets to represent IPv4 peers in 128-bit structures

6to4 Prefix Notation (RFC 3056)

2002:312c:0001::/48

Embeds the 32-bit IPv4 address after the 2002::/16 prefix

How Network Byte Order (Big-Endian) Integer Conversion Works

To routers, operating system kernels, and database indexes, an IPv4 address is simply an unsigned 32-bit integer and an IPv6 address is an unsigned 128-bit integer transmitted in Big-Endian network byte order (RFC 1700). For an IPv4 address with octets A.B.C.D, the 32-bit integer value is computed as:

Integer = (A × 256³) + (B × 256²) + (C × 256¹) + D = (A << 24) | (B << 16) | (C << 8) | D

For example, 192.168.1.1 evaluates to (192 × 16,777,216) + (168 × 65,536) + (1 × 256) + 1 = 3,232,235,777 (or 0xC0A80101 in hexadecimal). Compare protocol structures in IPv4 vs IPv6.

RFC 5952 IPv6 Canonicalization Rules

  • Hexadecimal digits a–f must always be rendered in lowercase.
  • Leading zeros within each 16-bit field must be suppressed (0200 becomes 200), leaving at least one digit per field.
  • The symbol :: shortens the single longest run of consecutive all-zero 16-bit fields (and is never used to shorten a single zero field).

Technical Specifications & Protocol Facts

Authoritative parameters, dimensions, and IETF RFC compliance

Parameter / DimensionTechnical SpecificationStandard / Authority
Canonical Document ScopeIP Address Converter — Route /ip-converterIPAddressLookup.in Technical Reference
Supported Address FamiliesIPv4 (32-bit dotted-decimal) & IPv6 (128-bit hexadecimal)RFC 791 / RFC 8200 / RFC 5952
Authoritative Registration ProtocolRegistration Data Access Protocol (RDAP) via IANA BootstrapRFC 7480–7484 / RFC 9224
Special-Purpose Range ClassificationPrivate LAN (RFC 1918), Shared CGNAT 100.64.0.0/10 (RFC 6598), ULA (RFC 4193)RFC 6890 IANA Registry

Frequently Asked Questions

Concise answers verified against IANA, APNIC, and IETF protocol standards

What is the primary purpose of IP Address Converter?

Convert IPv4 and IPv6 addresses across canonical, expanded, decimal integer, hexadecimal, binary, and reverse ARPA forms. Every output on IPAddressLookup.in follows IETF RFC standards and cites primary RIR/IANA sources.

Are IP and network queries on this page logged or shared with advertisers?

No. IPAddressLookup.in operates on a strict data-minimization model with stateless query execution, short-lived caching (15 minutes max for upstream RDAP/DNS), and zero persistent user lookup history.

How often is the technical documentation on IPAddressLookup.in reviewed?

All protocol calculators, RFC citations, and Indian telecom notes are verified by the 2026-11-01 editorial and engineering review cycle.

Contextual utilities and reference documentation verified for this workflow

IP Converter · Canonical: https://ipaddresslookup.in/ip-converter · Reviewed: 2026-11-01

Reviewer: IPAddressLookup.in Technical Network Utility Group · Stateless Privacy · Accuracy & Data Limits