Skip to main content

Sending Domains

Manage your sending domains to ensure email authentication and deliverability. Add, verify, and monitor domains used for sending emails, ensuring they meet necessary authentication standards such as SPF, DKIM, and DMARC for improved inbox placement and trust.

Overview​

Sending domains provide authentication and tracking for your emails:

+------------------+      +------------------+      +------------------+
|  EMAIL SENT      | ---> |  DNS RECORDS     | ---> |  RECIPIENT       |
|  from domain     |      |  SPF + DKIM      |      |  SERVER          |
+------------------+      +------------------+      +------------------+
                                  |
                                  v
                         +------------------+
                         |  VERIFICATION    |
                         |  - SPF: Pass     |
                         |  - DKIM: Pass    |
                         |  - Domain: Valid |
                         +------------------+

Why Domain Authentication Matters​

Deliverability​

  • SPF tells receiving servers which IPs can send for your domain
  • DKIM proves emails weren't modified in transit
  • Authenticated emails are less likely to be marked as spam

Brand Protection​

  • Prevent spoofing of your domain by unauthorized senders
  • Build reputation with consistent sending identity
  • Establish trust with recipients and email providers

Tracking Capability​

  • Click tracking uses your tracking domain for links in broadcasts
  • Open tracking uses your tracking domain for pixels in campaigns
  • Custom domains look more professional than third-party URLs

Viewing Sending Domains​

Navigate to Setup → Sending Domains to view all configured domains.

Page Features​

  • Add New button to add a domain
  • Our records / User records toggle to filter view
  • Filter by admin dropdown to filter by administrator
  • Show entries dropdown to control page size
  • Search box to find specific domains
  • Pagination for navigating through domains

Table Columns​

ColumnDescription
Sending DomainDomain name (clickable link)
Tracking PrefixSubdomain prefix for tracking (e.g., "email")
Redirection TypeMethod: cname, htaccess, or cloak
DKIMDKIM verification status
Tracking DomainTracking domain verification status
Created onDate and time domain was added
ActionsRow action menu

Status Indicators​

Both DKIM and Tracking Domain columns show these statuses:

StatusBadge ColorDescription
OFFDark/GrayFeature is disabled
PENDINGYellow/OrangeAwaiting verification
PASSEDGreenVerification successful
FAILEDRedVerification failed

Row Actions​

Click the ... (three dots) menu on any row to access:

ActionDescription
View sending domainOpen domain details page
Set ownership as verifiedManually verify domain ownership
Verify domain keyCheck DKIM DNS record
Verify tracking domainCheck tracking domain configuration
Download domain key pairDownload DKIM public/private keys
DeleteRemove this domain

Domain Status​

Overall Domain Status​

StatusBadgeDescription
ActiveGreenDomain is fully verified and can be used
InactiveGrayDomain is disabled
SuspendedRedDomain has been suspended by admin
Pending VerificationOrangeOwnership verification is pending (when domain verification is enabled in application settings)
Pending AuthenticationOrangeDNS records (DKIM, tracking, SPF, MX) are awaiting verification
Authentication FailedRedOne or more DNS verifications have failed

What Affects Domain Status​

The domain status is automatically calculated based on:

  • Domain ownership verification status (if enabled)
  • DKIM verification status
  • Tracking domain verification status
  • Bounce domain verification status (SPF + MX)
  • Whether all required DNS records have been confirmed

If any verification fails, the domain status changes to reflect the issue until it is resolved.

Domain Status Toggle​

The Domain Status toggle (Active/Inactive) allows you to manually enable or disable a sending domain. This toggle is available on the main DNS authentication page but is hidden during the ownership verification step when domain verification is mandatory.

Domain Setup Flow​

When a new sending domain is added, it goes through a two-step setup process (when domain ownership verification is enabled in application settings):

+------------------+      +------------------+      +------------------+
|  ADD DOMAIN      | ---> |  STEP 1:         | ---> |  STEP 2:         |
|  Enter domain    |      |  OWNERSHIP       |      |  DNS AUTH        |
|  name            |      |  VERIFICATION    |      |  DKIM + Tracking |
+------------------+      +------------------+      |  + Bounce        |
                                                     +------------------+

