Skip to content

// use case · SaaS founders, backend developers and product engineers who own the signup form, auth hooks or onboarding flow.

Stop fake and throwaway signups before they become accounts

Call /v1/lookup with the signup email before you create the account. Block when verdict.is_spam is true (disposable domain or a randomized local part) and send low_trust addresses such as role accounts to review instead of rejecting them. With skip_enrichment set, the check makes no LLM call and answers in milliseconds.

The problem

  • Half my new accounts never confirm their email and never log in again.
  • Someone keeps signing up with mailinator-style inboxes to get around our limits.
  • Our activation rate looks terrible because bots and test accounts sit in the denominator.
  • A regex says the address is fine, then the welcome email bounces.

How pingutil solves it

  1. 1

    Call the API from your signup handler

    Send the address to POST /v1/lookup with skip_enrichment: true. Run it server-side (or in your auth provider hook) so the API key never reaches the browser.

  2. 2

    Block on verdict.is_spam

    is_spam is true for disposable domains, reputation-flagged domains and randomized local parts. Return a clear message asking for a permanent address.

  3. 3

    Review, do not reject, low_trust

    Role, system and sales-outreach addresses set low_trust without is_spam. Let them in, tag the account, and decide later based on behaviour.

  4. 4

    Optionally confirm the mailbox

    For flows where a bounced welcome email hurts, call POST /v1/verify and use did_you_mean to suggest a fix for typos like gmial.com before the user leaves the page.

Fields you will use

Response fieldWhat to do with it
verdict.is_spamBlock the signup with a friendly error
verdict.reasonLog why it was blocked and pick the error message
verdict.low_trustAllow, but tag the account for review
categoryTell work, webmail and disposable signups apart
did_you_meanOffer a typo correction from /v1/verify
const res = await fetch('https://pingutil.com/v1/lookup', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.PINGUTIL_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({ input: email, skip_enrichment: true }),
}).then((r) => r.json());

if (res.verdict.is_spam) {
  throw new Error('Please use a permanent email address.');
}
if (res.verdict.low_trust) {
  await tagAccount(userId, `review:${res.verdict.reason}`);
}

Compared with the alternatives

The usual starting point is a regex plus a disposable-domain list copied into the repo. That works until the list goes stale and new throwaway domains slip through, and it never catches gibberish addresses on normal domains. Dedicated fraud platforms catch more by adding device and IP signals, at a much higher integration and contract cost.

See provider comparisons →

Limits to plan for

  • New disposable domains are missed until they land in the community list, which pingutil re-syncs weekly.
  • Privacy relays such as Apple Hide My Email or Firefox Relay can be flagged as randomized, so do not hard-block on randomized_local_part alone if those users matter to you.
  • Email signals are one layer. They do not see IP, device or payment data.

Common questions

Should I block disposable emails or just flag them?
Block them on flows that grant something valuable, like a trial or credits. On a newsletter or low-stakes signup, flagging is often enough. verdict.is_spam gives you the signal either way; the policy is yours.
Does the check slow down signup?
With skip_enrichment: true there is no LLM call, so the lookup returns in milliseconds. Mailbox verification through /v1/verify takes longer because it talks to the recipient mail server.
Can I call it from the browser?
Not with your API key. Call it from your backend, a serverless function or your auth provider hook, and keep the key in an environment variable.

Read next