EmailDesk provides a verifiable live health endpoint for current application and primary-database reachability. No historical uptime percentage is claimed.
Reviewed: July 29, 2026The health endpoint runs a primary-database ping. It returns a small JSON response and disables caching so the result reflects that request.
Use the endpoint itself for the current result rather than relying on a status copied into this static page.
A successful response does not verify every customer mailbox, Postfix or Dovecot operation, background worker, DNS record, API credential, SMTP gateway, WHM server, external provider, or recipient system.
It also does not establish historical uptime, message delivery, inbox placement, incident resolution, or compatibility with a particular client or integration.
Queued, gateway-accepted, rejected, deferred, bounced, Spam/Junk, and unknown outcomes are message-specific evidence. They are not represented by the application health endpoint.
Review EmailDesk history and the applicable provider or recipient evidence before deciding whether a message needs correction or a safe retry.
Existing customers should sign in and open a support ticket with the affected workspace, time, route or feature, and relevant EmailDesk identifiers.
Do not include passwords, API keys, SMTP credentials, mailbox app passwords, WHM tokens, or unnecessary message content.