Step 1: Domain Ownership Verification​

If domain ownership verification is enabled in application settings, the first page you see after adding a domain requires proving you own the domain.

Page indicators:

  • Domain name is displayed in the card header
  • A "Pending Verification" badge (orange) is shown next to the domain name
  • The Domain Status toggle and status labels are hidden during this step

Two verification methods are available:

Method 1: DNS Record (Default)​

  1. A TXT record is displayed with the host and hash value
  2. Add this TXT record to your domain's DNS zone
  3. The Current Value column fetches and displays the live DNS value automatically
  4. Click Verify Domain to confirm

Method 2: Upload File​

  1. Download the verification HTML file
  2. Upload it to the root folder of your domain
  3. Mumara checks if the file is publicly accessible
  4. Click Verify Domain to confirm
DNS Current Value

The current DNS value is fetched asynchronously when the page loads. If your DNS provider's records haven't propagated yet, the value may show "No value found". DNS propagation can take up to 48 hours.

tip

If domain ownership verification is disabled in application settings, this step is skipped entirely and domains go directly to the DNS authentication page.

Step 2: DNS Authentication​

After ownership is verified (or if verification is disabled), you are redirected to the main DNS authentication page where you configure DKIM, tracking domain, and bounce domain records.

Page indicators:

  • A "Verified" badge (green) appears next to the domain name
  • Domain Status toggle is visible
  • Status labels show Active, Pending Authentication, or Authentication Failed

DNS Record Host Formatting​

All DNS record tables use a smart host formatting system that helps you identify exactly what to enter in your DNS zone editor.

Click-to-Copy Host Records​

In every DNS record table (DKIM, Tracking CNAME, SPF, MX, and Ownership Verification), the Host column displays the record in a formatted way:

  • Bold text: The portion you need to enter in your DNS zone editor (click to copy to clipboard)
  • Gray text: The registrable domain (automatically appended by your DNS provider)

Example: For domain newsletters.marketing.example.com:

  • Bold: key._domainkey.newsletters.marketing (this is what you copy)
  • Gray: .example.com (your DNS zone already knows this)

This formatting uses the Mozilla Public Suffix List to accurately identify the registrable domain (e.g., example.com, example.co.uk) regardless of how many subdomain levels are used.

tip

Click on any host record in the DNS tables to instantly copy the relevant portion to your clipboard. A success notification will confirm the copy.

Creating a Sending Domain​

Navigate to Setup → Sending Domains and click Add New.

Domain Name​

Enter the domain you'll use for sending emails.

Examples:

  • example.com (main domain recommended)
  • yourbrand.com
  • mail.yourbrand.com (subdomain)
Use Main Domain

Using your main domain for sending emails increases the trust factor with recipients and email providers. Mumara will automatically create the necessary subdomain DNS records for tracking (e.g., email.example.com for tracking links).

Sending Domain Details​

After creating a domain (and completing ownership verification if required), you'll see the domain details page with configuration options.

Sending Domain Authentication Card​

The authentication card header displays:

ElementDescription
Domain NameThe full sending domain name displayed prominently in the card body
Verified BadgeGreen "Verified" badge (when ownership verification is enabled and passed)
Status LabelsActive, Pending Authentication, or Authentication Failed indicators
Recheck ButtonRe-verifies all DNS records
Domain Status ToggleEnable or disable the domain

DKIM Authentication​

DKIM (DomainKeys Identified Mail) signs your outgoing emails with a domain key to verify authenticity.

Automatic Key Generation​

When you first access the DNS authentication page, DKIM keys are automatically generated if they don't already exist. This eliminates the need to manually click "Generate Keys" before configuring DKIM.

info

Auto-generation only occurs on the main DNS authentication page, not during the ownership verification step. If key generation fails for any reason, you can always use the Regenerate Keys link manually.

Sign Outgoing Emails​

