Suped

How to set up DMARC/DKIM/SPF for Jellyfish

Published 22 Nov 2026
Updated 22 Nov 2026
11 min read
Summarize with
How to set up DMARC/DKIM/SPF for Jellyfish
Set up SPF and DKIM for the Namecheap mail service behind Jellyfish, then publish a DMARC TXT record at your domain's _dmarc hostname. Private Email uses include:spf.privateemail.com for SPF; cPanel provides the SPF record and DKIM key for your hosting account. Jellyfish filters the mail rather than providing a separate authentication setup wizard.
I identify the mailbox service and authoritative DNS provider first. Those determine which records to publish and where to publish them.

Add your domain

Connect the domain to Private Email or Namecheap cPanel mail. If mail already works through Jellyfish, keep the existing mailbox service and MX records.
  1. Private Email. Assign the domain when ordering the subscription. Open Namecheap > Private Email > Manage beside that domain. Use Create Mailbox, enter the mailbox details, and save if you need a new mailbox.
  2. cPanel mail. Confirm the domain appears in cPanel > Domains. For an additional domain, use Create A New Domain, enter its name, and submit. Use the Jellyfish hosting MX records below only for mailboxes on that hosting account.
  3. DNS location. For Namecheap BasicDNS, PremiumDNS, or FreeDNS, use Domain List > Manage > Advanced DNS. For hosting DNS, use cPanel > Zone Editor > Manage. For external nameservers, edit records at that DNS provider.
  4. Mail routing. For cPanel-hosted mailboxes using Jellyfish MX records, open cPanel > Email Routing, select the domain, choose Local Mail Exchanger, and click Change.
MX records: choose only the block for your mailbox servicedns
; Namecheap cPanel mail with Jellyfish example.com. IN MX 5 mx1-hosting.jellyfish.systems. example.com. IN MX 10 mx2-hosting.jellyfish.systems. example.com. IN MX 20 mx3-hosting.jellyfish.systems. ; Namecheap Private Email example.com. IN MX 10 mx1.privateemail.com. example.com. IN MX 10 mx2.privateemail.com.
For externally registered domains, Private Email verifies ownership through its required DNS configuration. Its checks run every 15 minutes; activation takes up to four hours. Publish its SPF record in the next section as well.
Verify Jellyfish access through cPanel > Exclusive for Namecheap customers > Jellyfish Spam Protection > Manage beside your domain. For Private Email, use Private Email > Manage > Spam Filter > Manage. Send and receive a mailbox test.
Illustrative Namecheap cPanel view of the Jellyfish domain Manage action.
Illustrative Namecheap cPanel view of the Jellyfish domain Manage action.

Set up SPF

SPF authorizes the sending IP for the SMTP MAIL FROM domain, usually shown in Return-Path after delivery. Jellyfish supports mail using your domain there; I verify that identity on a delivered message.
  1. Private Email. Publish the TXT value below at @ when Private Email is your only sender. If an SPF record already exists, merge the include into that record instead of adding another SPF record.
  2. cPanel mail. Open Email > Email Deliverability > Manage beside the domain. Under SPF, copy the suggested Name and Value. Preserve other authorized senders when updating the existing record.
  3. Publish once. Use Install the Suggested Record only when cPanel controls authoritative DNS. Otherwise publish the value at your DNS provider. Keep exactly one SPF TXT record at each sending hostname.
  4. Check limits. Keep lookup-causing SPF terms within the 10-term evaluation limit, including nested includes. If the actual Jellyfish relay still fails SPF, give Namecheap support the sending IP and full headers.
Private Email SPF value: TXT at @text
v=spf1 include:spf.privateemail.com ~all
Use the service's documented SPF value. An incoming MX hostname or a Jellyfish rDNS hostname is not an instruction to add another SPF include. Namecheap's Private Email Mail Settings can manage SPF without showing it under Host Records, so check public DNS before adding a record.
Run the SPF check against the actual MAIL FROM domain. With relaxed DMARC alignment, its organizational domain must match the visible From domain for SPF to contribute to DMARC.

SPF checker

Find SPF syntax issues, lookup limits, and weak records.

?/16tests passed
If another sending application forces a provider-owned Return-Path, editing your root SPF record cannot change that identity. An SPF alignment failure is acceptable for DMARC when a valid DKIM signature meets DMARC alignment instead.
For your normal Namecheap mailbox route, test both SPF authorization and the Return-Path identity before considering SPF complete.

Set up DKIM

