Free tools

RFC 3339 and ISO 8601 Timestamp Validator

Paste timestamps, one per line, to see whether each is RFC 3339, ISO 8601 or neither, and which instant in UTC it names.

Runs in your browserNothing is uploadedNo sign-up

One per line, up to 500. The examples show the cases that break parsers most often.

InputRFC 3339ISO 8601Instant in UTCNotes
2026-11-21T10:15:00ZYesYes2026-11-21T10:15:00.000Z

RFC 3339 date-time

2026-11-21T10:15:00.123456+01:00YesYes2026-11-21T09:15:00.123Z

RFC 3339 date-time

The fraction has 6 digits; JavaScript keeps milliseconds only, so 3 digits are dropped there.

2026-11-21 10:15:00ZYesNo2026-11-21T10:15:00.000Z

RFC 3339 date-time

A space instead of "T" is allowed by an RFC 3339 note for readability, but ISO 8601 and many strict parsers require "T".

2026-11-21T10:15:00NoYes

ISO 8601 extended date-time

Without Z or an offset this is not RFC 3339, which always states the offset.

There is no offset, so this is a local time: the instant depends on the reader's time zone.

20261121T101500ZNoYes2026-11-21T10:15:00.000Z

ISO 8601 basic date-time

Basic format (no dashes or colons) is ISO 8601 but not RFC 3339.

1990-12-31T23:59:60ZYesYes1990-12-31T23:59:59.999Z

RFC 3339 date-time

Second 60 is a leap second. JavaScript's Date and many other parsers reject it or roll it into the next minute.

2026-11-21T10:15:00-00:00YesYes2026-11-21T10:15:00.000Z

RFC 3339 date-time

The offset "-00:00" means the time is in UTC but the local offset is unknown (RFC 3339 section 4.3).

1763720100NoNo2025-11-21T10:15:00.000Z

Unix time in seconds

Unix time is a count, not an ISO 8601 or RFC 3339 string. Seconds vs milliseconds is a common bug between services.

2026-02-29T10:00:00ZNoNo

RFC 3339 date-time

Day 29 does not exist in 2026-02.

05/04/2026NoNo

Not recognised

This is not an RFC 3339 or ISO 8601 timestamp, Unix time or an HTTP date.

Slash dates like 05/04/2026 read as May 4 in the US and 5 April elsewhere; send YYYY-MM-DD instead.

RFC 3339 or ISO 8601

RFC 3339 is a profile of ISO 8601 for timestamps on the internet, and it is what OpenAPI and JSON Schema mean by the date-time format: an API that documents a field that way promises RFC 3339. It is stricter than ISO 8601 in some ways and looser in others:

TimestampRFC 3339ISO 8601Why
2026-11-21T10:15:00ZYesYesThe common form of both
2026-11-21T10:15:00.123+01:00YesYesFractions and numeric offsets are fine in both
2026-11-21 10:15:00ZYesNoRFC 3339 lets applications use a space for readability; ISO 8601 needs T
2026-11-21t10:15:00zYesNoRFC 3339 accepts lower-case t and z
2026-11-21T10:15NoYesRFC 3339 requires seconds
2026-11-21T10:15:00NoYesRFC 3339 requires Z or an offset
20261121T101500ZNoYesBasic format without separators is ISO 8601 only
2026-W47-6NoYesWeek dates are ISO 8601 only

Every check also confirms the date exists: 2026-02-29 fails, 2024-02-29 passes, and hours, minutes and offsets must be in range.

Edge cases that break tests

  • No offset. 2026-11-21T10:15:00 is a local time. JavaScript's Date reads a date-time without an offset as local time but a date alone as UTC, so the same string gives different instants on a laptop in Berlin and a CI runner in UTC. Send Z or an offset.
  • -00:00. RFC 3339 uses it to say the time is in UTC but the local offset is unknown, which is not the same claim as Z or +00:00. Code that compares offsets as strings treats the three as different.
  • Leap seconds. RFC 3339 allows second 60, as in 1990-12-31T23:59:60Z. JavaScript's date format allows seconds 00 to 59 only, and Node.js returns an invalid date for it; other parsers reject it or roll it into the next minute. The tool maps it to the last millisecond of that minute.
  • More than three fraction digits. .123456 is valid, but JavaScript's format has three digits of milliseconds, so the rest vanish and two timestamps a microsecond apart compare equal.
  • Hour 24. RFC 3339 allows hours 00 to 23, but JavaScript reads 24:00:00 as midnight at the start of the next day, so one service's valid input is another's error.
  • Seconds or milliseconds. 1763720100 and 1763720100000 are the same instant counted in seconds and in milliseconds. Mixing the two between services puts dates in January 1970 or tens of thousands of years from now.
  • Slash dates. 05/04/2026 is May 4 in the US and 5 April in most other places. The tool refuses it on purpose.

Testing date handling

Feed these cases to every parser at your system's edges: API request bodies, query strings, CSV imports and log ingestion. For which time zones and dates to run a suite under, see the time zone test matrix builder.

Sources

Get new posts by email.

Occasional email with new Testland posts and plugin releases.

Unsubscribe any time. Privacy policy