Toggle to enable DKIM signing for emails sent through this domain.

When enabled, Mumara will sign your outgoing emails with a domain key. Ensure that the public DNS entry is added after enabling.

DKIM Record Configuration​

After enabling, you'll see a table with the required DNS record:

ColumnDescription
HostThe DNS record host (e.g., key._domainkey.yourdomain.com) — click to copy
TypeRecord type (TXT)
ValueThe DKIM public key value to add
Current ValueThe current value found in DNS (fetched automatically)

Adding the DKIM Record​

  1. Click the Host value to copy it to your clipboard
  2. Copy the Value (DKIM public key) using the copy button
  3. Log into your DNS provider
  4. Add a new TXT record with the host and value
  5. Wait for DNS propagation
  6. Click Recheck to verify

Regenerate Keys​

Click Regenerate Keys to generate a new DKIM key pair. Use this if:

  • Your private key was compromised
  • You want to rotate keys for security
  • The current keys are not working
warning

Regenerating keys requires updating the DNS record with the new public key. The old key will no longer validate signatures.

Download Private Key​

Click Download Private Key to download the DKIM private key file for backup or external use.

Custom Tracking Domain​

Configure a custom tracking domain to replace the default system domain in all tracking links and image paths within your emails.

Enable Tracking Domain​

Toggle to enable custom tracking domain.

Tracking Prefix​

The subdomain prefix used for tracking. Default is typically "email".

Example: With prefix "email" and domain "example.com", tracking domain becomes email.example.com

Use Secure URL​

Toggle to enable HTTPS for all tracking links. When enabled, Mumara generates tracking URLs using the HTTPS protocol for this tracking domain.

SSL Certificate Required

If "Use Secure URL" is enabled, a valid SSL certificate must be installed on the tracking domain. Without it, tracking links will not work. Either install an SSL certificate or disable this option.

Redirection Types​

Choose how tracking requests are redirected to Mumara's tracking server:

CNAME​

Uses DNS CNAME record pointing to Mumara's primary domain.

Configuration:

  1. Add a CNAME record in your DNS
  2. Point it to the value shown (e.g., campaigns.mumara.dev)
ColumnDescription
HostYour tracking subdomain — click to copy (e.g., email)
TypeCNAME
ValueThe target domain to point to
Current ValueWhat DNS currently resolves to (fetched automatically)

Pros:

  • Simple DNS configuration
  • No server-side setup required

Cons:

  • Exposes Mumara's IP in trace routes

.htaccess​

Uses Apache .htaccess rewrite rules for redirection.

Configuration:

  1. Click Download File to get the .htaccess file
  2. Extract the downloaded file
  3. Upload the .htaccess file to the root folder of your tracking domain
ColumnDescription
HostYour tracking subdomain — click to copy
TypeCNAME (still requires DNS pointing)
ValueThe target domain
Current ValueCurrent DNS resolution (fetched automatically)

Pros:

  • Hides the primary domain IP in trace routes
  • More control over redirects

Cons:

  • Requires Apache web server
  • Requires file upload access to tracking domain

Index / Cloak​

Uses a PHP file for cloaking/redirection.

Configuration:

  1. Click Download File to get the PHP cloak file
  2. Place the file at the root folder of your tracking domain

Requirements:

  • allow_url_fopen must be enabled in PHP settings
ColumnDescription
HostYour tracking subdomain — click to copy
TypeCNAME
ValueThe target domain
Current ValueCurrent DNS resolution (fetched automatically)

Pros:

  • Hides the primary domain completely
  • Works with any web server supporting PHP

Cons:

  • Requires PHP support on tracking domain
  • Requires specific PHP configuration

Bounce Domain Configuration​

When bounce processing is enabled (via IMAP settings), additional DNS records are required for proper bounce handling.

Bounce Prefix​

The subdomain prefix used for bounce handling (e.g., "bounce"). This prefix can be edited inline on the domain details page.

SPF Record​

An SPF record must be added for the bounce subdomain:

