Nil UUID – Is 00000000-0000-0000-0000-000000000000 Valid?

Local only

Explain VetaTool's explicit recognition of the all-zero nil UUID as a special valid identifier.

36 chars · 1 line

Waiting for input

Valid nil UUID

Special UUID values

Is the all-zero nil UUID valid?

Yes. VetaTool explicitly recognizes 00000000-0000-0000-0000-000000000000 as the special nil UUID and labels it valid with version 0. It is a sentinel value, not a randomly generated UUID v4. This tool is free to use. No account or payment is required.

Last updated

What you can do here

  • Canonical 8-4-4-4-12 UUID validation
  • UUID version inspection
  • RFC 4122 variant checking
  • Nil UUID recognition
  • Uppercase hexadecimal support
  • Browser-local validation

Steps

  1. Paste the all-zero canonical UUID.
  2. Confirm the validator reports Valid nil UUID.
  3. Apply application-specific rules separately if nil UUIDs are not permitted in your domain.

Syntactic validity does not imply application acceptance

The nil UUID has a defined special meaning and VetaTool accepts it deliberately. An API, database column, or domain model may still reject nil as a missing or reserved identifier, which is a separate business-rule decision.

Nil UUID example

All 128 bits are zero and the validator recognizes the special value.

UUID input

00000000-0000-0000-0000-000000000000

Validation result

Valid nil UUID

Common questions

Frequently asked questions

What UUID version is the nil UUID?

VetaTool reports the special nil UUID with version 0.

Does valid nil UUID mean my API must accept it?

No. The validator reports UUID structure; application rules can separately forbid nil identifiers.

Debugging a specific UUID issue? Browse UUID troubleshooting.