// use case · Ecommerce engineers, fraud and risk analysts, and store owners dealing with card testing, fake accounts or coupon abuse.
Add cheap email signals to your checkout and account fraud checks
Email signals are a cheap, fast input to a fraud decision. Look up the buyer email with skip_enrichment and check_dns: disposable domains, randomized local parts and domains that cannot receive mail are all worth a higher risk score. Feed the result into your existing rules or fraud tool; do not let it decide alone.
The problem
- Card testers create hundreds of accounts with random addresses overnight.
- Order confirmation emails bounce, then the chargeback arrives.
- Our first-order discount gets claimed by the same person over and over.
- Our fraud tool is expensive per transaction and we want to filter the obvious junk first.
How pingutil solves it
- 1
Look up at account creation and checkout
Call /v1/lookup with skip_enrichment: true and check_dns: true. You do not need a company profile here.
- 2
Score the signals
Add risk for verdict.is_spam, a high email_signals.randomness_score, email_signals.domain_looks_random and domain_signals.can_receive_email false.
- 3
Escalate, do not auto-decline
Send high scores to 3-D Secure, manual review or your fraud provider. Keep auto-declines for combinations of signals.
Fields you will use
| Response field | What to do with it |
|---|---|
| verdict.is_spam | Raise the risk score sharply |
| email_signals.randomness_score | Add graded risk for gibberish addresses |
| email_signals.domain_looks_random | Flag throwaway-looking domains |
| domain_signals.can_receive_email | Flag domains with no way to receive mail |
| domain_signals.domain_exists | Catch made-up domains |
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: order.email, skip_enrichment: true, check_dns: true }),
}).then((r) => r.json());
let risk = 0;
if (res.verdict.is_spam) risk += 50;
if ((res.email_signals?.randomness_score ?? 0) > 70) risk += 20;
if (res.email_signals?.domain_looks_random) risk += 10;
if (res.domain_signals && !res.domain_signals.can_receive_email) risk += 30;
if (risk >= 60) await sendToReview(order.id, risk);Compared with the alternatives
Full fraud platforms combine device fingerprinting, IP intelligence, payment history and network data, and they catch far more than any email check. They also cost more per transaction. A practical setup runs cheap email signals first and spends the expensive check only where it matters.
See provider comparisons →Limits to plan for
- No IP, device, phone or payment data. Email is one signal among several.
- No domain age, WHOIS or SPF/DMARC checks, so a freshly registered but working domain looks normal.
- can_receive_email treats a null MX record as mail-capable, so a few domains that refuse mail still pass that check.
Common questions
- Can this replace my fraud provider?
- No. It is a cheap first filter. Use it to catch obvious junk and decide which transactions are worth a deeper, more expensive check.
- Does check_dns slow down checkout?
- It adds a DNS-over-HTTPS lookup the first time a domain is seen. Results are cached for 7 days, so repeat domains are fast.
- What about guest checkouts with Gmail?
- Gmail is category free and not spam by itself. Real Gmail addresses are common in fraud and in honest orders alike, so rely on your other signals there.
Read next
- Guide: Build a simple signup risk score from email and domain signals
Combine verdict, email_signals, domain_signals and mailbox status into one signup risk score with allow, step-up, review and block bands you can tune.
- Guide: Stop referral and promo-code farming at the email step
Catch referral and promo-code farming with disposable detection, Gmail dot and plus normalization you run yourself, and randomness signals, before payout.
- Card testing and fake accounts: where email signals help and where they don't
Card testing is stopped mainly by payment-side controls: rate limits, CAPTCHA, Radar-style rules and 3DS. Email signals help with the fake accounts around it.
- Building a simple email risk score from cheap, reliable signals
A practical email risk score for signups: which signals to use, hard rules vs points, score bands, and how to calibrate it against your own abuse data.
- Checking MX records to see if a domain can receive email
How to tell from DNS whether a domain accepts mail: MX lookups, the implicit MX fallback, null MX, and which DNS errors should never block a signup.