Fromenance is a communication provenance platform for banks, credit unions, insurers, and utilities. Communication provenance means the institution can state, with a record behind it, whether a specific message was sent to a specific recipient.
By the end of this page you will know the three moving parts and where to go next.
Registration
At send time your application, ESP webhook, or a journal copy tells Fromenance that a message went to a recipient. Only a keyed hash of the address and a fingerprint of the body are stored. Each registration gets a verify code such as KX73-PQ9G that you place in the footer.
Verification
A customer forwards the message to verify@yourdomain.com, which your mail platform redirects to your tenant inbox at Fromenance, or pastes it on yourdomain.com/verify. Fromenance extracts the code, the recipient, and a content fingerprint, matches them against the registry, and answers.
Verdict
Verified, Not verified, or Known fraud, in your voice, from your domain, within seconds. Every non verified submission becomes an indicator set you can export to your SIEM or takedown vendor.
No language model sits on the verdict path. Extraction is regular expressions, MIME parsing, a 64 bit SimHash, and HMAC comparison, so the same input always yields the same verdict.
| Signal | Where it comes from | Strength |
|---|---|---|
| Verify code | The footer, including OCR’d screenshots. Checksummed, so account numbers and order ids do not false match. | Strongest |
| Recipient | The forwarding customer’s address, hashed with your tenant secret and compared to the registered hash | Required alongside the code |
| Content fingerprint | SimHash of the normalized body, Hamming distance 6 or less by default | Confirms the code, or matches on its own with the recipient |
| Headers | DKIM for your sending domains when the customer forwarded as an attachment | When present |
| Indicators | URLs, domains, emails, phone numbers, IPs | Drives Known fraud |
A tenant is live once it has a verified domain, a working redirect rule, and one registered stream. The setup wizard in the admin app walks through the six steps; the quickstart below does the same from the command line.
