How to Set Up a Domain on Namecheap

Step-by-step guide to configure DNS records on Namecheap for Aurora SendCloud. Learn to set up SPF, DKIM, MX, and DMARC records for optimal email delivery.


Overview

This guide demonstrates how to add a primary domain or subdomain in Namecheap and configure the DNS records required by Aurora SendCloud for that domain or subdomain. This guide assumes that you already have a Namecheap account.

While this guide is designed to be as helpful and comprehensive as possible, there is a small chance that you may encounter errors or issues when configuring DNS records in Namecheap. If this occurs, we recommend contacting Namecheap's support team, as they will be able to identify and resolve the issue most quickly (or at least provide next steps).

Choosing a Primary Domain or Subdomain

Before proceeding, it's crucial to decide which domain to use—specifically, whether to use the primary domain or a subdomain of that primary domain. Because this can be a challenging decision, we recommend reviewing the following Aurora SendCloud article:

How to choose a sending domain

Let's briefly review two key terms: primary domain and subdomain.

Examples of primary domains include aurorasendcloud.com, mydnsexample.com, and google.com. Examples of subdomains include relay.aurorasendcloud.com, sc.mydnsexample.com, and mail.google.com.

Note the pattern: Subdomains have an additional prefix (sometimes multiple prefixes) before the main domain itself. In most cases, using subdomains with Aurora SendCloud is the preferred option.

Once you've made your decision, add the domain or subdomain to your Aurora SendCloud account, and our system will generate the various DNS records required.

Adding a Domain

There are several ways to add a domain or subdomain to Namecheap:

Method 1: Register a new domain/subdomain with Namecheap

Method 2: Transfer the registration of an existing domain or subdomain from another domain registrar to Namecheap

Method 3: Configure the name servers of the existing domain or subdomain at your domain registrar to reference Namecheap instead of your current DNS provider

This guide will focus on the first and third methods.

Register a New Domain (Method 1)

If you need to create a new domain or subdomain and have it hosted on Namecheap, follow these steps:

  1. Log in to your Namecheap account.
  1. Enter the new domain name you want to buy into the text box.
  1. Follow the prompts to provide payment and complete the domain registration process.

Use an Existing Domain (Method 3)

If you already have a domain or subdomain registered elsewhere but would like to manage your DNS with Namecheap, follow these steps:

  1. Log in to your Namecheap account.
  1. Hover over the Domains tab in the top navigation pane to display a list of options. Then click the FreeDNS option.
  1. Enter your existing domain in the text box, then click Get DNS.

  1. Click either the shopping cart icon on the row containing your domain or the Add to Cart button. Then click the Set up DNS button.
  1. Namecheap will display the specific NS records you need to configure at your domain registrar.

  2. Update the name server records at your domain registrar to the values provided by Namecheap.

Configure the Domain

Once the domain has been added, you can access it by following these steps:

  1. Log in to your Namecheap account
  2. Go to "Domain Management"
  3. Find the domain you want to configure and click "Manage"
  4. Click "Add Record" or a similar option to configure the DNS records

Configure SPF

SPF records help protect your domain from spoofed email and reduce the likelihood that your email will be marked as spam.

Configure an SPF Record for the Primary Domain

In your Namecheap dashboard, enter the SPF record information displayed in the Aurora SendCloud dashboard.

FieldValue
Record TypeTXT
Host Record@
Record Valuev=spf1 include:sendcloud.org ~all (When activating multiple regions, please configure according to the actual requirements on the page)
TTL600 (seconds)

Note: If you already have an SPF record for this primary domain, simply insert include:sendcloud.org into the existing SPF record. Ensure this text appears after v=spf1 and before ~all.

Configure SPF Records for Subdomains

FieldValue
Record TypeTXT
Host RecordSubdomain Prefix (e.g., sc)
Record Valuev=spf1 include:sendcloud.org ~all (When activating multiple regions, please configure according to the actual requirements on the page)
TTL600 (seconds)

Configure DKIM

DKIM records help verify your domain to prevent forged emails and reduce the likelihood of your emails being marked as spam.

Configure a DKIM Record for the Primary Domain

FieldValue
Record TypeTXT
Host Recordsendcloud._domainkey (or the value assigned by Aurora SendCloud for your domain)
Record Valuek=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUA... (Please configure according to the actual requirements on the page)
TTL600 seconds

Note: Your DKIM host record may have one of the following values: default.domainkey, sc.domainkey, etc. Be sure to use the value assigned by Aurora SendCloud for your domain.

Configure a DKIM Record for a Subdomain

FieldValue
Record TypeTXT
Host Recordsendcloud._domainkey.subdomain prefix (e.g., sendcloud._domainkey.sc)
Record Valuek=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUA... (Please configure as specified on the page)
TTL600 (seconds)

Configure MX Records

MX records specify where emails sent to your domain should be delivered.

Configure an MX Record for the Primary Domain

FieldValue
Record TypeMX
Host Record@
Record Valuemx.sendcloud.org (Please configure as specified on the page when enabling multiple regions)
Priority10
TTL600 (seconds)

Note: Ensure that only Aurora SendCloud MX records are configured for your domain. MX records for other email providers can result in unpredictable email delivery.

Configure MX Records for Subdomains

FieldValue
Record TypeMX
Host RecordSubdomain Prefix (e.g., sc)
Record Valuemx.sendcloud.org (When enabling multiple regions, please configure according to the instructions on the page)
Priority10
TTL600 (seconds)

Configure DMARC

DMARC (Domain-based Message Authentication, Reporting, and Conformance) is an email authentication protocol that protects your domain from spoofing and phishing attacks. It builds on SPF and DKIM to provide clear policy guidance for inbox providers.

Configure a DMARC Record for the Primary Domain

FieldValue
Record TypeTXT
Host Record_dmarc
Record Valuev=DMARC1; p=none; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1
TTL600 seconds

Parameter Description:

  • v=DMARC1: Protocol version
  • p=none: Monitor mode (no enforcement)
  • p=quarantine: Quarantine mode (messages that fail verification will be sent to spam)
  • p=reject: Reject mode (messages that fail verification will be rejected)
  • rua: Email address for aggregated reports
  • ruf: Email address for forensic reports
  • fo=1: Failure reporting option

Configure a DMARC Record for a Subdomain

FieldValue
Record TypeTXT
Host Record_dmarc.Subdomain prefix (e.g., _dmarc.sc)
Record Valuev=DMARC1; p=none; rua=mailto:[email protected]
TTL600 seconds

Update Domain Registrar and Name Server Records

If you recently migrated from another DNS hosting provider (or are currently migrating) and your Aurora SendCloud DNS records fail to verify in the Aurora SendCloud control panel, you may need to update your domain's registration information.

When switching DNS hosting providers, you must update your name server (NS) records in your registrar's system. Your registrar is the company from which you purchased your domain name and registered it on the internet.

If you need help identifying your domain's registrar, the ICANN WHOIS website can assist with this task.

Need Support?

Our Aurora SendCloud support team is happy to help! Contact us from the Support page in your Aurora SendCloud control panel, and we'll get back to you as soon as possible!

Important Notes

  • The DNS record values in this guide are examples only. Refer to the actual values displayed in your Aurora SendCloud dashboard.
  • After configuration, DNS records may take some time to propagate globally (typically several minutes to several hours).
  • Set the TTL to a low value (e.g., 300–600 seconds) for faster verification. After successful verification, you can increase it as needed.