Time a public host’s HTTP request from this browser

One bounded browser probe

• CURRENT BROWSER
• PUBLIC DOMAIN OR IPV4
• fetch · HEAD · no-cors · no-store
• ABORT AFTER 8 SECONDS
• WAIT 500 MS BETWEEN ATTEMPTS
• TIMES FROM SUCCESSFUL BROWSER REQUESTS

The measurement is a browser HTTP request chain

For every selected attempt, the browser starts a timer and fetches the submitted target with HTTPS, HEAD, mode: no-cors, and cache: no-store. The timer stops only when that browser request resolves; an AbortController ends an attempt after 8 seconds. This differs from ICMP echo traffic.

1. 1. Submit an accepted public target

   Enter a domain name or a public IPv4 address accepted by the editor. Acceptance only decides whether the editor starts its browser request; it does not establish that a host will respond.

2. 2. Run bounded HEAD attempts

   Choose from 1 to 20 attempts; the editor starts with 10. Each attempt is a separate browser fetch using HEAD, no-cors, and no-store, with a 500 ms wait before the next attempt.

3. 3. Group the completed run

   After the final attempt, the editor groups successful request durations and separately counts attempts that did not succeed or were aborted.

The input gate excludes local address space

The editor accepts a domain-shaped hostname or an IPv4 address, then rejects local or private destinations before it sends a request. A syntactically accepted public-looking target can still be unavailable to this browser request.

• localhost and names ending in .local
• 0/8, 10/8, 127/8, 169/8, 172/8, and 192/8 IPv4 ranges
• CGNAT addresses in 100.64/10
• multicast and higher IPv4 addresses (224 and above)

Published run boundaries

These are the current editor controls and request settings. They describe one finite run rather than a general reachability or packet-loss test.

• 1–20 — attempts selectable in the editor
• 10 — default number of attempts
• 8 s — abort time for each browser request
• 500 ms — wait between attempts

What the result fields calculate

The figures summarize this run’s successful HTTP request durations. The field labelled packet loss uses a calculation over browser attempts, not an observation of packets on the network.

Read a run in its request context

The displayed timing includes what happens while this browser makes the HTTP request to that target. It is a record of this application-level exchange, not a claim about every route, service, or packet.

• Compare only runs made with a similar target and browser context.
• A non-successful or aborted attempt means this browser request did not complete in the run; it does not identify the reason.
• Use an ICMP-capable system tool when the task specifically requires ICMP echo measurements.

Continue with adjacent network tools

These tools expose different browser-facing views. Their inputs, sources, and returned fields are separate from the HTTP timing run.

• DNS Lookup

  Inspect returned DNS records for a domain name.

• What Is My IP

  View the public-address information returned to this browser.

• Internet Speed Test

  Run the separate browser-to-Cloudflare measurement.

Questions about this HTTP timing probe