Publish the public key generated by the service that signs your mail. I copy the active selector and complete key rather than generating an unrelated key pair.
cPanel mail
Open Email > Email Deliverability > Manage. In DKIM, copy the suggested Name and Value. Use Generate Local DKIM Key if no local key exists. Install the public record locally and at authoritative DNS when those are different systems.
Private Email
Open Namecheap > Private Email > Manage beside the domain. Under DKIM, click Generate if needed, or Show DKIM for an existing key. Copy the DNS Record value and the hostname shown for your subscription.
  1. Select the hostname. Private Email subscriptions purchased before June 2, 2026 use default._domainkey. Newer subscriptions use privateemail._domainkey. For cPanel, use its displayed hostname.
  2. Publish the key. Add a TXT record at that selector hostname using the entire public value. Keep long TXT values as one logical record, even when the DNS editor splits it into character strings. Keep the private key off DNS.
  3. Verify signing. Send a fresh message and read d= and s= in DKIM-Signature. The signature must validate, and d= must meet your DMARC alignment setting against the visible From domain.
Use the hostname shown in the account if your subscription differs. A key at default._domainkey cannot validate a signature using s=privateemail.
DNS publication alone does not prove that the outbound route signs messages. Test the same webmail, SMTP client, or application route used in production.
Illustrative Private Email view showing where to copy the DKIM public record.
Illustrative Private Email view showing where to copy the DKIM public record.

Set up DMARC

For a domain without DMARC, start with p=none and reporting. If your domain already uses p=quarantine or p=reject, keep that policy while correcting Jellyfish authentication.
  1. Check first. Look up TXT at _dmarc.example.com. Edit an existing DMARC record instead of creating a second record at the same hostname.
  2. Add the record. In Namecheap Advanced DNS > Host Records, choose Add New Record > TXT Record, set Host to _dmarc, enter the value below, keep TTL Automatic, and save. For hosting DNS, use Zone Editor > Manage > Add Record > TXT.
  3. Set reporting. Replace dmarc@example.com with your real aggregate-report destination. Confirm it accepts reports; an ordinary mailbox collects XML attachments rather than turning them into monitoring.
  4. Keep defaults. Start with relaxed SPF and DKIM alignment unless your existing policy requires strict matching. A DMARC pass requires a passing SPF or DKIM result that also meets the relevant alignment requirement.
Starting DMARC value: TXT at _dmarctext
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Use the DMARC record generator to build the record with your actual reporting address. This policy applies to mail using your From domain across all sending services, including Jellyfish.
Check the published policy after DNS caches refresh. A lookup confirms record publication; a delivered-message test confirms that your mail passes DMARC.

DMARC checker

Look up a domain's DMARC record and catch policy issues.

?/7tests passed
A p=none policy requests monitoring without DMARC enforcement. Receivers still apply their own filtering, so an authenticated message is not guaranteed inbox placement.
If the checker finds no record, confirm you edited the authoritative DNS zone and did not accidentally create _dmarc.example.com.example.com.
Illustrative Namecheap Advanced DNS view of the DMARC TXT fields.
Illustrative Namecheap Advanced DNS view of the DMARC TXT fields.

Verify and troubleshoot

I verify a delivered message before changing enforcement. The email tester is the quickest check: send to its generated address and review the full diagnosis.
  1. Send directly. Send a new message through your usual Namecheap mailbox or application to the address shown below. Avoid forwarding the test message through another mailbox.
  2. Read the result. Check SPF authorization, DKIM validation, and DMARC alignment. Use the receiving server's Authentication-Results header when checking a separate recipient mailbox.
  3. Resolve DNS errors. For SPF permerror, check duplicate SPF records and lookup limits. For a missing DKIM key, query the exact s= selector under the d= domain. Recheck after the previous TTL expires.
  4. Test applications. Repeat for website forms and automated mail. If the application bypasses the mailbox's signing route, configure authenticated SMTP through your mail service and send another test.
A DNS checker sees published records. The message test checks the actual outbound IP and signature that reached the receiving server.
Keep the raw test message for troubleshooting. It contains the envelope identity and selector needed to diagnose an apparent mismatch.

Email tester

Send a real email to this address. Suped shows a results button when the test is ready.

?/43tests passed
This is an illustrative successful result for a newer Private Email subscription. Your receiver hostname and selector will differ.
Example received-message headerstext
From: sender@example.com Return-Path: <sender@example.com> Authentication-Results: receiver.example; spf=pass smtp.mailfrom=example.com; dkim=pass header.d=example.com header.s=privateemail; dmarc=pass header.from=example.com
A raw SPF pass with a different MAIL FROM domain does not prove DMARC alignment. If DKIM passes for your From domain, DMARC still passes when SPF fails after forwarding.

SPF alignment

DKIM alignment

DMARC

