Audit + initial DMARC setup
Diagnostic of current DNS, publishing of the DMARC record at p=none correctly formed, RUA and RUF mailbox configuration, validation against major mailbox providers within 48 hours.
People who sell DMARC usually leave you in p=none, which is seeing the problem without solving it. Our job is to walk you from monitoring to enforcement (p=quarantine, then p=reject) over nine to eighteen months, without blocking legitimate email from employees, CRM, payroll or vendor portals. When we hit enforcement, we add BIMI so your verified logo shows in Gmail, Yahoo and Apple Mail.
The latest EasyDMARC report analyzes 1.8 million global domains with three snapshots taken during 2023, 2025 and early 2026, which gives granularity enough to distinguish nominal adoption from effective implementation with real enforcement. The findings are stark and useful for understanding why publishing a DMARC record is not the same as being protected. About half of the top 1.8M have a DMARC record published. Only nine percent combines enforcement (p=quarantine or p=reject) with RUA reporting configured, which is the only configuration that really protects.
of global domains have no effective DMARC protection (1.15M analyzed, April 2026)
have partial coverage via p=quarantine or gradual rollout
have complete protection with p=reject at one hundred percent
configure enforcement plus RUA reporting (the only combination that really protects)
The gap between Fortune 500 and Inc. 5000 explains the pattern. Big corporations reached 95% adoption and over 80% in enforcement. Mid-market companies remain mostly parked at p=none, observing spoofing without acting. The operational difference: Fortune 500 has dedicated email security teams; mid-market typically has a provider that published the record and forgot.
Mailbox providers are no longer waiting. Google and Yahoo require DMARC for bulk senders since February 2024. Microsoft (Outlook, Hotmail, Live) rejects non-compliant senders since May 2025. Gmail escalated from soft warnings to active SMTP-level rejection in November 2025, which means a bulk email without DMARC enforcement no longer even enters the receiver filter system: it bounces first. That is the operational reality that determines deliverability today in Panama as much as in Boston.
The behavior depends on which DMARC policy you have published. Tap a policy to see the flow of a typical spoofing attack and how many emails would be blocked daily with an estimated base of 50,000 sends.
Attacker tries to send emails pretending to be yourdomain.com
Numbers estimated for a mid-volume Panama domain with a 50K contact base. The real spoofing rate is measured in RUA reports during the first month of monitoring.
Moving an active domain straight from p=none to p=reject without going through intermediate phases silently blocks legitimate email until the first client calls angry about not getting the monthly invoice. That happens every time because no team knows 100 percent of the services that send email on behalf of the domain: CRM, payroll, HR providers, marketing tools, web forms, ticketing systems, monitoring that sends alerts. Each one needs SPF or DKIM correctly aligned before raising enforcement, and the complete inventory only emerges when RUA reports start showing traffic from IPs nobody recognizes.
Pure monitoring. We receive aggregated RUA reports from Gmail, Yahoo, Microsoft. We identify each legitimate sender. We document in a spreadsheet with a technical owner for each one.
10% of unauthenticated traffic goes to spam. We verify no critical legitimate mail gets lost. If a sender breaks, we fix it before raising the percentage.
100% of unauthenticated traffic goes to spam. Final verification that alignment is stable above 95%. Without skipping this check there is no clean path to reject.
Full block. The receiving server drops malicious email before delivering it. Continuous monitoring to detect new legitimate senders that come in after.
This is the real DNS record published at the end of phase 04 for a domain that also runs BIMI:
; --- DMARC in full enforcement --- _dmarc.yourdomain.com. 3600 IN TXT "v=DMARC1; p=reject; pct=100; rua=mailto:dmarc-rua@yourdomain.com; ruf=mailto:dmarc-ruf@yourdomain.com; adkim=s; aspf=s; fo=1" ; --- BIMI with VMC to show logo in Gmail --- default._bimi.yourdomain.com. 3600 IN TXT "v=BIMI1; l=https://yourdomain.com/bimi/logo.svg; a=https://yourdomain.com/bimi/cert.pem" ; --- SPF and DKIM supporting enforcement --- yourdomain.com. 3600 IN TXT "v=spf1 include:_spf.google.com include:_spf.mailgun.org ip4:200.46.X.0/24 -all"
BIMI only works when DMARC is in enforcement (p=quarantine or p=reject). It is the visual reward for the migration work: your verified logo appears next to the sender in Gmail, Apple Mail, Yahoo, Fastmail, AOL. It does not appear in Outlook or Microsoft 365 yet, because Microsoft has not joined the standard.
The measurable impact is real. Red Sift and Entrust studies document +90% lift in consumer trust when seeing the verified logo, +4-6% open rate, +80% click-through rate, +44% brand recall. For a Panama operation with B2C base in Gmail and B2B with Apple Mail, BIMI pays back the certificate cost in a few months.
Choosing the certificate type is not trivial. Three options, each with a distinct profile.
| Self-asserted (no certificate) | CMC (recommended mid-market) | VMC (enterprise + trademark) | |
|---|---|---|---|
| Annual cost | $0 | $650 — $1,100 | $749 — $1,688 |
| Trademark required | No | No | Yes |
| Gmail (logo) | Does not show | Shows | Shows |
| Gmail blue checkmark | No | No | Yes |
| Apple Mail (iCloud, iOS) | No | Yes | Yes |
| Yahoo Mail · AOL · Fastmail | Yes | Yes | Yes |
| Outlook · Microsoft 365 | Not supported | Not supported | Not supported |
| Provisioning time | 1 — 3 days (DNS only) | 1 — 3 weeks | 2 — 4 weeks |
| Ideal for | Testing, secondary domains, Yahoo-heavy | Panama mid-market with mixed Gmail+Yahoo+Apple base | Enterprise with active trademark and massive B2C base |
For Panama companies with regional base, the default recommendation is CMC. The difference between CMC and VMC is the Gmail blue checkmark, real value but not decisive for most campaigns. The savings from not needing an active trademark offset losing the checkmark, especially if your trademark plan is in process or not a priority. For clients with a registered mark and high B2C Gmail volume, VMC has clear ROI because the checkmark moves measurable engagement metrics.
Diagnostic of current DNS, publishing of the DMARC record at p=none correctly formed, RUA and RUF mailbox configuration, validation against major mailbox providers within 48 hours.
Aggregated RUA reports parsed with parsedmarc plus Elasticsearch, custom Grafana dashboard showing identified senders, alignment rate by source, detected spoofing volume, month-over-month trends.
Four-phase plan (none → quarantine pct=10 → quarantine pct=100 → reject) with human validation between each step. Coordination with your IT team and SaaS providers (CRM, payroll, marketing).
Full BIMI setup with CMC or VMC based on your case. Coordination with DigiCert or Entrust. Preparation of SVG Tiny PS conforming to spec. PEM hosting. Publishing of the BIMI DNS record.
Automated alerts on Slack, Telegram or WhatsApp Business when a new unauthorized sender appears, when alignment rate drops, when detected spoofing spikes, or when the VMC certificate approaches expiration.
Monthly report written by a human explaining what happened with your authentication: new senders detected, gaps remediated, next steps. Not an auto-generated PDF: someone reads your dashboards and explains what matters.
The initial technical audit is free. We calibrate the tier after reviewing your current DNS and understanding how many real domains you operate (subdomains count).
1 domain · monitoring + reports.
Up to 5 domains · BIMI with CMC included.
Unlimited domains · managed VMC.
"I already have SPF and DKIM published. Do I really need DMARC?"
SPF and DKIM authenticate the sender. DMARC is the layer telling receivers what to do when those checks fail. Without DMARC, the receiver takes generic decisions (typically delivery with warning). With DMARC in enforcement, the receiver drops or marks per your choice. One extra critical point for bulk senders: since February 2024 Google and Yahoo require DMARC for senders over 5,000 emails per day. Without DMARC enforcement there is already measurable deliverability impact, not just phishing prevention.
"If I go to p=reject I will block legitimate email from my employees or vendor portals."
That is exactly the risk if you skip phases. That is why correct migration takes 9 to 18 months. You start at p=none with monitoring for 60-90 days to identify all legitimate domain senders (CRM, payroll, marketing tools, ATS, vendor portals, monitoring). Each one requires SPF or DKIM correctly aligned. When you reach 95-98% stable alignment for 30 days, move to p=quarantine with pct=10. Then pct=50, then pct=100. Only after quarantine 100% stable for 30 days do you move to reject. Any provider that does not respect this timeline breaks legitimate email. That is the line between a vendor who knows and a vendor who improvises.
"I have had p=none for two years and nothing visible happened. Does it really matter to move forward?"
p=none is seeing the problem without solving it. RUA reports show how many emails spoof your domain monthly (typically between 200 and 50,000 for mid-volume Panama domains). Those emails land in your customers, vendors and employees inboxes as if they came from you. Successful phishing from your domain can generate financial fraud reputationally attributable to your company. There is another operational reason: if you send over 5K emails daily from the domain, p=none already impacts your deliverability with Google and Yahoo since February 2024.
"There are free DMARC services. Why pay managed?"
Free dashboards do the job. What costs is not the dashboard, it is the monthly human work: reading XML reports, identifying new senders, coordinating fixes with the end-client IT team, deciding when to raise pct, communicating gaps to non-technical leadership. For 1 domain with a simple stack the free services may be enough. For 3+ domains with heterogeneous SaaS (typical Panama mid-market company) the monthly human operation exceeds the managed service cost. The real operational difference: we read the reports, you do not.
"My company is Panama B2B, my clients use Outlook. What good is BIMI?"
Honest answer: BIMI provides no visual benefit in Outlook or Microsoft 365 today, those products do not support the standard. Where it does work: Gmail, Apple Mail (iCloud, iPhone, iPad, Mac), Yahoo Mail, AOL, Fastmail. For B2C Panama, Gmail dominates (three of every four personal accounts). For B2B with international clients using Apple Mail, BIMI is a verified-brand signal. For companies with mostly Outlook base, we honestly recommend not investing in BIMI yet and keeping focus on DMARC enforcement, which does deliver cross-provider deliverability.
"Can you monitor domains outside Panama?"
Yes. The service is domain-jurisdiction agnostic. We operate DMARC + BIMI for clients with .com, .com.pa, .net, .org, .co.cr, .mx, LatAm regional and European domains. Operation runs from Panama in GMT-5 hours that cover LatAm and USA. For European clients we coordinate in overlap hours (Panama morning, European afternoon). DMARC report processing contains send metadata without sensitive personal recipient data, which keeps it outside strict Law 81 or GDPR scope for international transfer.
SPF and DKIM authenticate that mail comes from an authorized server and content was not modified. DMARC is the layer tying both together and telling the receiving server what to do if they fail: nothing (p=none), send to spam (p=quarantine) or reject (p=reject). Without DMARC, receivers see the failures but have no instructions from you, so they take generic decisions.
What matters for bulk senders: since February 2024 Google and Yahoo require DMARC for bulk senders. Microsoft since May 2025. Gmail actively rejects since November 2025. Without DMARC, no longer eligible for mass inbox.
That is exactly the risk and why correct migration takes 9 to 18 months. The methodology is:
Any provider that does not respect this timeline will break legitimate email.
Three cost components:
For one brand with active trademark and DMARC already in quarantine, total year-1 cost runs $1,200-$2,000 all-in. For CMC without trademark, $700-$1,100.
p=none is seeing the problem without solving it. RUA reports show how many emails spoof your domain each month (typically between 200 and 50,000 for mid-volume Panama domains). Those emails land in inboxes of your customers, vendors and employees as if they came from you.
Successful phishing from your domain can generate financial fraud reputationally attributable to your company. Second relevant factor: since February 2024 Google and Yahoo do not accept bulk senders without DMARC enforcement. If you send more than 5,000 emails per day from the domain, p=none already impacts deliverability.
Honest answer: BIMI provides no visual benefit in Outlook or Microsoft 365 today, those products do not support BIMI. Where it does work: Gmail, Apple Mail (iCloud, iPhone, iPad, Mac), Yahoo Mail, AOL, Fastmail.
For B2C Panama, Gmail dominates (three of four personal accounts). For B2B with international clients on Apple Mail, BIMI is a verified-brand signal. For regional companies with mixed base, we recommend BIMI with CMC ($650-$1,100/year) instead of VMC ($749-$1,688/year) for better cost-impact ratio.
Technically yes. Postmark Free DMARC, dmarcian Free, Valimail Monitor (free for low volume), MXToolbox free tier. What costs is not the dashboard, it is the human work of reading XML reports weekly, identifying unauthorized senders, coordinating fixes with the IT team, deciding when to raise the pct, and communicating gaps to non-technical leadership.
For 1 domain with simple stack the free services can suffice. For 3+ domains with heterogeneous SaaS the monthly human operation exceeds the managed service cost.
Yes. The service is domain-jurisdiction agnostic. We operate DMARC + BIMI for clients with .com, .com.pa, .net, .org, .co.cr, .mx, LatAm regional and European domains. Operation runs from Panama in GMT-5 hours covering LatAm and USA. For European clients we coordinate in overlap hours (Panama morning, European afternoon).
Compliance: DMARC report processing contains send metadata without sensitive personal recipient data, which keeps it outside strict Law 81 or GDPR scope for international transfer.
Open-source primary stack, complemented with commercial services for specific cases:
Stack choice gets discussed in the technical discovery.
Before proposing any tier we run a technical audit of your current DNS: status of published DMARC record (if any), SPF and DKIM policies alignment, presence or absence of BIMI, detectable spoofing in public logs, deliverability impact risk with Google/Yahoo rules. Report in forty-eight hours. If after you decide not to migrate, you keep the detailed report.