United KingdomLondon · Europe/London
--:--:--Server reference unavailableOn this GitHub mirror, live TIME functions call the Green Tank development Site API. The display stops when that service is unavailable.
TIME · global reference and reconstruction
Time is evidence.
Read UTC and a TAI-aligned estimate, compare civil time across the world, then test a claimed place and moment against the sky and publication record.
UTC · server estimate--:--:--Coordinated Universal Time
TAI · aligned estimate--:--:--International Atomic Time · derived display
WAITING FOR SERVERTAI − UTC: unavailableSource: not availableNetwork timing bound: unknownAbsolute UTC uncertainty: unknown
This development instrument has no NPL-disciplined time host. Its running numbers are estimates, not a verified atomic-time feed. If the server cannot be reached, the counters stop instead of using your device clock.
The quantum foundation
9,192,631,770 Hz.
The SI second is defined using the caesium-133 atomic transition frequency. TAI is an international time scale calculated from many atomic clocks and calibrated against frequency standards; no one clock is TAI.
Definitive TAI and UTC are calculated by the BIPM from laboratory contributions. Here TAI is a civil-style display derived from a UTC estimate and the IERS TAI−UTC offset. The word “quantum” describes the atomic reference, not this website counter.
Check my clock
How far is this device from the server?
No comparison yet
A positive value means the server clock appeared ahead of this device. The measured network component is about unknown; this does not measure the server's absolute error against UTC. Three HTTPS samples are taken and the lowest-latency response anchors a monotonic browser display.
One instant · many civil clocks
World time.
All rows use the same sampled instant. Local rules come from the browser's IANA-compatible Intl data; its installed database version is not exposed. Confirm recent legal rule changes independently.
Temporal reconstruction · version 1
Check a claimed moment.
Compare the stated capture time and location with timezone rules, solar conditions and a reported publication time. The result assesses consistency, not whether a photo, film or article is genuine or AI-generated.
Adopt this reference
Display it. Inspect the source.
The public HTTPS endpoints are read-only and return no-store JSON with an explicit health state. They are for display and comparison, not for synchronising an operating system. A future NTP/NTS service would be separate.
Small UTC/TAI widget
Preview the widget · /v1/now · /v1/status · /v1/convert · /v1/reconstruct
Green Tank's derived API may be embedded with attribution to this page. Source data remain governed by their respective organisations. Service availability and precision are not guaranteed.Media and publication verification
When did this information exist?
Put the claimed capture time, first publication, later reposts and edits on a single UTC timeline. Keep the original URLs, archive snapshots, bylines, file metadata and any available publisher records. A repost may carry an old image with a new timestamp; publication time is not automatically capture time.
Test independent background conditions: legal local time and daylight rules, calculated sun position, twilight and—when reliable archives are added later—weather, lightning, seismic events, aircraft or ship tracks. These are separate sources with their own coverage gaps and uncertainty. A reported natural event becomes useful only when the event record and the media claim can both be located in place and time.
A consistent result does not authenticate the source. A mismatch can reflect a wrong caption, delayed broadcast, archive footage, edited material, a device clock error or a different location. Time, daylight and repost order cannot by themselves establish that material was made by AI. AI provenance needs additional evidence such as authenticated publisher records, source files, signed capture records or a documented production chain.
The receipt records the inputs, calculated conditions and a digest of the reconstruction. Its SHA-256 identifies that record, not the original photograph, video or article. Keep observation, reconstructed condition and inference in separate fields.
Method and limits
A traceable route is still being built.
Current display: three HTTPS requests sample the Green Tank hosting runtime clock. The browser anchors the lowest-latency response to its monotonic timer, rechecks every 30 seconds and stops the display if the server response grows stale. The measured network bound and device comparison do not establish the server's absolute accuracy.
Required verified source: a separate host running a monitored NTP client disciplined to UTC(NPL), with independent health, offset, uncertainty and last-sync records. This Site cannot claim that source until it is deployed and checked. The status and API deliberately remain UNVERIFIED in the meantime.
TAI: the current +37-second relationship follows IERS Bulletin C 72, which announces no leap second at the end of December 2026. Historical conversions use the dated IERS steps since 1972; JavaScript timestamps cannot express the leap second 23:59:60 itself. The display pauses TAI if its bulletin review date passes without an update.
Civil time: representative cities and the 27 EU member states use IANA-style identifiers with the browser or server's Intl rules. IANA's latest release checked on 29 September 2026 is 2026d; the installed runtime data version is not exposed. Recent rule changes may lag, so reconstructions pause when a source review is due.
Sky: the solar altitude, azimuth and rise/set estimates use NOAA's published approximate equations and a standard refraction assumption. Clouds, terrain, buildings and artificial light are not observed. Moon, archived weather, lightning, seismic, aircraft and maritime layers await reliable sources and are not silently invented.
Quantum frontier: optical clocks may inform a future definition of the SI second. This page will adopt an internationally defined accessible standard when available; it does not simulate an optical clock.
Source and version ledger
Check the authority chain.
- NPL NTP serviceUTC(NPL) source for a future disciplined host; no connection claimed today.
- BIPM time metrologyInternational UTC/TAI definitions, Circular T and laboratory contributions.
- BIPM SI secondCaesium-133 frequency of 9,192,631,770 Hz exactly.
- IERS Bulletin C 726 July 2026 · TAI−UTC +37 seconds; no leap second at end of December 2026. Review due January 2027.
- IERS historical offsetsLeap-second steps from 1972; pre-1972 formulae are outside this version.
- IANA Time Zone Database2026d checked 29 September 2026; this runtime's embedded rules version is unknown. Review due 29 October 2026.
- NOAA solar equationsApproximate solar reconstruction; observations and forensic authentication require separate evidence.