Accuracy and transparency
Calculation and Editorial Methodology
How the site produces current answers, handles edge cases, chooses sources, and communicates uncertainty.
Current date and time
Date-sensitive pages render a UTC answer on the server so the core result exists in the initial HTML. In the browser, the page updates the display from the visitor’s device clock and local time zone. UTC is used as the stable server reference; the local label is shown when the answer has been rebased for the visitor.
A device with an incorrect clock or outdated time-zone data can produce an incorrect local result. Critical deadlines should be checked against the responsible organization or jurisdiction.
Calendars, day counts, and ISO weeks
Modern civil-date tools use the Gregorian calendar, including its leap-year rule. Calendar-day differences are calculated from date components rather than elapsed local-midnight milliseconds, avoiding one-hour daylight-saving changes. Inclusive counting is always labeled because counting both endpoints adds one day.
ISO week tools follow the Monday-through-Sunday system in which week 1 contains January 4—and therefore the year’s first Thursday. Near New Year, the ISO week year can differ from the calendar year.
Time zones and daylight saving time
Time-zone conversions use named IANA zones through the browser’s internationalization APIs. The conversion is made for the selected date, because offsets can change during the year. A local time skipped during a spring transition or repeated during an autumn transition is identified rather than silently treated as an ordinary time.
Time-zone laws change. Browser and operating-system updates supply the underlying rule data, so old devices may not know the newest legal changes. The authoritative reference for zone identifiers and releases is the IANA Time Zone Database.
Julian and ordinal dates
The site separates ordinal day-of-year codes from astronomical Julian Day Number, Julian Date, and Modified Julian Date. Shortened ordinal years are inherently ambiguous across decades; an interpretation must state the assumption it uses.
A manufacturer lot code is not assumed to be a date. Brand, plant, package, and country can use different layouts. A page only describes a brand-specific grammar as documented when a current first-party source supports it, and no production-code conversion is used to declare a product safe or to invent a best-by date.
Sources, review, and corrections
Primary standards, public agencies, standards bodies, and manufacturers are preferred. Secondary sources may help explain a topic but should not override a primary specification. Publication and update dates reflect substantive editorial work, not an automated freshness change.
When a calculation changes, representative boundary cases are tested before release. Corrections that affect user results are prioritized. Report a problem through the contact page with the URL, inputs, expected result, actual result, time zone, and browser when relevant.