Appearance
Introduction
DISIFY checks email syntax, mail DNS, and disposable-address indicators. Use it in sign-up forms, waitlists, and imports. Core checks work without an account or API key, subject to rate limits and quotas.
What it does
| Capability | Description |
|---|---|
| Disposable detection | Checks known disposable domains, subdomains, and mail servers, plus heuristic signals. |
| Format & DNS validation | Checks syntax and whether mail DNS can be resolved. This does not verify mailbox existence or ownership. |
| Plus-alias detection | Catches temp-mail services that hand out +alias addresses on real Gmail / Outlook / iCloud mailboxes. |
| Confidence scoring | Provides a 0–100 detection score and supporting signals alongside the verdict. |
| Premium checks | SPF / DKIM / DMARC, domain age, inbox provider, deliverability score, and spam-trap detection (Pro tier). |
| Bulk validation | Checks lists of emails or domains, synchronously or as queued jobs. Limits depend on your tier. |
How detection works
The API combines domain checks with per-email detection:
- Format check — syntax validation for the email or domain.
- Domain checks — trusted-provider handling, blacklist matches, patterns, keywords, and entropy signals.
- Mail DNS — MX hostnames and IPs are checked for disposable infrastructure.
- Per-email checks — known base-account matches and alias patterns are evaluated even on trusted providers.
- Result — read
disposableas the final verdict, withconfidenceandsignalsas context. A provider whitelist does not override an individual disposable verdict.
See Confidence Scoring and Detection Signals for the full model.
Base URL
Email, domain, and bulk-validation requests use this base URL:
https://disify.com/api
Single checks return JSON. The bulk result viewer returns JSON progress or a plain-text result list. Public blacklists are plain text at https://disify.com/blacklist/, outside the API base path.
CORS permits anonymous browser requests. Use backend requests for enforced validation and keep API keys server-side. Always check HTTP status before interpreting a result; see Error Handling.
Next steps
- Quick Start — make your first request in seconds.
- Integrate with an AI Agent — a copyable setup prompt and test cases.
- Authentication — API keys and usage tiers.
- API Reference — every endpoint, parameter, and response field.