Suped

How to set up DMARC/DKIM/SPF for Cbsolt

Published 22 Nov 2026
Updated 22 Nov 2026
10 min read
Summarize with
How to set up DMARC/DKIM/SPF for Cbsolt, with email and DNS symbols.
To set up DMARC, DKIM, and SPF for Cbsolt, authorize its outbound servers in the SPF record for your envelope-sender domain, activate DKIM signing with your own domain, and publish a DMARC TXT record at _dmarc on your From domain. I verify a freshly delivered email before changing the DMARC policy.
Cbsolt supports return-path alignment, so SPF can contribute to a DMARC pass. DKIM also needs a passing signature whose signing domain matches your From domain under your DMARC alignment settings. Start with p=none when introducing DMARC; keep an existing p=quarantine or p=reject policy.

Add your domain

I start with the hosting administrator and access to the authoritative DNS zone. Domain provisioning belongs in the Cbsolt hosting account; publishing authentication records belongs wherever your DNS is managed.
I could not verify Cbsolt-specific control-panel labels or a current universal SPF include in public support documentation. Get the account-specific configuration sheet from your hosting provider, including the ownership check and DKIM records.
  1. Open the account: Use the administration portal supplied with your Cbsolt hosting account. Ask the hosting administrator to perform provisioning if your login only opens a mailbox.
  2. Provision the domain: Add your sending domain, such as example.com, or have the administrator add it. Reuse an existing domain entry rather than creating a duplicate.
  3. Verify ownership: Publish the exact verification record, with its supplied type, hostname, and value. Run the account's ownership check after the public DNS answer matches. Keep any required verification record in place.
  4. Prepare a sender: Create or select a mailbox under that domain. Obtain the account's authenticated SMTP settings and confirm that a test message leaves through Cbsolt.
Request the complete DNS handoff
Ask the hosting administrator for the current outbound SPF authorization, the envelope-sender domain, every custom DKIM selector and public DNS value, and confirmation that custom DKIM signing is active. MX changes are a separate inbound-mail migration decision.

Set up SPF

SPF checks the domain in the SMTP envelope sender, normally visible in the delivered Return-Path header. I check that domain first, because publishing SPF only on the visible From domain does not authenticate a different envelope-sender domain.
For Cbsolt, request an envelope sender under your domain. With default relaxed DMARC alignment, example.com and bounce.example.com share the same organizational domain. A Return-Path under cbsolt.net does not match a From address under example.com.
  1. Read existing DNS: Query TXT records for the actual envelope-sender domain and save the current SPF value before editing.
  2. Obtain authorization: Copy the outbound SPF include or IP mechanisms supplied for your Cbsolt account. Do not derive an include from the service name or copy its MX IPs.
  3. Merge the record: Keep exactly one TXT record beginning v=spf1 at each SPF owner name. Insert Cbsolt's authorization before the final all mechanism and preserve other authorized senders.
  4. Publish and check: Save the record on the envelope-sender domain. Check the complete evaluation against the 10 DNS-lookup limit, including nested includes. SPF records are not inherited by subdomains.
SPF template only, replace the uppercase placeholdertext
Name: example.com Type: TXT Value: v=spf1 include:SPF_HOST_FROM_PROVIDER ~all
SPF_HOST_FROM_PROVIDER is a placeholder, not a verified Cbsolt hostname. Replace it with the value issued for your account. This template assumes Cbsolt is the only sender; retain the authorization for any other legitimate senders.
Check the completed DNS record below. Preserve an existing -all unless you have a specific reason to change it; an SPF fail and a DMARC reject policy are separate controls.

SPF checker

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

?/16tests passed
A valid SPF record proves that the policy can be evaluated. A received test email establishes whether the actual outbound IP passes SPF for the envelope-sender domain.
If SPF passes for cbsolt.net but SPF alignment fails for your domain, ask the hosting administrator to configure the supported domain-based return path. Passing DKIM with a matching signing domain still satisfies DMARC while that is corrected.

Set up DKIM

