Pacific Blue Software Logo

Your External Visibility

Your External Visibility Information

This page shows your public IP address and browser/connection details visible to websites you visit.

Public IP Address:
216.73.217.18 (IPv4)

Address Details:
• Address type: Public - reachable across the Internet
• Binary: 11011000.01001001.11011001.00010010
• Hexadecimal: 0xD849D912
• 32-bit integer: 3628718354

Network Prefix Example:
If your address is part of a /24 network, the first 24 bits (216.73.217) identify the network and the last 8 bits (18) identify your connection within it, giving a range of 216.73.217.0 to 216.73.217.255. The real prefix size is set by your provider and cannot be worked out from the address alone.

Browser & Platform Details:
Full User Agent:
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)

Detected Information:
• Browser: Unknown
• Operating System: Unknown
• Device Type: Desktop

Connection Information:
• Protocol: HTTPS (Secure)
• Port: 443
• Request Method: GET

The Address You Requested:
• Scheme: https
• Host: pacificblue.software
• Port: 443
• Path: /whatsmyip
• Query: (none)
• Fragment: not sent to the server (see below)

Browser Preferences:
• Accepted Languages: Not specified
• Accepted Encoding: gzip, br, zstd, deflate
• Do Not Track (DNT): Not enabled

Note: This information is publicly visible to any website you visit. Using a VPN or proxy will show the VPN/proxy IP address instead of your actual IP.

Understanding Your IP Address

What Is an IP Address?

An IP address is the number that identifies a device on a network so that data can be delivered to it. Every request your browser makes carries your address, so the web server knows where to send the reply. That is why every website you visit can see the address shown above.

Public and Private IP Addresses

Your home or office router usually has one public address on the Internet. The devices behind it are given private addresses from ranges reserved for local networks:

10.0.0.0    - 10.255.255.255   (10.0.0.0/8)
172.16.0.0  - 172.31.255.255   (172.16.0.0/12)
192.168.0.0 - 192.168.255.255  (192.168.0.0/16)

Private addresses are never routed across the Internet. Your router uses Network Address Translation (NAT) to share its public address between all of your devices, which is why this page shows the router's public address and not the address of your computer.

Carrier-Grade NAT (CGNAT)

There are not enough IPv4 addresses for every customer to have one, so many mobile networks and some broadband providers share a single public address between many customers. Your router is given an address from the shared range 100.64.0.0/10, and the provider's equipment translates it to a public address that other customers also use.

Behind CGNAT you cannot forward ports to host a server or game from home, and a block placed on the shared address affects everyone using it. To check, compare the WAN or Internet address shown in your router with the address on this page. If the router shows an address from 100.64.0.0 to 100.127.255.255, you are behind CGNAT.

IPv4 and IPv6

An IPv4 address is 32 bits, written as four numbers from 0 to 255 separated by dots. That allows about 4.3 billion addresses, which have run out. An IPv6 address is 128 bits, written as eight groups of four hexadecimal digits separated by colons. Leading zeros in a group can be dropped, and one run of all-zero groups can be replaced with ::, so these are the same address:

2001:0db8:0000:0000:0000:0000:0000:0001
2001:db8::1

If your connection supports both, your browser will usually use IPv6, so this page may show either kind of address.

A Short History of the IP Address

The Internet Protocol grew out of ARPANET, the research network funded by the US Department of Defense. In 1974 Vint Cerf and Bob Kahn published the design that split the job in two: TCP to deliver data reliably, and IP to route each packet by address. IPv4 as we know it was fixed in RFC 791 in September 1981, and on 1 January 1983 ARPANET switched over to it in a single day. The 32-bit address was chosen for a network of a few hundred machines; four billion addresses looked like more than anyone could use.

The first addresses were handed out in classes. The first number of the address told you whether it was a Class A network with 16 million addresses, a Class B with 65,536 or a Class C with 256. Universities and companies were given whole Class A blocks, and much of the space went to a few hundred organisations before the public Internet existed. By the early 1990s the waste was obvious, and three fixes arrived in quick succession: CIDR in 1993 let networks be any size, NAT in 1994 let many devices share one address, and the private ranges above were set aside in 1996 so that sharing did not need globally unique addresses at all.

Those fixes bought twenty years. The central pool run by IANA gave out its last blocks on 3 February 2011. The Asia-Pacific registry ran out two months later, North America in 2015 and Europe in 2019. Since then an IPv4 address has been something you buy from someone who has one spare, and a provider that cannot buy enough puts its customers behind CGNAT instead.

Why IPv6 Was Invented

