Suped

How to set up DMARC/DKIM/SPF for Energe3

Published 5 Jul 2026
Updated 6 Nov 2026
14 min read
Summarize with
How to set up DMARC, DKIM, and SPF for Energe3.
Updated on 6 Nov 2026: We clarified Energe3 setup requirements, DNS verification, and DMARC enforcement, including options when custom-domain authentication is unavailable.
Authenticate Energe3 mail with your domain only when the visible From address uses a domain you control and Energe3 has supplied records for that domain. Start by sending a real enrollment or training notification, then check the visible From domain, the Return-Path domain used by SPF, and the DKIM d= domain. Use these identifiers with Authentication-Results to confirm which domain each check authenticates and whether DMARC passes.
Public learner documentation confirms emails for an Energe3-hosted training portal, but the public sources reviewed do not document a customer sender-domain screen, universal SPF include, DKIM selector, or branded Return-Path CNAME. Treat values shown inside your tenant, or supplied by your Energe3 account administrator, as the source of truth. If no custom-domain records are supplied, do not invent them or copy values from another domain.
Before you start
  1. DNS access: You need permission to add TXT and CNAME records for the domain used in the visible From address.
  2. Energe3 access: You need an account administrator who can confirm whether branded sender authentication is enabled.
  3. Real message: Use an Energe3 notification sent through the same workflow learners receive.
  4. Sender inventory: List every approved service that sends with the same visible From domain before changing DMARC.

Confirm the sending domain

The domain after @ in the visible From address is the DMARC Author Domain. The Return-Path identifies the domain SPF authenticates, while the d= value in the DKIM-Signature identifies the signing domain. If the visible From address uses an Energe3-owned domain, only that domain's owner can publish its DMARC record. In that case, verify the delivered message instead of changing your DNS.
  1. Send a notification: Trigger an Energe3 enrollment, reminder, or learner message to a mailbox you control.
  2. Inspect the headers: Record the From, Return-Path, DKIM d=, DKIM s=, and Authentication-Results values.
  3. Confirm custom-domain support: Ask your Energe3 account administrator for the branded sender-domain procedure if no setting appears in the tenant.
  4. Enter your domain: If Energe3 provides a sender-domain field, use the domain in your intended visible From address.
  5. Copy exact DNS values: Keep each record type, host, target, selector, and TXT value unchanged.
  6. Keep the setup evidence: Save the supplied records and one successful message header for later troubleshooting.
Illustrative Energe3 sender-domain setup with pending SPF and DKIM DNS records.
Illustrative Energe3 sender-domain setup with pending SPF and DKIM DNS records.
Use these values
  1. From domain: The domain after @ in the intended Energe3 sender address.
  2. Tenant records: Only the record types and values supplied for your account.
  3. Dedicated subdomain: A bounce host used only when Energe3 instructs you to create one.
Avoid these mistakes
  1. Wrong DNS zone: Do not add records to an Energe3-owned domain.
  2. Copied records: Do not reuse DNS values from another organization or tenant.
  3. Duplicate host: Do not place a CNAME where another record already exists.
Tenant values matter
A DKIM key, selector, bounce host, or verification token can be unique to one account. Publish only the values supplied for your Energe3 tenant. If no values are available, ask the account administrator to confirm whether the platform supports authentication with your domain before making any DNS change.

If Energe3 cannot authenticate your domain

If Energe3 cannot provide authentication that satisfies DMARC for your visible From domain, pause custom-domain sending. Adding an SPF include to your root domain does not fix a message that still uses unrelated domains for both SPF and DKIM.
  1. Ask the account administrator whether a provider-managed From address is supported for your account, then verify that messages using it pass DMARC.
  2. Use your own address as Reply-To only if Energe3 supports it. Reply-To controls replies and is outside DMARC's domain checks.
  3. Keep your existing DMARC policy. A dedicated learner subdomain still needs working authentication; creating a subdomain alone does not fix DMARC.
  4. Resume sending with your own From domain only after a real notification passes DMARC. For p=reject, require valid DKIM signatures rather than relying solely on SPF.

Set up SPF

SPF checks the SMTP MAIL FROM domain, normally recorded in the delivered Return-Path header. SPF contributes to a DMARC pass when it passes and its authenticated domain shares the organizational domain of the visible From address under relaxed alignment. Publish an Energe3 SPF include or Return-Path CNAME only when your tenant or account administrator supplies it.
  1. Identify the supplied record: Confirm whether Energe3 supplied a TXT record, an include value, or a return-path CNAME.
  2. Use the exact host: Publish the record on the root or bounce subdomain specified in the setup details.
  3. Keep one SPF record: If an SPF TXT record already exists at that exact host, insert the supplied include before its final all mechanism. Keep existing approved senders and the existing ~all or -all policy instead of adding a second SPF record.
  4. Publish CNAME delegation separately: If Energe3 supplies a return-path CNAME, copy its target exactly and do not also create a TXT record at that host.
  5. Check the lookup limit: The 10-term SPF lookup limit includes nested include and redirect evaluations. Exceeding it produces permerror; remove only mechanisms for senders you have retired.
