For CIOs and CISOs
Addresses that only you hold. If anyone else writes to them, you know it.
Today, free of charge: a suspicious message can be read without loading an image, following a link, or opening an attachment. With Version Pro, rolled out in batches, sentinels placed in your tools flag any sender you were not expecting.
Today · free
A suspicious message, read without triggering anything
Submit it just as you received it. None of its links are requested, none of its images loaded: flagging it here sends nothing to whoever sent it, not even confirmation that your inbox exists.
- — Read a suspicious message without triggering anything: identity, authentication, links.
- — Check that SPF, DKIM, and DMARC hold on your mailings, as received.
- — Know where a brand usually sends from, when faced with a message claiming to be theirs.
The security check
- 01 What the message says about itself: what it displays, what is signed, where it comes from, who a reply goes to.
- 02 Where its links lead, unwrapped along the chain, without following a single one.
- 03 What it carries: each attachment, its declared type and its actual type.
- 04 What could not be verified, stated plainly, and what to do now.
Version Pro · an example
Unexpected use of a sentinel
A sentinel is an address you place yourself, in your CRM, your store, or a form, and that no one else holds. If another sender writes to it, that is a fact: dated, with its evidence, with no cause attributed to anyone.
-
3 February
Placed in your CRM
Added as an ordinary contact, with its placement conditions: the system, the segment, the consent. We date the placement, you declare the rest.
-
5 February
First email received
The sentinel becomes active. Every email it receives is measured on arrival and kept as evidence.
-
Every send
Still monitored
It only receives. Every sender that writes to it is compared against the ones you expect: your domains, your group, the vendors you've declared.
-
22 April
Another sender writes to it
An address only you held receives a message from a sender nothing connects to you: an unexpected use, dated, with its evidence.
-
22/04 · 14:37
The alert goes out, with its evidence
The fact, dated; where and when the sentinel was placed; the places to check; the evidence. Never a cause, and only one alert per new sender.
Unexpected use of a sentinel
- Sentinel
- mc-n03@temoin.example
- Placed
- By you, in your CRM, on 3 February
- Sender
- infos.expediteur-tiers.example
- Subject
- Your perks this week
- Where to check
- Vendors, exports and syncs, access, shared lists
- The fact, and the point of entry
- Who wrote, when, and to which sentinel — placed by you, in which system, on what date. We know how the address went in; what made it come out, the alert does not say.
- Where to check
- The providers who send on your behalf, recent exports and syncs from the system where the sentinel is placed, access to that system, lists shared with a partner. Places, never causes.
- One alert per sender
- The first message from an unexpected sender opens the event; later ones attach to it without a new alert. Your own domains and the brands in your group trigger nothing.
Sentinels open up with Version Pro, by batches. Request access →
Version Pro · your tests
What your sentinels test
Commitments chosen from a control plan, never written by hand: each has its own protocol, and its result is replayed from the log.
-
The address serves only you
A sentinel you created yourself, and that you have given to no one else. If it receives mail from a third party, the address has left your systems: attributable by construction, with no form or consent to argue over.
Passive: no action, the sentinel receives · Ongoing
-
Nothing goes out in your name without coming from you
Four signals on every message received: authentication that breaks after holding up, a sudden change of sending platform, a template with no match, link domains never seen before. Received on an address that only you hold, a message claiming to be from you without actually coming from you tells you where the address came from.
Passive: no action, the sentinel receives · Ongoing
Your questions
What we're asked first
Do we need to give you access, a key, a delegation? +
None. We read what an address receives, never your systems: no connector, no token, no service account to approve.
Can a booby-trapped message trigger anything? +
We load no image, follow no link, and open no attachment: the message reads like plain text, and submitting it sends no request to anything it points to.
Where are messages kept? +
The message is written once, exactly as it arrived, never modified, and kept in Europe, read-only. The service is hosted in France.
Who sees what our sentinels receive? +
Version Pro
Your account, and only your account. What a sentinel receives enters no public statistic, no comparison, no ranking.
Is one more address in our CRM a risk? +
Version Pro
It is an opaque address, on a domain reserved for us, that says nothing about its function. It opens nothing and clicks nothing; you know where it is placed, and you remove it whenever you want.
What if a legitimate provider writes to it? +
Version Pro
Declare it: its messages are recorded and set aside, never alerted on. A declaration made after the fact files the event among those set aside, without erasing it.
Start with a suspicious message
It is read free of charge, with no account, and nothing it points to is requested. Sentinels come next, with Version Pro.