Base32Hex Encode Online Tool
Enter the text to be encoded
Triacontakaidecimal is another alternative design for Base 32, which extends hexadecimal in a more natural way and was first proposed by Christian Lanctot, a programmer working at Sage software, in a letter to Dr. Dobb's magazine in March 1999 as a proposed solution for solving the Y2K bug and referred to as "Double Hex". This version was described in RFC 2938 under the name "Base-32". RFC 4648, while acknowledging existing use of this version in NSEC3, refers to it as base32hex and discourages labelling it as "base32".
Similarly to hexadecimal, the digits used are 0-9 followed by consecutive letters of the alphabet. This matches the digits used by the JavaScript parseInt() function and the Python int() constructor when a base larger than 10 (such as 16 or 32) is specified. It also retains hexadecimal's property of preserving bitwise sort order of the represented data, unlike RFC 4648's base-32 or base-64.
Unlike many other base 32 notation systems, triacontakaidecimal is contiguous and includes characters that may visually conflict. With the right font it is possible to visually distinguish between 0, O and 1, I. Other fonts are unsuitable because the context that English usually provides is not provided by a notation system that is expressing numbers. However, the choice of font is not controlled by notation or encoding which is why it's risky to assume a distinguishable font will be used.
|
Value |
Symbol |
|
Value |
Symbol |
|
Value |
Symbol |
|
Value |
Symbol |
|---|---|---|---|---|---|---|---|---|---|---|
|
0 |
0 |
9 |
9 |
18 |
I |
27 |
R |
|||
|
1 |
1 |
10 |
A |
19 |
J |
28 |
S |
|||
|
2 |
2 |
11 |
B |
20 |
K |
29 |
T |
|||
|
3 |
3 |
12 |
C |
21 |
L |
30 |
U |
|||
|
4 |
4 |
13 |
D |
22 |
M |
31 |
V |
|||
|
5 |
5 |
14 |
E |
23 |
N |
|
||||
|
6 |
6 |
15 |
F |
24 |
O |
|||||
|
7 |
7 |
16 |
G |
25 |
P |
|||||
|
8 |
8 |
17 |
H |
26 |
Q |
|||||