Set up your email sending domain (SPF & DKIM)
Verify your domain so emails you send arrive in the inbox, not spam. You add a few DNS records where your domain is managed; this applies whichever email provider you use.
1. Why this matters
Mailbox providers (Gmail, Outlook) check that your domain authorised the sender. Without SPF and DKIM, real emails are often marked as spam or rejected.
This is provider-agnostic: your email provider (Resend, or another HTTPS email API) gives you the exact records; you add them where your DNS lives.
2. Add the DNS records
- In your email provider, start verifying your domain — it shows the records to add.
- SPF: a TXT record on your domain that lists who may send for it.
- DKIM: one or more records (usually CNAME or TXT) that sign your mail to prove it really comes from you.
- Add each record where your domain is managed (often where you bought it), exactly as shown (name and value).
- Back in the provider, click Verify — propagation can take minutes to a few hours.
DMARC (an extra TXT record) is recommended once SPF and DKIM pass — start with p=none to observe.
3. Where your DNS lives
Add the records wherever your domain’s DNS is managed — often where you bought it, or Cloudflare if your domain is there. If you bought your domain through Makasi, ask your agent where to add them.
4. Common problems
Verification stays pending: a record’s name or value is off by a character, or DNS has not propagated yet — re-check and wait.
Emails still go to spam: DKIM is not verified, or you are sending from a domain you did not authorise.
Two SPF records: you can only have one TXT SPF record — merge them into a single line.