About us
The people behind DMARCTrust
Two email veterans who got tired of watching organizations fight the same DMARC battle for 18 months. We built the tools we always wished existed.
How we got here
Marc and Florian first met at Mailjet, the Paris-based email platform, back when the whole team fit in one room. Marc was one of the early hires on the infrastructure side, building the systems that handled actual message delivery. Florian came in as an engineer working on developer tools, gave talks at Paris-Web, and was generally the person to ask when something in the email stack wasn't making sense. Different jobs, the same fixation.
After Mailjet, they went separate ways for several years. Marc took on consulting, helping enterprises work through DMARC rollouts across Europe and North America. Florian started a few companies, always gravitating toward the same problem: make technical infrastructure something normal people can operate without a specialist on retainer.
The actual push came from a retail client of Marc's: 18 months into a DMARC rollout, still stuck at p=none. The intent was there. The budget was there. What was missing was a tool that could map every sending source, track every third party, and show a clear path to p=reject instead of just piling on more data. Marc called Florian. The conversation was short. Two weeks later, they started building.
Meet the team
Between us, over 30 years of email infrastructure. Most of it the hard way.
Marc Lelu
Co-founder — Email Deliverability & DMARC Expert
Marc spent his first decade in email infrastructure. Orange first, then an early hire at Mailjet, where he helped build the delivery systems from scratch.
After Mailjet, he went independent. Enterprise clients mostly: teams trying to get DMARC right without breaking their outbound mail in the process. His method is the same every time: map every sending source first, work through third parties one by one, and don't move to p=reject until you're sure nothing legitimate will bounce.
He's done this for domains with 40 sending sources and organizations spread across a dozen subsidiaries. When something breaks in your email authentication, Marc is who you want on the phone.
Florian Le Goff
Co-founder & CTO
Florian joined Mailjet as an engineer and spent several years building developer tools and integrations. On the side, he gave talks at Paris-Web: once on storing personal data without getting the ethics wrong (2011), once on feedback loops in application design (2013). Both turned out to be more relevant to what he'd build later than he expected at the time.
After Mailjet, he started a few companies. The thread running through all of them: make technical tools that don't require a specialist to operate. His usual test for any feature: can someone who doesn't know how email works figure out what's wrong and what to do about it? If not, it's not done.
At DMARCTrust, Florian runs product and engineering. The emphasis on explaining why something is failing, not just flagging it, comes directly from him.
Compliance should not require a consultant
The tools existed. The standards existed. Google and Yahoo had just made DMARC mandatory for bulk senders. And yet the same organizations kept showing up in Marc's inbox after months of trying, dashboards full of data they couldn't act on.
We built DMARCTrust because the right tool would make this achievable for any organization, not just the ones with a dedicated email engineer on staff. Continuous monitoring. Alerts that tell you what to do, not just that something happened. A path to enforcement that doesn't require someone on retainer to interpret. That's the product we wanted. So we built it.
It should not take 18 months and three failed attempts to get to full enforcement.
Visibility without noise
Every sending source visible. No hunting through raw XML or guessing which ESP is failing authentication.
Direction, not just data
The platform tells you what to fix and why it matters. The difference between a dashboard and a tool.
Built by practitioners
Marc ran the consulting. Florian built the tools. The product is what happens when those two jobs finally talk to each other.
Ready to reach p=reject?
Start with the platform, or talk to Marc directly if you need hands-on help.