byte fidelity probe
Kept on Base Sepolia · 0x483f606498B255112a5CFb02644A4bcCedF908F0
DKIM verified · gmail.com
gmail.com signed this message. The signature was
checked when the message arrived, and the signed bytes are what is on chain. You do not
have to trust this service: save the
original and run it through any DKIM validator.
| from | gmail.com |
| date | 2026-08-19T18:46:57.000Z |
| bytes | 6400 |
| sha256 | 3c8edcf92a522d799a4a005ec2ba1318d3d5f4b534d452a33eae4f7c00c57fa0 |
| lane | whole |
| dkim | pass |
| signed by | gmail.com |
The message
Read back from the chain, 6,400 bytes stored. Original.
One message, two providers, one DKIM signature.
Postmark and Resend each get their own copy of these exact bytes. If the two
stored versions differ, the difference is the provider, not the sender.
Line endings matter here. So does a non-ASCII character: café, Ω, 東京.
This page is disposable. The record is on chain and anyone can serve it from chain data alone.