What is an IP address?

Every device that talks to the internet needs a way to be found. This is it.

The short answer

An IP address is the number that identifies your device on a network, the way a street address identifies a building. When you load a page, your request has to carry a return address, or the answer has nowhere to go. IP stands for Internet Protocol, the set of rules that says how those numbers are written and how traffic carrying them gets moved along.

If you came here because something asked you for "your IP address," the number you almost certainly want is the one at the top of our front page. That is your public address, the one the rest of the internet sees.

In a hurry?

Copy the IPv4 line. It looks like 203.0.113.42, four numbers with dots between them. Almost everything that asks for "your IP" wants that one. If you also see a longer address full of colons, that is IPv6, and you only need it if you were specifically asked for it.

You have two addresses, and they are not interchangeable

This is the single most common source of confusion, and it trips up experienced people as often as newcomers. Your device has a private address on your own network, and your household or office shares one public address out on the internet.

Your router sits between the two and performs a translation called NAT. Traffic leaving the house gets its private return address swapped for the public one, and replies get swapped back on the way in. Your laptop, your phone, and your TV all swim under the same flag as far as the outside world is concerned.

How private addresses share one public address Three devices on a home network hold private 192.168.1.x addresses. The router performs network address translation, so every one of them reaches the internet using the single public address the ISP assigned. Your home network (private) Laptop 192.168.1.14 Phone 192.168.1.22 Smart TV 192.168.1.37 Router doing NAT one shared exit What the internet sees 203.0.113.42 This is the number IP Narwhal shows you. Every device above shares it. Private ranges are reserved and unroutable: 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16.
Three devices, three private addresses, one public address. If you look up your address on a phone and then on a laptop connected to the same Wi-Fi, you get the same answer, because you are reading the address of the exit and not of the device.

That is why an address starting with 192.168. or 10. is not the number a game server, a camera app, or a vendor allowlist is asking for. Those ranges are reserved for private use and are not routable on the public internet. Full detail lives in Public IP vs Private IP.

What the number actually says

An IPv4 address is a 32-bit number. Writing 32 ones and zeros would be miserable, so it is split into four 8-bit chunks called octets, each written in decimal and separated by dots.

Anatomy of an IPv4 address The address 192.168.1.1 split into four octets. Each octet is eight bits, holding a value from 0 to 255, and the four together make 32 bits. 192.168.1.1, one octet at a time 192 168 1 1 . . . 11000000 10101000 00000001 00000001 8 bits 8 bits 8 bits 8 bits 32 bits in total 2 to the power of 32, which is 4,294,967,296 possible addresses Each octet holds 0 through 255, so 256.1.1.1 is not a valid address.
Each octet holds a value from 0 to 255, because eight bits cannot count higher. This is why an address like 192.168.300.1 is invalid on sight, and it is a useful thing to be able to spot when reading a config file.

Those 32 bits allow a little over 4.3 billion addresses, which felt limitless in 1981 and stopped being enough about twenty years later. The replacement, IPv6, uses 128 bits instead. The difference is far larger than it sounds.

IPv4 and IPv6 address space compared IPv4 holds about 4.3 billion addresses. IPv6 holds about 340 undecillion, a number so much larger that the IPv4 pool is not visible at the same scale. IPv4 32 bits 4,294,967,296 addresses. At this scale that bar is 4 pixels wide. IPv6 128 bits 340,282,366,920,938,463,463,374,607,431,768,211,456 addresses. To draw this bar to the same scale as the one above, it would need to stretch far past the moon. The teal sliver at its left edge is all of IPv4. Put another way IPv6 could give every grain of sand on Earth its own address and barely notice the dent.
Adding 96 bits does not make the pool three times bigger. It multiplies it by roughly 79 octillion, which is why IPv6 was designed to never need a successor for address exhaustion alone.

How a request actually finds its way

There is no master map of the internet. No single machine knows the full route from your couch to a server in Virginia. Each device along the way knows only one thing: which neighbor to hand the packet to next in order to get it closer.

The hops a packet takes A packet leaves your device, passes through your router, your internet service provider, and several backbone networks, then arrives at the destination server. Each hop reads only the destination address and forwards it onward. Nobody plans the whole route. Each hop just knows the next one. You Router ISP Backbone networks Destination server private public many hops What every hop reads The destination address, and nothing else it does not need. Routers do not open the payload, and no single one of them knows the full path from end to end.
Routers read the destination address, consult a table of which direction that range lives in, and forward. The path is assembled hop by hop, and two packets in the same conversation can take different routes.

This is why the internet survives damage. If a link goes down, the neighbors update their tables and traffic reroutes around the gap without anyone rewriting a master plan. It is also why latency varies: you are at the mercy of a chain of independent decisions, not a reserved lane.

Where addresses come from

Addresses are not first come, first served. They are handed down through a hierarchy, which is worth understanding because it is also the reason IP geolocation works at all.

LevelWhoWhat they hand out
GlobalIANAVery large blocks, to the five regional registries
RegionalThe five RIRs: ARIN, RIPE NCC, APNIC, LACNIC, AFRINICSmaller blocks, to internet service providers and large organizations
LocalYour ISPA single address, or a small block, to your connection
Your networkYour router, using DHCPPrivate addresses to each device in the house

Each of those handoffs is recorded. That public record is the backbone of IP geolocation: a database can look up which provider holds your block and where that provider operates, which is how a website guesses your city without ever asking your permission.

What your address does and does not reveal

People tend to be told one of two wrong things about this: that an IP address is meaningless, or that it is a home address. Neither is right.

What it generally does reveal

What it does not reveal

About the map on our front page

The pin is an estimate derived from a database, not a fix on your device. On mobile networks it can land in a different state, because the address may belong to a carrier gateway hundreds of miles from you. If it looks wrong, it probably is, and there is a specific reason why.

Three things people get wrong

"My IP address is permanent"

Most residential connections get a dynamic address that can change after a reboot, an outage, or a lease expiry. If you gave a vendor your address for an allowlist, it may quietly stop working in a week. Why Does My IP Change? covers what triggers it and what to do instead.

"Changing my IP makes me anonymous"

An address is one identifier among many. Cookies, browser fingerprints, and account logins all persist across an address change. Changing the number is a much smaller move than most people assume.

"The number on my computer is my IP"

If it starts with 192.168., 10., or 172.16. through 172.31., that is your private address. Useful for reaching a printer, useless for anything outside your network.

Where to swim next

Pick the current that matches your question.