ColumnDescription
HostBounce prefix + subdomain — click to copy (e.g., bounce.newsletters.marketing)
TypeTXT
ValueSPF include value (e.g., v=spf1 include:spf.mumara.com ~all)
Current ValueCurrent DNS value (fetched automatically)

MX Record​

An MX record must be added for the bounce subdomain:

ColumnDescription
HostBounce prefix + subdomain — click to copy
TypeMX
ValueBounce mail server domain
Current ValueCurrent DNS value (fetched automatically)

DNS Current Values​

All DNS record tables fetch their Current Value column automatically when the page loads. The system uses multiple DNS lookup methods with automatic fallback to ensure reliable results.

A loading spinner is displayed in the Current Value column while the lookup is in progress. If no value is found after all methods are tried, "No value found" is displayed.

Verification Process​

Domain Ownership Verification​

When enabled in application settings:

  1. Add a new sending domain
  2. Choose verification method (DNS Record or Upload File)
  3. Configure DNS or upload file as instructed
  4. Click Verify Domain
  5. Upon success, you're redirected to the DNS authentication page

The verification checks all TXT records for the domain (not just the first one) and handles quoted values and whitespace automatically.

DKIM Verification​

  1. DKIM keys are auto-generated when you first access the DNS page
  2. Enable Sign Outgoing Emails
  3. Copy the DKIM record details (click host to copy)
  4. Add TXT record to your DNS
  5. Wait for DNS propagation (up to 48 hours)
  6. Click Recheck or Verify domain key from actions menu
  7. Status changes from PENDING to PASSED

Tracking Domain Verification​

  1. Enable Tracking Domain
  2. Choose redirection type (CNAME, .htaccess, or Index/Cloak)
  3. Configure DNS or upload files as required
  4. Click Recheck or Verify tracking domain from actions menu
  5. Status changes from PENDING to PASSED

Bounce Domain Verification​

  1. Enable bounce processing
  2. Add SPF TXT record to your DNS
  3. Add MX record to your DNS
  4. Click Recheck to verify both records
  5. Both SPF and MX must pass for bounce verification

Verification Statuses​

StatusMeaning
PendingVerification not yet attempted or in progress
PassedDNS record verified successfully
FailedDNS record not found or incorrect

Managing Sending Domains​

Viewing Domain Details​

  1. Click on the domain name in the list, OR
  2. Click ... menu → View sending domain

Verifying DNS Records​

Verify DKIM:

  1. Click ... menu → Verify domain key
  2. System checks DNS for DKIM record
  3. Status updates to Passed or Failed

Verify Tracking:

  1. Click ... menu → Verify tracking domain
  2. System checks DNS/file configuration
  3. Status updates to Passed or Failed

Manual Ownership Verification​

If automatic verification isn't working:

  1. Click ... menu → Set ownership as verified
  2. Domain ownership is manually marked as verified

Downloading DKIM Keys​

  1. Click ... menu → Download domain key pair
  2. Download contains public and private key files
  3. Use for backup or external configuration

Deleting a Domain​

  1. Click ... menu → Delete
  2. If the domain is assigned to lists or sending nodes, you'll see a dependency check modal
  3. Optionally reassign assets to another domain before deletion
warning

Deleting a domain used by contact lists or sending nodes requires unassigning or reassigning those assets first.

DNS Record Reference​

SPF Record​

PropertyValue
TypeTXT
HostBounce prefix + subdomain (e.g., bounce)
Valuev=spf1 include:_spf.mumara.com ~all

DKIM Record​

PropertyValue
TypeTXT
Hostselector._domainkey + subdomain
Value(auto-generated by Mumara — starts with v=DKIM1; k=rsa; p=...)

Tracking CNAME​

PropertyValue
TypeCNAME
HostTracking prefix (e.g., email)
Value(provided by Mumara — your primary domain)

MX Record​

PropertyValue
TypeMX
HostBounce prefix + subdomain
Value(provided by Mumara — bounce server domain)

Best Practices​

