DMARC Configuration for Aesthetic Practice Subdomains
Published by Practice SRE Engineering · Reading Time: 7 minutes · Field Incident Reference: ISS-001 (`reply.` Subdomain Drift)
Why Your Patient Confirmation Emails Land in Spam: Your office IT provider configured SPF and DMARC for your root domain (`yourpractice.com` on Google Workspace or Microsoft 365). Meanwhile, your marketing agency configured GoHighLevel (LeadConnector) or Mailgun to send consultation confirmation emails from a subdomain like `reply.yourpractice.com`. Without explicit subdomain SPF, DKIM, and `sp=` DMARC alignment, Gmail and Yahoo silently quarantine your pre-consult instructions.
1. The "Two-Domain" Reality of Aesthetic Practices
Modern plastic surgery and med spa practices operate two distinct email channels:
- Staff & Clinical Mail (`@yourpractice.com`): Hosted on Google Workspace, Microsoft 365, or Proofpoint Essentials for coordinator correspondence.
- Automated CRM & Marketing Mail (`@reply.yourpractice.com` or `@mail.yourpractice.com`): Delegated to GoHighLevel / LeadConnector, Mailgun, SendGrid, or PatientNow to dispatch instant consultation confirmations, deposit receipts, and VIP event invitations.
2. The Three-TXT DNS Triad Required for 10/10 Deliverability
To guarantee that every patient receives their consultation confirmation in their Primary Inbox, Practice SRE enforces and monitors the Three-TXT DNS Triad across both the root domain and every active CRM subdomain:
; 1. Root Domain SPF (Google Workspace / M365)
yourpractice.com. IN TXT "v=spf1 include:_spf.google.com ~all"
; 2. Delegated CRM Subdomain SPF (GoHighLevel / Mailgun)
reply.yourpractice.com. IN TXT "v=spf1 include:mailgun.org ~all"
; 3. Root DMARC with Explicit Subdomain Policy (sp=) & RUA Telemetry
_dmarc.yourpractice.com. IN TXT "v=DMARC1; p=quarantine; sp=quarantine; adkim=r; aspf=r; rua=mailto:dmarc@practicesre.com"
3. Common Mistakes That Trigger Gmail & Yahoo Rejections
- Duplicate `_dmarc` TXT Records: When a marketing agency adds a second `_dmarc` record instead of merging with the existing one, DNS resolvers treat DMARC as invalid (RFC 7489 Section 6.6.3), dropping your domain's authentication score to zero.
- Missing `reply.` SPF Record: Relying solely on a CNAME or MX record on `reply.yourpractice.com` without an explicit `v=spf1` TXT record causes strict receivers to flag the Return-Path envelope.
- Exceeding the 10-DNS-Lookup SPF Limit: Stacking `include:` statements for Google Workspace, Microsoft 365, Mailchimp, Constant Contact, Zendesk, and Mailgun on the root domain triggers an SPF `PermError`. Delegating CRM traffic to `reply.` isolates lookup counts cleanly.
4. Continuous Subdomain Drift Monitoring with Practice SRE
DNS configurations rarely stay static. Agencies switch ESPs, domains renew, and IT providers edit zone files. Practice SRE's `EMAIL_DMARC` probe inspects your root domain and all delegated subdomains (`reply.`, `mail.`, `lc.`, `mg.`) every 6 hours, plus verifies live inbox placement via our VIP Seed Inbox trap.
Inspect Your Root & `reply.` Subdomain DMARC Right Now
Enter your practice domain in our Complimentary Passive Front Door Check to verify your root `_dmarc` and CRM subdomain SPF alignment in 30 seconds.
Run Passive Subdomain DMARC Check →