# 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](https://docs.disify.com/guide/rate-limits.md).

## What it does

| Capability | Description |
| --- | --- |
| **[Disposable detection](https://docs.disify.com/api/signals.md)** | Checks known disposable domains, subdomains, and mail servers, plus heuristic signals. |
| **[Format & DNS validation](https://docs.disify.com/api/email.md)** | Checks syntax and whether mail DNS can be resolved. This does not verify mailbox existence or ownership. |
| **[Plus-alias detection](https://docs.disify.com/api/plus-alias.md)** | Catches temp-mail services that hand out `+alias` addresses on real Gmail / Outlook / iCloud mailboxes. |
| **[Confidence scoring](https://docs.disify.com/api/confidence.md)** | Provides a 0–100 detection score and supporting signals alongside the verdict. |
| **[Privacy forwarding](https://docs.disify.com/api/forwarding.md)** | Paid plans detect known privacy aliases separately from disposable mail and include optional rejection controls. |
| **[Premium checks](https://docs.disify.com/guide/premium-features.md)** | SPF / DKIM / DMARC, domain age, inbox provider, deliverability score, and spam-trap detection (Pro tier). |
| **[Bulk validation](https://docs.disify.com/api/bulk.md)** | Checks lists of emails or domains, synchronously or as queued jobs. Limits depend on your [tier](https://docs.disify.com/guide/authentication.md). |

## How detection works

The API combines domain checks with per-email detection:

1. **Format check** — syntax validation for the email or domain.
2. **Domain checks** — trusted-provider handling, blacklist matches, patterns, keywords, and entropy signals.
3. **Mail DNS** — MX hostnames and IPs are checked for disposable infrastructure.
4. **Per-email checks** — known base-account matches and alias patterns are evaluated even on trusted providers.
5. **Result** — read `disposable` as the disposable verdict, with `confidence` and `signals` as context. A provider whitelist does not override an individual disposable verdict.

See [Confidence Scoring](https://docs.disify.com/api/confidence.md) and [Detection Signals](https://docs.disify.com/api/signals.md) 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](https://docs.disify.com/api/bulk.md) returns JSON progress or a plain-text result list. Public [blacklists](https://docs.disify.com/resources/blacklists.md) 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](https://docs.disify.com/api/errors.md).

## Next steps

- [Quick Start](https://docs.disify.com/guide/quickstart.md) — make your first request in seconds.
- [Integrate with an AI Agent](https://docs.disify.com/guide/agents.md) — a copyable setup prompt and test cases.
- [Authentication](https://docs.disify.com/guide/authentication.md) — API keys and usage tiers.
- [API Reference](https://docs.disify.com/api/email.md) — every endpoint, parameter, and response field.

Source: https://docs.disify.com/guide/introduction.html