# Decoder

Paste any opaque value. It names what it looks like and why, then decodes it: Base64 and other layers, number bases, hashes, JWTs, certificates, SIDs, User-Agents and MAC addresses.

Paste any opaque value and the page tells you what it looks like, and why, before it decodes anything. That covers encoded blobs, numbers, hashes, tokens, certificates, SIDs, User-Agents and MAC addresses. If a value fits more than one shape, it offers the others too.

## How to read it

Read the reason line. A guess with its reason is easy to check, and a wrong guess is one button away from the right tab.

Peel layers is for obfuscated payloads. It chains Base64, hex, XOR, gzip and so forth, and shows every intermediate step so you can see where it turned readable.

Treat a pasted JWT or certificate like a secret. The page never saves what you paste here, and it asks before putting one in a share link.

## Tab by tab

### Peel layers

Open it: https://www.cyberkit.win/tools/decoder/?tab=peel

Layered encoding is everywhere in DFIR: a dropped script, a PowerShell one-liner from an EDR alert, a config blob in the registry. It is cheap, reversible obfuscation meant to dodge signatures, and you peel it one layer at a time.

Paste the blob and build a recipe. Each step reads the bytes the step before it produced, so a chain that breaks still shows where and why.

For XOR with no key, leave the key blank. All 256 single-byte keys are tried and the five that give the most printable text are listed. Type the best one into the step to keep going.

Gzip and Deflate use the browser's DecompressionStream. Everything else is a small implementation in this page.

### Number bases

Open it: https://www.cyberkit.win/tools/decoder/?tab=number

Binary, octal, decimal, and hex are four ways to write the same number. Hex wins in computing because one byte is exactly two hex digits, which is much easier to read than eight ones and zeros.

Pick the base your value is in and type. Every other base updates as you go. The math uses big integers, so values past JavaScript's safe-integer limit still convert exactly.

The ASCII row reads the value's bytes two hex digits at a time. If every byte is printable, the number is probably encoded text, which is a quick check on a value pulled from a hex dump or a packet.

### Hash

Open it: https://www.cyberkit.win/tools/decoder/?tab=hash

A hash proves a piece of evidence has not changed since you collected it. It is also the fastest triage step on an unknown file, because you can check it against a threat feed before you ever open it.

Paste text or choose a file and every digest updates. Text is hashed as UTF-8, so a trailing newline gives a different result than the same text without one.

Paste a known hash into Verify and the tool says which algorithm matched. Paste a bare hash into Identify when you have no context for it. Several algorithms share a length, for example MD5 and NTLM, so Identify lists candidates with a confidence level rather than one answer.

SHA family digests use the browser's Web Crypto API. MD5 is computed by a small implementation checked against RFC 1321's own test vectors.

### JWT

Open it: https://www.cyberkit.win/tools/decoder/?tab=jwt

JWTs show up constantly in investigations: a bearer header in a proxy log, a token pulled from browser storage, an API credential in a config file. This decodes one so you can read who it claims to be and when it expires.

Paste the token. The header names the signing algorithm, and the payload holds the claims. Registered claims such as exp and iat are shown as dates.

It decodes only. Checking the signature needs the issuer's secret or key, and this page has neither. A token that decodes cleanly is not proof that it is genuine.

An alg of none means the token carries no signature at all. A server that accepts one is a finding on its own.

### Certificate

Open it: https://www.cyberkit.win/tools/decoder/?tab=certificate

Turn a PEM or DER certificate into fields you can read and pivot on. Operators rotate C2 addresses freely and keep certificates for months, so the fingerprint and serial are often the better lead.

This decodes. It does not verify. There is no signature check, chain or revocation lookup, so a clean decode can still be self-signed or revoked.

Browsers match the hostname against the Subject Alternative Names, not the CN. Read the SAN list.

Pivot on the SHA-256 fingerprint in Censys, Shodan or crt.sh. A self-signed certificate with an odd subject string has tied together whole families of tooling.

### SID and access mask

Open it: https://www.cyberkit.win/tools/decoder/?tab=sid

A Windows access-control entry is a short sentence: a SID naming who, and an access mask naming what they may do. Both read as noise until you split them apart, and both show up in ACLs, in 4663 object-access events, and in the Recycle Bin's folder names.

Paste a SID or a mask, or use a preset. A SID reads S-1-authority-sub-authorities, and the last sub-authority is the RID. RID 500 is the built-in Administrator and 512 is Domain Admins.

A RID of 1000 or above is an ordinary account or group, and only a domain controller can name it. The tool says so rather than guessing.

A mask splits into generic rights in the top bits, standard rights in the middle, and object-specific rights at the bottom. Pick file or registry to read the bottom bits correctly.

### User-Agent

Open it: https://www.cyberkit.win/tools/decoder/?tab=user-agent

A User-Agent is a plain text header the client picks for itself. It is trivially faked, so it is a lead, not an identity. Its real value is spotting a rare, malformed, or inconsistent one in a pile of log lines.

Paste the header value or try a sample. The browser, engine, and OS are best-effort readings of the tokens in the string, and every caveat for this particular string is listed under the table.

Stack-count User-Agents across a proxy or web log and sort ascending. Real browsers collapse into a few common values, so the one-off strings at the bottom are the ones to read.

### MAC address

Open it: https://www.cyberkit.win/tools/decoder/?tab=mac

Every network interface has a 48-bit MAC address, and its structure says a few things before you look up who made the hardware. The first three bytes are the vendor's OUI, and two bits in the first byte say how the address was assigned and who it targets.

Type an address in any common format. The U/L bit says whether it was burned in at the factory or set in software, such as a VM NIC, a VPN adapter, or a phone randomizing its Wi-Fi address. The I/G bit says whether it targets one device or a group.

It does not name the vendor. Look the OUI up in the IEEE registry for that. A locally administered address will not be in the registry at all.

## Related

- [Timestamp Converter](https://www.cyberkit.win/tools/timestamp-converter/)
- [File Hashes](https://www.cyberkit.win/reference/file-hashes/)
- [Decode Range: Encodings](https://www.cyberkit.win/drills/decode-range/?stage=encodings)

Canonical: https://www.cyberkit.win/tools/decoder/

This runs in the browser. Nothing you enter is uploaded.