SPF TXT template when an include is supplieddns
example.com TXT v=spf1 include:ENERGE3_VALUE include:EXISTING_SENDER ~all
ENERGE3_VALUE and EXISTING_SENDER are placeholders. Replace them with confirmed include domains, and retain your existing final SPF policy. SPF records apply to the exact host being checked; a root-domain record does not automatically cover a bounce subdomain.
Illustrative Energe3 SPF setup with a Return-Path CNAME and DNS verification status.
Illustrative Energe3 SPF setup with a Return-Path CNAME and DNS verification status.

SPF checker

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

?/16tests passed
Use Suped's SPF checker on the actual Return-Path domain to check record count, syntax, and recursive lookup use. If it finds two SPF records at the same host, merge them before testing Energe3 mail again.

Check

Pass signal

Fix

Record count
One per host
Merge duplicates
Lookup-causing terms
10 or fewer
Reduce mechanisms
Return-Path
Authorized domain
Copy supplied record
DMARC match
Shared organizational domain under relaxed alignment
Use a supported branded Return-Path; strict alignment needs an exact domain match
SPF checks for Energe3

Set up DKIM

Get DKIM passing before DMARC enforcement. DKIM links the message signature to a signing domain through the d= value. It often survives ordinary forwarding when signed headers and message content remain unchanged, while SPF commonly fails after forwarding. Message modification can still break DKIM.
  1. Request the DKIM record: Use the selector and DNS value supplied for your Energe3 tenant.
  2. Confirm the record type: Energe3 must specify whether to publish a TXT public key or a CNAME target.
  3. Copy the host: Keep the full selector._domainkey host unchanged and avoid duplicating your domain suffix.
  4. Copy the value: Paste the complete public key or CNAME target without adding spaces or quotation marks.
  5. Use a strong key: Choose a 2048-bit DKIM key when the Energe3 setup supports that key length.
  6. Verify the selector: After DNS propagation, complete any verification or signing-activation step Energe3 supplies, then confirm that the selector resolves and a fresh message passes DKIM.
DKIM TXT templatedns
selector._domainkey.example.com TXT v=DKIM1; k=rsa; p=ENERGE3_PUBLIC_KEY
The selector and ENERGE3_PUBLIC_KEY in this template are placeholders. Replace them with the tenant-supplied values. If Energe3 supplies a CNAME, publish that CNAME instead of this TXT example.
Illustrative Energe3 DKIM setup with a selector and TXT public key.
Illustrative Energe3 DKIM setup with a selector and TXT public key.
DKIM pass target
Send a fresh Energe3 notification to a mailbox you control. Confirm dkim=pass and check that its d= domain meets the DMARC matching mode for the visible From domain.
  1. Authentication result: Look for dkim=pass in the Authentication-Results header.
  2. Signing domain: Under relaxed alignment, the d= domain and visible From domain must share an organizational domain.
  3. Selector value: The s= selector in the signature should match the selector published in DNS.

Set up DMARC

The owner of the visible From domain controls its DMARC policy. Start with p=none unless the domain already uses quarantine or reject. If the domain is already enforced, keep its policy and verify that Energe3 passes DMARC before sending production notifications.
  1. Create reporting: Use a reporting address that can receive and process DMARC aggregate reports. A destination outside the policy domain needs the external authorization record managed by the report recipient.
  2. Choose the policy domain: Publish at _dmarc.<visible-From-domain> and at _dmarc.<organizational-domain> when those domains differ. Review existing records and any inherited enforcement before adding a subdomain policy.
  3. Start in monitoring mode: For a domain without existing enforcement, use p=none while you identify Energe3 and every other approved sender.
  4. Keep existing enforcement: Do not weaken a quarantine or reject policy solely to add Energe3.
  5. Review aggregate reports: Confirm that Energe3 passes DMARC through SPF or DKIM with the required domain match.
The defaults adkim=r and aspf=r use relaxed alignment, which requires a shared organizational domain. With adkim=s or aspf=s, the corresponding authenticated domain must exactly match the visible From domain. Check these tags before assuming that a branded bounce subdomain is sufficient.
Recommended DMARC monitoring recorddns
_dmarc.example.com TXT v=DMARC1; p=none; rua=mailto:dmarc@example.com
For a From address such as training@learn.example.com, an explicit record is at _dmarc.learn.example.com. Without one, receivers discover an inherited policy; on an existing subdomain, the applicable organizational-domain sp policy takes precedence over p when sp is present.
Use the DMARC record generator to create a starting record with your reporting address.

