npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@isan3/checkemail

v1.0.11

Published

Fast, zero-dependency email validation: syntax, MX/DNS lookup, disposable detection, alias analysis, provider fingerprinting, and confidence scoring.

Readme

@isan3/checkemail

npm version npm downloads License: MIT

Fast, zero-dependency email validation for Node.js. No API keys. No rate limits. Runs entirely offline (except DNS lookups).

Features

| Check | How | |---|---| | ✅ Syntax validation | RFC 5321/5322 compliant | | ✅ Domain existence | DNS A/CNAME lookup | | ✅ MX record check | DNS MX lookup | | ✅ Disposable detection | 9,000+ domains, updated twice a week | | ✅ Provider fingerprinting | 10 providers + custom domain detection via MX/SPF | | ✅ Plus-addressing | [email protected] → ALIAS_CONFIRMED | | ✅ Dot-stripping | [email protected] → canonical [email protected] | | ✅ Role-based detection | 370+ role prefixes (admin@, noreply@, support@, ...) | | ✅ Confidence scoring | 0–100 composite score |

Zero runtime dependencies — uses Node's built-in dns module with Cloudflare/Google DoH fallback. No Redis, no Docker, no API calls.

Install

bun add @isan3/checkemail
# or
npm install @isan3/checkemail

Requires Node.js >= 18.

Not using Node.js? Use Docker

If your backend is Python, Java, .NET, Go, PHP — or anything other than Node — just run the Docker image. It exposes a simple HTTP API that any language can call.

docker run -p 3000:3000 saiakashneela/checkemail

Then call it from any language:

curl "http://localhost:3000/[email protected]"
# Python
import requests
r = requests.get('http://localhost:3000/validate', params={'email': '[email protected]'})
print(r.json())
// Java (any HTTP client)
HttpRequest request = HttpRequest.newBuilder()
    .uri(URI.create("http://localhost:3000/[email protected]"))
    .build();
// .NET
var result = await httpClient.GetFromJsonAsync<object>(
    "http://localhost:3000/[email protected]");

Endpoints:

| Endpoint | Description | |---|---| | GET /validate?email= | Validate an email address | | GET /health | Health check |

Using in the Browser / Plain HTML

Want to validate emails directly on a static website or in client-side HTML without running your own backend?

You can query MX and DNS records directly in the browser via Cloudflare's open DNS-over-HTTPS (DoH) endpoint. It supports CORS out of the box:

<script>
// Query MX records directly from client-side JavaScript (no server required)
async function checkMX(domain) {
  const res = await fetch(`https://cloudflare-dns.com/dns-query?name=${domain}&type=MX`, {
    headers: { 'accept': 'application/dns-json' }
  });
  const data = await res.json();
  const hasMx = Boolean(data.Answer && data.Answer.length > 0);
  return { hasMx, answers: data.Answer || [] };
}
</script>

Combine this with client-side syntax regex, disposable domain matching, and alias detection for an entirely serverless frontend validator.

Node.js Usage

import { validateEmail } from '@isan3/checkemail';

const result = await validateEmail('[email protected]');
console.log(result);
{
  "email": "[email protected]",
  "validations": {
    "syntax": true,
    "domain_exists": true,
    "mx_records": true,
    "is_disposable": false
  },
  "confidence": {
    "score": 65,
    "status": "LIKELY",
    "is_role_based": false,
    "alias_status": "ALIAS_CONFIRMED",
    "canonical_email": "[email protected]",
    "equivalent_domains": ["gmail.com", "googlemail.com"]
  },
  "provider": {
    "id": "GMAIL",
    "name": "Gmail"
  },
  "meta": {
    "latency_ms": 47
  }
}

More examples

// Disposable — exits immediately, no DNS needed
await validateEmail('[email protected]');
// → { confidence: { score: 0, status: 'DISPOSABLE' }, ... }

// Role-based on a custom domain
await validateEmail('[email protected]');
// → { confidence: { is_role_based: true, score: 70 }, ... }

// Custom domain on Google Workspace — detected via MX
await validateEmail('[email protected]');
// → { provider: { id: 'GOOGLE_WORKSPACE', name: 'Google Workspace' }, ... }

// Proton alias — domain normalised to canonical
await validateEmail('[email protected]');
// → { confidence: { canonical_email: '[email protected]', alias_status: 'ALIAS_CONFIRMED' }, ... }

Response Reference

confidence.status

| Value | Meaning | |---|---| | LIKELY | Passes all checks — valid, real, deliverable | | INVALID_FORMAT | Syntax is wrong | | INVALID_DOMAIN | Domain doesn't exist in DNS | | NO_MX_RECORDS | Domain exists but can't receive mail | | DISPOSABLE | Throwaway / temporary email address |

confidence.alias_status

| Value | Meaning | |---|---| | MAYBE_NOT_ALIAS | No alias signals detected | | ALIAS_CONFIRMED | Definitively an alias (Gmail dot trick, plus-addressing on known providers) | | ALIAS_POSSIBLE | May be an alias (e.g. Google Workspace where plus addressing is optional) | | ALIAS_UNKNOWN | Unknown provider, can't determine |

provider.id

| ID | Description | |---|---| | GMAIL | Gmail (gmail.com, googlemail.com) | | GOOGLE_WORKSPACE | Custom domain on Google Workspace (detected via MX) | | MICROSOFT_CONSUMER | Outlook, Hotmail, Live, MSN | | MICROSOFT_365 | Custom domain on Microsoft 365 (detected via MX) | | APPLE_ICLOUD | iCloud, me.com, mac.com | | PROTON | Proton Mail (all domains) | | YAHOO | Yahoo Mail (all regional variants) | | FASTMAIL | Fastmail (all domains) | | ZOHO | Zoho Mail | | YANDEX | Yandex Mail | | GOOGLE_GROUPS | Google Groups mailing list |

How the disposable list works

The bundled list comes from the community-maintained disposable-email-domains repository, which is updated daily by a GitHub Actions bot.

This package fetches the latest list and republishes to npm twice a week (Monday and Thursday) automatically via CI. No action needed on your end — just keep your package up to date with bun update @isan3/checkemail.

What is role-based detection?

A role-based address belongs to a team or function, not a real person: support@, admin@, noreply@, billing@, etc. The package detects 370+ such prefixes.

Important: role-based detection is skipped for consumer domains. [email protected] is a personal email, not a role address.

What are consumer domains?

Consumer domains are personal email providers (Gmail, iCloud, ProtonMail, etc.) as opposed to company/custom domains. The package knows 120+ consumer domains across all major providers and their regional variants.

License

MIT © Sai Akash Neela