Custom Domains

Send emails from your own domain instead of noreply@makeemwait.com.

Pro Plan Required Custom email domains require a Pro plan.

Overview

By default, emails are sent from noreply@makeemwait.com. With a custom domain, you can send from your own address (e.g., noreply@yourcompany.com), which improves deliverability and brand trust.

We recommend using a subdomain (e.g., send.yourcompany.com) rather than your root domain. This isolates your sending reputation — if your transactional email subdomain ever gets flagged, it won’t affect your root domain’s reputation.

You can verify multiple domains, but only the first verified domain is used as the sender address. The sender format is always noreply@yourdomain.com — the local part (noreply) is not configurable.

Verify a Domain

Step 1: Start Verification

Go to Domains and enter your domain name (e.g., send.yourcompany.com).

API: POST /domains/verify

{
  "domain": "yourcompany.com"
}

Response:

{
  "domain": "yourcompany.com",
  "status": "pending",
  "dns_records": [
    {
      "type": "TXT",
      "name": "send._domainkey.yourcompany.com",
      "value": "v=spf1 include:send.resend.com ~all",
      "purpose": "SPF"
    },
    {
      "type": "CNAME",
      "name": "resend._domainkey.yourcompany.com",
      "value": "xxxxxxxx.dkim.resend.dev",
      "purpose": "DKIM"
    },
    {
      "type": "CNAME",
      "name": "resend2._domainkey.yourcompany.com",
      "value": "xxxxxxxx.dkim2.resend.dev",
      "purpose": "DKIM"
    }
  ]
}

Step 2: Add DNS Records

Add the DNS records shown in the response to your domain’s DNS settings. The exact records depend on your domain, but typically include SPF (TXT) and DKIM (CNAME) records. Each record in the response may also include ttl and priority fields — use those values if your DNS provider requires them.

Where you add these depends on your DNS provider (e.g., Cloudflare, Route 53, GoDaddy, Namecheap).

DNS changes can take up to 72 hours to propagate, though most complete within a few minutes.

We also recommend adding a DMARC record to your domain for maximum deliverability:

Type: TXT
Name: _dmarc.yourcompany.com
Value: v=DMARC1; p=none; rua=mailto:dmarc@yourcompany.com

DMARC tells receiving mail servers how to handle messages that fail SPF/DKIM checks. Start with p=none (monitor only) and move to p=quarantine or p=reject once you’ve confirmed emails are authenticating correctly.

Step 3: Check Verification Status

After adding the DNS records, check the status:

From the dashboard: Click Check Status on the domains page.

API: GET /domains/{domain}/status

{
  "domain": "yourcompany.com",
  "status": "verified"
}

The status will be "pending" until DNS propagation completes, then change to "verified".

List Domains

API: GET /domains

{
  "domains": [
    {
      "domain": "yourcompany.com",
      "verification_status": "verified",
      "created_at": "2025-03-15T10:30:00.000Z"
    }
  ]
}

Delete a Domain

API: DELETE /domains/{domain}

Returns 204 No Content. This removes the domain from both MakeEmWait and Resend.

After deletion, all future emails (blasts, notifications, verification) will fall back to the default sender (noreply@makeemwait.com). Any emails already in flight when the domain is deleted will still be delivered from the old address — only future sends are affected.

Deleting a domain does not remove the DNS records from your domain provider. You can clean those up manually.

Using Your Custom Domain

Once verified, your custom domain is automatically used as the sender address for:

Email blasts sent to your waitlist
Any automated emails (signup confirmations, referral milestones)

No additional configuration is needed — the system detects your verified domain and uses it.

Email Blasts — send bulk emails using your custom domain
Email Templates — create reusable templates for automated emails
Security — data protection and encryption details

Previous Webhooks & Integrations Next Team Management