If you can predict the correction with good accuracy, why wouldn't you just fix the address on the backend? The only reason I can think of is to avoid spamming someone else in case of a wrong guess. But for popular domain name spelling errors, that should be almost never.
What is someone actually has a domain that is similar to a popular one? They would never actually be able to enter their email since it would constantly be "corrected" to the wrong address.
Comments
If you can predict the correction with good accuracy, why wouldn't you just fix the address on the backend? The only reason I can think of is to avoid spamming someone else in case of a wrong guess. But for popular domain name spelling errors, that should be almost never.
"Almost never" is not good enough when you silently send someone's sensitive files to the wrong person.
What is someone actually has a domain that is similar to a popular one? They would never actually be able to enter their email since it would constantly be "corrected" to the wrong address.
That would be an awful suggestion. What would this poor chap do? http://gail.com/
Do both? I'd personally like to know if/when I enter my email address incorrectly.