Seal the message
Outgoing DKIM + SHA-256 fingerprints
With direct SMTP delivery, MailCerty contacts the recipient MX and distinguishes acceptance, deferral and refusal. The response joins the sealed message, its attachments and timestamped history.
Illustrative preview · all names and statuses are fictional.
PROOF OF EMAIL
MailCerty records the recipient MX, server IP, SMTP codes and replies. On a direct delivery attempt, a final 250 means that server accepted the message; a 4xx defers it and a 5xx refuses it. This proves neither inbox placement nor reading.
DIRECT SMTP TRANSACTION · EXAMPLE
On a direct attempt, MailCerty records which recipient MX was contacted and its SMTP response. If only an intermediary relay accepts the message, that is reported as relay acceptance—not as recipient-server delivery.
The sent message and attachments retain their integrity references.
Acceptance, temporary deferral and refusal are different outcomes.
A direct MX acceptance can produce delivery evidence; it does not prove inbox placement or reading.
To camille@example.com · 1 attachment
PROOF OF EMAIL — DIRECT SMTP DELIVERY
MailCerty seals the outgoing message, contacts the recipient MX and records the SMTP result. A separate, timestamped delivery certificate follows a direct MX acceptance.
Outgoing DKIM + SHA-256 fingerprints
Server, IP and SMTP transaction
250 accepted · 4xx deferred · 5xx refused
Sending and delivery PDFs · RFC 3161
SMTP DELIVERY
The status documents the direct SMTP attempt and does not claim that the message was read.
MailCerty resolves the recipient domain mail server and records the server contacted.
The direct attempt distinguishes 250 acceptance, 4xx deferral and 5xx refusal.
The message is DKIM-signed; content and every attachment have a SHA-256 fingerprint.
The sending certificate is timestamped. After direct acceptance, a separate delivery certificate reproduces the server response and receives its own RFC 3161 timestamp.
SMTP RESPONSE MAP
Codes shown below describe the direct MX attempt. A 250 response confirms server acceptance, not inbox placement or reading.
| Function | Recorded fact | Availability |
|---|---|---|
| Direct SMTP attempt | MX server, IP, SMTP reply and timestamp recorded | Direct delivery path |
| 250 response | Receiving server accepted the submitted message | After DATA |
| 4xx response | Temporary deferral is queued for retry | Up to retry limit |
| 5xx response | Refusal is recorded as a failed attempt | Direct response |
| Message and attachment integrity | Outgoing DKIM signature and SHA-256 fingerprints | Sending certificate |
| Separate delivery certificate | MX reply and transaction extract, timestamped with RFC 3161 | Direct MX acceptance |
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.
From Outlook, Thunderbird or the MailCerty workspace, the sender deposits the quote and files through the evidence route.
The file links the received message, recipients, attachment fingerprints, deposit time and available server responses. It does not claim the email was read.
An instruction is sent with enough context to retrieve the exact exchange later.
One reference links the message, its content, attachments and the timeline of facts actually observed.
The team sends a deadline or update from its usual mailbox.
Tracking separates deposit and technical delivery from any later access or acknowledgement, which appears only when the selected mode records it.
It records technical acceptance by the receiving server contacted. It does not prove inbox placement or reading.
Temporary 4xx replies and 5xx refusals are distinct states; a deferred attempt may be retried.
No. SMTP acceptance, content access and express acknowledgement are different facts, shown separately.
MAILCERTY
The Free plan provides essential email evidence. Business and On-Premise scopes can be reviewed with our team.