Output will appear here
Click in the output to select all text
Output will appear here
Click in the output to select all text
Generate RFC 4122 compliant UUIDs (v4 random, v1 timestamp, NIL, or batch).
Validate UUID strings and identify version (v1, v3, v4, v5) and variant.
Decode and inspect PEM-encoded X.509 certificates (subject, issuer, validity, SANs).
Validate MAC addresses and reformat between colon, hyphen, and dot-separated notation.
Generate Microsoft Windows GUIDs with braces, registry format, and uppercase options.
This OID helper parses and formats Object Identifiers used in SNMP MIBs, ASN.1 definitions, X.509 certificates, and LDAP schemas, presenting the dot-notation string in a clear, structured way. It's a niche but essential utility for network engineers writing SNMP monitoring configurations, security engineers inspecting certificate extension OIDs, and developers implementing ASN.1-based protocols who need to double-check an object identifier parser output before hardcoding it. Object identifiers like 1.3.6.1.4.1.9 look like arbitrary number strings, but each arc has meaning within a hierarchical registration tree, and this tool helps validate the structure follows correct ASN.1 formatting rules. Rather than manually counting dots and checking arc value ranges, you get instant feedback on whether an OID is well-formed. Parsing happens entirely in your browser with nothing ever transmitted. Enter an OID below to validate and inspect its structure.
An OID is a globally unique, hierarchical string of dot-separated integers used to identify objects, standards, or organizations in protocols like SNMP, LDAP, and X.509 certificates.
The first arc can only be 0 (ITU-T), 1 (ISO), or 2 (joint-iso-itu-t), per the ASN.1 standard.
X.509 certificates use OIDs to identify things like the signature algorithm, extension types, and policy identifiers within the certificate structure.
This is the 'private enterprise' arc under the Internet OID tree, under which organizations register their own enterprise-specific OID branches.
It validates the OID's structural format; identifying the specific meaning of a given OID typically requires consulting the relevant MIB or registry documentation.
Standards don't impose a strict universal maximum, but practical implementations often support well over 128 arcs; extremely long OIDs are uncommon in practice.
This tool works with numeric dot-notation OIDs; symbolic names would need to be resolved against a specific MIB file first.