Whoever manages your domain or DNS: your web person, IT, or whoever has access to your domain registrar or DNS host. It takes a few minutes.
Add each record exactly as shown. Enter the Name as written. Some providers automatically add your domain to the end (so "send" becomes "send.yourname.com") which is normal and correct.
| Type | Name | Value |
|---|---|---|
| TXT | resend._domainkey | p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQChosNjkVMFV6c1I4Qb91zDyQmlF0aojHlppkVKB9NCh/EXK/PoETYa2teZ3jSqsxn21264x5ZqdJMtsom9QWpKVorMM6XEJdnurkcvMMkWUf9AaANHQ3kYWNhZ5/c1X5JGFB/kz526WxpBHgiQlwCgfNSX+iJEPPFAts/EwICDywIDAQAB Lets us sign emails as you (DKIM). |
| TXT | send | v=spf1 include:amazonses.com ~all Authorises our sending service to send on your behalf (SPF). |
| CNAME | links | links1.resend-dns.com Makes tracked links in emails use your domain. |
| MX | send | feedback-smtp.eu-west-1.amazonses.com Routes delivery and bounce feedback. |
DMARC rounds out the setup above. It tells inboxes how to treat any mail that fails the checks, and Gmail and Yahoo now expect it from anyone sending to a sizeable list, so it directly helps your fan emails land. It is recommended rather than strictly required to start sending.
| Type | Name | Value |
|---|---|---|
| TXT | _dmarc | v=DMARC1; p=none; Monitoring only, and safe to start with. Once everything above is authenticating cleanly, whoever manages your email can tighten the policy later. |
Once the four records are saved, the domain can be verified and your fan emails will send from it through the platform. DNS changes can take a little time to take effect across the internet, so if verification does not pass straight away it usually clears within a few hours.