Check My IP Address
Instantly check your public IPv4/IPv6 address, ISP, and approximate location.
Detecting type...
Loading info...
How to read your IP result
Even when both IPv4 and IPv6 are available, this page is reached through one active path. Compare the Current badge, location estimate, DNS, and WebRTC results to understand VPN, ISP, and corporate-network differences.
Current means the live connection path
If both IPv4 and IPv6 are detected, the Current badge marks the address your browser used for this page request. A dual-stack network can still connect over IPv4 when the site or route prefers it.
IP address lookup →VPN checks need more than the IP
Your public IP can change to a VPN while DNS lookups or WebRTC candidates still reveal another network. Compare IP, DNS leak, and WebRTC leak results after turning the VPN on.
DNS leak test →Location is an estimate
IP geolocation comes from databases, not GPS. Carrier NAT, VPNs, CDNs, and corporate proxies can show a city or provider that differs from your physical location.
VPN privacy check →One public IPv4 can be shared
Mobile networks, office networks, home routers, and carrier-grade NAT can make many users share one public IPv4 address. For account or firewall issues, check ASN and ISP as well.
ASN lookup →Other Tools
What is my IP address?
This page separates the public IP used by the current browser request from the IPv4 and IPv6 addresses that can be detected. If both families are available, the address marked Current is the one this request actually used.
IP checking is the first step for VPN validation, IPv6 rollout, access troubleshooting, and security review. ipnawa separates the current connection from available address families so dual-stack users can see whether the page is actually reached over IPv4 or IPv6.
- Confirm whether a VPN, proxy, or mobile hotspot changed your public IP.
- Distinguish current IPv4 versus IPv6 web connectivity on dual-stack networks.
- Collect IP, ISP, location, and ASN evidence for account, firewall, or support issues.
Common IP, VPN, And DNS Questions
Start from the current IP result, then open the guide that explains the confusing part in plain language.
Why does my device IP differ from the IP a website shows?
Your device may use a private address such as 192.168.x.x or 10.x.x.x, while websites see the public IP assigned to the router, VPN, or ISP. For external access problems, compare public IP, NAT, firewall, and port-forwarding paths together.
Why does my IP show the wrong city?
IP geolocation uses network and GeoIP database signals, not your device GPS. VPNs, mobile carrier NAT, CGNAT, office proxies, CDN exits, and stale GeoIP records can make the visible city differ from your physical location.
Why does my IP keep changing?
Home and mobile connections often use dynamic IP addresses. Router restarts, DHCP lease renewal, VPN exit rotation, mobile tower changes, and IPv4/IPv6 path selection can all change the public IP visible to websites.
Why am I connected over IPv4 when IPv6 is available?
IPv6 availability does not force every request to use IPv6. The target site, DNS response, browser preference, and network policy can still make the current request use IPv4.
What should I check first when IPv6 is missing?
Compare the IP checker and DNS leak results on the same network. If IPv6 remains undetected, review ISP support, router IPv6 mode, operating system IPv6 settings, and VPN behavior in that order.
What should I check first when port forwarding does not work?
Compare the public IP shown by the IP checker with the WAN IP shown in your router. If they differ, or the router WAN address is private or CGNAT-like, normal router port forwarding may not be enough for inbound access.
Does a wrong VPN location mean I am leaking?
Not always. Compare current IP, DNS leak results, and WebRTC candidates in the same browser, then check whether browser location permission, cookies, or logged-in accounts are influencing the displayed location.
Why does DNS still show the old IP after I changed it?
Run DNS propagation checks across multiple resolvers first. If the authoritative nameserver has the new value but recursive resolvers still show the old value, TTL or cache delay is the likely cause.
Internet Diagnostic Tools
Browse ipnawa tools by DNS, email, privacy, webmaster, developer, and network troubleshooting intent.
DNS and Domain
Free diagnostic tools and related guides for checking DNS and Domain issues in one place.
Email Deliverability
Free diagnostic tools and related guides for checking Email Deliverability issues in one place.
VPN and Privacy
Free diagnostic tools and related guides for checking VPN and Privacy issues in one place.
Webmaster and SEO
Free diagnostic tools and related guides for checking Webmaster and SEO issues in one place.
Developer Utilities
Free diagnostic tools and related guides for checking Developer Utilities issues in one place.
Network Connectivity
Free diagnostic tools and related guides for checking Network Connectivity issues in one place.
Guide
IP checking is the first step for VPN validation, IPv6 rollout, access troubleshooting, and security review. ipnawa separates the current connection from available address families so dual-stack users can see whether the page is actually reached over IPv4 or IPv6.
Best for
- Confirm whether a VPN, proxy, or mobile hotspot changed your public IP.
- Distinguish current IPv4 versus IPv6 web connectivity on dual-stack networks.
- Collect IP, ISP, location, and ASN evidence for account, firewall, or support issues.
- Build a baseline before running DNS leak, WebRTC leak, or IP lookup checks.
How to use
- Review the IPv4 and IPv6 cards at the top of the page.
- Use the Current badge to identify the address used for this request.
- Change VPN, DNS, or network conditions and refresh to compare results.
- Continue with IP lookup, DNS leak, or WebRTC leak tests when the result looks unexpected.
Interpretation tips
- Having IPv6 available does not guarantee that every website request uses IPv6.
- IP geolocation is an estimate from public databases, not a GPS-level location.
- Corporate networks, VPN gateways, and carrier-grade NAT can make many users share one public IPv4 address.
Privacy & notes
The check uses browser-side IP providers and local server echo data. You do not need to enter passwords, tokens, or private identifiers.
How To Interpret The Result
Classify the result as good, needs review, or requires action before you change production settings.
Matches the expected signal
If Check My IP Address matches the expected domain, IP, browser, or configuration and there are no critical warnings, you can treat it as a baseline.
Recheck under another condition
Check My IP Address can vary by network, DNS cache, CDN, VPN, browser setting, or mail provider, so retest when the signal looks inconsistent.
Cross-check before production changes
Before changing production settings, confirm the same cause with related tools such as Privacy Exposure Score, VPN & Privacy Check, DNS Leak Test.
Related Tool Categories
Tool collections that help you check the same issue from more than one angle.
Troubleshooting Playbook
Use these symptom-based checks when a result does not match what you expected.
IPv6 is available, but the current connection shows IPv4.
Check whether the target site returned AAAA records and whether browser, VPN, or ISP policy sent this request over IPv4.
Compare DNS leak and WebRTC signals to see whether the same public address is exposed elsewhere.
The VPN is on, but ISP or location did not change.
Do not rely on cache or UI labels. Compare public IP, DNS resolvers, and WebRTC candidate addresses.
Run the VPN check, then repeat the DNS leak test in the same browser session.
The location looks wrong.
IP geolocation is based on network databases, ISP data, and ASN routing. It is not GPS location.
Compare IP trace and ASN lookup to separate a stale location record from a proxy or routing path.
FAQ
What does Check My IP Address show?
Why does it say IPv4 is current when I also have IPv6?
Why is my IP location different from my real location?
How do I check whether my VPN is really working?
Recommended Next Steps
Follow this order before changing production settings so you can validate the likely cause faster.
Privacy Exposure Score
Start with the most important signal.
Score IP, IPv6, WebRTC, DNS, browser fingerprint, cookie, storage, screen, and timezone signals to see what a website can observe in one report.
VPN & Privacy Check
Then cross-check adjacent policy or configuration.
Combines WebRTC leak, DNS leak, and IP analysis to verify whether your VPN is actually protecting your privacy.
DNS Leak Test
Finish by confirming user-facing or security impact.
Check whether DNS requests are leaking outside expected network paths.
Concept Guides For This Tool
Use these short explainers to understand why the result matters before you act on it.
IP result normal, warning, and fix-needed examples
IP results become more useful when current connection, IPv4/IPv6, ISP, ASN, location, and VPN state are grouped into normal, warning, and fix-needed examples. Visitors can judge their own result faster and continue to the right tool.
How to interpret your IP result: current connection, IPv4, IPv6, and location
An IP checker is more useful when you read current connection, available IPv4/IPv6, ISP, ASN, and approximate location as separate signals. That helps explain VPN routing, CGNAT, IPv6 rollout, proxies, and location mismatch.
Related Tools
Use these tools together for better diagnostics.
WebRTC Leak Test
Check whether WebRTC exposes network addresses and potential leak risk.
DNS Leak Test
Check whether DNS requests are leaking outside expected network paths.
Privacy Exposure Score
Score IP, IPv6, WebRTC, DNS, browser fingerprint, cookie, storage, screen, and timezone signals to see what a website can observe in one report.
VPN & Privacy Check
Combines WebRTC leak, DNS leak, and IP analysis to verify whether your VPN is actually protecting your privacy.
Ping Test
Measure round-trip latency to known endpoints and custom hosts.
Data Handling & Privacy
ipnawa is a diagnostics service. Inputs are used to produce results and are not intended for account-based profiling.
- Server-side tools (WHOIS, SSL, DNS, header checks) send your input domain/IP to our server for lookup.
- Browser-side tools (fingerprint, cookies, JavaScript) run primarily in your browser when supported.
- Standard web/server security logs may include IP address, timestamp, and User-Agent.
- Some checks call external providers such as ipinfo.io and bigdatacloud.net.
- Ads and non-essential cookies are loaded only after your consent choice.
External Processors
- ipinfo.io (IP/ASN/location lookups)
- bigdatacloud.net (reverse geocoding)
- Advertising partners (only after ad-consent acceptance)
You can review or change cookie/ad consent at any time.