
Security News
How Enterprise Security Is Adapting to AI-Accelerated Threats
Socket CTO Ahmad Nassri discusses why supply chain attacks now target developer machines and what AI means for the future of enterprise security.
email-validator-dns-provider-rules
Advanced tools
Strict Email Validator with checking DNS MX records and email providers rules in browser!
Examples, that other validators pass:
| invalid email | reason |
|---|---|
| som_e-one@gmail.com | Gmail don't allows "_" and "-" symbols |
| someone@8avymt4v93mvt3t03.com | "8avymt4v93mvt3t03.com" isn't real domain and dont have DNS MX records |
| s!o#m$e%o^n&e@realdomain.com | 99.99% public email providers allow only "a-z","0-9",".","_","-","+" before "@" part |
| someone@hotnail.com | possibility of adding your blocklist of domains and MX domains |
Works in Browser and Node. TypeScript and JavaScript.
Please install NPM package
npm install email-validator-dns-provider-rules
Validation:
import {validateEmail} from "email-validator-dns-provider-rules";
const result = await validateEmail('someone@gmail.com');
if (!result.valid) {
alert(`Your email is invalid: ${result.reasonText}`);
}
You can map result.reasonId with your version of text:
const customReasons = {
[INVALID_REASON_AMOUNT_OF_AT]: 'no @ symbol or too many of them',
[INVALID_REASON_USERNAME_GENERAL_RULES]:
'invalid username before @ by general email rules',
[INVALID_REASON_DOMAIN_GENERAL_RULES]:
'invalid domain after @ by general domain rules',
[INVALID_REASON_NO_DNS_MX_RECORDS]: 'domain after @ has no DNS MX records',
[INVALID_REASON_DOMAIN_IN_BLOCKLIST]: 'email domain is in blocklist',
[INVALID_REASON_USERNAME_VENDOR_RULES]:
'invalid username before @ by domain vendor rules',
};
const result = await validateEmail('someone@gmail.com');
if (!result.valid) {
alert(`Your email is invalid: ${customReasons[result.reasonId]}`);
}
const yourBlocklistDomains = ['somedomain.com', '...'];
validateEmail('someone@gmail.com', {blocklistDomains: yourBlocklistDomains});
You can choose other DNS over HTTPS provider or even create your own
validateEmail('someone@gmail.com', {dohProviderUrl: 'https://your-provider-site/dns-query'});
You also can use this library for double checking on backend side.
In this case you can specify own mxResolver function that uses Node package DNS:
import {resolveMx} from 'dns/promises';
async function nodeResolver(emailDomain: string): Promise<string[] | false> {
try {
let records = await resolveMx(emailDomain);
return records.map(rec => rec.exchange);
} catch (error) {
if (error.message.includes('ENOTFOUND')) {
return []; // empty records treated as invalid
}
return false;
}
}
isValidEmail('someone@gmail.com', {mxResolver: nodeResolver});
FAQs
Strict Email Validator with checking DNS MX records and email providers rules in browser!
The npm package email-validator-dns-provider-rules receives a total of 212 weekly downloads. As such, email-validator-dns-provider-rules popularity was classified as not popular.
We found that email-validator-dns-provider-rules demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Socket CTO Ahmad Nassri discusses why supply chain attacks now target developer machines and what AI means for the future of enterprise security.

Security News
Learn the essential steps every developer should take to stay secure on npm and reduce exposure to supply chain attacks.

Security News
Experts push back on new claims about AI-driven ransomware, warning that hype and sponsored research are distorting how the threat is understood.