Skip to main content
Utilnivo

Everyday Tools

Utilnivo

UUID Lookup

Service UUID lookup: inspect version, variant, and embedded timestamps.

No registration
  • On your device

Browse more in Everyday Tools or all tools.

Private on your device

Your information stays on your device and is not uploaded.

Related tools

Paste a service UUID or any UUID to inspect its version, RFC variant bits, and embedded timestamp for v1 and v7 IDs. Parsing works on your device—there is no public owner registry.

Service UUID lookup usually means inspecting an identifier used by an API, microservice, Windows/COM GUID, or Bluetooth GATT characteristic—not looking up who owns a random UUID on the public internet.

This tool decodes the UUID bits: version, RFC variant, nil detection, and embedded timestamps for time-based versions—so you can confirm whether a service UUID is random (v4), time-ordered (v7), or time-based (v1).

Bluetooth SIG 16-bit assigned numbers are not name-resolved here. Paste the 128-bit form to inspect version and variant; use official Bluetooth docs for assigned service names.

When debugging production IDs, correlate v1/v7 timestamps with logs rather than treating the UUID as a searchable directory key.

How to use this tool

1. Paste a service UUID or other UUID. 2. Run lookup. 3. Read version/variant fields. 4. For v1 or v7, review extracted time if shown. 5. Use UUID Generator when you need new IDs.

Worked example

Example 1: a service UUID that is v4 shows random layout with RFC variant bits. Example 2: a v1 UUID exposes a timestamp you can correlate with log times when debugging old event IDs.

When to use this

  • Inspecting a service UUID from logs, APIs, or config.
  • Checking whether an ID is v1 vs v4 vs v7.
  • Validating pasted IDs before a DB or registry lookup.
  • Teaching RFC 4122 layout quickly.
  • Correlating v1 or v7 timestamps with events.

Common examples

  • Service UUID from an API shows version and RFC variant.
  • v1 UUID exposes timestamp useful near log correlation.
  • Invalid hex or wrong length fails parse with a clear error.
  • NIL UUID 00000000-0000-0000-0000-000000000000 recognized.
  • Mixed-case UUID normalized for field inspection.

Common mistakes

  • Expecting a public “owner” lookup registry.
  • Treating NIL UUID as a real entity id.
  • Assuming all service UUIDs embed timestamps.
  • Confusing Bluetooth 16-bit assigned numbers with full UUIDs.
  • Using lookup instead of generating new IDs.

How it works

Paste a service UUID or any RFC UUID to inspect version, variant, and (for v1/v7) timestamp hints. Does not call a public UUID owner registry—interpretation is local.

Limitations

Results are based on the inputs you provide and may not cover every edge case. This tool is for general use and is not professional advice.

Privacy and file handling

Your data stays on your device and is not uploaded.

Formula or method

Parses 128-bit layout per RFC 4122. Version is the high nibble of clock_seq-related bits; variant bits distinguish RFC vs legacy encodings.

FAQ

Frequently asked questions

What is a service UUID lookup?

It means inspecting a UUID used as a service or API identifier—version, variant, and any embedded timestamp. It does not map a UUID to a company or Bluetooth SIG assigned name.

Which UUID versions show timestamps?

Version 1 and version 7 UUIDs can include embedded timestamps when present. Version 4 (random) service UUIDs do not.

Is my UUID uploaded?

No. UUID parsing works on your device.

What information can UUID lookup show?

Version, variant, and for v1/v7 UUIDs, timestamp-related fields when present. It does not identify who created the UUID.

Is there a global UUID registry?

No public universal registry maps arbitrary UUIDs to owners. Interpretation is based on the UUID bits themselves.

v1 vs v4—what should I use for new service IDs?

v4 (random) or v7 (time-ordered) are common for new identifiers. Use the UUID Generator tool to create them; use lookup to inspect existing values.

Related pages

Page last reviewed: