Recovery Code Group Format Check
Audit caller recovery-code alphabet/group policy only, format does not establish issued/unused recovery code or entropy.
Description
Recovery-code formatting depends on an explicit alphabet, separator and group lengths.
Recovery-code formatting depends on an explicit alphabet, separator and group lengths.1
Matching that format does not establish issuance, uniqueness or cryptographic randomness. Use Recovery Code Group Format Check to evaluate the supplied inputs under the specific model below.
When to use Recovery Code Group Format Check
Use Recovery Code Group Format Check to evaluate the supplied inputs under the specific model below. Choose the intended encoding, alphabet or check and keep the exact character, key and measurement conventions described below.
How to use Recovery Code Group Format Check and understand its results
- Choose the intended encoding, alphabet or check and keep the exact character, key and measurement conventions described below.
- Enter Recovery code, Caller alphabet, Caller group lengths, Caller separator using the field table and validation rules below, then run the tool.
- Read Valid caller recovery format, Observed group lengths and interpret units, signs, ordering and placeholders as explained below.
- If the tool reports an input error, correct that field and rerun. A successful false result, empty match list or unknown-evidence placeholder has the specific meaning described here; check the limitations before applying the result.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| recoveryCode | Recovery code | string | Required; constraints below |
| callerAlphabet | Caller alphabet | string | Required; constraints below |
| callerGroupLengths | Caller group lengths | array of number | Required; constraints below |
| callerSeparator | Caller separator | string | Required; constraints below |
Enter a recovery-code string of at most 16384 characters, a separator exactly one UTF-16 code unit long, a nonempty unique-symbol allowed alphabet of at most 128 units and declared integer group lengths from 1 to 128. The separator must not occur in the alphabet. Split on the exact separator and compare group count, lengths and allowed-symbol membership. Return a format boolean and observed lengths; an ordinary format mismatch is false. No randomness, uniqueness or recoverability is established.
valid = observedGroups match declaredLengths and every nonseparator symbol belongs to allowedAlphabet Field order, units and branch conditions follow the implementation explanation above.
| Output field | Meaning | Value type |
|---|---|---|
| validCallerRecoveryFormat | Valid caller recovery format | boolean |
| observedGroupLengths | Observed group lengths | array of number |
{
"input": {
"recoveryCode": "ABCD-EFGH",
"callerAlphabet": "ABCDEFGHIJKLMNOPQRSTUVWXYZ",
"callerGroupLengths": [
4,
4
],
"callerSeparator": "-"
},
"output": {
"validCallerRecoveryFormat": true,
"observedGroupLengths": [
4,
4
]
}
}Limitations and assumptions
Matching that format does not establish issuance, uniqueness or cryptographic randomness. Apply the exact scope and assumptions described above.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are stated above; extremely large inputs or outputs can also be rejected. These errors differ from successful results such as false, no matches or unknown evidence.
Alternative or Complementary methods
Use WPA Passphrase Length/Charset Check for a related task: WPA input forms can distinguish a printable passphrase from a raw hexadecimal key.
Use TOTP Secret Base32 Padding Check for a related task: Base32 encodes bytes as alphabet symbols with optional format-specific padding.
References
-
Recovery Code Group Format Check — tool.io
Similar or alternative tools
- WPA Passphrase Length/Charset Check
WPA input forms can distinguish a printable passphrase from a raw hexadecimal key.
- TOTP Secret Base32 Padding Check
Base32 encodes bytes as alphabet symbols with optional format-specific padding.