Reported mail with evidence NOM-151
Prove what you sent, when and What happened.
Mailack and keeps technical evidence of each consignment sealed with a constancy NOM-151 That any third party can check.
- Constance of PSC Codex
- Infrastructure in Mexico
- Reportable by third parties
A message tour
What's wrong with a registered email, step by step.
Pulse a step or reproduce the path. To the right light the facts that Mailack can prove as they occur.
Your system sends message
Your system sends the mail to Mailack by APIEach shipment has a unique key, so a reattempt never doubles.
The following are registered: Application acceptedActs that can be shown
"Delivery" means that the recipient's server accepted the message and does not mean "read."
Scope of evidence
What proof? Mailackand No.
Clarity from the start prevents misunderstandings with customers, legal areas and authorities.
Contenido exacto
What did the message say, Byte by Byte, by his fingerprint.
Issuer
When it was issued, and the time of seal of constancy.
Acceptance at delivery
That the recipient's server accepted the transmission with its literal response.
surrender or rejection
The technical outcome with the DSN notice archived as well.
Integrity in time
That the evidence didn't change from seal.
Reportable by third parties
Any person checks the test without dependent on Mailack.
Each fact has its own record, caught at the time it happens. If there's no record, Mailack He doesn't say so.
Live check
Change a letter and See what's up.
Proof with example data that calculates real SHA-256 prints in your browser. Edit the message: the print changes and the path no longer reaches the sealed root.
1. A certified message (editable)
Finger SHA-256 from message
2. Test results
Sealed root (sign of example)
3. Window evidence tree (8 messages)
Examples. Mailack The complete canonical message and the root are sealed with a constancy NOM-151 and PSC Codex. To check a actual test use mailack.com / verify.
Choose your scheme
Three questions, a recommendation.
Answer as per your operation. The recommendation is oriented and a person from JAAK confirms the scheme with you.
Do you need a record? NOM-151 by message?
How much e-mail do you send a month?
Do you require dedicated IP, SLA or strict regulation?
Certificate
For legal, compliance, payroll and collection areas with legal impact messages.
- The whole Transactional thing.
- Merkle and constancy sealed NOM-151 and PSC Codex
- Proof bundle downloadable and covered attachments
- Optional dedicated IP
Value by volume
Request quoteCustomer's Portal
Check and manage your account in a single place.
The portal serves to consult and manage and text sending is integrated by API from their systems.
Contributions, indicators and start-up guide
- Getting-started guide in three steps: create an API key, verify a domain and send the first message.
- Assessment of the monthly (UTC) of certificates and of regular, in independent bags.
- Indicators of messages entered, delivered, bounced and sealed NOM-151.
For IT and engineering equipment
The API, To detail.
Sending via API, tracking via webhooks and error codes, as your team will see them.
It activates the technical view to see the example code, batch calculation, states, events and error code.
Prove with his message.
Match a technical demo and check the complete path: sending, evidence, monitoring and verification.
- hola@mailack.com
- mailack.com
- mailack.com / es / docs
The constancy does not prove that a person has read the message.