Your public address is what websites and APIs see when your browser connects. These values come from your browser calling ipify—IPv4 and a dual-stack check that may show IPv6 when available—useful behind VPNs, CGNAT, or dual-stack networks.
Your public address
Direct requests from your device to ipify; SynthQuery does not insert a server-side “connection IP” row.
Loading addresses…
Geolocation & network
Location is estimated from IP routing and registry data—not GPS. Accuracy varies by carrier, mobile networks, and corporate VPN exit nodes. Use it for debugging and education, not for emergency services.
Browser environment
Local hints your browser exposes (not derived from IP). Helpful when comparing reported timezone against IP geolocation.
Signal
Value
Time zone
—
Primary language
—
Languages (ordered)
—
Screen
—
Protocol
—
Privacy & networking notes
VPNs, corporate proxies, and mobile carriers can change your public IP and geolocation without any change on your laptop. IPv6 adoption means some households show a stable IPv6 prefix while IPv4 is shared via CGNAT—so IPv4 “what is my IP” tools may show a carrier-grade NAT address that differs from what certain websites log.
IP and coarse location are requested directly from ipify and ipapi.co in your browser; SynthQuery does not run a separate server-side “what IP hit our app” lookup on this page. We do not store your IP in a marketing profile from this utility—see our Privacy Policy for general platform practices.
WebRTC and some legacy plugins can leak local network addresses in other contexts; this tool does not run WebRTC discovery. For leak testing use a dedicated security-focused checker after reviewing your browser permissions.
About this tool
“What is my IP address?” is one of the most common diagnostic questions on the modern internet—and the answer is more layered than a single number in a monospace font. Your public IP is the network address that servers on the wider internet use to send responses back to your home, office, phone, or cloud workstation after you open a page, call an API, or start a video call. It is different from the private addresses inside your LAN (often 192.168.x.x or 10.x.x.x) that your Wi‑Fi router hands out with DHCP. It is also different from loopback (127.0.0.1), which only talks to your own machine. SynthQuery’s Free “What Is My IP” utility makes those distinctions actionable: IPv4 and dual-stack checks from ipify run directly in your browser (so you see the egress your HTTP client uses), geolocation context from ipapi.co uses the same browser-origin model, and a concise panel of browser-reported signals such as IANA time zone and language preferences lets you compare “where the network thinks I am” with “what my OS claims locally.” We intentionally do not show a separate “app server connection” IP row, because reverse-proxy header chains are easy to misconfigure and can mislead visitors; the readings here reflect your device’s path to public endpoints.
The page belongs to our Free tools series alongside the HTML Online Viewer, CSS Grid Generator, image utilities, calculators, Word Counter, Dictionary & Thesaurus, and Grammar Checker—lightweight utilities you can use without signing up, nested under the broader SynthQuery catalog at /tools when you need AI detection, readability depth, plagiarism review, paraphrasing, or summarization. We designed the layout for support engineers proving a VPN split tunnel, marketers debugging geo-targeted pay-per-click previews, privacy-conscious users learning how carrier-grade NAT changes IPv4 visibility, and students studying IPv6 adoption. Copy buttons sit next to every address we display so you can paste into tickets without transcribing digits, and an OpenStreetMap deep link appears when latitude and longitude are present so you can sanity-check coarse location estimates responsibly—remember IP geolocation is statistical, not GPS. Throughout, we are explicit about limits: geolocation providers can be rate-limited, and IPv4 versus IPv6 paths can differ when ISPs use CGNAT or dual-stack.
What this tool does
At the top of the interactive dashboard you will find a navigation strip with anchors to Addresses, Geolocation, Browser, and Privacy sections plus a Refresh control that re-fetches ipify and ipapi.co from your browser.
The addresses card calls ipify’s public JSON endpoints directly from your browser. IPv4 uses api.ipify.org; the dual-stack endpoint api64.ipify.org may return IPv6 when your ISP and device expose it, or IPv4 when IPv6 is unavailable—so we explain the result in context rather than promising a magic “always IPv6” badge. VPNs, split tunnels, and happy eyeballs can change which address you see per endpoint; none of those signals alone proves malicious behavior—they document paths.
Geolocation uses ipapi.co’s JSON API from the browser (the same origin model as the ipify calls). When the provider returns structured fields, we render a table covering country, region, city, postal code, timezone, UTC offset, ASN, organization, announced network prefix, reported IP version in their database, regional languages, currency metadata, and telephony calling codes. Errors or rate limits surface as human-readable messages instead of silent failure. Browser environment metrics—time zone from Intl, ordered language list, screen resolution with device pixel ratio, and page protocol—hydrate after mount to avoid React hydration mismatches between server HTML and client reality. A collapsible User-Agent string helps compare desktop versus mobile emulation without opening devtools on a locked-down workstation.
Privacy copy on the page reminds readers that VPNs and mobile carriers routinely shift public IPs, IPv6 prefixes may be stable longer than DHCP IPv4 leases, and WebRTC leak testing is a separate concern we do not execute here. This page does not expose a SynthQuery-hosted “open IP lookup” API—measurements are initiated from your browser to public endpoints for self-diagnosis only.
Use cases
Site reliability engineers and developers use the tool to sanity-check public egress after VPN or DNS changes. Customer support teams ask end users to open the page, copy the IPv4 or dual-stack value shown, and paste it into tickets when debugging rate limits or geo-fenced admin panels—much faster than walking non-technical customers through operating-system network dialogs. Digital marketers validate whether an office egress IP matches the geography their ad platforms believe they are browsing from before blaming creative for delivery anomalies.
Security and compliance analysts teaching workshops compare IPv4 and dual-stack readings to illustrate split-tunnel VPN behavior, demonstrate why IP allowlists are fragile on roaming laptops, and contrast NAT44 with IPv6 prefix delegation. Students preparing for networking certifications translate abstract textbook diagrams into concrete strings they can map to ASN and country fields, reinforcing that BGP announcements—not moral character—drive geolocation databases.
Game server moderators and community managers occasionally need a quick external IP to share with friends for allowlisted private servers; we still recommend dynamic DNS or proper authentication rather than long-lived IP secrets, but the copy affordances make honest mistakes less likely. Remote workers on satellite or LTE links observe how carrier-grade NAT collapses many subscribers behind one IPv4 while IPv6 reveals a different story, informing decisions about VoIP quality-of-service tickets. Content teams referencing SynthQuery’s Writer, Paraphraser, or Grammar Checker can keep this utility bookmarked next to word-count and readability flows so “publishing readiness” spans both language quality and network context when incidents strike.
How SynthQuery compares
Generic “what is my IP” pages range from ad-heavy iframes to single-line displays with no explanation of IPv6 or geolocation uncertainty. SynthQuery combines parallel browser-side IPv4 and dual-stack checks, structured ASN context when ipapi.co returns data, and integration with the rest of our Free tools and AI suite. The matrix below highlights common differences—pick based on workflow depth, not marketing superlatives.
Aspect
SynthQuery
Typical alternatives
Measurement paths
Parallel browser ipify IPv4 and dual-stack checks with explanatory hints; no misleading server-side “connection IP” row.
Often one outbound request with no IPv6 context or explanation.
Proxy / header clarity
Focuses on what your browser’s HTTP stack actually uses for public endpoints—avoids mis-parsed reverse-proxy headers on our origin.
Some pages show an origin-inferred IP that reflects the hosting stack rather than the visitor.
Geolocation depth
Tabular ASN, organization, timezone, currency, and calling-code context when the provider returns data.
Frequently a map teaser with coarse city only or aggressive upsell modals.
Workflow adjacency
Linked from /free-tools and /tools next to HTML, Grid, grammar, counting, and AI detection utilities.
Standalone pages that do not connect to broader editorial or QA workflows.
Abuse resistance
No SynthQuery-hosted open resolver; third-party calls originate from the visitor’s browser for self-checks only.
Some sites expose open APIs that double as third-party reconnaissance tools.
How to use this tool effectively
Open /what-is-my-ip and wait for the initial load: your browser fetches ipify and ipapi.co in parallel. Read the IPv4 row first, then the dual-stack row—when they differ, you are often seeing IPv6 on dual-stack paths or divergent routing.
Toggle Refresh after connecting or disconnecting VPN software to watch addresses change; capture screenshots for change-management records if your policy requires evidence. Move to Geolocation and verify that timezone roughly matches expectation. If you are on mobile data, expect city-level drift; if you are on satellite backhaul, expect country-level accuracy at best.
Open the OpenStreetMap link only when you understand that coordinates estimate ISP presence, not your kitchen GPS. Compare browser time zone from Intl with the network timezone row—mismatches often indicate VPN exit nodes in another region while the laptop clock stays local. Copy whichever IP your downstream system actually needs: some firewalls want IPv4 literals, while modern APIs may prefer IPv6. When documentation asks for “the IP you use to reach the internet,” use the value that matches the tool or firewall you are configuring—often the IPv4 literal or the dual-stack reading shown here. After networking checks, follow internal links to Grammar or Word Counter if you are drafting incident summaries, or to the AI Detector if you are documenting AI-assisted postmortems. Bookmark /free-tools to rediscover every utility without searching.
Limitations and best practices
Geolocation databases lag reality: BGP changes, Anycast, and reseller addressing can place you hundreds of kilometers from the label shown. Never use IP-derived location for emergency services, custody decisions, or sole authentication factors. Header-based client IP detection depends on trusted proxies—if attackers can spoof X-Forwarded-For because your edge is permissive, logs may lie; lock configuration to known hop counts and strip client-supplied junk. IPv4 carrier-grade NAT means many subscribers share one public address; rate limiting by raw IPv4 alone can punish innocent neighbors—pair with authenticated user IDs or fairer tokens when possible. IPv6 privacy extensions rotate interface identifiers; do not assume stability forever without measuring. Third-party APIs may rate-limit; if geolocation fails, retry later or rely on ipify outputs alone. This page educates and assists honest diagnostics; it is not a penetration-testing arsenal—respect applicable laws and corporate policies when interpreting addresses.
Searchable archive of every lightweight SynthQuery utility, including HTML, Grid, resizers, calculators, counting, dictionary, grammar, and this IP dashboard.
Optimize screenshots attached to tickets after you capture network settings or traceroute outputs.
Frequently asked questions
A public IP address is routable on the global internet: when you fetch a website, the origin server sends packets back to that address (or to an upstream carrier NAT that ultimately maps to you). A private IP address lives inside a local network segment defined by RFC 1918—common ranges include 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16—and is not globally unique. Your Wi‑Fi router hands private addresses to laptops and phones, then performs Network Address Translation so many devices share one public IPv4. SynthQuery shows public-facing information useful for allowlists, support tickets, and geo debugging; it does not scan your LAN for private DHCP assignments. If you see 10.x or 192.168.x in an application log unexpectedly, that usually means a proxy misconfiguration rather than your true internet egress. IPv6 introduces additional patterns such as unique local addresses and privacy extensions, but the same conceptual split applies: global unicast prefixes are world-routable; link-local fe80::/10 stays on the segment. Understanding the distinction prevents false alarms when junior analysts paste the wrong field into firewall rules.
Networks rarely offer a single canonical “truth.” Your browser calls two ipify endpoints: one IPv4-oriented check and one dual-stack check that may return IPv6 when available. They can differ when your ISP provides both stacks, when IPv6 is disabled, or when split-tunnel VPNs send different traffic types out different paths. VPN software, corporate proxies, satellite backhaul, and mobile tethering can all produce divergent readings that are simultaneously valid for different layers. We display them side by side with copy buttons so you can attach the precise value your firewall team, cloud vendor, or game server host requested. If every number matches, you likely have a simple residential path; if they differ, compare ASN and geolocation rows to reason about which path each subsystem might see.
Think “regionally useful,” not “laser pointer.” Providers aggregate routing registry data, ISP billing locations, and crowdsourced corrections to estimate where an address is announced—not where a person stands. Accuracy is often excellent at country level, decent at state or city level for fixed broadband, and unreliable for mobile carriers that centralize egress in distant cities. Corporate VPNs place you at the data-center geography of the exit node. Satellite and wireless ISPs may geolocate at national granularity. SynthQuery surfaces latitude and longitude when available and links to OpenStreetMap for visual context, but you must not treat coordinates as proof of physical presence for legal, medical, or law-enforcement purposes. For fraud scoring, combine IP signals with device posture, authentication history, and behavioral analytics. For marketing personalization, A/B test assumptions because database vendors refresh on different cadences.
IPv6 expands the address space beyond 32-bit IPv4 notation into 128-bit hexadecimal groups, reducing reliance on large-scale NAT and enabling end-to-end features—though operational reality still includes NAT66, privacy temporary addresses, and dual-stack networks. You might only see IPv4 if your ISP has not deployed IPv6, if your router disabled it, if your VPN tunnels IPv4-only, or if the particular endpoint you are measuring never attempted IPv6. Our dual-stack ipify call explains when the returned address is still IPv4 because IPv6 was unavailable to that HTTP client. Enterprises often run IPv6 internally while external SaaS remains IPv4-first; do not equate “no IPv6 on this page” with “my network has zero IPv6.” When planning firewall rules, ask whether partners require literal IPv6 allowlisting or DNS-based names that abstract churn.
X-Forwarded-For is a de-facto standard header where each trusted proxy appends the observed client address, producing a comma-separated list from user to edge. Application servers parse the leftmost or rightmost hop depending on documented trust policies. The header is trivially forgeable if a client sends it directly to an origin that naïvely trusts every value—attackers could inject fake IPs. Correct deployments terminate TLS at a controlled edge, strip inbound X-Forwarded-For from untrusted sources, and append authoritative values themselves. This SynthQuery page does not display a reverse-proxy-derived “connection IP” because misconfigured chains are a common source of confusion; instead we show browser-originated public checks. If you operate services, configure frameworks to trust only known proxy CIDRs and hop counts. If you consume third-party APIs, read their documentation on which header they honor.
Usually yes for the public addresses, because VPN clients route tunneled traffic through an exit server that owns a different global address block. What you see depends on full-tunnel versus split-tunnel routing, browser extensions, DNS-over-HTTPS, and operating-system policy. Some corporate VPNs send only “corporate SaaS” subnets through the tunnel while general web browsing exits locally—then ipify might still show your residential ISP while an internal wiki sees the office range. Refresh the page after toggling VPN states to capture before-and-after evidence. Remember that VPNs improve privacy against casual observers but are not invisibility cloaks: sites can still fingerprint browsers, read language preferences, and correlate sessions. Combine VPNs with other controls when threat models demand it, and never violate workplace acceptable-use policies while testing.
Regulators increasingly treat IP addresses as personal data when they can identify an individual directly or indirectly, especially when combined with timestamps and logs—though interpretations vary by jurisdiction and context. This utility loads ipify and ipapi.co directly from your browser; SynthQuery does not use it to build advertising profiles. For enterprise deployments, consult your Data Processing Agreement, logging retention schedule, and legal counsel about whether storing support-ticket IP copies requires bases of processing or data subject rights workflows. Individuals exercising privacy rights should remember that clearing cookies does not rotate ISP-assigned IPv4 addresses; you may need to talk to your provider or use privacy-protective networking tools where lawful. Educational use of this page should emphasize proportionality: collect only the IPs you truly need, minimize retention, and protect access to logs.
Your browser asks ipapi.co for structured metadata; if you hit rate limits, if the provider blocks a particular range, or if transient network failures occur, the UI surfaces a readable error instead of pretending success. Some privacy-focused ISPs anycast addresses in ways that confuse stale database rows, yielding blank fields. Retry after a few minutes, test from another network, or rely on ipify outputs for at least the numeric address. If you operate a high-volume integration, consider licensing a commercial geo provider with SLAs rather than depending on free tiers. For classroom demos, precompute examples on a known-good network to avoid embarrassing empty tables.
No. WebRTC leak tests typically create peer connections to discover local interface candidates; we intentionally omit that surface to reduce accidental exposure on shared machines and to keep the page lightweight. DNS leak testing requires observing which resolver answers your queries—often implemented by specialized security sites or desktop apps with explicit consent. SynthQuery focuses on HTTP-level public IP visibility and ASN context. If your threat model includes aggressive tracking, use a curated security checklist from trusted auditors, keep browsers updated, review extension permissions, and configure DNS-over-TLS thoughtfully. For enterprise zero-trust rollouts, combine this page’s IP evidence with endpoint compliance agents rather than treating any single website as an all-in-one audit suite.
This page is for checking the public addresses your own browser reaches ipify and ipapi.co with—not for querying arbitrary third-party targets. Looking up third-party IPs without authorization can violate workplace policy, terms of service, or local computer misuse laws depending on context. If you are handling abuse on your own platform, use your authoritative server logs, WAF dashboards, and lawful process—not public “doxing” workflows. Educators should frame IP addresses as network metadata subject to responsible use, comparable to phone numbers in a directory: sometimes public, sometimes sensitive, always contextual.
SynthQuery’s core value is content intelligence—AI detection, SynthRead readability, grammar, plagiarism, summarization, translation, and creation flows—but real editorial work happens on networks with VPNs, zero-trust gateways, and geo-fenced admin pages. This utility keeps lightweight diagnostics in the same brand universe as your writing stack so support and content teams share bookmarks. After you verify connectivity, jump to Grammar to polish customer emails explaining DNS fixes, open Word Counter to hit executive-summary length targets, or run the AI Detector on incident postmortems that may include machine-generated drafts. The /tools index lists every product surface when you graduate from utilities to full analyses.
Start at /free-tools for the “Free tools” hub: searchable cards for HTML utilities, CSS Grid, converters, calculators, resizers, counting, dictionary, grammar, and this IP address dashboard—all designed for quick tasks without signing in. When you need the complete SynthQuery offering, open /tools for AI-powered detection, readability depth beyond quick counts, plagiarism checks, humanization, paraphrasing, summarization, translation, and more, with pricing context on /pricing. Footer navigation on every marketing page also links to All tools and Free tools so you can move between hubs without memorizing URLs. Bookmark both pages if you split your day between infrastructure triage and editorial quality gates.