Pass
Pass
Pass
Pass
Fail
Pass
Fail
Pass
Pass
Fail
Fail
Fail
Each Pass requires both successful authentication and matching DMARC identity.
DNS checks: use your domain and the selector seen in the messagebash
dig +short NS example.com dig +short MX example.com dig +short TXT example.com dig +short TXT privateemail._domainkey.example.com dig +short TXT default._domainkey.example.com dig +short TXT _dmarc.example.com

Get alerted when it breaks

Suped is our DMARC reporting and email authentication platform. Its DMARC monitoring turns receiver reports into source-level authentication results and detected issues, so a changed sending route does not depend on someone repeating a manual test.
  1. Enable notifications. In Suped notification settings, enable Issues detected and Sending sources need verification. Enable DMARC summary emails for routine review.
  2. Investigate the source. When notified, inspect the affected source and record details. Compare the sending IP, MAIL FROM domain, and DKIM d= with the expected Namecheap route before verifying a source as legitimate.
  3. Apply the fix. Use Suped's issue-specific steps to identify the correction, make the change in Namecheap or authoritative DNS, and retest a message. Use DNS history to check for an unexpected record change.
Keep report delivery active and review newly detected sources before authorizing them. A Jellyfish hostname alone is not proof that a sender belongs to your business.
Allow for report delays
DMARC aggregate reports normally arrive daily. Suped's notifications depend on the data received, so they are not instant notifications for every failed message. Use a fresh message test immediately after an authentication change.

Secure your domain with p=reject

I move to p=reject after reports and message tests confirm the legitimate sending routes. A high overall pass rate alone is insufficient if a low-volume billing system still fails authentication.
  1. Inventory senders. Use Suped's source view to review Namecheap mail and every other service using your From domain. Include infrequent sending jobs and forwarded-mail paths in the review.
  2. Fix legitimate failures. Confirm each approved source has passing SPF alignment or passing DKIM alignment. Keep DKIM working for routes where forwarding changes the SPF result.
  3. Stage enforcement. After resolving known failures, move p=none to p=quarantine if you need an intermediate stage. Review reports and delivery failures, then set p=reject. Keep an already enforced policy in place.
  4. Review subdomains. Check explicit subdomain policies and the sp tag before changing the parent policy. Keep reporting and Suped notifications enabled after enforcement.
Reject affects legitimate failures too
p=reject asks receiving servers to reject messages that fail DMARC. Resolve known legitimate failures first. The policy protects use of your domain in the From address; it does not prevent display-name impersonation or mail using a lookalike domain.
Suped's Hosted DMARC lets your team manage policy changes from the dashboard after its DNS setup. Use the source diagnostics to decide when to change policy; keep SPF and DKIM configuration in the appropriate Namecheap mail service.
Enforced DMARC value: retain your actual reporting destinationtext
v=DMARC1; p=reject; rua=mailto:dmarc@example.com
Retain your real reporting destination when changing the policy. After the change, confirm the published record and test each production sending route.

Frequency asked questions

The jellyfish.systems suffix is associated with Namecheap's Jellyfish filtering infrastructure, used with services including Private Email and Shared Hosting mail. Check the connecting IP's actual PTR record and trusted receiver headers. The suffix alone does not identify the customer or authenticate the From address.

Use your mailbox service's instructions. Private Email publishes v=spf1 include:spf.privateemail.com ~all. Namecheap cPanel mail provides a suggested record under Email Deliverability > Manage. Merge authorized senders into one SPF record at each hostname.

Namecheap documents default for subscriptions purchased before June 2, 2026 and privateemail for newer subscriptions. Copy the hostname shown in your account and verify it against s= in a new message's DKIM-Signature header. cPanel's selector comes from its own Email Deliverability settings.

Yes. A valid DKIM signature whose d= domain meets the From-domain alignment requirement is sufficient for DMARC. This is useful after forwarding or when an application uses a provider-owned Return-Path. A DKIM pass for an unrelated domain is insufficient.

Check for the wrong selector, a truncated public key, cached DNS, or a message sent through a different signing route. Message changes after signing also break validation. Compare the actual d= and s= values with DNS, then send a fresh test through the same production route.

Publishing p=reject tells receiving servers how to handle mail that claims your From domain and fails DMARC. Jellyfish's incoming filtering remains controlled by its separate settings. Keep monitoring your domain's legitimate outbound mail after changing enforcement.
DMARC monitoring

Start monitoring your DMARC reports today

Suped DMARC platform dashboard
What you'll get with Suped
Real-time DMARC report monitoring and analysis
Automated alerts for authentication failures
Clear recommendations to improve email deliverability
Protection against phishing and domain spoofing