38.3.5 Email Masking – Step by Step Guide

Overview #

Setting up email masking on your domain only takes a few steps. In this guide, we’ll walk you through the full process – from entering your custom email domain in our platform to configuring the necessary DNS records in your domain provider (like GoDaddy or Cloudflare).

If you’re not familiar with DNS records, don’t worry- we’ve made this as simple and clear as possible.

---

Step 1 – Enter Your Custom Domain #

In our platform:

1. Go to the Settings > App Details section in your CMS.
2. Scroll down to the “Email Masking“ section.
3. In the “Sender Domain“ field, enter the domain you would like to send from. For example example.com or a subdomain such as events.example.com
4. In the “Sender Username“ field, either leave it blank for noreply. Or populate it with the address you would like to send from. For example contact would result in [email protected]
5. Select if you would like to use MAIL FROM masking or not, if you’re unsure what this means please refer to the previous page (38.3.4) for more details.
6. Click the “Save“ button in the bottom right

Once entered, we’ll automatically generate a list of DNS records you need to add and display them in a table below these fields

---

Step 2 – Copy the Required DNS Records #

After configuring your domain you’ll now see a table of records that need to be added. Any marked with an ℹ️ circle are optional however are recommended.

Each record will include:

• Type (CNAME, TXT, MX)
• Name (or Host)
• Value (or Target)

These records are unique to your domain, make sure to copy them exactly.

Alternatively you can download a “zone“ file, this is a file that can be uploaded to supported DNS providers to automatically create all of the required records without room for error.

---

Step 3 – Add Records in Your DNS Provider #

Log into your DNS provider (like GoDaddy, Cloudflare, 123 Reg, etc.) and add each record as shown.

Example for GoDaddy: #

Field	What to Enter
Type	CNAME
Name / Host	some-key._domainkey
Value / Points to	A long AWS-generated URL ending in .amazonses.com.

Make sure to:

• Remove any trailing dots (.) if your DNS provider doesn’t allow them
• Keep TTL at the default setting unless instructed otherwise

Example for Cloudflare: #

Cloudflare users should:

• Ensure each CNAME record is set to DNS only (⚠️ Not proxied through the orange cloud)
• Leave TTL as “Auto” unless needed otherwise

---

Step 4 – Confirm Records in Our CMS #

Once you’ve added all DNS records:

1. Return to the Email Masking section in the CMS.
2. Click Check Email Validity.
3. Your email sending identity will be verified by our email provided (AWS SES)

If verification fails, don’t worry – we’ll cover troubleshooting in the next page (3.3.6).

---

Summary #

Task	Where to Do It
✅ Enter email address	In your CMS
✅ Copy DNS records	From CMS table or zone file download
✅ Add DNS records	In your DNS provider (GoDaddy, Cloudflare, etc.)
✅ Verify setup	Back in the CMS using Check Validity