The "ID Card" of Email
When you send an email, the receiving server (like Gmail) asks: "Who are you, and are you allowed to send emails for this domain?" DNS records are your answer. If you don't have them, you are treated as a forgery (Spam).
If you use SendScale Domain Purchase Process, we configure these automatically. You do not need to touch anything. If you Connect Your Own Domain (e.g., purchased from GoDaddy or Namecheap), you must add these records manually in your registrar's DNS settings.
1. SPF (Sender Policy Framework)
What it is: A guest list of IP addresses allowed to send email for you.
The Record: It looks like v=spf1 include:_spf.google.com ~all.
The Rule: You can only have ONE SPF record per domain. If you have multiple (e.g., one for Outlook and one for Mailchimp), you must merge them into a single line.
2. DKIM (DomainKeys Identified Mail)
What it is: A digital wax seal. It adds an encrypted signature to the header of your emails.
Function: It proves that the email wasn't tampered with during transit.
Setup: You generate a "Key" in your Google/Microsoft admin panel and paste it into your DNS as a TXT record.
3. DMARC (Domain-based Message Authentication, Reporting, and Conformance)
What it is: The instruction manual for the receiver. It tells Google/Outlook what to do if an email fails SPF or DKIM checks.
The Record: v=DMARC1; p=none; rua=mailto:[email protected].
Best Practice: Start with p=none (Monitor mode). This tells servers: "If authentication fails, let the email through but tell me about it." Do not use p=reject unless you are an advanced IT administrator, as it can block legitimate mail.