Network

IP Address Converter

Paste an IPv4, IPv6, or IPv4-mapped IPv6 address, or just type a decimal integer, and the tool recognizes which one it is and lists every equivalent form at once: dotted decimal, integer, hexadecimal, binary, the compressed and fully expanded IPv6 forms, and the reverse DNS query name. It also tells you whether the address is public, private, loopback, link-local, or a documentation and reserved range. Detection and conversion run in the browser, so it fits reading integer IPs in logs, setting up reverse DNS, and reviewing firewall rules.

  • Auto-detects IPv4, IPv6, IPv4-mapped IPv6, and decimal integers, with a clear message when input is invalid
  • Lists dotted decimal, integer, hexadecimal, and binary for any IPv4 at once
  • Shows the RFC 5952 compressed form, the fully expanded form, the 128-bit integer, and hex for IPv6
  • Builds in-addr.arpa and ip6.arpa reverse DNS names ready for PTR records
  • Classifies public, private, loopback, link-local, unique local, documentation, and reserved addresses
tools/IP Address Converter

Accepts IPv4, IPv6, IPv4-mapped IPv6, and decimal integers. An integer up to 4294967295 is read as IPv4, larger values as IPv6.

Address properties

3 items
Detected type
IPv4
Scope
Private address
Publicly routable
No

All forms

6 items
Dotted decimal
192.168.1.1
Integer
3232235777
Hexadecimal
0xC0A80101
Binary
11000000.10101000.00000001.00000001
IPv4-mapped IPv6
::ffff:192.168.1.1
Reverse DNS
1.1.168.192.in-addr.arpa

Overview

Brings every form of a single IP address, and its classification, into one panel that updates as you type.

  1. 01

    Automatic type detection

    No mode to pick first. The tool reads the input and decides whether it is IPv4, IPv6, IPv4-mapped IPv6, or a decimal integer.

  2. 02

    IPv4 in every notation

    A single IPv4 shown as dotted decimal, integer, hexadecimal, and bitwise binary, so log and config notations all line up.

  3. 03

    IPv6 compressed and expanded

    The RFC 5952 compressed form alongside the eight-group expanded form, with the 128-bit integer and hexadecimal added.

  4. 04

    IPv4-mapped extraction

    Unwraps a mapped address like ::ffff:192.168.1.1 back to its IPv4, and also shows the mapped form of an IPv4.

  5. 05

    Reverse DNS names

    Generates the in-addr.arpa name for IPv4 and the ip6.arpa name for IPv6, ready to paste into a PTR record.

  6. 06

    Address classification

    Labels public, private, loopback, link-local, unique local, documentation, and reserved addresses, and notes whether each is publicly routable.

How to use

Enter an address or integer, and the detected type and every form update as you type.

  1. 01

    Paste an IPv4, IPv6, IPv4-mapped IPv6 address, or a decimal integer into the input box.

  2. 02

    Click one of the examples to try typical inputs without typing them by hand.

  3. 03

    Read the address properties first: detected type, scope, and whether it is publicly routable.

  4. 04

    Scroll through every form: integer, hexadecimal, binary, compressed and expanded IPv6, and the reverse DNS name.

  5. 05

    Copy the organized result into a ticket, change record, or DNS configuration.

Details

The same address raises different questions when you read logs, set up DNS, or review a firewall, so this tool keeps those views on one page.

  • Integer and hex forms show up in database fields, logs, and configs, and read better back as dotted decimal
  • The binary view exposes each bit, which helps explain subnet boundaries and address types
  • Compressed and expanded IPv6 side by side reduce mistakes when comparing configs or regex matches
  • IPv4-mapped extraction quickly reveals which IPv4 sits inside an IPv6 address
  • Reverse DNS names drop straight into a PTR record or a reverse-lookup investigation
  • Address classification separates public, private, loopback, and documentation ranges at a glance

Use cases

