- Joined
- Nov 8, 2013
- Messages
- 3,378
- Likes received
- 648
- Thanks received
- 177
You should know if it is salted because the salt values would be stored as well. Alternatively query for duplicate encrypted strings, unless the represented data (car reg.) is unique in which case that won't help.
A sample of one isn't very useful. Post a few more if you can.
It does look like base64 encoding that has been hacked a bit. I did that in Excel VBA to protect my passwords list, took a standard online GNU script and fiddled about with a few lines.
DL13 UHU comes out as QT/xMBEVRUX< in my script unfortunately so not the same hack.
Unless they salt with a constant, or some other field such as date/name/whatever that is not labelled as the salt.You should know if it is salted because the salt values would be stored as well.
Unless they salt with a constant, or some other field such as date/name/whatever that is not labelled as the salt.
Here are a few more...
( again not sure if space has been removed )
AE07 GVD -> 4ZRxfz6IfsY=
PJ56 EDU -> IYE31M+sx5E=
YT51 YZM -> q8EXdgQXoOg=
The system creators are the types to find the first thing on google that they could copy and paste.

$~ base64 -d <<< Mw+w2j5CLBc= | od -An -t x1
33 0f b0 da 3e 42 2c 17
$~ base64 -d <<< q8EXdgQXoOg= | od -An -t x1
ab c1 17 76 04 17 a0 e8
$~ base64 -d <<< IYE31M+sx5E= | od -An -t x1
21 81 37 d4 cf ac c7 91
$~ base64 -d <<< 4ZRxfz6IfsY= | od -An -t x1
e1 94 71 7f 3e 88 7e c6