Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

DNS validation fallacy #22

Closed
msigley opened this issue Jun 21, 2020 · 2 comments · Fixed by #23
Closed

DNS validation fallacy #22

msigley opened this issue Jun 21, 2020 · 2 comments · Fixed by #23

Comments

@msigley
Copy link

msigley commented Jun 21, 2020 •
edited

It is perfectly valid for a domain to not have an MX record but have a valid A record instead and receive email. Its definitely not best practice but it follows the spec for email delivery.

I wrote a similar PHP library in the past and handled this issue and bad dns providers who return results for all A record look ups. Feel free to reference it to fix this issue.

https://github.com/msigley/mailcheck-php/blob/b9e8003c59ea7d542100b6ba991676ea69220b62/mailcheck.php#L177
@chris001
Copy link

True. The official (RFC specified) fallback for no MX record in the zone, is the A record.

@daveearley
Copy link
Owner

Thanks for the info @msigley! I'll update the code to reflect this

daveearley added a commit that referenced this issue Jun 21, 2020
@daveearley
Check for DNS A/AAA records (closes #22)
4b29c05
@daveearley daveearley mentioned this issue Jun 21, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Check for DNS A/AAA records daveearley/Email-Validation-Tool
3 participants
@daveearley @chris001 @msigley