I request custom DKIM signing for the domain used in the From address. A passing shared provider signature alone does not establish DMARC authentication for your own domain.
  1. Generate the setup: Ask the Cbsolt administrator to enable custom DKIM and supply the selector, full DNS hostname, record type, and public value for your domain.
  2. Publish the public record: Create the supplied TXT record or CNAME delegation exactly as issued. Keep a CNAME hostname free of conflicting records, and check whether the DNS editor appends your domain automatically.
  3. Complete activation: Have the hosting administrator verify the published record and confirm that signing is active. Publishing a public key alone does not enable the server's signer.
  4. Inspect a new message: Read d= and s= in DKIM-Signature, then check the receiving server's DKIM result. The selector identifies the DNS key; the d= domain is the identity DMARC compares with your From domain.
Shared signing domain
For From: user@example.com, a valid signature with d=cbsolt.net authenticates the provider's domain. It does not satisfy DKIM alignment for example.com.
Your signing domain
For the same From address, a passing signature with d=example.com satisfies DKIM alignment. Under relaxed alignment, a signing subdomain of example.com also qualifies.
Use only the public key or delegation issued by the hosting account. Keep private keys with the signing server. During a key rotation, retain the old selector until previously signed mail has cleared delivery queues.

Set up DMARC

I publish DMARC on the domain in the visible From address. For mail sent as user@example.com, the DNS owner name is _dmarc.example.com, regardless of the Cbsolt server hostname.
If the domain already uses p=quarantine or p=reject, keep that policy and repair Cbsolt's authentication. The monitoring record below is for a domain introducing DMARC or already using p=none.
  1. Inspect the policy: Look up TXT records at _dmarc on the From domain. Edit the existing DMARC record instead of publishing a second one.
  2. Generate the value: Use the DMARC record generator to prepare the policy and reporting destination.
  3. Publish the TXT record: Set the host to _dmarc if your DNS editor appends the domain. Use the monitoring value below after replacing the example reporting address.
  4. Confirm reporting: Use a working mailbox or report-processing destination that accepts aggregate reports. For an external reporting domain, confirm that its operator publishes the required authorization.
Initial DMARC value at _dmarc.example.comtext
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Replace dmarc@example.com with your actual reporting destination. The example address does not collect reports for your organization. Leave existing reporting destinations intact unless you intend to change them.
The p=none policy requests monitoring without requesting quarantine or rejection for DMARC failures. Omitting aspf and adkim keeps their default relaxed alignment settings.

DMARC checker

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

?/7tests passed
Check that public DNS returns one valid DMARC policy at the intended owner name. DNS validation does not prove that Cbsolt is signing outgoing messages or using the expected return path.
Reporting receivers usually send aggregate data daily. Allow roughly 24-48 hours for initial reports after real mail has been sent, and investigate the reporting address and external authorization if nothing arrives. Reporting coverage depends on the receiving systems.

Verify and troubleshoot

I send a fresh email through the same Cbsolt mailbox or application route used in production. Rechecking an old message cannot demonstrate that a DNS or signing change worked.
The email tester below supplies a destination address. Send your test message to it to get a diagnosis of the received authentication results, including the domains involved.

Email tester

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

?/43tests passed
Read the Authentication-Results added by the receiving system you trust. Check the visible From domain against the authenticated envelope-sender domain and DKIM signing domain; separate pass results alone are insufficient.
This illustrative result has passing SPF and DKIM for example.com, plus a DMARC pass. The cb1 selector is an example, not a Cbsolt setup value.
Illustrative successful receiver resultstext
Authentication-Results: receiver.example; spf=pass smtp.mailfrom=example.com; dkim=pass header.d=example.com header.s=cb1; dmarc=pass header.from=example.com
  1. SPF errors: Check for duplicate SPF records, an omitted outbound server, an invalid include, or too many DNS lookups. Inspect SPF on the envelope-sender domain rather than assuming it is the From domain.
  2. DKIM failures: Query the hostname formed by the actual s= selector and d= domain. Check for a duplicated domain suffix, a wrong key, pending signing activation, or message modification after signing.
  3. Alignment failures: A pass using an unrelated provider domain does not satisfy DMARC. Obtain a matching envelope sender or custom DKIM signature. DMARC needs at least one passing method with the required domain match.
  4. Forwarded messages: Forwarding often breaks SPF. A surviving DKIM signature with a matching domain can still produce a DMARC pass. Diagnose direct Cbsolt delivery separately before changing SPF.
  5. Stale answers: Compare authoritative DNS with your recursive resolver and allow cached answers to expire according to TTL. Retest every production sending route after the update is visible.

