Professional Email on Your Own Domain for a Medical Practice (SPF, DKIM, DMARC) 2027
Set up professional email on your medical practice's own domain in 2027. MX, SPF, DKIM and DMARC in plain English, Gmail and Yahoo rules, and mail app setup.
By ClinikEHR Team
Duration
13 MINSProfessional email on your own domain means your practice sends from [email protected] instead of a free Gmail or Yahoo address. To set it up, you add four kinds of DNS records at your domain registrar. MX tells the internet where to deliver your mail. SPF lists who is allowed to send as your domain. DKIM signs each message so it can't be altered undetected. DMARC tells receiving servers what to do when a message fails those checks. Get them right and patients see your practice name in the From line, and your emails reach their inbox instead of spam.
This guide explains each record in plain English, covers the Gmail and Yahoo sender rules, and shows how ClinikMail walks you through the setup.
Quick Answer
- You need four records: MX (receiving), SPF and DKIM (proving your mail is really yours), and DMARC (your policy for failures).
- Gmail requires every sender to use SPF or DKIM, and to send over TLS. Senders of more than 5,000 messages a day to personal Gmail accounts also need SPF, DKIM and DMARC (Gmail sender guidelines, checked September 2026).
- Yahoo's rules are similar: SPF or DKIM at minimum for all senders, and for bulk senders both SPF and DKIM plus a DMARC policy of at least p=none (Yahoo sender best practices, checked September 2026).
- ClinikMail checks all four records live in a guided DNS wizard, and turns on sending only once all four pass.
Your practice's own domain, set up with a guided wizard
Why a Practice Should Use Its Own Domain
- Trust.
[email protected]tells a patient who is writing.[email protected]could be anyone. - Protection from impersonation. With DMARC in place, receiving servers can reject mail that pretends to be from your domain.
- You keep the address. Staff, providers and email vendors can change, and your domain stays yours.
- HIPAA. Free consumer email can't come with a Business Associate Agreement. A business provider on your own domain can. See Is Gmail HIPAA Compliant?
The Four Records, in Plain English
| Record | Plain-English job | Analogy | What goes wrong without it |
|---|---|---|---|
| MX | "Deliver mail for this domain to this provider" | Your mailing address | You don't receive email |
| SPF | "These servers may send as us" | A guest list at the door | Your mail looks forged and lands in spam |
| DKIM | A digital signature on every message | A wax seal on a letter | Receivers can't tell whether a message was altered |
| DMARC | "If SPF or DKIM fails, do this, and send us reports" | House rules for the bouncer | Spoofers can use your name freely |
MX: where your mail goes
The MX record points your domain at your email provider. Change it and new mail starts going to the new provider. If your domain already has email somewhere else, don't change MX until you're ready to move, or new messages will start arriving in the new system.
SPF: who may send
SPF is a single TXT record listing the services allowed to send email as your domain, such as your mailbox provider and perhaps your booking or newsletter tool. A domain should have only one SPF record. If one already exists, add the new service to it rather than creating a second record.
DKIM: the tamper-proof seal
Your email provider signs each outgoing message with a private key. You publish the matching public key in DNS, usually as a TXT or CNAME record under a "selector" name. Receiving servers check the signature, which shows the message really came from your domain and wasn't altered on the way.
DMARC: your policy and your reports
DMARC is a TXT record at _dmarc.yourpractice.com. It sets a policy for mail that fails authentication:
- p=none: monitor only. Nothing is blocked, but you get reports. Gmail's bulk-sender guidance says the policy "can be set to none," and Yahoo asks bulk senders for "at least p=none."
- p=quarantine: send failing mail to spam.
- p=reject: refuse failing mail outright.
A sensible approach is to start at p=none, read the reports for a few weeks to make sure every legitimate sender passes, then move to quarantine and eventually reject.
Gmail and Yahoo Sender Requirements (Verified)
Google's email sender guidelines (checked September 2026) apply to mail sent to personal Gmail accounts (@gmail.com and @googlemail.com):
- All senders: SPF or DKIM, a TLS connection, valid forward and reverse DNS, and spam rates kept below 0.3% in Postmaster Tools.
- More than 5,000 messages a day: SPF and DKIM, DMARC, alignment between the From domain and the SPF or DKIM domain, and one-click unsubscribe for marketing messages.
Yahoo's sender best practices (checked September 2026) ask all senders for "SPF or DKIM at a minimum" and a spam rate below 0.3%. Bulk senders need both SPF and DKIM and a DMARC policy of at least p=none that passes.
If your mailboxes send fewer than 5,000 messages a day to Gmail, the bulk-sender rules may not apply to you. Setting up all four records anyway is the simplest way to stay deliverable, and it's what a patient's mail provider expects.
Step-by-Step Setup Checklist
- Take stock. List every service that sends email as your domain: mailboxes, booking reminders, newsletters and billing.
- Get the records from your email provider.
- Add them at your registrar (the company you bought the domain from, or your DNS host).
- Wait for propagation. DNS changes commonly take up to an hour.
- Verify in your provider's dashboard.
- Send test messages to a Gmail and a Yahoo address and check they land in the inbox.
- Start DMARC at p=none, review the reports, then tighten the policy.
Moving an Existing Domain Without Losing Mail
Most practices aren't starting from scratch. They already have email on their domain, perhaps with a web host, an old IT provider or a Workspace account set up years ago. A move goes smoothly when you run the new provider alongside the old one before switching anything that affects delivery.
- Create the mailboxes first. Set up every address, including shared ones like
reception@, in the new provider before you touch DNS. Check that each person can sign in. - Add the new provider to your existing SPF record rather than replacing it, so mail from both providers passes during the changeover.
- Publish the new DKIM record. DKIM records use their own selector names, so the new provider's record can sit beside the old one without conflict.
- Pick a quiet time and switch MX. A Friday afternoon or a weekend is usually best for a clinic. From that point new mail starts arriving at the new provider.
- Keep the old account open for a few weeks. Some messages may still arrive there while the change spreads, and you'll want time to copy across any old mail you need to keep for your records.
- Update phones and desktop mail apps with the new settings, then remove the old account from each device.
- Tidy up. Once nothing is sending from the old provider, remove it from SPF and delete its DKIM record.
Common DNS Mistakes That Break Practice Email
- Two SPF records. Adding a second record for a new service instead of editing the existing one can cause SPF to fail for all your mail.
- Forgetting other senders. Your booking system, newsletter tool or billing software may send as your domain too. If they aren't covered, their messages can land in spam, including appointment reminders patients rely on.
- Doubled hostnames. Many registrars add your domain to the end of the name you type. Entering
_dmarc.yourpractice.comin such a form can create_dmarc.yourpractice.com.yourpractice.com. If a check keeps failing, look at exactly what was saved. - Jumping straight to p=reject. A strict policy on day one can block your own legitimate mail from a service you forgot. Start at p=none and tighten once the reports are clean.
- Reports nobody reads. Send DMARC reports to an address someone actually checks, or to a tool that summarizes them.
- A lapsed domain. If the registration expires, email stops. Turn on auto-renew and keep the payment card current.
Who Should Own the Domain?
Register the domain in the practice's name, on an account the practice controls, with at least two people who can sign in. Some clinics only discover that their domain sits in a former employee's or web designer's personal account when they need to change a record. If that's you, transfer the domain to a practice-owned account before you start the email move.
Product Insight: ClinikMail's Guided DNS Wizard and IMAP
ClinikMail gives you mailboxes on your own domain on every plan, and it's HIPAA-compliant and covered by our BAA. The setup follows the Help Center:
- Add your domain in Settings → Communications & AI → Mail. It appears with four live checks (MX, SPF, DKIM, DMARC), each marked Pending, Verified or Failed.
- Select Verify now after adding the records. The badge changes to Receiving only once MX passes, and to Sending enabled once all four pass. Mail to a domain that's still Pending isn't delivered.
- Want to start straight away? A free
@clinikmail.comaddress needs no DNS, where it's available in your region. - Mail apps over IMAP. Turn on mail-app access for a mailbox and issue an app password for each device. Each password is shown once, and revoking one stops only that device, so a lost phone doesn't lock out anyone else. The settings the app needs are shown next to each new password, and on an iPhone or iPad a setup link fills them in for you.
- Two-factor stays deliberate. A mail app can't prompt for a second factor, so if your practice requires two-factor sign-in, only the owner can allow mail-app access, and withdrawing that turns it off for every mailbox at once.
Plan limits: Free includes 1 domain of your own, Essential ($99.90/month) 3 and Team ($250/month) 10. See pricing. To put booking or store pages on your domain, see custom domains.
Frequently Asked Questions (FAQs)
1. What are SPF, DKIM and DMARC?
They're DNS records that prove your email is really from your domain. SPF lists who can send, DKIM signs each message, and DMARC tells receivers what to do when a message fails those checks and sends you reports.
2. Does Gmail require DMARC?
Google requires DMARC for senders of more than 5,000 messages a day to personal Gmail accounts, and says the policy can be set to none. All senders need SPF or DKIM.
3. Which DMARC policy should a medical practice use?
Start with p=none to collect reports. Once every legitimate sender passes, move to p=quarantine, then p=reject.
4. Can I have two SPF records?
No. A domain should have one SPF record. Add every sending service to that single record.
5. How long does DNS take to verify?
Often within an hour, sometimes longer. Recheck the records at your registrar and select Verify again.
6. Can I use my own domain on ClinikEHR's Free plan?
Yes. The Free plan includes 3 mailboxes, 5 GB of storage and one domain of your own, set up with the guided DNS wizard.
Conclusion
Email on your own domain is one of the cheapest trust signals a practice can have. Four records do the work: MX to receive, SPF and DKIM to prove your mail is yours, and DMARC to protect your name. Add them once, start DMARC at p=none, tighten it once the reports are clean, and give every mail app its own password you can revoke.
Key takeaways:
- MX receives mail; SPF, DKIM and DMARC protect and deliver it
- Gmail and Yahoo require SPF or DKIM from every sender, and DMARC from bulk senders
- Keep one SPF record and start DMARC at p=none
- Use a separate app password for each device so you can revoke just one
- ClinikMail checks all four records live and includes your own domain on every plan
Ready to put your practice's email on its own domain? Try ClinikEHR free, see our pricing, or book a free demo.
Disclaimer: Sender requirements were checked on Google's and Yahoo's websites in September 2026 and can change. This article is educational and not legal or technical advice for your specific setup. ClinikEHR and its authors shall not be held liable for any decisions made based on the information provided herein.
Related Articles
Stay in the loop
Subscribe to our newsletter for the latest updates on healthcare technology, HIPAA compliance, and exclusive content delivered straight to your inbox.