UUID Timestamp & MAC Extractor
UUID Timestamp & MAC Extractor: Reconstructs 60-bit 100-nanosecond timestamp count since Oct 15, 1582 and extracts 48-bit MAC node address.
About this uuid timestamp & mac extractor
Reconstructs 60-bit 100-nanosecond timestamp count since Oct 15, 1582 and extracts 48-bit MAC node address Runs entirely in-memory using Web Crypto primitives to keep sensitive tokens, certificates, and cryptographic keys secure from third-party interception.
Encoding & cryptographic principles
Parses a UUID's version and variant. For version 1 it reconstructs the Gregorian-epoch timestamp and node field; for version 7 it reads the encoded Unix-millisecond timestamp. Other UUID versions do not expose those fields.
Worked verification example
Scenario: Inspect a canonical version-4 UUID without inventing time or node data.
Sample input:
Processing: Parse five hexadecimal groups, identify version and variant, then derive time only for v1 or v7.
Illustrative output:
Security parameters & input constraints
The tool requires the canonical hyphenated shape but does not verify that a UUID was issued by a trusted source. Only versions 1 and 7 produce timestamps; other versions return null. A decoded timestamp reflects encoded bits, not an independently verified creation time, and malformed/out-of-range dates can fail.
Cryptographic digests, encoded strings, and signatures generated by UUID Timestamp & MAC Extractor should be verified against target authentication systems before production use.
Client-side Web Crypto boundary
Key derivation, hashing, and encoding in UUID Timestamp & MAC Extractor execute in local memory using Web Crypto APIs without remote socket transmission.
Cryptographic specifications & RFC standards
Technical specifications and cryptographic RFC standards governing algorithms and key representations:
- RFC 9562 (Universally Unique IDentifiers - UUIDs)
- RFC 4122 (Universally Unique IDentifier URN Namespace)
UUID Timestamp & MAC Extractor verification · Audit standards
How to use it
- Enter a hyphenated UUID in the 8-4-4-4-12 hexadecimal form.
- Run locally to read its version and variant bits; version 1 and 7 also yield a decoded timestamp.
- Read or copy the JSON with normalized UUID, version, variant, timestamp, and version 1 node field.
Frequently asked questions
Which UUID versions yield a timestamp here?+
The page accepts a trimmed 8-4-4-4-12 hexadecimal UUID, reports its version and variant, and derives an ISO timestamp only for version 1 or version 7. A version-1 result also exposes the final 12-hex-digit node field.
How is a version-1 timestamp reconstructed?+
It combines time_low, time_mid and the low 12 bits of time_hi into 100-nanosecond ticks, subtracts the 15 October 1582 UUID epoch, then converts milliseconds to a JavaScript Date. Version 7 instead reads its leading 48 bits as Unix milliseconds.
What example can I run locally?+
processed 550e8400-e29b-41d4-a716-446655440000 as version 4 with RFC 4122/RFC 9562 variant and returned null timestamp and node. This confirms it does not invent v1 data for that UUID.
Which UUID claims are outside this tool?+
It does not authenticate issuer, prove uniqueness, validate every RFC semantic constraint, recover a MAC for non-v1 values, or guarantee ISO conversion for a time outside JavaScript Date range.