Use HTTP Date and Age for a Coarse Time Check Through a Proxy
Use an HTTP Date response for a coarse time check and account for cached response age before interpreting it.
A web response can provide a coarse time reference when the available outbound route is an HTTP proxy. For a controlled endpoint whose clock you trust, request its response headers through that route:
curl --head --proxy http://proxy.example.net:8080 https://time.example.net/The host is an example endpoint, not a public time service. If the trusted endpoint is publicly reachable and the network permits an unauthenticated public intermediary, the HTTP proxy list can supply candidates for the proxy address; it does not supply the trusted clock. A response might contain:
Date: Thu, 29 Oct 2026 08:15:20 GMT
Age: 45Date represents the time the HTTP message originated. It does not necessarily mean “the current instant at this client.” A cached response can have an older Date while remaining valid for reuse. The Age field expresses the cache's estimate of the response's age in seconds.
In this illustrative response, adding the reported age gives a rough reference around 08:16:05 GMT before accounting for transfer delay and estimation error. It is not a measured offset. Record when the client sent the request and received the response if the application wants to describe the uncertainty.
Some servers do not support HEAD as expected or omit usable timing metadata. Treat a missing or malformed field as a failed time observation. A 407 response describes the proxy exchange, so its Date is not automatically the clock of the endpoint you intended to query.
Choose what the observation is for
This can help identify a clock that is wrong by hours or days, or attach an approximate remote timestamp to a diagnostic report. It does not provide NTP's clock-selection and delay/offset processing, and should not drive precision-sensitive clock adjustments.
For actual system synchronization, use the network's approved time service and a supported time-synchronization path. An HTTP proxy route can carry the header check above without making the NTP protocol itself available.