Check an address from different countries with ping, traceroute, MTR, HTTP, port and DNS. Measurements are sent from your browser to the Globalping network.
Example: example.com, 1.1.1.1 or https://example.com
Test type
Protocol
Locations
Cost
Location
Network
Status
Details
Latency
Measured by the Globalping network. The target and results are stored publicly at Globalping. Probes are mostly data center lines; to measure from home and operator lines use the Türkiye home/ISP option.
RespondingPartial responseNo responseOpenUnreachableMeasuringProbe offlineNot measuredTarget reachedPacket loss {n}%{r} / {t} packets{r} / {t} connectionsDNS {dns} · TCP {tcp} · TLS {tls} · First byte {ttfb} msNo recordPing result: {target}HTTP result: {target}Port {port} result: {target}DNS {type} result: {target}{ok} / {n} respondedTraceroute result: {target} · {proto}MTR result: {target} · {proto}{ok} / {n} reached the targetLocations respondingAverageFastest, {loc}Slowest, {loc}Locations reaching the targetThis test uses {n} probes.This test used {n} probes. Remaining in your hourly allowance: {r} probes.Enter an address.Enter a valid IP address, domain name or URL.Private or reserved addresses cannot be tested.Enter a domain name for the DNS test.Your hourly allowance is used up. Try again in {m} minutes.No suitable probe was found in the location you chose.The measurement service could not be reached. Try again shortly.Some probes did not answer in time.The Istanbul measurement point is not responding right now, try again shortly.{n} hops · {loss}% lossAddressLossSentAvg (ms)BestWorstStDevNo packet loss is visible on the path.Loss is visible at hop {n}, but the following hops are clean. This is usually the router limiting its replies, not real packet loss.Loss starts at hop {n} and continues to the end of the path ({loss}% at the last hop). This may be real packet loss.Many sites block ICMP; the target may still be working. Try the same path over TCP {port}.Measure again over TCP {port}Headers and certificateHeadersResponse headersTLS certificateStatusSubjectAlternative namesIssuerValidityProtocolKeySHA-256 fingerprintSerial numberTrustedYesNo{n} days left1 day leftexpired {n} days agoexpired 1 day ago{n} days ago1 day agoCertificate.Same certificate at all responding locations ({n}): {cn} · {iss} · {proto}, {key} · expires on {date} ({days}).The certificate differs by location ({k} different certificates): {list}. Open the rows to see each location's certificate.{n} × {cn} ({iss}, {days})The certificate expired on {date} ({ago}); locations affected: {n}. Browsers open this site with a warning.The certificate is not trusted{err}; locations affected: {n}. Browsers open this site with a warning.Same certificateLess than 30 days leftDifferent certificatesExpiredUntrusted certificateCopy linkCopiedAnyone with the link can see this result.Shared result.Measured on {when} ({ago}). The result reflects that moment; the current state may differ.This result is gone or could not be found. Globalping usually keeps results for up to six months. Press Run test to measure again with the same settings.The result could not be read right now. Try again in a few seconds.Sponsor: {name}The Istanbul measurement point is sponsored by {name}.Home/ISP{n} hops to the target from the Orfi Istanbul measurement pointtotal {ms}no responseprivate networkTarget not reached{n} hopsThe traceroute could not be completed.Measure again
What is checked?
Ping: latency and packet loss from each location
Traceroute: the path to the target from each location, with hop addresses and latencies (ICMP or TCP)
MTR: packet loss, latency and jitter per hop from each location
HTTP: status code with DNS, TCP, TLS and first byte times; response headers and the TLS certificate (is it the same everywhere, when does it expire)
Port: whether a TCP connection to a single port can be made
DNS: the answer each location's resolver returns for the record type you pick
Worldwide, Türkiye, Türkiye home and ISP lines, Europe, North America, Asia or a country you choose
How do I read the result?
Responding: the location reached the target. Partial response: some packets were lost. No response: none came back.
If only one location fails, the problem is usually that location's network rather than the target, or the target blocks that region.
Traceroute: hops that do not answer at the end of the path are often a firewall; the target may still be working. For sites that block ICMP, choose the TCP protocol.
MTR: loss shown at one hop but not at the following hops is usually the router limiting its replies, not real loss; only loss that continues to the end of the path is real.
Certificate banner: green means every location sees the same certificate. Yellow means the certificate expires in less than 30 days or the certificate differs by location; red means it has expired or is not trusted. The button on a row opens that location's headers and certificate.
Probes are mostly data center lines; to see home and operator lines use the Türkiye home/ISP option.
Frequently asked questions
Who runs the measurement?
Probes on the Globalping network. Your browser starts the test; our server does not generate the measurement traffic.
Are the results public?
Yes. Globalping stores the target and the result publicly, and your IP address reaches Globalping when you run a test. Do not test a private address with this tool.
Why does the certificate differ by location?
Some CDNs serve a different certificate depending on the location or client; if the issuer and expiry date match, it is fine. If old and new certificates show up together on one address, the rollout after a renewal may still be in progress.
How do I share a result?
Once a test starts, the link in the address bar points to that measurement; you can take it with the Copy link button. Whoever opens the link sees the same result without running the test again; Globalping usually keeps results for up to six months.
Why is my hourly allowance limited?
Globalping gives each visitor IP address a limited number of probes per hour, and each location counts as one probe. Your remaining allowance is shown after a test, and when it runs out you see when it reopens.
Why does it not tell a closed port from a filtered one?
If a TCP connection attempt gets no answer, the cause can be a closed port or a firewall. The tool shows both as unreachable.
Who provides the Istanbul measurement point?
A server sponsored by Orfi (Netvia Bilisim). It is a probe joined to the Globalping network, it takes part in every test when "Türkiye" is selected and carries a "Sponsor: Orfi" label in the results. Link: orfi.net.tr