ping123 Transparent IP Check
Auto IP check No silent WebRTC

Public IP check

What is my IP?

Use ping123 to see the public IP address that websites can observe from this browser session. The first check shows the server-visible IP, ISP, ASN, country, city, timezone, IP version, and basic VPN or proxy risk clues.

Check my IP now Check if this IP is leaking more data

Example ping123 result screenshot

The screenshot below uses the designated sample IP 89.116.88.34, not a current visitor IP. Use it as a visual reference for the fields explained on this page.

ping123 public IP result showing observed IP cards, IPv4, IPv6 status, location, ASN, timezone, and risk level
An example ping123 public IP result using the designated sample IP 89.116.88.34.

Start with the IP that the server actually sees

A public IP check answers a simple question first: which address did this request use when it reached a website? That is the address a login page, payment page, ad platform, forum, or API gateway can usually see before any browser-only privacy test runs. If you are using a VPN, proxy, mobile hotspot, corporate network, or public Wi-Fi, this visible address may be different from your home connection.

ping123 separates that server-visible result from manual browser tests. The public IP profile can load automatically because it is based on the normal web request. WebRTC, DNS, and fingerprint checks are separate actions so you can choose when to create additional local or network signals.

Read IP, ISP, ASN, and location together

The IP address alone is rarely enough. ISP and organization names tell you who appears to operate the network. ASN identifies the routed network block. Country, city, latitude, longitude, and timezone are approximate database fields, not GPS. IP version tells you whether the request used IPv4, IPv6, or only one of them.

A normal result is one where these fields match the network you expected. If you connected to a New York VPN exit, a United States country, matching timezone, and datacenter-style ASN may be ordinary. If you expected a residential mobile connection but the ASN looks like a hosting provider, that is a clue to inspect risk and reputation before using the session.

Use the result as the first checkpoint

Before logging into an important account, changing an ad account, testing an e-commerce store, or opening a region-sensitive workflow, record the public IP result first. Then run the related leak checks only if you need a deeper answer. This order makes troubleshooting calmer because you know which signal changed after each network or browser adjustment.

If the public IP changes after you connect a VPN, that is expected. If the IP changes but DNS, WebRTC, browser language, or timezone still point to a different place, the public IP check has done its job: it gave you a baseline for the next test instead of pretending one field proves privacy.

What the result fields mean

Public IP The address observed by the server when your browser requests ping123.
IPv4 or IPv6 The protocol path used by this request. Some leaks appear only on IPv6.
ISP / organization The network operator name associated with the IP database or Cloudflare context.
ASN The autonomous system that routes the IP block. It helps distinguish ISP, hosting, VPN, and proxy networks.
Country and city Approximate geolocation from IP databases, not device GPS.
Risk level A rule-based estimate that should be confirmed with leak and reputation checks.

Normal signals vs. risk signals

Usually normal

  • The visible IP changes after connecting to the VPN or proxy you intended to use.
  • Country, timezone, ASN, and browser language are consistent with the session purpose.
  • IPv6 is either protected by the same tunnel or not observed at all.
  • ISP and organization names match the network type you expected.

Needs attention

  • The IP still belongs to your home or office ISP after you expected a VPN exit.
  • Country or timezone conflicts with the account region you are about to use.
  • The ASN looks like hosting or proxy infrastructure when you expected residential access.
  • IPv4 looks protected but IPv6 or WebRTC may still need manual checks.

Next action

Check my IP now

Continue with the live ping123 check before trusting this browser session.

Check if this IP is leaking more data

Fixes and next steps

DNS leak Turn on DNS leak protection in the VPN or proxy client, disable browser Secure DNS if it bypasses the tunnel, set system DNS to the provider's DNS or a trusted encrypted resolver, then rerun the DNS check.
WebRTC leak Limit or disable WebRTC direct candidates, use a browser profile that blocks WebRTC IP exposure, restart the browser, then rerun the WebRTC check before logging in.
Datacenter ASN If the task needs a consumer-looking account environment, switch from a datacenter/VPS ASN to a stable residential, mobile, or dedicated ISP exit and keep the region consistent.
Blacklist or abuse history Do not keep using a high-risk or listed IP for important accounts. Change the IP range or provider, wait for reputation to stabilize, and retest before continuing.
Timezone or language mismatch Align the IP country, system timezone, browser language, account region, and DNS/WebRTC routes so the session tells one consistent location story.
  1. Reconnect the VPN and choose the exact country or city required for the session.
  2. Disable IPv6 in the VPN client or operating system if your provider does not tunnel it safely.
  3. Run the IP leak test and WebRTC leak test before logging in.
  4. Check DNS settings after switching networks or enabling secure DNS.
  5. Use a clean browser profile when account region and browser language must stay consistent.
  6. If the IP is shared or suspicious, check IP reputation before using it for payment, signup, or ads.

FAQ

What is my public IP address?

It is the IP address that websites can observe from your current browser request. It may belong to your ISP, VPN, proxy, mobile carrier, or company gateway.

Why is my IP location different from my real location?

IP geolocation is based on network databases and routing records. It can point to an ISP office, VPN exit, regional gateway, or outdated database entry.

Can a VPN change my public IP?

Yes. A VPN normally changes the server-visible IP to the VPN exit. You should still check DNS, WebRTC, IPv6, and browser signals.

Does knowing my IP prove I am anonymous?

No. A public IP check is only the first signal. Accounts, cookies, browser fingerprints, DNS, WebRTC, and behavior can still identify a session.

Should I check my IP before logging in?

Yes when account safety matters. Confirm the IP region, reputation, proxy type, and browser consistency before sensitive logins.

Before you continue

Run the check before you continue

A quick check now is easier than troubleshooting a login warning, proxy mismatch, or privacy leak later.

Check my IP now Check if this IP is leaking more data