22 RFCs and counting
DMARCguard references 22 RFCs across its protocol implementations
not as marketing decoration, but as implementation guidance
when I started building the SPF flattener, I re-read RFC 7208 three times to get the macro expansion edge cases right
the ARC chain validator follows RFC 8617 to the letter on seal validation ordering
#DMARC #EmailSecurity #RFC #BootstrappedStartup #Engineering
named senders changed everything.
every platform shows you IPs.
I wanted to see names. Mailchimp, Google Workspace, Salesforce, SendGrid. not CIDR blocks.
so I built a sender identification system.
it maps IPs to known ESPs and cloud providers automatically.
when you look at your DMARC report in DMARCguard, you see "Mailchimp sent 4,200 messages, 98% aligned". not a wall of numbers.
the free tier bait-and-switch is killing trust in the DMARC market
I designed DMARCguard's free tier to be permanently useful:
- 7 protocols
- 2 domains
- 30 days retention
enough to help you decide whether it's the right tool for your organization
the pro tier adds:
- 2 more protocols (DANE, ARF)
- $6.9/domain until 10 domains, then $4.9/domain, no punish for growth
- and advanced monitoring
I built DMARCguard because every DMARC tool told me what happened
never what to do
that's the core philosophy I built DMARCguard around:
tell me what to do, not what happened
9+ protocols
28+ free tools
23+ RFCs referenced
no VC funding
no enterprise sales team
just a product built by someone who got tired of translating XML into action items at 2am
Meysam
Scientific World