signup-guard
GitHub

Score a sign-up in your browser

signup-guard checks the email and the IP address of a sign-up for throwaway inboxes, typos in common mailbox domains, shared role addresses, datacenter, Tor and relay addresses and too many attempts, and answers allow, review or block with the reasons behind it. This page runs the JavaScript library on the data snapshot of the package. Nothing you type leaves the tab.

Disposable domains
10,274
IP ranges
27,774 from 12 providers, 12,034 IPv4 and 15,740 IPv6
Data snapshot
domains 2026-11-16, IP ranges 2026-11-16
Examples
11, each checked against its test vector
Page built
2026-11-17, Node v22.23.4
Commit
447b8a4
An example from the test vectors, scored when the page was built. Open the scorer

Loading an example

Try it

Pick an example or type your own. The page loads the data snapshot once and scores everything here: pressing the button makes no request, and the email and the IP address stay in this tab.

Each press records one attempt, as a sign-up form would. Press the button a few times with the same input to trip a limit. The counters live in this tab.

Adds email_free_mail for addresses at Gmail, Outlook.com, Yahoo Mail and other free consumer mailboxes. Off by default.

The data snapshot loads when you get here.

Loading the data

10,274 domains and 27,774 IP ranges

Reasons and points

The score is the sum of the points of the reasons. Nothing else goes into it. Below 30 the decision is allow, from 30 it is review, from 70 it is block. A reason with 0 points still appears, as information for your logs.

CodePointsAdded whenHint shown to the user
email_invalid100The address fails the syntax check (one @, dot-atom local part up to 64 characters, host name with at least two labels, ASCII)Check the email address for typos.
email_disposable70The domain or a parent domain is on the disposable list or your blockDomainsPlease use a permanent email address.
email_typo0suggestEmail finds a likely typo of a common mailbox domain; suggestion holds the corrected addressDid you mean (the corrected address)?
email_role10The part before @ is a shared mailbox such as admin, info, support or no-replyPlease use an email address of your own, not a shared team address.
email_free_mail30Only with freeMail: true: the domain belongs to a free consumer mailbox service, or is on your freeMailDomainsPlease use your work email address.
email_normalized0Normalization removed a tag or dots or replaced a domain aliasnone
ip_datacenter40The address is in a cloud or services rangeTurn off your VPN or proxy, or switch to your home or mobile connection, and try again.
ip_tor40The address is a Tor exitPlease sign up without Tor.
ip_cdn15The address is in a CDN edge rangeIf you use a VPN or a privacy service, turn it off and try again.
ip_privacy_relay0The address is an iCloud Private Relay egressnone
ip_not_public0Private, CGNAT, loopback, link-local, documentation or other special-use addressnone
ip_invalid0The IP string does not parsenone
velocity_ip30An ip rule is over its limitToo many attempts. Please try again later.
velocity_network30A network rule (/24 or /64) is over its limitToo many attempts. Please try again later.
velocity_email40An email rule is over its limitToo many attempts. Please try again later.
velocity_<key>30A rule on your own field is over its limit (velocity_other sets the default)Too many attempts. Please try again later.

These are the defaults, and weights and thresholds are options. No network signal blocks on its own: a block needs either a bad email or several signals together. The hint never names a limit or a list, so it is safe to show to the person signing up.

Use it in your sign-up form

Call it on the server when the form is submitted, with the client IP your own proxy reports. The JavaScript and the PHP port take the same input, share one set of test vectors and give the same answer.

Install from npm, Node.js 20 or newer
npm install @moonetix/signup-guard
Count the attempt, then score it
import { assessSignup, VelocityLimiter } from '@moonetix/signup-guard';

const limiter = new VelocityLimiter(); // in-memory: fine for one process, see "Velocity stores" otherwise

async function screenSignup({ email, ip }) {
  const now = Math.floor(Date.now() / 1000);
  const velocity = await limiter.check({ now, ip, email }); // count the attempt before you judge it
  return assessSignup({ email, ip, velocity });
}

const result = await screenSignup({ email: 'Jane.Doe+promo@googlemail.com', ip: '3.5.140.2' });

console.log(result.decision, result.score);
for (const r of result.reasons) console.log(`${r.code} +${r.points}: ${r.message}`);
console.log(result.email.normalized);
Both print
review 40
email_normalized +0: Normalized to janedoe@gmail.com (lowercased, domain alias replaced, plus tag removed, dots removed). Check duplicates against this form.
ip_datacenter +40: 3.5.140.2 is in a datacenter range: Amazon Web Services (cloud, 3.5.128.0/19).
janedoe@gmail.com

Store email.normalized in a column with a unique index and keep sending mail to the address the user typed.

What to do with the decision

Data in the package and on this page: disposable domains as of 2026-11-16 (10,274 domains), IP ranges as of 2026-11-16 (12,034 IPv4 and 15,740 IPv6 ranges from 12 providers). A scheduled job refreshes the snapshot every Monday; the sources and licenses are in data/SOURCES.md.

Maintained by Moonetix, an affiliate network.