gibberish
The username reads as keyboard mash
Six letters or more with no vowel, or six consonants in a row, and nothing the bundled name lists recognise — deliberately conservative.
- risk weight
- +20
- dataset
- local-part-analysis
- reads from
- is_gibberish
- verdict reason
- none: a score-only signal
What it means
y counts as a vowel to protect names like krzysztof, anything under six letters is never flagged, digit-only usernames are never flagged, and a username the name dictionary recognises is never mash. It is independent of looks_generated: both can fire on one address.
It reads from is_gibberish and comes with no verdict reason.
What to do
Weigh it with the rest: alone it is a hint, beside a young domain or a catch-all it is a pattern.
Example response
{
"email": "[email protected]",
"deliverable": "deliverable",
"is_gibberish": true,
"local_part_pattern": "word",
"risk_signals": [
{
"signal": "gibberish",
"weight": 20,
"dataset": "local-part-analysis"
}
]
}Abbreviated: a real answer carries all 46 fields, listed in the verify-email reference. The risk_signals entry shown is the one this signal adds; the weights of every entry in the list sum to risk_score.
Related
- generated · the username looks machine-made or a placeholder
- alias · the address carries a plus-tag
- All risk signals
- How Spaw computes the risk score
- API reference
markdown version: /docs/signals/gibberish.md