Domain Selection​

  • Use main domain — Increases trust factor with recipients and providers
  • Consistent branding — Use your primary brand domain for recognition
  • Plan for growth — Consider multiple domains for different business units if needed

DNS Configuration​

  • Click to copy — Use the click-to-copy feature on host records to avoid typos
  • Verify records carefully — Ensure you only copy the bold portion (your DNS zone adds the registrable domain automatically)
  • Check propagation — Use DNS lookup tools to verify before clicking Recheck
  • Document configurations — Keep records of DNS settings
  • Set appropriate TTLs — Lower TTLs for faster changes

Security​

  • Protect DKIM keys — Keep private keys secure
  • Use HTTPS — Enable "Use Secure URL" for tracking when SSL is available
  • Implement DMARC — Add DMARC policy to your domain
  • Monitor reports — Review authentication reports for issues

Verification​

  • Verify before sending — Always verify domains before campaigns
  • Check regularly — DNS changes can break authentication
  • Re-verify after changes — Use Recheck button after DNS updates

Troubleshooting​

DKIM Keys Show "No Key Found"​

Possible causes:

  • OpenSSL configuration not available on the server
  • Key generation failed during auto-generation

Solutions:

  • Click Regenerate Keys to manually trigger key generation
  • Check that OpenSSL is properly configured on your server
  • Verify the OPENSSL_CONF environment variable points to a valid openssl.cnf file

DKIM Verification Failed​

Possible causes:

  • DNS record not added
  • Wrong host name (check you copied only the bold portion)
  • Public key truncated
  • DNS propagation not complete

Solutions:

  • Verify TXT record exists in DNS
  • Click the host record to copy the exact value needed
  • Ensure full public key is in record (long TXT values may need to be split)
  • Wait up to 48 hours for propagation

Domain Ownership Verification Failing​

Possible causes:

  • TXT record not yet propagated
  • DNS provider returning cached results
  • Record added with wrong host name

Solutions:

  • Wait for DNS propagation (up to 48 hours)
  • The system checks all TXT records for your domain, not just the first one
  • The system automatically falls back to alternative DNS lookup methods if the primary method fails
  • Verify the Current Value column shows your expected hash value
  • As a last resort, use Set ownership as verified from the domain list actions

Current Value Shows "No Value Found"​

Possible causes:

  • DNS record not yet added or propagated
  • Local DNS resolver cannot reach the record
  • Deeply nested subdomains may not resolve with all DNS lookup methods

Solutions:

  • The system automatically falls back to alternative DNS methods
  • Wait for DNS propagation
  • Verify the record exists using an external DNS lookup tool (e.g., MXToolbox)

Tracking Domain Not Working​

Possible causes:

  • CNAME not configured correctly
  • .htaccess file not uploaded
  • PHP file missing or misconfigured
  • SSL certificate issues
  • DocumentRoot not pointing to Mumara's root directory

Solutions:

  • Verify DNS record for CNAME type
  • Check file exists at tracking domain root
  • Ensure allow_url_fopen is enabled for Cloak/Index method
  • Check tracking domain has valid SSL certificate if "Use Secure URL" is enabled
  • If using CNAME, ensure the server's DocumentRoot points to Mumara's installation directory

Domain Shows Warning Status​

Possible causes:

  • DKIM verification failed
  • Tracking domain verification failed
  • Bounce domain issues (SPF or MX)

Solutions:

  • Click Recheck to re-verify all records
  • Fix any failed verifications
  • Review and correct DNS records

DNS Provider Guides​

Adding Records in Common Providers​

Cloudflare:

  1. Login to dashboard → Select domain → DNS
  2. Click Add Record
  3. Enter Type, Name, Content
  4. Save

GoDaddy:

  1. Login → My Products → DNS
  2. Click Add under Records
  3. Select type, enter details
  4. Save

Namecheap:

  1. Login → Domain List → Manage
  2. Advanced DNS → Add New Record
  3. Enter details → Save

AWS Route 53:

  1. Login → Route 53 → Hosted zones
  2. Select domain → Create record
  3. Enter details → Create

Next Steps​

Last updated on