DMARC checker

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

?/7tests passed
Suped's DMARC checker should find an applicable policy. If none is found, confirm the visible From domain and policy location. Keep one DMARC policy record per DNS name: RFC 9989 discards duplicate records during discovery, while older implementations can report permerror.
Do not enforce too early
Use p=reject only after Energe3 and every other approved source pass DMARC in real mail. A missing custom DKIM signature is especially risky when SPF uses a provider-owned Return-Path domain.

Use current DMARC policy tags

RFC 9989 replaced RFC 7489 as the DMARC specification, while RFC 9990 and RFC 9991 define aggregate and failure reporting. Keep v=DMARC1 as the first tag. The pct tag is historic because receivers applied percentage values inconsistently; ri and rf are also historic and should be omitted from new records.
  1. Remove pct: Do not use pct=25 or another percentage in a new or updated DMARC record.
  2. Use t=y carefully: The current test tag asks receivers to apply handling one policy level below p=quarantine or p=reject.
  3. Keep DMARC1: RFC 9989 did not change the required v=DMARC1 value.
  4. Keep aggregate reporting: The rua destination remains the basis for finding sources and authentication failures.
Alternative DMARC test-mode records (publish only one)dns
v=DMARC1; p=quarantine; t=y; rua=mailto:dmarc@example.com v=DMARC1; p=reject; t=y; rua=mailto:dmarc@example.com
Test mode is still a request
A receiver that does not recognize t ignores it and can apply the p policy as written. Receivers also apply local handling rules. Use aggregate reports and delivered-message tests to measure the effect, and do not treat t=y as a substitute for fixing legitimate sources before enforcement.

Verify and troubleshoot

Verification requires a real Energe3 message, not DNS lookups alone. Trigger an enrollment notification, course reminder, or learner email to a mailbox you control, then inspect Authentication-Results and the underlying identifiers.
Publish records with the DNS host responsible for your authoritative nameservers. Check whether its editor appends your domain automatically, so _dmarc does not become _dmarc.example.com.example.com. Keep authentication CNAMEs in DNS-only mode if a proxy option is available.
Check the saved records at the authoritative nameservers before retrying any Energe3 verification step. Cached answers persist until their TTL expires, so there is no universal 24-hour deadline. Once DNS is correct, send a fresh notification through each learner-email workflow you use.
  1. Send live mail: Use the same Energe3 workflow learners receive, not a generic DNS-only test.
  2. Check From: The visible From domain should be the domain you intended to authenticate.
  3. Check SPF: Authentication-Results should show spf=pass for smtp.mailfrom, and that domain must have DMARC domain alignment to contribute to a pass.
  4. Check DKIM: Authentication-Results should show dkim=pass for a d= domain with DMARC domain alignment.
  5. Check DMARC: Authentication-Results should show dmarc=pass when at least one authenticated identifier has domain alignment.
  6. Save raw headers: Keep the complete headers when the account administrator needs to trace the sending route.

Email tester

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

?/43tests passed
The email tester gives you a destination address for a real Energe3 message, then checks SPF, DKIM, DMARC, headers, DNS, and message content. Use its results together with the original message headers before learners receive mail.
For a broader sequence, use this verification checklist after your first Energe3 message passes.

Symptom

Likely cause

Fix

SPF fail
Sending IP not authorized for MAIL FROM, or forwarding changed the SMTP path
Check the actual Return-Path record and test a direct delivery
DKIM fail
Wrong selector or key, missing signature, or changed signed content
Check d= and s=, supplied DNS values, and signing activation
DMARC fail
Neither SPF nor DKIM passes with the required domain match
Check the From domain, adkim/aspf, DKIM, and Return-Path
SPF permerror
Duplicate or excess lookups
Merge and simplify
No reports
Missing or unauthorized rua, reporting delay, or no traffic seen by a reporting receiver
Check the report destination and external authorization; allow a reporting cycle
Common Energe3 authentication fixes
SPF exception
If Energe3 cannot use a branded Return-Path, SPF can pass for a provider-owned domain without matching your visible From domain. DMARC can still pass through DKIM when its d= domain meets the configured matching mode. Do not add an SPF include to your visible From domain unless Energe3 explicitly supplies it.

Monitor Energe3 authentication and configure alerts

