IP Addresses & Geolocation:
What Developers Should Know
IP addresses are the foundation of internet networking. From NAT to geolocation accuracy to practical debugging — understand the addresses that make the internet route packets.
What an IP Address Actually Is
An IP address is a unique numerical identifier assigned to every device connected to the internet. It serves two fundamental purposes: identifying the host (or more precisely, its network interface) and providing the destination address that routers use to forward packets across the internet. Every request your browser makes, every email your client sends, every video your streaming app buffers — all of it moves through the internet as packets labeled with source and destination IP addresses. Without IP, there's no routing. Without routing, there's no internet.
Two versions coexist today. IPv4 addresses look like 192.168.1.1 — four numbers from 0 to 255 separated by dots, providing about 4.3 billion (2³²) possible addresses. Designed in 1981 when the internet was a research project, IPv4's address space was exhausted at the global level by 2011. IPv6 addresses look like 2001:0db8:85a3:0000:0000:8a2e:0370:7334 — eight groups of four hexadecimal digits, providing roughly 340 undecillion (2¹²⁸) addresses. IPv6 adoption has been gradual — about 40-45% of global internet traffic uses IPv6 as of 2024 — but it's the future, and every modern network stack supports it.
Public vs. Private IPs and NAT
Your home router has a single public IP assigned by your ISP. Every device on your home WiFi — laptop, phone, smart TV, game console — gets a private IP from the router's DHCP server. These private IPs come from reserved ranges defined in RFC 1918: 192.168.0.0/16 (most home routers use 192.168.0.x or 192.168.1.x), 10.0.0.0/8 (common in corporate networks), and 172.16.0.0/12 (used by Docker by default). These addresses are not routable on the public internet.
When your laptop makes a request to a website, your router translates your private IP (192.168.1.5) to its public IP (203.0.113.42) using Network Address Translation (NAT). The router tracks the connection in a NAT table — source IP, source port, destination IP, destination port — so when the response comes back, it knows which internal device to forward it to. This is why every device on your home network appears to the outside world as the same IP: websites see your router's public IP, not your individual device IPs. Check your public IP with our My IP Address tool.
Static vs. Dynamic IPs
Most residential internet connections use dynamic IPs — your ISP can change your public IP at any time, typically when your modem reboots or the DHCP lease expires (usually every 24 hours to a few weeks). Business-grade connections often provide static IPs that never change, for an additional monthly fee. For hosting servers at home, you need either a static IP, or a dynamic DNS (DDNS) service that automatically updates your domain's A record whenever your IP changes. Services like DuckDNS, No-IP, and Dynu provide this for free or cheap.
IPv4 vs. IPv6
| IPv4 | IPv6 | |
|---|---|---|
| Format | 192.168.1.1 | 2001:db8::1 |
| Address size | 32 bits (4 bytes) | 128 bits (16 bytes) |
| Addresses | ~4.3 billion | ~340 undecillion |
| NAT required | Yes (shortage) | No (abundance) |
| Adoption | Universal | ~40-45% of traffic |
| Packet header | 20-60 bytes | 40 bytes (simpler) |
What IP Geolocation Reveals (and What It Doesn't)
IP addresses are allocated to ISPs in blocks by regional internet registries (ARIN for North America, RIPE for Europe, APNIC for Asia-Pacific, LACNIC for Latin America, AFRINIC for Africa). Commercial geolocation databases from companies like MaxMind and IP2Location map these allocated blocks to approximate physical locations. Accuracy varies dramatically: country identification is ~99% reliable at the ISP level; city identification is ~70-80% accurate; street-level or neighborhood-level lookups are essentially useless for most IPs. Mobile IPs are particularly unreliable — they often geolocate to the carrier's data center rather than the user's actual location. VPNs and proxies further reduce accuracy by routing traffic through different geographic locations.
For applications requiring precise location, use the browser's Geolocation API (with explicit user permission), which combines GPS, WiFi triangulation, and cell tower data — not IP lookup. IP geolocation is best used for coarse analytics (which countries are my users in?), fraud detection (is this purchase from the same country as the credit card?), and content localization (which language should I default to?). Our IP Lookup tool shows the approximate location, ISP, and timezone for any public IP.
Debugging IP Issues
"Users in a specific country can't access my site." Check whether you're using geo-blocking (via Cloudflare, AWS WAF, or server config). Look up the affected IPs to confirm their geolocation matches the blocked region. Geo-blocking databases go out of date; an IP range that was allocated to one country might have been reallocated to another. False positives are common with mobile carrier IPs that span regions.
"My firewall whitelist broke because my IP changed." If you're whitelisting IPs for SSH access, API authentication, or database connections, a dynamic IP will break the whitelist every time it changes. Switch to key-based or token-based authentication instead. If IP whitelisting is required, use a static IP from your ISP or a cloud-hosted jump box.
"Someone is attacking my server from this IP." Look up the IP to find the hosting provider or ISP. Most have an abuse contact (abuse@provider.com or a web form) where you can report malicious activity. Include timestamps in UTC, relevant log excerpts showing the attack pattern, and your server's IP. ISPs typically respond to abuse reports within 24-72 hours for clear-cut cases.
IP Addressing in Cloud Infrastructure
Cloud providers add layers of indirection between IP addresses and your actual servers. AWS Elastic IPs are static public IPv4 addresses that you can remap between instances — useful for failover and whitelisting. Load balancers (ALB, NLB) have their own IPs that may change; you access them via DNS name, not IP. Cloudflare and other CDNs sit in front of your origin, so visitors see Cloudflares IP, not yours. Understanding this chain — user → CDN → load balancer → instance → application — is essential for debugging connectivity issues. The IP the user connects to is rarely the IP of your actual server.
Private IP ranges in cloud VPCs (Virtual Private Clouds) are even more important than public IPs for security. Your database should have a private IP only, accessible from your application servers within the VPC but not from the public internet. Security groups and network ACLs filter traffic by IP and port. A common misconfiguration: opening a database port to 0.0.0.0/0 (all IPs) instead of restricting it to the VPCs CIDR block. Always apply the principle of least privilege to IP-based access rules.