When an address needs a different notation, or you first have to confirm which address space it belongs to, a quick pass here is usually the shortcut.

  1. Read integer IPs in logs

    Some systems store IPs as integers or hex. Paste one in and get the familiar dotted decimal back.

  2. Set up reverse DNS

    Take the in-addr.arpa or ip6.arpa name straight into a PTR record instead of expanding nibbles by hand.

  3. Review firewalls and allowlists

    Confirm whether an address is public, private, or loopback before wiring an internal or reserved range into an external rule.

  4. Make sense of IPv6

    Move between the compressed and expanded forms to confirm two configs really name the same address.

  5. Handle IPv4-mapped addresses

    Pull a ::ffff: address out of a dual-stack service log and resolve it to the IPv4 it actually represents.

  6. Prepare changes and docs

    Paste every form and property of one address into a change record so reviewers all see the same facts.

See also

If you need the range and mask of a whole network rather than a single address, open the Subnet Calculator for CIDR subnet math. When the investigation also touches which port a service is exposed on, reach for the Port Reference to check the protocol and common use behind that port.

Best practices

A converted form is just one view of the facts. Whether you change a config from it still depends on the real network policy.

  • Normalize stored integer or hex IPs back to dotted decimal before comparing them, so notations do not get mixed up.
  • Before configuring a PTR record, confirm the reverse name maps to the exact address you mean to resolve.
  • When deciding public versus private, read the address together with the actual NAT and routing policy.
  • Pin one notation in docs and tickets, and prefer the RFC 5952 compressed form for IPv6.
  • For IPv4-mapped addresses, be explicit about whether the service treats them as IPv4 or IPv6.
  • Add address classification to a pre-release checklist as shared ground for review.

Limitations

This tool focuses on converting and classifying a single address. It does not scan the network or look up real DNS records for you.

  • Reverse DNS only builds the query name. It does not resolve or verify that a matching PTR record exists.
  • Classification follows published address-block assignments. Real reachability still depends on routing, NAT, and firewalls.
  • A decimal integer carries no type, so values up to 4294967295 are read as IPv4 and larger values as IPv6.
  • Whole-subnet math with a CIDR prefix lives elsewhere. Use the subnet calculator for that.
  • Invalid input returns a clear validation message rather than a guessed result.
  • It does not run end-to-end connectivity tests, so a correct conversion does not mean the address is reachable.

FAQ

Common questions about detection rules, conversions, edge cases, and how data is handled.

Why is an integer treated as an IP address?

A decimal integer has no type on its own. The tool reads an integer up to 4294967295 as IPv4, and a larger one up to 2 to the power of 128 minus one as IPv6.

What address is 3232235777?

It equals 192.168.1.1. Paste the integer in to see the matching dotted decimal, hexadecimal, and binary forms.

What is the range of an IPv4 integer?

IPv4 is a 32-bit address, so the integer range is 0 to 4294967295. Larger values are handled as an IPv6 integer or flagged as out of range.

What is the difference between compressed and expanded?

The compressed form follows RFC 5952 and shortens a run of zero groups to ::. The expanded form writes all eight groups, which is safer for comparison and regex matching.

How is ::ffff:192.168.1.1 handled?

It is an IPv4-mapped IPv6 address. The tool detects the embedded IPv4, resolves it to 192.168.1.1, and keeps the mapped form as well.

Can I use the reverse DNS name directly?

You can paste it into a PTR record. The tool only builds the name, though, so whether the record actually exists still has to be confirmed in DNS.

How is publicly routable decided?

It follows the address block the address sits in. Only ordinary public unicast is marked yes; private, loopback, link-local, documentation, and reserved ranges are marked no.

What is a documentation address?

These are blocks that RFCs reserve for documentation and examples, such as IPv4 192.0.2.0/24 and IPv6 2001:db8::/32, and they are never assigned to real hosts.

Does it support CIDR subnet math?

This tool handles a single address. For network and broadcast addresses and usable host ranges, use the subnet calculator.

Is my input sent to a server?

No. Detection and conversion run entirely in your browser, and the page does not send the address or integer you enter to any server.

Related tools

For the next step in network troubleshooting, the same set of tools can compute a whole subnet, look up port usage, or check the browser runtime.