Network Guide · Level 1: Foundations · Lesson 3 of 21
You land in a new city, open your banking app, and see: We noticed a login from a new location. Please verify it’s you. You never turned on GPS for the app. You never typed your city.
So how did the bank know? One answer is your IP address. IP addresses are among the simplest networking concepts—and one of the most misunderstood.
Short answer: An IP address is a numeric address that helps packets find devices on a network. Your phone usually has a private address inside your home, while your router or provider presents a public address to the internet. Your bank can see that public address and use geolocation data to estimate where the connection originates.
In Lesson 1: What Actually Happens When You Open Your Banking App?, we saw how your phone receives an address and how NAT translates private IPv4 addressing. In Lesson 2: The OSI and TCP/IP Models, Without the Memorization, we placed this responsibility at Layer 3, the Network layer.
An IP address gives the network a location, not your exact physical location.
Addresses in plain terms
Every device communicating over an IP network needs an IP address. An IP packet carries source and destination addresses, and routers use the destination to decide where to forward it.
A useful comparison: an IP address works like a mailing address. Part identifies the network—the neighborhood—and another part identifies the device within that network.
Now that you understand the purpose of an IP address, let’s look at its two main versions: IPv4 and IPv6.
IPv4: the address you already recognize
An IPv4 address is 32 bits long and is written as four numbers from 0 to 255, separated by dots. For example: 203.0.113.45.
IPv4 provides roughly 4.3 billion possible addresses. As the internet expanded, that address space became insufficient, so networks increasingly relied on private addressing and NAT.
Picture a growing city: imagine planning billions of house numbers, only to discover that almost everyone wants several connected devices. The numbering system eventually becomes crowded.
IPv4 has limited address space. What was designed to provide a much larger alternative?
IPv6: the address built to last
An IPv6 address is 128 bits long and uses hexadecimal groups separated by colons. For example: 2001:db8:85a3:0:0:8a2e:370:7334.
IPv6 provides approximately 3.4 × 1038 addresses. It also supports shortened notation, where consecutive zero groups can be compressed using ::.
Many networks use both IPv4 and IPv6 together, known as dual stack. Your phone may use IPv6 for one service and IPv4 for another.
| Feature | IPv4 | IPv6 |
|---|---|---|
| Address size | 32 bits | 128 bits |
| Written as | Four decimal numbers: 203.0.113.45 | Hexadecimal groups: 2001:db8::1 |
| Total addresses | About 4.3 billion | About 3.4 × 1038 |
| NAT needed? | Common at home | Not required for address conservation |
| Internal-use addressing | RFC 1918 private ranges | Unique local addresses |
| Configuration methods | DHCP | SLAAC or DHCPv6 |
The example addresses used here come from ranges reserved for documentation, not real networks.
IPv4 and IPv6 describe address formats. But the distinction you’ll use most often in everyday IT work is public versus private addressing.
Public versus private IP addresses
A public IP address is globally unique when publicly routed across the internet. A private IP address is reserved for internal networks and is not routed across the public internet.
That’s why thousands of homes can use addresses such as 192.168.1.x without conflicting with one another.
Here’s an everyday comparison: your private IP is an apartment number inside a building. Your public IP is the building’s street address.
Private addresses work inside. Public addresses face outside.
IPv4 address classes (A–E)
Before CIDR became standard, IPv4 addresses were organized into five historical classes, each with a different purpose and address range.
| Class | First octet | Address range | Default mask | Traditional purpose |
|---|---|---|---|---|
| Class A | 1–126 | 1.0.0.0 – 126.255.255.255 | /8 | Very large networks |
| Class B | 128–191 | 128.0.0.0 – 191.255.255.255 | /16 | Medium-sized networks |
| Class C | 192–223 | 192.0.0.0 – 223.255.255.255 | /24 | Small networks |
| Class D | 224–239 | 224.0.0.0 – 239.255.255.255 | Not applicable | Multicast |
| Class E | 240–255 | 240.0.0.0 – 255.255.255.255 | Not applicable | Reserved / experimental |
Picture the network sizes: Class A historically served very large networks, Class B medium-sized networks, and Class C smaller ones. Classes D and E had different special purposes.
Important: Classful addressing is historical. Modern networks use CIDR, allowing flexible network sizes such as /20, /24 and /27. An address class does not determine whether an address is public or private.
The three private IPv4 ranges
These three ranges are reserved for private networks under RFC 1918. They can be used in homes, offices, campuses and enterprise networks.
| Private range | Where you often see it |
|---|---|
| 10.0.0.0/8 | Large companies, campuses, enterprise networks |
| 172.16.0.0/12 | Medium-sized networks and cloud environments |
| 192.168.0.0/16 | Home and small-office networks |
These are common examples, not restrictions. A business can use 192.168.0.0/16, and a home lab can use 10.0.0.0/8, provided the network is planned correctly.
Other addresses worth recognizing
| Address | What it means |
|---|---|
| 127.0.0.1 | Loopback: refers to your own device. The entire 127.0.0.0/8 range is reserved for loopback. |
| 169.254.x.x | IPv4 link-local address, often automatically assigned when DHCP cannot provide an address. |
| 100.64.0.0–100.127.255.255 | Shared address space commonly used for carrier-grade NAT (CGNAT). |
| fe80::/10 | IPv6 link-local address range used for communication on the local network link. |
Your phone may use a private address, but your bank normally sees a public one. Who decides which public address you receive?
Who decides which public IP address you get?
Public addresses are distributed through a chain. Large address blocks go to regional internet registries, smaller blocks go to providers, and providers assign addresses to customers.
This allocation history helps associate public IP blocks with providers and broad geographic areas.
Consider the postal system: a postal authority assigns ZIP-code ranges to regions and smaller ranges to local delivery offices. The range gives you a clue about the area, not the exact house.
If address blocks are associated with providers and regions, how can your bank turn that information into a rough location?
How your bank estimates your location
Geolocation companies combine address-registration data, provider information and network observations to estimate where an IP block is being used. The result is an estimate, not GPS.
| Location level | Typical accuracy |
|---|---|
| Country | Usually very reliable |
| Region or city | Often useful, but can be wrong |
| Street or home | Not available from the IP address alone |
IP geolocation estimates your network location. It does not pinpoint your home.
Your provider may be able to associate an assigned public address with a customer account. The IP address itself does not contain your name or street address.
If geolocation is only an estimate, what can make that estimate inaccurate?
Why a public IP address can mislead
Mobile carriers may send traffic through infrastructure far from where you are standing, making your connection appear to come from another city. Carrier-grade NAT can also place many customers behind one public IPv4 address.
A VPN or proxy changes the public address the destination sees. Dynamic public addresses can also change over time, so a new IP alone does not prove that a different person logged in.
A new IP does not mean a new person. A familiar IP does not mean a safe person.
If an IP address cannot prove someone’s identity, why does your bank still use it?
What your bank actually does with the IP address
Your bank treats an IP address as one risk signal among many. It may compare it with previous logins, device information, VPN or proxy indicators, reputation data and user behavior.
A new address on a familiar device may look normal. A new address, a new device and an unusual location together may trigger extra verification.
Another signal is called impossible travel. If two logins appear from locations you could not realistically travel between in the available time, the pattern may look suspicious.
An IP address is a signal, not proof.
This brings us back to the opening message: the bank is not claiming your IP proves who you are. It is saying the login pattern looks different enough to verify.
Let’s put private and public addressing into one simple picture.
Simple diagram: private inside, public outside
INSIDE YOUR HOME YOUR ROUTER / PROVIDER THE BANK
+----------------+ +-------------------+ +------------------+
| Your phone | | NAT / public side | | Bank edge |
| 192.168.1.23 | ----> | 203.0.113.45 | ----> | sees |
| private IP | | public IP | | 203.0.113.45 |
+----------------+ +-------------------+ +---------+--------+
|
v
Geolocation lookup:
"This block is used
in this region"
In a typical IPv4 home NAT setup, the bank sees the public source address rather than your internal 192.168.1.23.
Put simply: the bank sees the building’s street address, not the apartment number your device uses inside.
Public addressing gives the bank useful context, but what are the security risks and limitations?
The risk angle: what IP addresses do and do not tell you
| Risk or limit | What it means | Where it matters |
|---|---|---|
| IP spoofing | An attacker forges a source address, making normal two-way communication difficult. | DDoS attacks |
| Location is not identity | An IP suggests where traffic originates, not who is using it. | Account security |
| Location mimicry | Fraudsters may use residential proxies near a target area. | Fraud detection |
| False alarms | Travel, VPNs, mobile networks and CGNAT can make legitimate logins look unusual. | Verification prompts |
| Shared reputation | Many users may share one public address under CGNAT. | Blocking and reputation |
| Exposed services | Internet-facing services may be scanned or probed. | Lessons 6, 11, 12 |
| Private-address conflicts | Duplicate or misconfigured addresses can break local connectivity. | Lessons 5 and 7 |
Three practical rules follow: treat IP geolocation as a hint, not authentication; knowing an IP address alone does not automatically compromise a device; and a VPN changes the public address remote services see.
Here’s another way to look at it: knowing someone’s street address tells you where the front door is. It doesn’t tell you whether the door is unlocked.
These concepts matter differently depending on your role in IT.
What this means for your IT role
| Role | Where this lesson matters | Focus on next |
|---|---|---|
| Help desk | Recognizing private addresses, 169.254 addresses and unexpected configurations | Lessons 4, 5 |
| Sysadmin | Planning address ranges, avoiding overlap and assigning server addresses | Lessons 5, 9 |
| Network engineer | IPv4/IPv6 coexistence, address planning and CGNAT | Lessons 9, 10, 11 |
| Security analyst | Using geolocation and reputation as signals while understanding their limits | Lessons 12, 13, 15 |
| Student | Understanding public/private and IPv4/IPv6 | Lesson 4 |
From an infrastructure perspective, the important thing is knowing what an IP address can tell you—and what it cannot.
Three takeaways
- An IP address is a network location, not an exact location on the map. Geolocation databases provide estimates.
- Private addresses stay inside; public addresses face the internet. NAT commonly translates private IPv4 traffic for internet access.
- An IP address is a signal, not proof. Banks combine it with device, reputation, location and behavior information.
Quick check
- Which is private:
172.20.4.9,203.0.113.45, or8.8.8.8? - Why can a bank estimate your city from an IP address but not your street?
- If your laptop shows
169.254.18.7, what probably happened?
Answers: (1) 172.20.4.9, because it belongs to the RFC 1918 private range. (2) Address blocks can be associated with providers and regions, but the IP address does not identify a specific home. (3) The device probably did not receive an IPv4 address through DHCP and assigned itself a link-local address.
Frequently asked questions
Can my bank see my exact location from my IP address?
No. An IP address usually provides a broad location estimate, such as a country, region or city. Precise phone location generally requires access to location services.
Does my IP address reveal who I am?
Not by itself. It can reveal information about your provider and approximate network location, but the address itself does not contain your name.
Why does my bank ask me to verify when I travel?
Your public IP may appear in a different region. Combined with other signals, that change can trigger extra verification.
What is the difference between a public and private IP address?
A public address is used across the internet. A private address is used inside an internal network and typically reaches the internet through NAT in an IPv4 home setup.
What is 192.168.1.1?
It is a private IPv4 address commonly used by home routers. It is often the default gateway and may also open the router’s management page.
Why does my public IP address change?
Many residential connections use dynamic addressing, so your provider may assign a different public address over time.
Does a VPN hide my IP address from my bank?
It replaces the public address your bank sees with the VPN server’s address. Your login may therefore appear to originate from the VPN server’s location.
Is IPv6 more secure than IPv4?
Not automatically. IPv6 removes the need for address-conservation NAT, but proper firewalling and security controls are still required.
Key terms I introduced
IP address, IPv4, IPv6, dual stack, public address, private address, RFC 1918, loopback, link-local address, CGNAT, regional registry, geolocation, impossible travel, IP spoofing and IP reputation.
Next lesson
Lesson 4: DNS: The Phone Book Attackers Love to Forge.
Your IP address identifies the destination, but how does your phone find that address from a website name? Next, we’ll explore DNS and how attackers manipulate those lookups.
Think back to the opening: you land in a new city, open your banking app, and the bank asks you to verify your login. It noticed a change in your network context—not your exact physical location.
An IP address gives context, not certainty.
Use IP addresses as evidence, not proof of identity.
Related reading on US WealthTech
If you want to explore the security side of banking technology, read Is it safe to link bank accounts?, Is Face ID Safe for Banking?, and Are Your Browser Extensions Safe for Banking?.