Network Journey
Type a URL and see everything that actually happens when you press Enter — your connection, DNS, redirects, every network hop, the CDN or proxy in front, the TLS handshake, and the server that finally answers.
Enter any website URL above to map its full journey — from your own connection all the way to the origin server.
🗺️ Path On The Map
Start point Fast hop Slower hop Slow / no reply
📇 DNS Resolution
🛡️ Edge, CDN & Proxies
🔒 TLS Handshake
🖥️ Origin Server
🛣️ Network Hops
—| # | Address | Network / Owner | Location | Latency |
|---|
↪️ Redirects Before The Final Page
| # | URL | Status | Time |
|---|
🔍 What's real here: your own IP, ISP and location come from your browser's actual connection. DNS, redirects, the TLS handshake, response headers and origin ownership are measured live by our server. The hop-by-hop path is a genuine traceroute run from a Globalping probe in your country — a browser cannot run traceroute itself, so this is the closest real vantage point to you, and the exact probe used is named above the table. Nothing on this page is simulated.
HOW IT WORKS
Seven Stages, All Measured
Opening a URL is never one step. Your browser first has to turn the name into an address (DNS), often follow one or more redirects, cross dozens of networks belonging to your ISP and various transit providers, usually terminate at a CDN edge rather than the real server, negotiate an encrypted connection (TLS), and only then receive a response from the origin. This page measures each of those stages separately and lays them out in order. Your endpoint details come from your own browser; DNS, redirects, TLS, headers and ownership are measured by our .NET backend; and the network hops come from a real traceroute run by a probe in your own country, because no website can run traceroute from inside your browser. Every stage that cannot be measured says so plainly rather than showing a plausible-looking guess.
What else can you check?
These tools all work on the same connection and address data — pick whichever question you actually have.
Want to know your public IP?
See your IPv4 and IPv6 addresses, location, ISP and ASN.
Want to check your tower & route?
Live ping, speed, DNS, traceroute and a map of nearby points.
Want to ping from around the world?
Real latency from real probes across 12 countries, live on a map.
Want to locate any IP address?
City, region, country and coordinates for any public IP.
Want to know if an IP is risky?
Proxy, VPN, Tor, hosting and abuse-report indicators.
Want to know if you're blacklisted?
Check an address against major spam and abuse DNSBLs.
Want to know who owns an IP?
Network owner, ASN, CIDR range and abuse contact.
Want to explore an AS number?
Announced prefixes, BGP neighbours and registry details.
Want to test your connection speed?
Measure real download, upload, ping and jitter.
Want to see what changed?
Word-level diff between two blocks of text or code.
Network Journey FAQ
Is this the exact path my own browser takes?
The endpoint details are exactly yours. The hop-by-hop path is measured from a real probe in your country, which is the closest honest approximation available — no website can run a traceroute from inside your browser, because JavaScript cannot send the ICMP packets a traceroute depends on. The probe's actual city is named above the hops table so you always know the vantage point.
Why does the trace end at a CDN and not the real server?
Because that's genuinely where your request ends. When a site sits behind Cloudflare, CloudFront, Akamai or similar, the edge answers you directly and the origin's address is never exposed to the public internet. The Edge panel names which provider answered and shows the exact header that proved it.
Can it detect firewalls?
Partially, and only what's genuinely observable. A WAF that identifies itself in response headers is detected and named. Hops that show no reply usually mean a router is configured not to answer probes — which is normal, not a fault. We don't port-scan, so we can't and don't claim to map a firewall's rules.
Why do some hops show no location?
Router addresses on transit networks are frequently not present in geolocation databases, or are registered to a company head office rather than the rack the device sits in. Rather than plot a plausible-looking dot, hops we can't confidently place are shown without a location and left off the map.
Why is the hop path optional?
It uses the free Globalping network, whose keyless tier is shared across everyone using this site. Making it opt-in keeps the quota available for people who actually want it, and the rest of the journey still works instantly without it.