Work on a replacement began in 1994, when the exhaustion date was already being predicted, and the design was published in 1995 and settled as RFC 2460 in 1998. The main change is the size of the address: 128 bits instead of 32, which is about 340 undecillion addresses, enough to give every grain of sand on Earth its own network. There is no version 5 because that number had already been used by an experimental streaming protocol in the 1980s.

A larger address was the point, but the designers took the chance to tidy up. Every device can have its own public address, so NAT is not needed and two devices can talk directly. A device can work out its own address from the network prefix it hears on the wire, without a DHCP server. The packet header is simpler and fixed in size, so routers have less to do, and features that were bolted on to IPv4 later, such as multicast and IPsec, are part of the design.

Why Are We Not All Using IPv6?

Roughly half of the people who reach Google do so over IPv6, after more than twenty-five years, and the figure varies widely by country. Mobile networks moved early, because they add millions of devices a year and could never have bought enough IPv4 addresses. Many broadband providers and most company networks are still IPv4 only. The reasons are practical rather than technical:

• NAT worked too well. Sharing one address between a household or a whole office removed the pressure that IPv6 was built to relieve. Scarcity became a cost, not a crisis.
• The two versions do not talk to each other. An IPv6-only device cannot reach an IPv4-only website, so everyone runs both, and as long as both run nobody can switch off IPv4. The last site to move holds everyone else back.
• Nobody sees a benefit. A web page looks the same over either version, so a customer never asks for IPv6 and a provider gains nothing visible by offering it.
• Old equipment. Routers, firewalls, printers and in-house software were built for IPv4, and replacing or testing them costs money that is hard to justify for no new feature.
• Skills and habit. Network staff know IPv4, and a 128-bit hexadecimal address with a different set of rules for firewalls and addressing is a real change to learn.

The change is still happening, just slowly. New mobile networks, cloud platforms and large websites run IPv6 as a matter of course, and some cloud providers now charge for each IPv4 address, which is the first cost most companies have ever seen attached to staying on the old version. If this page showed you an IPv6 address, your provider has already made the move.

How Network Prefixes Work

An IP address has two parts: the network it belongs to and the device within that network. The split is given by the prefix length, written after a slash (CIDR notation). In 192.168.1.0/24 the first 24 bits identify the network and the last 8 bits the device, giving 256 addresses from 192.168.1.0 to 192.168.1.255. This is the same as the subnet mask 255.255.255.0. A /16 covers 65,536 addresses.

The older classful scheme (Class A, B and C) fixed the split by the first number of the address. It was replaced by CIDR in 1993, so the position of a number in the address does not tell you whether it is part of the network or the device. In IPv6 each local network is normally a /64: the first 64 bits identify the network and the last 64 bits, the interface ID, identify the device.

Why Does My IP Address Change?

Most home and mobile connections are given an address dynamically, and it can change when your router reconnects or restarts, or when the provider reassigns it. A fixed (static) address is usually available from your provider, often at extra cost. With IPv6, devices also use temporary privacy addresses that change regularly, so the interface ID can change even when the network prefix stays the same.

VPNs and Proxies

A VPN or proxy sends your traffic through its own server, so websites see that server's address instead of yours. Any location shown by a website that looks up your IP address will be the location of the VPN server.

Finding Your Local IP Address

The address on this page is your public address. To see the private address of the device you are using:

Windows  : ipconfig              (IPv4 Address under your active adapter)
macOS    : ipconfig getifaddr en0
Linux    : ip -4 addr

How a Web Server Sees Your Address

The server takes your address from the network connection itself, not from anything your browser sends. In code it is read like this:

PHP              : $_SERVER['REMOTE_ADDR']
Delphi WebBroker : Request.RemoteAddr
Delphi Indy      : ARequestInfo.RemoteIP   (TIdHTTPServer.OnCommandGet)

When a site sits behind a proxy, load balancer or CDN, the connection comes from that proxy, so the visitor's original address is passed on in the X-Forwarded-For header. That header is ordinary text that any client can set, so only trust it when the request came from a proxy you control, and use the address that your proxy added (the last entry) rather than the first.

How a URL Is Structured

https://example.com:443/articles/page?name=value#section

• Scheme https : the protocol used to connect.
• Host example.com : the server, looked up through DNS to find its IP address.
• Port 443 : usually left out, because 443 is the default for https and 80 for http.
• Path /articles/page : the page or file on that server.
• Query name=value : extra values for the page, after the ?.
• Fragment section : a position within the page, after the #. It is used only by the browser and never sent to the server, which is why it cannot be shown in The Address You Requested above.

More Tools

Random Password Generator
Back to Internet Tools
Back to Developer Tools