How to Add and Verify a Sending Domain in Sparkforge Email

By Sparkforge Support Team ·Last reviewed May 3, 2026

Add your domain under Settings > Email Services > Dedicated Domain & IP, then either auto-configure with a supported DNS provider or paste the SPF, DKIM, DMARC, CNAME, and MX records manually. SSL issues 1–10 minutes after verification.

Verifying a sending domain protects your reputation, blocks spoofing, and keeps your email out of spam. Sparkforge accepts any domain or subdomain you control — a subdomain like mail.yourdomain.com is the recommended setup.

Before you start

Login to your DNS provider (Cloudflare, GoDaddy, AWS Route 53, Namecheap, Google Domains, etc.).
The domain or subdomain you want to send from.
Permission to add or edit DNS records.
A basic grasp of TXT, CNAME, MX, SPF, DKIM, and DMARC records.

Step 1: Add the domain in Sparkforge

Go to Settings > Email Services > Dedicated Domain & IP.
Click + Add Domain in the top right.
Enter the domain or subdomain (e.g., mail.yourdomain.com).
Click Add & Verify.

Step 2: Verify DNS records

Sparkforge will show the records your domain needs. Each record type does a specific job:

SPF — declares which servers are allowed to send for the domain.
DKIM — signs outgoing email so recipients can confirm the message wasn't tampered with.
DMARC — sets the policy and reports for SPF/DKIM failures.
CNAME / MX — routing and tracking.

Option 1: Auto-configure

After adding the domain, click Continue.
Sparkforge detects your DNS provider (Cloudflare, GoDaddy, Namecheap, etc.).
Authorize Sparkforge to write the records.
The domain status changes to Verified once propagation finishes.

If your provider isn't supported, you'll fall through to manual setup.

Option 2: Manual DNS setup

Sparkforge shows the exact record values — copy them as-is.

Type: TXT, CNAME, or MX as listed.
Name / Host: @ for a root domain, or just the subdomain label (e.g., mail) for subdomains.
Value: paste exactly — no extra spaces or quotes.
TTL: 5 minutes (300 seconds) where allowed.

Provider quick reference

Provider	Where to add records
Cloudflare	Domain > DNS settings
GoDaddy	Domains > Manage DNS
AWS Route 53	Route 53 > Hosted Zones
Namecheap	Domain List > Manage > Advanced DNS
Google Domains	Select domain > DNS

After verification

SSL issues 1–10 minutes after verification.
Domain status flips to Verified / Active.
Send a test email and confirm SPF and DKIM pass in the headers.
Watch DMARC reports for the first week to catch misconfigurations.

If verification fails

Compare the record value byte-for-byte against what Sparkforge displayed.
Confirm the record type (TXT vs CNAME vs MX) is right.
Check the Host field — don't double up on @ or paste the full domain into a subdomain field.
Lower TTL to 300 seconds.
Wait. DNS propagation can take 24–48 hours on slow providers.
Only one DMARC record per domain. Only one SPF TXT record per domain.

Frequently Asked Questions

Should I send from a root domain or a subdomain?

Use a subdomain like mail.yourdomain.com. It isolates your sending reputation from the root domain so a deliverability hit on marketing email doesn't damage transactional or human email.

How long does verification take?

Usually 1–10 minutes. In rare cases DNS propagation runs 24–48 hours — mostly on registrars with long default TTLs.

What if my DNS provider isn't on the auto-configure list?

Use the manual option. Copy each record value from Sparkforge and paste it into your provider's DNS panel exactly as shown.

Do I need a separate DMARC record on the subdomain?

No. A DMARC record on the root domain covers subdomains by default. Adding a second one can cause conflicts.

What breaks if SPF or DKIM is wrong?

Email lands in spam, gets quarantined, or fails outright at major mailbox providers. Your sender reputation drops fast — fix it before sending volume.