Energe3 authentication can break after a DNS edit, DKIM key rotation, sender-address change, or mail-route change. Setup checks capture one point in time; DMARC aggregate reports and alerts expose later changes. Reports usually arrive daily and do not provide immediate notification of an individual learner-email failure; inspect delivery errors and headers when troubleshooting live mail.
  1. Process aggregate reports: Track Energe3 volume, source IPs, domain alignment, and policy results.
  2. Watch source changes: Investigate new infrastructure sending with your domain before approving it.
  3. Alert on failures: Notify the domain owner when Energe3 authentication results drop or selectors stop resolving.
  4. Include reputation checks: Pair authentication alerts with blocklist (blacklist) monitoring for relevant sending domains and IPs.
Suped's DMARC monitoring processes aggregate reports, identifies sending sources, and alerts the people responsible when SPF, DKIM, or DMARC results change. Suped's product also keeps the DNS fix beside the affected source.
Notification settings page with DMARC alerts, weekly summary, toggles, and preview buttons
Notification settings page with DMARC alerts, weekly summary, toggles, and preview buttons
Suped alert workflow
  1. Detect the change: Suped identifies a new source, authentication drop, or DNS issue.
  2. Notify the owner: Suped sends the alert according to the threshold and recipient settings.
  3. Review the evidence: The source and authentication result show whether Energe3 or another sender changed.
  4. Apply the fix: Use the affected record and remediation steps to make the scoped DNS change.

Secure your domain with p=reject

Move to p=reject only after Energe3 and every other approved sender pass DMARC in production. Domains publishing p=reject must apply valid DKIM signatures and must not rely solely on SPF. Use monitoring and quarantine observation periods, then compare aggregate reports before changing policy again.
  1. Monitor at p=none: For a domain also used by staff, collect at least one month of reports. Include every learner-notification cycle and any less frequent approved sender before deciding whether to enforce.
  2. Classify every source: Authenticate approved senders and investigate unknown sources before treating their failures as unauthorized use.
  3. Observe p=quarantine: For a domain also used by staff, observe quarantine for an equally long period. Review policy overrides and legitimate failures before the next change.
  4. Check indirect mail: Review mailing-list and forwarding paths used by people on the domain before reject.
  5. Publish p=reject: Publish p=reject only when reports show no unresolved legitimate source or business-critical indirect path.
  6. Keep monitoring: Continue alerts after enforcement because vendor routing and DNS records change.
DMARC enforcement stages (publish only one record)dns
v=DMARC1; p=none; rua=mailto:dmarc@example.com v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com v=DMARC1; p=reject; rua=mailto:dmarc@example.com
Enforcement readiness
Base the decision on unresolved legitimate mail, not a pass-rate percentage alone.
Ready
No legitimate failures
Energe3 and every approved source pass across normal sending cycles.
Review
Known work remains
A known legitimate source or indirect mail path still needs a decision.
Hold
Unresolved failures
Reports contain unexplained sources or business-critical failures.
Hosted DMARC configuration dialog showing policy controls, CNAME setup, and expanded advanced options
After the initial DNS delegation, Suped's Hosted DMARC lets you change policy in Suped's product without editing DNS at each stage. Use its reports to confirm Energe3 and other approved sources before moving to quarantine or reject, then keep alerts active after enforcement.

FAQ

When Energe3 sends with a domain you control, configure the tenant-supplied DKIM record, configure SPF or a branded Return-Path when supplied, and publish DMARC for the visible From domain. If the visible From address uses an Energe3-owned domain, its owner manages those records and you verify the delivered headers.

The public sources reviewed do not establish a universal Energe3 SPF include. Copy only the SPF include, TXT value, or Return-Path CNAME supplied inside your tenant or by your Energe3 account administrator. Do not publish a guessed include.

Keep an existing reject policy when real Energe3 mail passes DMARC with valid DKIM signing. For a new deployment, monitor all sending cycles and resolve legitimate failures before enforcement. On a domain also used by staff, observe at least a month at p=none and an equally long period at p=quarantine before considering reject.

SPF fails when the Return-Path domain does not authorize the sending IP, a supplied CNAME is missing, or forwarding changes the evaluated SMTP path. DKIM still passes when the signature validates. DMARC passes if the successful DKIM d= domain has domain alignment with the visible From domain.

SPF and DKIM can both pass for provider-owned domains while neither satisfies DMARC for your visible From domain. Check smtp.mailfrom and the passing DKIM d= domain against the From domain. With adkim=s or aspf=s, the relevant domain must match exactly; sharing an organizational domain is insufficient.

Suped's product processes DMARC aggregate reports, groups Energe3 traffic by source, alerts the domain owner when authentication changes, and keeps remediation steps beside the affected record. Hosted DMARC can manage the later policy changes after approved sources pass.
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