Base32 §6 (A-Z 2-7)
- Input
- test
- Expected output
- ORSXG5A=
Standard for 2FA and .onion addresses.
base32 rfc 4648 alphabet
RFC 4648 defines three encoding schemes: Base64 (§4), Base32 (§6) and Base32hex (§7). Each Base32 variant has specific uses. This page documents the differences and helps you choose the correct variant.
Standard for 2FA and .onion addresses.
For DNSSEC and lexicographic ordering.
If the other side says RFC 4648 without qualifying, it means the A-Z2-7 alphabet with padding. Use base32hex when the alphabetical order of the encoded text has to follow the numeric order of the data, which is the case for NSEC3 in DNSSEC. Use Crockford when the code will be read and typed by people and you want to catch errors on the spot with the check symbol. Use z-base-32 when the value will be spoken aloud. Picking the wrong one corrupts nothing, but the other side will not be able to decode it.
Base32 §6 uses digits 2-7 (not 0, 1, 8, 9) because: 0 and O are ambiguous, 1 and l are ambiguous. 8 and 9 were excluded to reserve space for 2-7 after the 26 letters, keeping the total at 32. Base32hex §7 uses 0-9 and A-V because the goal is lexicographic ordering, not human typing.
No. It helps explain the scenario and use the tool more safely, but real decisions should consider official sources, full context and qualified guidance when needed.
ABCDEFGHIJKLMNOPQRSTUVWXYZ234567Everything is computed in your browser, including the loaded file and any pasted secret. Nothing is sent to a server.