When you set up business email, you’re asked to add four records with strange names: MX, SPF, DKIM and DMARC. They look technical, but each one answers a simple question that every email server on the internet asks about your domain. Let’s go through them one by one.
A quick word on DNS
DNS is the internet’s address book. When someone types your website or emails you, their computer looks up your domain in DNS to find out where to go. Your domain can have many entries (called records). Email uses the four below.
MX record: where should email for this domain go?
The MX (mail exchanger) record tells other servers which computer accepts email for your domain. Without it, nobody can email you at your domain.
| Type | Name | Value | Priority |
|---|---|---|---|
| MX | @ | mx.whysharedmail.com | 10 |
The @ means “the domain itself”. If you have old MX records from a previous email service, remove them — otherwise some mail goes to the old place.
SPF record: who is allowed to send as this domain?
SPF (Sender Policy Framework) is a TXT record listing the servers that may send email using your domain. Receiving servers compare the sending server with this list.
Example: v=spf1 include:_spf.whysharedmail.com ~all
v=spf1says “this is an SPF record”.include:adds a provider’s list of servers.~allmeans “anything else is suspicious” (soft fail).
Only one SPF record per domain. If your website also sends mail through another service, add its include: to the same record instead of creating a second one.
DKIM record: is this email really from you, and unchanged?
DKIM (DomainKeys Identified Mail) adds an invisible digital signature to every email you send. The matching public key sits in your DNS. Receivers check the signature with the key: if it matches, they know the message really came from your domain and wasn’t altered on the way.
The DKIM record has a name like default._domainkey and a long value starting with v=DKIM1; k=rsa; p=. Each domain gets its own key, which you copy from your dashboard.
DMARC record: what should happen when checks fail?
DMARC ties SPF and DKIM together and tells receivers what to do with mail that claims to be from you but fails both checks:
p=none— just monitor, deliver as normalp=quarantine— put it in spamp=reject— refuse it
Example: v=DMARC1; p=quarantine; adkim=r; aspf=r added as a TXT record named _dmarc. Since 2024 Gmail and Yahoo expect a DMARC record from anyone sending in bulk, so it’s worth adding even if you send only a little mail.
Why you need all four
| Without… | What happens |
|---|---|
| MX | You can’t receive email at your domain. |
| SPF | Your mail looks suspicious and often goes to spam. |
| DKIM | Receivers can’t verify your mail; deliverability drops. |
| DMARC | Scammers can more easily pretend to be you; big providers trust you less. |
How to add and check them
- Open your domain’s DNS settings at your registrar or hosting provider.
- Add each record exactly as shown in your dashboard — the copy buttons help avoid typos.
- Wait a few minutes, then click Check in the dashboard.
If you register your domain through WhySharedMail and use our nameservers, these records are added for you. New to all of this? Start with our complete setup guide, and if mail still lands in spam afterwards, see why emails go to spam.
Frequently asked questions
Can I have two SPF records?
No. A domain must have exactly one SPF record. If you use two services to send mail, combine them into a single record with two include: parts.
What DMARC policy should I start with?
Many businesses start with p=none to monitor, then move to p=quarantine once they are sure all their legitimate mail passes SPF or DKIM. p=reject is the strictest.
How do I know if my records are correct?
Your WhySharedMail dashboard checks MX, SPF, DKIM and DMARC for your domain and shows a green tick for each record that is found and correct.
Do these records affect my website?
No. They are separate DNS records that only affect email. Your website’s A and CNAME records stay as they are.