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
  • Open tracking uses your tracking domain for pixels
  • 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 AuthenticationYellowDomain awaiting verification
WarningRedDomain has unresolved verification issues

What Affects Domain Status​

The domain status is automatically calculated based on:

  • DKIM verification status
  • Tracking domain verification status
  • Bounce domain verification status
  • Whether ownership has been confirmed

If any verification fails, the domain status may show a warning until issues are resolved.

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
  • companyname.com
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, you'll see the domain details page with configuration options.

Sending Domain Authentication​

The authentication section shows:

OptionDescription
Use Secure URLEnable HTTPS for tracking links
Domain StatusToggle to enable/disable the domain
RecheckButton to re-verify all DNS records

DKIM Authentication​

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

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 before enabling.

DKIM Record Configuration​

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

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

Adding the DKIM Record​

  1. Copy the Host value
  2. Copy the Value (DKIM public key)
  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.

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

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 (e.g., email.yourdomain.com)
TypeCNAME
ValueThe target domain to point to
Current ValueWhat DNS currently resolves to

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

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

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

Pros:

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

Cons:

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

Verification Process​

DKIM Verification​

  1. Enable Sign Outgoing Emails
  2. Copy the DKIM record details
  3. Add TXT record to your DNS
  4. Wait for DNS propagation (up to 48 hours)
  5. Click Verify domain key from actions menu
  6. Status changes from PENDING to PASSED

Tracking Domain Verification​

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

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. Confirm deletion
warning

Deleting a domain used by contact lists or sending nodes requires updating those configurations first.

DNS Record Reference​

SPF Record​

PropertyValue
TypeTXT
Host@ or subdomain
Valuev=spf1 include:_spf.mumara.com ~all

DKIM Record​

PropertyValue
TypeTXT
Hostselector._domainkey.yourdomain.com
Value(provided by Mumara - starts with v=DKIM1; k=rsa; p=...)

Tracking CNAME​

PropertyValue
TypeCNAME
HostTracking prefix (e.g., email)
Value(provided by Mumara)

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​

  • Verify records carefully - Copy exact values provided
  • Check propagation - Use DNS lookup tools to verify
  • 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
  • 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 Verification Failed​

Possible causes:

  • DNS record not added
  • Wrong host name
  • Public key truncated
  • DNS propagation not complete

Solutions:

  • Verify TXT record exists in DNS
  • Check host matches exactly (including selector)
  • Ensure full public key is in record
  • Wait up to 48 hours for propagation

Tracking Domain Not Working​

Possible causes:

  • CNAME not configured correctly
  • .htaccess file not uploaded
  • PHP file missing or misconfigured
  • SSL certificate issues

Solutions:

  • Verify DNS record for CNAME type
  • Check file exists at tracking domain root
  • Ensure allow_url_fopen is enabled for Cloak
  • Check tracking domain has valid SSL certificate

Domain Shows Warning Status​

Possible causes:

  • DKIM verification failed
  • Tracking domain verification failed
  • Bounce domain issues

Solutions:

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

Domain Status Pending​

Possible causes:

  • Initial verification not complete
  • DNS changes not detected
  • Manual confirmation needed

Solutions:

  • Complete DNS configuration
  • Click verification options in actions menu
  • Use "Set ownership as verified" if needed

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