How to set up DMARC/DKIM/SPF for Carrierzone
Published 22 Nov 2026
Updated 22 Nov 2026
10 min read
Summarize with

Authenticate Carrierzone email by publishing your account's SPF include, enabling DKIM signing for your domain and adding a DMARC TXT record. A documented c40 setup uses include:spfc40.carrierzone.com and the DKIM CNAME hmail._domainkey pointing to hmail._domainkey.carrierzone.com. Confirm those values with your hosting provider before publishing them.
I check a delivered message before changing DNS because hosted websites and mailbox accounts do not always use the same outbound route. DMARC passes when SPF or DKIM passes with domain alignment to the visible From address.
Add your domain
Start in the hosting account that supplies your Carrierzone email service. The domain must be provisioned there, and DNS changes must be made at its authoritative DNS host. Carrierzone's public website does not provide a documented domain onboarding wizard.
- Select the domain. Sign in to your hosting provider's account and select the domain attached to your website or email service. For a new domain, ask that provider to provision the domain and the sending mailbox before testing.
- Confirm DNS access. Look up the domain's NS records and open the DNS editor for those nameservers. Export or copy the current zone before editing it.
- Get account values. Ask hosting support for the outbound SPF include, DKIM selector and target, and confirmation that signing is enabled for your domain. Also confirm the SMTP server and supported custom envelope sender.
- Verify the sender. Send a message through the actual mailbox or application. Record the visible From domain, Return-Path domain and DKIM signing domain. Complete any domain ownership check your hosting provider supplies; do not invent a verification TXT record.
Identify the authoritative DNS host and existing mail routingtext
dig +short NS example.com dig +short MX example.com
The c40 SPF and hmail DKIM examples are recorded in a customer's Carrierzone support exchange. They are account examples, not universal settings. Keep existing MX records unless you are deliberately changing where incoming mail is delivered.
Set up SPF
Carrierzone supports a matching Return-Path domain. SPF checks the SMTP envelope sender, so publish SPF at that domain, including a subdomain if your application uses one.
- Read the existing record. Query TXT records at the envelope sender domain. Keep exactly one record beginning with v=spf1; leave unrelated TXT records intact.
- Confirm the include. Use the hostname assigned by hosting support. Use spfc40.carrierzone.com only for an account confirmed to use that include; do not guess the cluster number from an MX hostname.
- Merge authorized senders. Add the confirmed include before the existing all mechanism. Preserve other legitimate senders and keep one final all mechanism. The example below applies only when the confirmed c40 service is the sole sender.
- Check the envelope. Set the application's supported envelope sender to your domain or an appropriate subdomain. With default relaxed DMARC alignment, it must share the organizational domain of the visible From address.
Example SPF TXT value for a confirmed c40 accounttext
v=spf1 include:spfc40.carrierzone.com ~all
In the DNS editor, use type TXT and the host name of the envelope sender domain. Use @ for the zone root when your DNS editor supports that notation. Enter the value without extra surrounding quotes.
Check the complete SPF evaluation against the 10 DNS lookup limit, including nested includes. Do not substitute include:carrierzone.com or include an MX hostname without an explicit instruction from the provider and a valid SPF record at that hostname.
SPF checker
Find SPF syntax issues, lookup limits, and weak records.
?/16tests passed
Enter the actual envelope sender domain above. Correct duplicate SPF records, unresolved includes and lookup-limit errors, then wait for the previous DNS TTL to expire before retesting.
A passing SPF result for a Carrierzone-owned Return-Path does not establish SPF alignment for your domain. Request the supported custom Return-Path configuration. A passing DKIM signature with a matching domain still satisfies DMARC while that SPF alignment issue is being resolved.
Set up DKIM
DKIM requires both a published public key and outbound signing by Carrierzone. Adding a DNS record alone does not turn signing on. I verify the signing domain in a delivered message after publishing the record.
- Confirm the selector. Ask support whether your account uses the hmail selector and the target below. Use a different selector or target if support supplies one.
- Publish the CNAME. For the documented hmail configuration, create a CNAME named hmail._domainkey in your domain's zone. Point it to hmail._domainkey.carrierzone.com, without adding your domain to the target.
- Avoid a name conflict. Do not publish a TXT record and CNAME at the same selector name. If a record already exists there, confirm which active service owns it before replacing it.
- Activate and test signing. Have hosting support confirm signing for your domain, then send a fresh message. Check for dkim=pass, selector hmail and a signing domain matching your From domain under the applicable DMARC alignment mode.
DKIM CNAME example, subject to account confirmationtext
hmail._domainkey IN CNAME hmail._domainkey.carrierzone.com.
DKIM that satisfies DMARC
For From: sender@example.com, a passing signature with d=example.com satisfies DKIM alignment. A signing subdomain also works under relaxed alignment when it shares the same organizational domain.
DKIM that does not satisfy DMARC
For From: sender@example.com, a passing signature with d=carrierzone.com does not satisfy DKIM alignment. Pointing your selector CNAME to Carrierzone is valid; the signature's d= domain is what matters.
If the application sends through a local web server, confirm that its outbound route receives the same DKIM signing as mailbox SMTP. Test the website form separately after any routing change.
Set up DMARC
For a domain without an enforcement policy, start with p=none and collect aggregate reports. If the domain already uses p=quarantine or p=reject, keep that policy and repair Carrierzone authentication without weakening it.
- Read the current policy. Query TXT records at _dmarc.example.com. Edit the existing DMARC record if one exists; do not create a second policy record.
- Prepare the report mailbox. Create a working destination for aggregate XML reports. Replace dmarc@example.com below with your real reporting address before publishing.
- Publish the TXT record. Use type TXT and name _dmarc in the example.com DNS zone. Keep the current reporting destinations when updating an existing policy.
- Confirm report authorization. If the reporting address is on another domain, follow that recipient's external reporting authorization instructions. Leave aspf and adkim at their relaxed defaults unless you have a tested reason to require strict matching.
Initial DMARC TXT value at _dmarc.example.comtext
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Use the DMARC record generator to build the record with your real report destination. The rua address receives reports; it does not enable DKIM or authorize outbound IP addresses.
Check the published policy below after saving DNS. A valid record confirms DNS configuration; a delivered-message test confirms whether Carrierzone mail actually passes DMARC.
DMARC checker
Look up a domain's DMARC record and catch policy issues.
?/7tests passed
Enter the visible From domain. Resolve missing or duplicate policies and reporting-address errors before relying on aggregate reports.
p=none requests monitoring without requesting quarantine or rejection for DMARC failures. Receiving systems still apply their own filtering. Reports usually arrive on a daily cycle, and not every recipient system sends them.
Verify and troubleshoot
I test each sending route independently: a mailbox SMTP test does not prove that a hosted contact form uses the same envelope sender or DKIM signer.
- Send through production. Trigger a real website form, application notification or mailbox message with the normal From address. For contact forms, put the visitor's address in Reply-To and use your authenticated domain in From.
- Inspect trusted results. Read Authentication-Results added by the final receiving system. Compare smtp.mailfrom and header.d with header.from; do not rely on authentication text inserted by the sender.
- Trace SPF failures. Check the connecting outbound IP, the envelope sender domain and that domain's SPF record. For an unmatching Return-Path, configure Carrierzone's supported custom envelope sender.
- Trace DKIM failures. For dkim=none, check signing activation and the outbound route. For a failed signature, check the selector's DNS target, key availability and message changes after signing.
- Recheck DNS. Query the live records below and repeat the message test after cached records expire. Replace the selector if your provider assigned one other than hmail.
Check the published recordstext
dig +short TXT example.com dig +short CNAME hmail._domainkey.example.com dig +short TXT hmail._domainkey.example.com dig +short TXT _dmarc.example.com
|
|
|
|---|---|---|
SPF | Pass, matching domain | Wrong include or route |
DKIM | Pass, matching domain | Missing signer or key |
DMARC | Pass | Neither path matches |
Website form | Own domain in From | Visitor address in From |
DMARC needs at least one passing authentication method with domain alignment.
The email tester is the quickest check of a real message. It prompts you to send a test email and returns a diagnosis covering authentication and delivery-related checks.
Send to the generated test address through the same Carrierzone route your application normally uses. Save the results so a later failure can be compared with a known working message.
Email tester
Send a real email to this address. Suped shows a results button when the test is ready.
?/43tests passed
Confirm DMARC passes and inspect both authentication domains. A successful DNS lookup alone does not prove DKIM signing is active or that SPF covers the actual outbound server.
If authentication passes but delivery still fails, capture the recipient's exact SMTP rejection and the test timestamp for hosting support. Authentication does not guarantee inbox delivery.
Get alerted when it breaks
Suped is our DMARC platform. Its DMARC monitoring turns aggregate reports into source-level authentication results, detected issues and notification emails, so Carrierzone failures do not depend on someone repeating a manual test.
- Enable issue notifications. In Suped's notification settings, enable Issues detected and Sending sources need verification. Enable DMARC summary emails for routine review.
- Verify the Carrierzone source. Check the sending IPs and authentication domains against the service your hosting provider confirmed. Verify legitimate sources after that review; a familiar rDNS suffix is insufficient.
- Investigate the affected records. When an issue arrives, inspect the Carrierzone source and individual record diagnostics. Separate SPF authorization failures, DKIM failures and domain alignment problems.
- Confirm the repair. Follow the issue's fix steps, repeat the production-route email test and review fresh aggregate data. Use DNS history when a failure coincides with a record change.
Alerts follow report availability
Suped detects issues in the data it receives. DMARC aggregate reports are delayed, so these alerts are not instantaneous notifications for each outgoing message. Use a fresh email test when you need immediate confirmation after a change.
Secure your domain with p=reject
Move to p=reject after all legitimate sending routes pass DMARC consistently. I check each source and its business purpose before enforcement; a high overall pass rate can hide a broken low-volume application.
- Cover the full sending cycle. Review Carrierzone mailbox traffic, website messages and scheduled application jobs, plus every other legitimate sender using the domain.
- Fix legitimate failures. Use Suped's source table and record diagnostics to resolve failures. Prefer working DKIM with a matching domain on every route because forwarding frequently breaks SPF.
- Stage enforcement. For a domain starting at p=none, change to p=quarantine and review fresh reports and delivery problems before advancing. Keep existing enforcement while correcting a newly added sender.
- Advance with evidence. Set p=reject once intended messages pass reliably. Keep aggregate reporting enabled and review subdomain policies before applying the same protection across them.
- Keep monitoring active. After the change, review Suped issue alerts and new-source notifications. Retest Carrierzone after hosting migrations, SMTP routing changes or DKIM key changes.
Final policy example after authentication is verifiedtext
v=DMARC1; p=reject; rua=mailto:dmarc@example.com
Replace the example report address and retain any other required DMARC settings. A reject policy requests rejection when neither SPF nor DKIM passes with domain alignment; receivers retain control over final handling.
Suped's Hosted DMARC supports managing the policy in the dashboard after its DNS setup. Together with source verification and issue diagnostics, this gives a team managing Carrierzone a concrete way to base each policy change on observed mail.
Frequency asked questions
The carrierzone.com suffix is associated with Carrierzone hosting mail infrastructure. Hostnames such as mail314c28.carrierzone.com appear in mail routing records. Confirm the connecting IP and its reverse DNS, then inspect the message's authentication domains. Carrierzone also handles forwarded mail, so the suffix alone does not identify the original sender or prove authorization.
No. It is a documented c40 account example. Get the include assigned to your account from your hosting provider, and merge it into the single SPF record at the envelope sender domain. Do not infer the include solely from an MX hostname.
No. The CNAME publishes a path to the public key. Carrierzone must also sign outgoing messages for your domain. Confirm dkim=pass and a signing domain matching the visible From domain after your hosting provider confirms signing activation.
SPF can pass for a Return-Path domain that differs from the visible From domain. If DKIM also lacks a passing signature with a matching domain, DMARC fails. Configure the supported custom Return-Path or repair DKIM signing for your domain.
The website can use a different outbound route or envelope sender. Test the form itself, use your domain in From and put the visitor's address in Reply-To. Ask hosting support to confirm that the application's outbound route is covered by the assigned SPF include and receives DKIM signing.
Keep an existing p=reject or p=quarantine policy. Correct Carrierzone's SPF and DKIM configuration and verify a fresh message. The p=none example is for an initial monitoring setup on a domain that is not already enforcing DMARC.

