Disify
Flag disposable and throwaway email addresses in one GET
Disify checks an email address or domain and tells you whether it is disposable, whether the domain has valid DNS/MX records, and a confidence score with the signals behind it. Handy for filtering burner addresses out of signup flows. Just append the address to the path and read the JSON.
GET https://www.disify.com/api/email/test@mailinator.com
{
"format": true,
"domain": "mailinator.com",
"disposable": true,
"dns": true,
"whitelist": false,
"confidence": 100,
"role": false,
"free": false
}curl "https://www.disify.com/api/email/test@mailinator.com"const res = await fetch("https://www.disify.com/api/email/test@mailinator.com");
const data = await res.json();
console.log(data);import requests
res = requests.get("https://www.disify.com/api/email/test@mailinator.com")
print(res.json())BROWSER CALLS BLOCKED (NO CORS/HTTPS) — USE THE CURL SNIPPET
/email/test@mailinator.comPROBEDFlag disposable and throwaway email addresses in one GET
/emailEmail — documented GET route.
/email/1Email details by ID (example: 1).
/email?limit=10Email — documented GET route.
/email/search?q=testSearch by query parameters.
We probe a documented GET and expect 2xx JSON — full uptime and health score. Export includes every documented route below.
Stable. No schema drift observed since monitoring began — the response shape has not changed under our checks.
Disify: common questions
Is Disify free to use?
Yes — Disify is a free social & work API. Free tier: Free — limits not published. Whether the free tier allows commercial use is unclear — check the provider docs.
Does Disify need an API key?
No — Disify needs no API key or signup. You can call it straight away; rate limits still apply (30 req/window · 21 remaining).
Can I call Disify from the browser?
Not directly — Disify doesn't send browser-friendly CORS headers, so call it from a server or proxy instead. Copy the curl or Python snippet on this page to get started.
Is Disify up right now?
As of our last scheduled check, Disify is dying with 42.2% uptime over 90 days and a 1075 ms median response. We re-probe it every sweep — the status badge and uptime chart above always show the latest.