Prepare the email
Compose from your MailCerty workspace or connected email client. Add recipients and files, then choose the journey that fits your needs.
Outlook · Thunderbird · MailCerty workspaceChoose the evidence level, send from your usual tool and monitor each event in MailCerty. The recipient needs no account.
Illustrative preview · all names and statuses are fictional.
HOW IT WORKS
MailCerty integrates at sending time, then presents the facts in the workspace. The recipient follows a clear, mobile-friendly journey.
FROM EMAIL TO EVIDENCE
A simple journey for the sender, with a precise record underneath. MailCerty keeps the source message, transport response and recipient action in separate, readable steps.
Choose the journey and send from MailCerty or a supported email client.
Record the response actually returned by the mail infrastructure.
Download the available certificate and inspect the events in one file.
To camille@example.com · 1 attachment
FROM MESSAGE TO EVIDENCE
Keep your usual workflow. MailCerty links the message and its attachments, then shows the events that were actually returned or completed.
Compose from your MailCerty workspace or connected email client. Add recipients and files, then choose the journey that fits your needs.
Outlook · Thunderbird · MailCerty workspaceThe message and its files are linked to one reference. The file separates sending from any response returned by the recipient’s mail server.
One reference · distinct eventsFind the timeline, integrity details and available PDF certificate. An opening or acknowledgement appears only if it was actually observed.
Tracking · attachments · PDF exportEVIDENCE FILE PREVIEW
Each record answers a simple question: which message, which attachments, what technical response and any recipient action?
SHA-256 · 8F2A…91C4SHA-256 · 43D1…0A72Illustrative mock-up: all references, names and fingerprints are fictional.
ONE JOURNEY, CLEAR STATES
The interface explains each recorded fact without confusing relay acceptance, MX response and human reading.
Extensions and dedicated addresses avoid changing tools.
Compose, search and export from MailCerty.
APIs and webhooks connect your own processes.
The journey remains available without a MailCerty account.
WHAT MAILCERTY RECORDS
Availability depends on the selected journey and on facts actually returned by the mail infrastructure or completed by the recipient.
| Function | Recorded fact | Availability |
|---|---|---|
| Original message and headers | Linked to the evidence reference | Every mode |
| Attachment fingerprints | SHA-256 per document | Every mode |
| Sending timestamp | Observed when MailCerty receives the message | Every mode |
| Delivery-server response | Recorded when returned by the receiving infrastructure | When available |
| Protected content access | Successful controlled access only | Protected modes |
| Explicit acknowledgement | Voluntary recipient confirmation | Acknowledgement mode |
| Identity journey | Planned ID Nixa result and separate certificate | Not enabled in production |
| Evidence certificate | PDF timeline and technical references | Every completed file |
| Integrity verification | Fingerprints can be checked against the exported file | Every completed file |
| Workspace tracking | Search, status, quotas and downloads | Account workspace |
FIVE EVIDENCE LEVELS
The interface makes the difference between transport evidence, controlled access, acknowledgement and identity verification explicit.
| Capability | Discreet proof | Notified copy | Protected content | Acknowledgement | ID Nixa delivery · planned |
|---|---|---|---|---|---|
| Recipient notified | — | ✓ | ✓ | ✓ | Planned |
| Content kept behind access control | — | — | ✓ | ✓ | Planned |
| Explicit recipient action | — | — | Access | Acknowledgement | Planned |
| Identity check | — | — | — | — | Planned |
| PDF evidence file | ✓ | ✓ | ✓ | ✓ | Planned |
The ID Nixa MailCerty production integration is not enabled yet. This column describes the target journey only.
REAL-WORLD EXAMPLES
Each scenario names the sender’s action, the recipient’s journey and what the evidence file can show.
The sender chooses a mode for the current message before sending.
The recipient sees only the steps for that mode; the MailCerty workspace groups the resulting events.
The team prepares a send or reviews evidence and status from the dashboard.
Search, timeline and downloads remain attached to the file reference.
An organisation can connect its process to MailCerty through the interfaces available on its plan.
Returned events are added to the evidence file; availability depends on the API and integration actually enabled.
No. You continue using your usual address and mail client.
No. The journey runs in their browser.
Yes. Compatible plans provide API and webhook access.
MAILCERTY
The Free plan provides essential email evidence. Business and On-Premise scopes can be reviewed with our team.