Get alerted when it breaks

I keep authentication monitoring active after the initial test. Suped is our DMARC reporting platform, and its DMARC monitoring connects reported Cbsolt failures with source verification and specific issue-resolution steps.
  1. Enable notifications: With reports already flowing into Suped, enable Issues detected and Sending sources need verification notifications. Enable DMARC summaries for regular review.
  2. Verify the source: Confirm that the Cbsolt sending IPs and authenticated domains belong to your hosting account before marking the source as verified. An rDNS suffix alone is insufficient.
  3. Investigate a failure: Open the affected source and inspect its record details for SPF, DKIM, and DMARC results. Use the issue's fix steps and compare DNS history with recent changes.
  4. Close the loop: Assign the provider-side correction to the Cbsolt administrator, send another test message, and confirm the improvement in subsequent reports before resolving the issue.
Suped keeps source investigation and authentication history together, which makes it practical to track failures after a DNS edit or a hosting change. Keep a named owner responsible for reviewing notifications and following up with the hosting provider.
Report-based alerts depend on incoming data
DMARC aggregate reports are delayed and do not contain every message. Suped can surface an issue when the relevant data arrives; use a fresh email test and the provider's SMTP logs when a sending problem needs immediate investigation.

Secure your domain with p=reject

I move to p=reject after identifying legitimate senders and confirming that each production route passes DMARC. Suped's hosted DMARC provides policy management in the dashboard, while its source and detail views supply the evidence for each policy change.
  1. Inventory all senders: Review reports across a representative business cycle, including infrequent billing and notification mail. Confirm Cbsolt and every other authorized sending route.
  2. Fix legitimate failures: Use Suped's issue details to locate the failed method and domain mismatch. Correct Cbsolt's SPF authorization and custom DKIM setup, then test the affected route again.
  3. Stage enforcement: For a domain starting at p=none, evaluate p=quarantine before p=reject. Review new reports and delivery errors after each change. Keep an existing enforcement policy while correcting setup issues.
  4. Review subdomains: Check inherited policy and explicit subdomain DMARC records. Set sp deliberately if subdomains need a different policy; test their actual sending identities.
  5. Keep the domain match practical: Retain relaxed alignment unless you have a specific requirement for exact domain matching. p=reject does not require strict aspf or adkim settings.
Final policy example, retain your real reporting destinationtext
v=DMARC1; p=reject; rua=mailto:dmarc@example.com
Apply the policy through the domain's existing management method: hosted policy controls when configured, or its authoritative TXT record otherwise. Confirm the published policy, run another Cbsolt email test, and keep monitoring legitimate failures in Suped. A reject policy requests rejection for DMARC failures; receiving systems retain control of their handling decisions.

Frequency asked questions

Use the current include or IP authorization supplied for your Cbsolt hosting account. I have not verified a universal Cbsolt-published include. Do not assume that include:cbsolt.net is correct because cbsolt.net appears in a server hostname. Merge the supplied authorization into the existing SPF record.

A valid DKIM signature can use a provider domain unrelated to your From domain. Configure custom signing for your own domain and confirm the receiving server reports a pass for that signature. DMARC also passes when SPF passes with the required domain match, even if DKIM fails.

No. DMARC passes when DKIM passes with a signing domain that matches the From domain under the policy settings. That result is valid even when SPF alignment fails. Cbsolt supports return-path alignment, so request that configuration for direct sends; forwarding still needs separate diagnosis.

The cbsolt.net suffix is associated with Cbsolt managed email hosting infrastructure. I treat that suffix as a source-identification clue. Confirm the sending IP, trusted receiver headers, and authenticated domains with your hosting administrator before treating the traffic as authorized for your organization.

Keep an existing p=reject or p=quarantine policy. Complete and test Cbsolt authentication before routing production mail through it. The p=none starter record is for a domain introducing DMARC or already monitoring without enforcement.

No. MX records route inbound email. SPF, DKIM, and DMARC authenticate outgoing identities through their respective DNS records and server settings. Change MX only when your hosting migration requires it, using the inbound routing values supplied for your account.
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