Is mailfloss API down?
Current status, daily uptime history and troubleshooting for the mailfloss API (Email).
No, mailfloss is up
mailfloss answered our last daily check (Nov 15, 2026, 13:58 UTC) in 2077 ms with HTTP 200.
Checking mailfloss now…
Sending a request from our server.
mailfloss API uptime history
- Uptime
- 100% of 10 checks
- Last check
- Nov 15, 2026, 13:58 UTC
- Response
- 2077 ms · HTTP 200
- Last up
- Now
We check mailfloss's listed URL (https://developers.mailfloss.com) once a day. History started when mailfloss was first checked, so new entries show fewer than 30 days.
mailfloss API not working for you?
- mailfloss needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string.
- A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header.
- If it works from one network but not another, check firewalls, VPNs and regional blocks.
- Check the provider's documentation, status page or social accounts for planned maintenance or a changed endpoint.
Email APIs up at their last check
- 1
Kickbox API
Online · 754 msEmail verification API. A free email API by Powered by Kickbox.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 2
mail.gw API
Online · 602 msAPI for creating temporary email accounts.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 3
mail.tm API
Online · 625 msTemporary Email Service. A free email API by Mail.tm.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 4
StopMailing API
Online · 738 msDisposable email addresses with a free, no-signup REST API.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 5
Vetto API
Online · 1170 msCheck email domains in bulk for disposable providers and dead domains, no key needed.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS
mailfloss API status FAQ
Is mailfloss API down right now?
mailfloss answered our last daily check (Nov 15, 2026, 13:58 UTC) in 2077 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether mailfloss is responding at this moment.
How do you check whether mailfloss API is up?
Once a day our checker requests mailfloss's listed URL (https://developers.mailfloss.com) and records whether it answers within 15 seconds. Answers like 401 (needs a key), 403 (blocks bots) or 429 (rate-limited) count as up, because the server responded. The listed URL is often the documentation page, so an API endpoint can occasionally fail while its docs stay up.
How reliable is mailfloss API?
mailfloss answered 100% of our last 10 daily checks. Above 99% is excellent for a free API; below 95% means you should cache responses and keep a fallback ready.
What can I use if mailfloss API is down?
Free Email APIs that were up at their last check include Kickbox, mail.gw, mail.tm. See the full list of mailfloss alternatives for a comparison.
Why does mailfloss API work for others but not for me?
mailfloss needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string. A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header. If it works from one network but not another, check firewalls, VPNs and regional blocks.