If you have ever wondered how to check the address your own device uses on a network, a clear ipv4 ip address example is the best place to start. An IPv4 address is a numeric label assigned to your own computer, phone, tablet, or router so that other devices on the same network can find it and send information back to it. It is not a name, a password, or a personal record. It is simply a routing label, written as four numbers separated by dots, and learning to read one takes only a few minutes. This guide focuses only on finding and understanding your own address, on your own device, on your own connection.
Every ipv4 ip address example follows the same basic pattern, and once you recognise that pattern, the numbers stop looking random. The four groups are called octets, and each octet can range from 0 to 255. That range comes from the way computers store each group as eight bits, which gives 256 possible values. Put four octets together and you get an address such as 192.0.2.10, a standard documentation address used in guides because it is reserved for examples and is not assigned to a real home or business. Reading it from left to right tells you which network block it belongs to, and reading the whole string tells you the specific device address inside that block.
This article walks through what an IPv4 address looks like, how to find your own address on your own device, how to tell a private home-network address from a public internet address, and what to do when the numbers do not look right. You will not need any special software, and you will not need to look up anyone else. Everything here is about your own equipment, your own home network, and your own connection settings.
Working through an ipv4 ip address example on your own device makes the next ipv4 ip address example you meet much easier to recognise.
What an ipv4 ip address example Shows
An ipv4 ip address example shows four decimal numbers separated by three dots, and each number sits between 0 and 255. The address 192.0.2.10 is a good illustration because it is short, clear, and easy to break apart. The first number, 192, is the first octet. The second number, 0, is the second octet. The third number, 2, is the third octet. The fourth number, 10, is the fourth octet. Together, the four octets form one complete address, and no octet can be left out or the address will not work.
The dotted-decimal style was chosen because it is easier for people to read than the long string of ones and zeros that computers use underneath. Behind the scenes, each octet is eight binary digits, so the full address is 32 bits long. That is why IPv4 is described as a 32-bit system. With 32 bits, there are roughly 4.3 billion possible addresses, which once sounded enormous. As phones, laptops, smart televisions, and countless other devices came online, that pool began to feel tight, which is one reason newer systems were developed. For everyday home use, however, IPv4 remains the format most people still see on their own devices.
When you look at an ipv4 ip address example, try not to treat it as a secret code. Think of it like a house number on a street. The earlier numbers narrow down the area, and the later numbers narrow down the individual property. A network works in a similar way. The earlier octets often identify the network, while the later octets identify the device on that network. The exact split depends on the subnet mask, a setting that tells the device where the network part ends and the device part begins, but for a first reading, the street-and-house comparison is a helpful starting point.
The quickest way to learn is to copy an ipv4 ip address example by hand, check each octet, and then compare it with a second ipv4 ip address example.
How to Find Your Own IPv4 Address
Finding your own address is a settings task, not a search task, and the steps are similar on most devices. On a Windows computer, open Settings, go to Network and Internet, choose the connection you are using, and look at its properties. Your IPv4 address will be listed there, usually beside a label that says IPv4 address. On a Mac, open System Settings, choose Network, select your active connection, and look at the details panel. On a phone, open Settings, go to Wi-Fi, tap the network you are connected to, and look for the IP address field. In each case, you are viewing information about your own device only.
Another way to see your own address is through your router. When your device joins a home Wi-Fi network, the router gives it a local address so it can communicate with other devices in the home. Your router’s own admin page, reached from a browser on your own home network, usually lists connected devices and their local addresses. If you open that page, check only your own device entry. There is no need to open, copy, or share details for other devices in the household, and this guide does not ask you to do so.
If the address field is blank, or if it shows a string starting with 169.254, your device may not have received an address from the network yet. That range is used when a device assigns itself an address because it could not reach the router or the network service that hands out addresses. The usual fix is simple and local: check that Wi-Fi is switched on, move closer to the router if the signal is weak, disconnect and reconnect to your own network, and restart your own device if needed. If the problem continues, restarting your own router is the next sensible step, because it refreshes the local addresses for your own home.
Once you can read an ipv4 ip address example, the difference between a private ipv4 ip address example and a public one becomes clear.
Reading an ipv4 ip address example Step by Step
Take the address 203.0.113.25, another reserved documentation address that is safe to use in guides. Start by counting the dots. There should be exactly three. Then split the address into its four parts: 203, 0, 113, and 25. Check each part in turn. Is it a whole number? Is it between 0 and 255? If the answer to both questions is yes for all four parts, the format is valid. If any part is above 255, contains a letter, or is missing, the address is not a valid IPv4 address, and it has probably been mistyped.
Next, look for clues about what kind of address it is. Addresses beginning with 10, or with 172.16 through 172.31, or with 192.168, are private addresses. These are used inside homes and offices and are not directly reachable from the wider internet. An address such as 192.168.1.20 is a typical private address for a device on a home network. By contrast, a public address is the address your internet provider assigns to your home connection as a whole, and it is the address the wider internet sees. Your device’s private address and your connection’s public address are different numbers, and both are normal.
A common source of confusion is the difference between an IPv4 address and a subnet mask. The subnet mask looks like an address, for example 255.255.255.0, but it is not a device address. It is a filter that shows which part of the address identifies the network. Similarly, a gateway address, often 192.168.1.1 on a home network, is the address of your own router, the device that forwards traffic between your home network and the internet. Knowing these three labels, address, mask, and gateway, makes your own network settings much easier to understand at a glance.
A table of ranges is easier to use when you test each row against a real ipv4 ip address example, then against another ipv4 ip address example from the same range.
Private and Public Addresses Explained
Private addresses exist so that millions of homes can reuse the same local numbers without clashing. Your neighbour’s home network may also use 192.168.1.20 for one of its devices, and that causes no problem, because each private address only has meaning inside its own home network. Your router keeps track of which local device asked for which piece of internet traffic, and it directs the replies back to the right device. This system, called network address translation, is why a whole household can share a single public address.
Public addresses, by contrast, must be unique on the internet at any given moment. Your internet provider manages a pool of public addresses and assigns one to your connection, sometimes for a long period and sometimes for a shorter session. If you restart your router, you may receive a different public address next time, and that is normal. It does not mean your account has changed or your device has broken. It simply means the provider handed your connection a different label from its pool.
For privacy, it is wise to treat your own public address the way you would treat any connection detail: useful for troubleshooting your own setup, but not something to post publicly or share casually. You do not need to hide your private home-network address from yourself, since it only works inside your own home, but sharing screenshots of your full network settings online is still a bad habit. Crop or cover the numbers before posting any screenshot, and keep troubleshooting notes to your own device and your own connection.
If a setting looks wrong, compare it with a known-good ipv4 ip address example before changing anything, and keep that ipv4 ip address example handy while you test.
Common IPv4 Address Ranges and What They Mean
A table makes the main ranges easier to remember, because the same patterns come up again and again in home settings. The table below uses only generic and documentation ranges, so you can study the pattern without worrying about real-world assignments.
| Range | Type | What it usually means |
|---|---|---|
| 10.0.0.0 to 10.255.255.255 | Private | Large home or office networks |
| 172.16.0.0 to 172.31.255.255 | Private | Medium-sized private networks |
| 192.168.0.0 to 192.168.255.255 | Private | Typical home Wi-Fi networks |
| 192.0.2.0 to 192.0.2.255 | Documentation | Reserved for examples and guides |
| 203.0.113.0 to 203.0.113.255 | Documentation | Reserved for examples and guides |
| 169.254.0.0 to 169.254.255.255 | Link-local | Device could not get an address from the network |
| 127.0.0.1 | Loopback | Refers to your own device itself |
The loopback address deserves a special note because it often surprises beginners. When software on your own computer connects to 127.0.0.1, it is connecting to the same computer, not to another machine somewhere else. Developers and testers use it to check programs locally before they ever touch a network. If you see it in your own settings, it is not an error and it is not a stranger’s address. It is simply your own device talking to itself.
Another range worth recognising is the documentation range. Addresses such as 192.0.2.10, 198.51.100.20, and 203.0.113.25 are set aside purely so that books, guides, and training material can show a realistic-looking ipv4 ip address example without pointing at a real user. Whenever you see one of those three blocks in a tutorial, you can be confident it is an illustration, not a live destination. That is good practice for your own notes too: use a documentation address whenever you write down an example.
Even when a device shows both systems, an ipv4 ip address example remains the easiest ipv4 ip address example to read at a glance.
Troubleshooting Your Own IPv4 Address
Most home IPv4 problems fall into a small set of patterns, and each one points to a local fix. If your device shows no address at all, the connection itself is the first suspect. Check that Wi-Fi is on, that you are joined to your own network rather than a neighbouring open network, and that the router is powered on with its normal lights showing. If you are using a cable, check that it clicks firmly into both the device and the router, and try a different cable or port if one is available.
If your device shows a 169.254 address, it is telling you that it asked for an address and heard nothing back. Restarting your own device clears its old network request, and restarting your own router refreshes the service that hands out addresses. Wait a couple of minutes after the router restarts before checking again, because routers take time to come fully back online. If several of your own devices show the same problem at once, the router or the connection to your provider is the likelier cause than any single device.
If your device has an address but pages will not load, check the gateway and DNS settings on your own device. The gateway should point to your own router, and the DNS setting tells your device how to turn names into addresses. Switching your own device temporarily to automatic settings often clears a mistyped manual entry. If automatic settings work and manual settings do not, the manual entry is where the error lives. Write down the working automatic values before changing anything else, so you can always return to a known good state.
For readers who want a broader grounding in how networks are named and described, a related guide to another name for a network explains the everyday vocabulary around connections, while a guide to how to find an IP address on a Mac walks through the same own-device check on that system in more detail. Both are useful follow-ups once the basic pattern in this guide feels familiar.
Before the questions below, remember that every ipv4 ip address example in this guide uses a documentation range, so no ipv4 ip address example here points to a real home.
IPv4 Versus IPv6 in Plain Language
IPv6 is the newer addressing system, built because the IPv4 pool is limited. An IPv6 address is much longer, uses hexadecimal characters and colons instead of four decimal octets, and offers a vastly larger pool of addresses. Many modern devices and connections support both systems at once, which is why your own device settings may show an IPv4 address and an IPv6 address side by side. Seeing both is normal, and neither one replaces the other overnight.
For everyday home use, IPv4 is still the format most people recognise, and it is the format most home routers display most prominently. If a support article asks for your IP address and does not specify a version, it usually means the IPv4 address. If you are ever unsure which one to share with your own provider’s support team, share only the details they ask for, through their official support channel, and only for your own connection. Never share connection details in a public forum or comment thread.
One more practical point is that an ipv4 ip address example can look slightly different depending on where you view it. A router page may show the address with its subnet mask beside it, a phone may show it alone, and a computer’s detailed network view may add gateway and DNS entries underneath. These are the same address in different layouts. As long as the four octets match, you are looking at the same label, and the extra fields are simply helpful context rather than a different address.
Keep one trusted ipv4 ip address example in your notes, and every new ipv4 ip address example you encounter will be quicker to check.
Frequently Asked Questions
What is a simple ipv4 ip address example?
A simple ipv4 ip address example is 192.0.2.10. It has four octets, three dots, and every octet falls between 0 and 255. It belongs to a documentation range reserved for guides, so it is ideal for learning the pattern without referring to a real connection.
How do I find my own IPv4 address?
Open the network settings on your own device and look for the IPv4 address field for your active connection. On a computer, this sits in the connection properties. On a phone, it sits in the Wi-Fi network details. You are viewing your own device’s local address.
Why does my home address start with 192.168?
Addresses starting with 192.168 are private addresses for home and small office networks. They work inside your own home only, and your router translates them when your devices reach the wider internet. Seeing one is normal and expected.
What does a 169.254 address mean?
A 169.254 address usually means your device could not obtain an address from your own network. Reconnect to your own Wi-Fi, restart your own device, and restart your own router if needed, then check the address again.
Is my public address the same as my private address?
No. Your private address identifies your device inside your home network, while your public address identifies your whole home connection to the internet. Both are assigned automatically in most homes, and both can change over time.
Conclusion
An IPv4 address is far less mysterious once you can read its four parts. An ipv4 ip address example such as 192.0.2.10 shows the whole system in miniature: four octets, three dots, and a range of 0 to 255 for each group. From there, you can find your own address in your own device settings, recognise a private home address, spot a documentation example, and understand why a 169.254 address means your device is still waiting for a proper assignment. Keep the focus on your own device and your own connection, use documentation addresses in your own notes and examples, and treat your real connection details as private troubleshooting information rather than something to share. With that habit in place, checking your own IPv4 address becomes a quick, confident, and completely routine task.
