What Is This String? Format Identifier

The detector looks for strong markers first: matching PEM or OpenPGP boundaries, parseable JWT or JWE headers, OpenSSL Salted__ bytes, data URIs, structured password hashes, JSON, XML-shaped text, UUIDs, ULIDs, binary strings, hex, Base32, Base64URL, Base64, and selected file signatures after decoding.

A strong structural match means required markers or parseable fields were present. A possible match means the alphabet, length, or byte shape fits, but context is still needed. When several representations are valid, the page keeps the alternatives visible instead of inventing a confidence percentage.

A string by itself usually cannot distinguish encrypted, compressed, random, or undocumented binary data. A PEM label does not validate the object inside it, a JWT shape does not verify its signature, and a file signature does not establish that the complete file is valid or safe. Use the reported evidence as a routing decision, not a security verdict.

1. Inspect one unchanged value and read the evidence for the primary match.
2. Review alternative interpretations when the alphabet or length overlaps.
3. Open the suggested specialized tool without transferring the original input.
4. Verify the value against its source-system documentation before making a security decision.

• OpenSSL AES Decrypt Checker - Inspect a Salted__ envelope, match its recipe, and test decryption locally.
• Base64 Decode - Inspect decoded UTF-8, binary bytes, padding, and file-signature hints.
• Hash Identifier - Inspect marked password hashes and raw digest-shaped values.
• JWT Decode - Read the header and claims from a confirmed JWT structure.
• SAML Decoder - Inspect a copied SAMLRequest or SAMLResponse query container without treating decoding as signature verification.
• Key Inspector - Classify a confirmed PEM or DER key container.
• Hex to ASCII - Decode confirmed hexadecimal bytes as ASCII text.