Signed PDF certificate
Affidavit summarising the captured content, hash, and timestamp.
To certify an email as legal evidence, capture it in webmail with a Browser Session or upload the original .eml source file as a File certificate. The signed PDF binds the message to a qualified RFC 3161 timestamp — much harder to dispute than a forwarded copy or screenshot.
Email evidence is challenged more often than any other digital evidence type.
Affidavit summarising the captured content, hash, and timestamp.
For Browser Session captures, a video of the email opened with headers shown.
Full original message with all headers preserved.
For browser captures, proves which provider served the message.
Qualified independent signature on the captured content.
Manifest, signature, public key, hashes, timestamp request/response.
Open the email in webmail and use a Browser Session to capture the page, or save the source .eml file and use a File certificate. Both produce a signed PDF with a qualified RFC 3161 timestamp bound to the content.
Yes. Capture the message in webmail with full headers shown, or upload the .eml source file. The certificate binds the content's SHA-256 hash to an independent timestamp — any later modification breaks the hash.
The certification process is identical. Gmail, Outlook, Yahoo, Proton, and others all work — the capture records what the webmail interface displayed at the moment of certification.
Yes, but note that forwarding strips the original DKIM signature. If the original sender is reachable, request the original message and certify it directly.
No. This service creates technical evidence artifacts. Legal admissibility depends on jurisdiction and circumstances. Consult qualified legal counsel for advice specific to your situation.
Whether you are sending or proving receipt, a certified email resolves the dispute faster.