Check whether a device clock is noticeably wrong
Troubleshoot mismatched login codes, logs or meeting times.
Calibrate the displayed clock from repeated low-latency server samples and compare it with your device clock. The result is a network estimate, not a claim of atomic-clock precision.
Show calibrated time, device time and their offset together.
Display round-trip latency, estimated uncertainty, IANA zone and UTC offset.
Troubleshoot mismatched login codes, logs or meeting times.
Demonstrate clock offset and latency together in a classroom or technical session.
Requires network access to /api/time. If the Worker is unavailable, HTTP Date is only a lower-precision fallback; browser scheduling and network jitter affect the estimate.
No. It estimates current time from server timestamps and round-trip latency, and shows an uncertainty range.
Routing, device load and browser scheduling change. Repeated samples and low-latency selection reduce their effect.
No. A web page cannot change the operating-system clock; it only reports the difference and general setup guidance.
The page can open offline, but it cannot obtain a new network sample and will show device time with an offline notice.