Certified email · for people and businessesClear email evidence, from your usual mailbox
mailcerty

See the recipient server response — not just “sent”.

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.

  • ✓Recipient MX and SMTP response
  • ✓250 · 4xx · 5xx tracked
  • ✓Separate timestamped certificate
MCMailCertyMAIL TRACKINGILLUSTRATIVE RECORD
EMAIL / RECORDEmail evidence
SubjectService agreement · review
Recipientcamille@exemple.fr
ReferenceMC-DEMO-0000
RECIPIENT JOURNEY
✓Sending recorded24 sept. · 09:42
✓Server responseSeparate event
…Evidence PDFShown only when observed

Illustrative preview · all names and statuses are fictional.

ONE REFERENCE, DISTINCT FACTS✓Recipient MX and SMTP response✓250 · 4xx · 5xx tracked✓Separate timestamped certificate

PROOF OF EMAIL

The result comes from the response of the server contacted.

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

From the sealed email to the server’s actual reply.

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.

  • Sealed source

    The sent message and attachments retain their integrity references.

  • Observed server response

    Acceptance, temporary deferral and refusal are different outcomes.

  • Separate certificate

    A direct MX acceptance can produce delivery evidence; it does not prove inbox placement or reading.

Explore the evidence file
MailCertyDirect SMTP response · fictional example
SMTP
REFERENCE MC-DEMO-0000

Service agreement

To camille@example.com · 1 attachment

Message sealedSource and attachment linked
09:42
Recipient MX acceptedFictional direct response · SMTP 250
09:43
Human readingNever inferred from SMTP acceptance
Not claimed
Direct-delivery certificate · exampleIllustration
Illustrative mockup: fictional server response, dates and names, with no evidentiary value.

PROOF OF EMAIL — DIRECT SMTP DELIVERY

See what the recipient mail server actually replied.

MailCerty seals the outgoing message, contacts the recipient MX and records the SMTP result. A separate, timestamped delivery certificate follows a direct MX acceptance.

01

Seal the message

Outgoing DKIM + SHA-256 fingerprints

02

Contact recipient MX

Server, IP and SMTP transaction

03

Read the response

250 accepted · 4xx deferred · 5xx refused

04

Retrieve certificates

Sending and delivery PDFs · RFC 3161

SMTP DELIVERY

What each server response means.

The status documents the direct SMTP attempt and does not claim that the message was read.

Recipient MX connection

MailCerty resolves the recipient domain mail server and records the server contacted.

Distinct SMTP outcomes

The direct attempt distinguishes 250 acceptance, 4xx deferral and 5xx refusal.

Sealed message

The message is DKIM-signed; content and every attachment have a SHA-256 fingerprint.

Linked certificates

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

Follow the outcome from acceptance to refusal.

Codes shown below describe the direct MX attempt. A 250 response confirms server acceptance, not inbox placement or reading.

FunctionRecorded factAvailability
Direct SMTP attemptMX server, IP, SMTP reply and timestamp recordedDirect delivery path
250 responseReceiving server accepted the submitted messageAfter DATA
4xx responseTemporary deferral is queued for retryUp to retry limit
5xx responseRefusal is recorded as a failed attemptDirect response
Message and attachment integrityOutgoing DKIM signature and SHA-256 fingerprintsSending certificate
Separate delivery certificateMX reply and transaction extract, timestamped with RFC 3161Direct MX acceptance

FIVE EVIDENCE LEVELS

Choose the journey according to the risk.

The interface makes the difference between transport evidence, controlled access, acknowledgement and identity verification explicit.

CapabilityDiscreet proofNotified copyProtected contentAcknowledgementID Nixa delivery · planned
Recipient notified—✓✓✓Planned
Content kept behind access control——✓✓Planned
Explicit recipient action——AccessAcknowledgementPlanned
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

Here is what MailCerty does in each situation.

Each scenario names the sender’s action, the recipient’s journey and what the evidence file can show.

Send a quote with its attachments

SITUATION

From Outlook, Thunderbird or the MailCerty workspace, the sender deposits the quote and files through the evidence route.

WHAT THE FILE SHOWS

The file links the received message, recipients, attachment fingerprints, deposit time and available server responses. It does not claim the email was read.

Trace a contractual instruction

SITUATION

An instruction is sent with enough context to retrieve the exact exchange later.

WHAT THE FILE SHOWS

One reference links the message, its content, attachments and the timeline of facts actually observed.

Document a customer notice

SITUATION

The team sends a deadline or update from its usual mailbox.

WHAT THE FILE SHOWS

Tracking separates deposit and technical delivery from any later access or acknowledgement, which appears only when the selected mode records it.

CLEAR ANSWERS

Know exactly what is being evidenced.

All frequently asked questions →
What does an SMTP 250 response mean?+

It records technical acceptance by the receiving server contacted. It does not prove inbox placement or reading.

What happens if the server defers or refuses delivery?+

Temporary 4xx replies and 5xx refusals are distinct states; a deferred attempt may be retried.

Is an SMTP response the same as recipient acknowledgement?+

No. SMTP acceptance, content access and express acknowledgement are different facts, shown separately.

MAILCERTY

Start with the evidence level your exchange requires.

The Free plan provides essential email evidence. Business and On-Premise scopes can be reviewed with our team.

View plans ↗Talk to an expert →