Search... ⌘ K
Get Started Contact Sales

Email DNS Records Quick Reference

Last updated

Table of Contents

Look up the record type, name format, and content format for each email-related DNS record. For a step-by-step walkthrough, see Manage Email DNS Records.

MX records

Purpose: Direct email delivery to mail servers

Record type: MX

Format:

  • Name: @ or blank (root domain)
  • Priority: Number (lower = higher priority)
  • Mail server: Hostname (e.g., mail.example.com)

Example:

Name: @
Priority: 10
Mail server: mail.example.com

Common uses:

  • Email hosting (Google Workspace, Microsoft 365)
  • Email forwarding (auto-configured by DNSimple)

Note

See Set Up MX Records for Email Hosting for details.

SPF records

Purpose: Authorize email senders

Record type: TXT

Format:

  • Name: @ or blank (root domain)
  • Content: v=spf1 [mechanisms] [qualifier]

Example:

Name: @
Content: v=spf1 include:_spf.google.com include:spf.mtasv.net ~all

Common mechanisms:

  • include:domain.com - Include another domain’s SPF
  • ip4:1.2.3.4 - Authorize specific IPv4 address
  • ip6:2001:db8::1 - Authorize specific IPv6 address
  • a - Authorize domain’s A records
  • mx - Authorize domain’s MX records

Qualifiers:

  • +all - Pass (default)
  • ~all - Soft fail (recommended initially)
  • -all - Hard fail (strongest protection)

Note

See Set Up SPF Records for details.

DKIM records

Purpose: Cryptographic email signing

Record type: TXT

Format:

  • Name: selector._domainkey (e.g., google._domainkey)
  • Content: DKIM public key (provided by email service)

Example:

Name: google._domainkey
Content: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3...

Common selectors:

  • google - Google Workspace
  • selector1, selector2 - Microsoft 365
  • Various - Other email services

Note

See Set Up DKIM and Manage Multiple DKIM Selectors for details.

DMARC records

Purpose: Email policy enforcement and reporting

Record type: TXT

Format:

  • Name: _dmarc
  • Content: v=DMARC1; [tags]

Example:

Name: _dmarc
Content: v=DMARC1; p=none; rua=mailto:dmarc@example.com

Common tags:

  • p=none - Monitor only (start here)
  • p=quarantine - Quarantine failures
  • p=reject - Reject failures (strongest)
  • rua=mailto:address@example.com - Aggregate reports
  • ruf=mailto:address@example.com - Forensic reports
  • aspf=r - Relaxed SPF alignment (default)
  • adkim=r - Relaxed DKIM alignment (default)

Note

See Set Up DMARC and Implement a Gradual DMARC Policy for details.

CNAME records for email

Purpose: Autodiscover and other email services

Record type: CNAME

Common records:

Autodiscover (Microsoft 365):

Name: autodiscover
Value: autodiscover.outlook.com

Webmail (varies by provider):

Name: webmail
Value: webmail.provider.com

Verification TXT records

Purpose: Domain verification for email services

Record type: TXT

Format:

  • Name: @ or as specified by provider
  • Content: Verification string from email provider

Example:

Name: @
Content: google-site-verification=abc123...

Quick verification commands

Check MX records

dig +short yourdomain.com MX

Check SPF record

dig +short yourdomain.com TXT | grep "v=spf1"

Check DKIM record

dig +short selector._domainkey.yourdomain.com TXT

Check DMARC record

dig +short _dmarc.yourdomain.com TXT

Common configurations

Google Workspace

MX record:

  • Priority: 1
  • Mail server: smtp.google.com
  • Domains set up before 2023 may use the older aspmx MX records instead. Google still supports them.

SPF:

v=spf1 include:_spf.google.com ~all

DKIM:

  • Selector: google
  • Record at: google._domainkey.yourdomain.com

Microsoft 365

MX record:

  • Priority: 0
  • Mail server: the value shown in the Microsoft 365 admin center for your domain (for example, yourdomain-com.mail.protection.outlook.com)

SPF:

v=spf1 include:spf.protection.outlook.com ~all

DKIM:

  • Selectors: selector1, selector2
  • Records at: selector1._domainkey.yourdomain.com, selector2._domainkey.yourdomain.com

Autodiscover:

  • CNAME: autodiscover -> autodiscover.outlook.com

Email forwarding (DNSimple)

MX and SPF records:

  • DNSimple adds them automatically when you create an email forward. It deletes any other MX records at the root of the zone, and merges the forwarding service into your existing SPF record if you have one.
  • Do not add or edit these records by hand. If they are missing, the domain’s page shows a warning with a button.

Best practices

  • One SPF record: Only one SPF record per domain
  • Multiple DKIM selectors: Each service may need its own selector
  • Gradual DMARC: Start with monitoring, gradually increase
  • Verify records: Use dig to verify after changes
  • Document configuration: Keep track of all email records

Have more questions?

If you have additional questions or need any assistance with email DNS records, contact support, and we will be happy to help. You can also read more about DNS hosting at DNSimple.