We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[email protected]
OVH
check-if-email-exists-cli 0.9.1
It appears the response is always "safe" for AOL email addresses.
{ "input": "[email protected]", "is_reachable": "safe", "misc": { "is_disposable": false, "is_role_account": false, "gravatar_url": null, "haveibeenpwned": null }, "mx": { "accepts_mail": true, "records": [ "mx-aol.mail.gm0.yahoodns.net." ] }, "smtp": { "can_connect_smtp": true, "has_full_inbox": false, "is_catch_all": false, "is_deliverable": true, "is_disabled": false }, "syntax": { "address": "[email protected]", "domain": "aol.com", "is_valid_syntax": true, "username": "sadfasd", "normalized_email": "[email protected]", "suggestion": null } }
The text was updated successfully, but these errors were encountered:
I was able to identify the issue. It appears we always use login.yahoo.com for AOL email addresses. We should be using login.aol.com instead.
Sorry, something went wrong.
No branches or pull requests
Email to check
[email protected]
From where did you run check-if-email-exists?
OVH
Version of check-if-email-exists (if running it yourself)
check-if-email-exists-cli 0.9.1
What happened?
It appears the response is always "safe" for AOL email addresses.
Relevant log output
The text was updated successfully, but these errors were encountered: