BounceShift now returns a did_you_mean correction on every validation, in the API, the dashboard, and the batch results CSV, so mistyped addresses can be recovered instead of silently lost.
Someone signs up, types [email protected] instead of [email protected], and you never hear from them again. It is one of the most common ways a real customer goes missing from a list, and until now BounceShift only told you about it in one narrow case.
Every validation now comes back with a did_you_mean field: the corrected address when the domain is within a character or two of a major provider, and null otherwise. It is in the API response, on the dashboard result, and as a column in the batch results CSV.
This is the part that changed our thinking. A misspelled domain nobody owns has no mail server: you send, it bounces, your ESP records a hard bounce, and you remove the address. Annoying, but the system tells you.
A misspelled domain somebody does own is a different problem. gmil.com and hotmial.com are registered and accept mail. Your message is delivered — to nobody. There is no bounce, no complaint, and nothing in any report to look at. The contact sits in your list looking perfectly healthy, never opening anything, quietly dragging down the engagement rate mailbox providers use to judge you.
You cannot find those from bounce data, because they never produce a bounce. The only way to catch them is to notice the domain is one letter away from a real provider — which is exactly what this field does.
did_you_mean on every /v1/validate/single response.did_you_mean column in the CSV, and a count of how many addresses had a suggestion on the batch page — so you can see it without opening the file.The correction never changes the verdict, and we never validate a different address from the one you sent. The mailbox at the misspelled domain might genuinely exist, and quietly rewriting someone's input would mean you end up mailing an address your customer never gave you.
The right move is to put the suggestion in front of the person who typed it. At a signup form, that is a "did you mean [email protected]?" prompt before they submit — the API answers fast enough to do that inline. For a list you already have, treat the suggestions as contacts to confirm rather than addresses to swap.
No. It is on for everyone, on single checks and batches alike. If you already read result.suggested_correction, that key still works — did_you_mean is simply the first-class version of it, and it now populates in cases where the old key never did.
Want to check a list right now without writing any code? The free email typo finder scans a pasted list and flags which misspellings accept mail instead of bouncing.
Get 100 free validations to test our service. No credit card required.
Start free trial