REGEXVAULTv2.0
Dev & Systems/Log Parsing
Verified Safe

ISO 8601 Log Timestamp Regex for PHP

/^(\d{4})-(0[1-9]|1[0-2])-(0[1-9]|[12]\d|3[01])T([01]\d|2[0-3]):([0-5]\d):([0-5]\d)(?:\.(\d{1,9}))?([+-][01]\d:[0-5]\d|Z)?/

What this pattern does

This page provides a comprehensive, battle-tested regular expression for matching iso 8601 log timestamp, ported and verified for PHP. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your PHP project — whether you're validating in a Laravel validator, a WordPress plugin, or a standalone PHP script.

Php Implementation

Php
<?php
// ISO 8601 Log Timestamp
// ReDoS-safe | RegexVault — Dev & Systems > Log Parsing

define('ISO_8601_LOG_TIMESTAMP_PATTERN', '/^(\d{4})-(0[1-9]|1[0-2])-(0[1-9]|[12]\d|3[01])T([01]\d|2[0-3]):([0-5]\d):([0-5]\d)(?:\.(\d{1,9}))?([+-][01]\d:[0-5]\d|Z)?/');

function validate_iso_8601_log_timestamp(string $input): bool {
    return (bool) preg_match(ISO_8601_LOG_TIMESTAMP_PATTERN, $input);
}

// Example
var_dump(validate_iso_8601_log_timestamp("2024-01-15T10:30:00Z")); // bool(true)

Test Cases

Matches (Valid)
Rejects (Invalid)
2024-01-15T10:30:00Z2024-13-01T10:30:00Z
2024-01-15T10:30:00.123Z2024-00-15T10:30:00Z
2024-01-15T10:30:00+08:002024-01-32T10:30:00Z
2024-12-31T23:59:59.999999999Z2024-01-15 10:30:00
2024-01-15T10:30:0001-01-2024T10:30:00Z

When to use this pattern

This pattern is drawn from the Dev & Systems > Log Parsing category and carries a ReDoS-safe certification. That matters for PHP developers because especially relevant in PHP where PCRE backtracking limits can trigger silent failures on malicious input. RegexVault audits patterns against known backtracking attack vectors, ensuring you have the necessary context before using this regex in a high-stakes production environment.

Common Pitfalls

Logs from different timezones can appear out of order when sorted lexicographically. Normalize all timestamps to UTC before indexing or comparison.

Technical Notes

Groups: 1=year, 2=month, 3=day, 4=hour, 5=minute, 6=second, 7=subseconds, 8=timezone. Subseconds accept up to 9 digits (nanosecond precision used by Go and Rust). Z = UTC.

Have a pattern that belongs in the vault?

Submit it for review — community-verified patterns get credited to your GitHub handle. Free submissions join the queue. Priority review available for $15.

Submit a Pattern