Suped

How to set up DMARC/DKIM/SPF for NextGen Web Solutions

Published 22 Nov 2026
Updated 22 Nov 2026
11 min read
Summarize with
SPF, DKIM and DMARC setup for NextGen Web Solutions.
Set up NextGen Web Solutions email authentication by requesting your account's sending-domain records, configuring a custom Return-Path for SPF, enabling DKIM signing, and publishing DMARC in your authoritative DNS. I test a real application email before changing the domain's enforcement policy.
If your domain has no DMARC policy, start with p=none and aggregate reporting. If it already uses p=quarantine or p=reject, keep that protection while you configure Next Gen. DMARC passes when either SPF or DKIM passes with domain alignment to the visible From address.

Add your domain

I first confirm which Next Gen application sends the email. The supplied domain belongs to Next Gen Web Solutions, whose products include Dynamic Forms and JobX. Use the institutional support contact for your application to arrange sender-domain setup; do not assume a web-hosting control panel applies.
  1. Identify the sender. Give your product support contact the institution name, application, account identifier and intended From address, such as forms@example.com.
  2. Request the records. Ask for the custom Return-Path hostname, required SPF or delegation records, DKIM selector and record type, and any domain-ownership verification record.
  3. Publish ownership proof. If support supplies a verification token, add its exact TXT or CNAME record at your authoritative DNS provider. Ask support to confirm the domain is enabled for your account.
  4. Confirm the route. Establish whether messages leave through Next Gen's servers or your institution's mail relay. Configure authentication on the route that actually sends the messages.
An application login, a verified user email address and a verified sending domain are separate checks. Completing an account-confirmation email does not enable DKIM signing for your institution's domain.
Next Gen's public website lists separate institutional support contacts by product. I use that route to obtain the exact DNS values rather than copy another institution's records.
Next Gen's institutional support section lists contacts by product.
Next Gen's institutional support section lists contacts by product.
Finish this step with a confirmed sending route and a written list of DNS names, types and values. The following SPF and DKIM changes use those support-issued values.

Set up SPF

NextGen Web Solutions supports Return-Path alignment. I request a dedicated bounce subdomain, such as bounce.example.com, and configure the SPF authorization for the domain actually used in the SMTP MAIL FROM.
  1. Configure the Return-Path. Ask support to use your approved bounce subdomain. Changing the visible From or Reply-To address does not change the envelope sender.
  2. Use the supplied authorization. Publish the exact SPF TXT value or CNAME delegation that support provides. There is no universal SPF include value established by the public documentation reviewed for this setup.
  3. Preserve existing senders. If a TXT-based setup uses a hostname with an existing SPF record, edit that single record. Never add a second v=spf1 record at the same hostname.
  4. Check delegation conflicts. If the supplied setup uses a CNAME, do not also publish TXT or MX records at that owner name. Ask support to resolve conflicting requirements.
  5. Check lookup limits. Keep SPF evaluation within the 10 DNS-lookup-causing term limit, including nested includes and redirects. Only authorize the sending infrastructure that support specifies.
Enter the actual Return-Path domain in the SPF checker below. Checking only example.com misses SPF published at bounce.example.com.
With relaxed SPF alignment, bounce.example.com and a From domain of example.com share the same organizational domain. With strict SPF alignment, they must match exactly; a bounce subdomain does not satisfy that setting.

SPF checker

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

?/16tests passed
A valid DNS result confirms that the SPF record can be evaluated. A delivered test message must also show spf=pass for the actual envelope sender and a domain relationship that satisfies your DMARC settings.
If a particular sending route keeps a provider-owned Return-Path, adding SPF to your own domain will not fix that mismatch. SPF alignment errors are acceptable for DMARC only when DKIM passes with domain alignment. Continue checking any separate receiver requirements for SPF authentication.

Set up DKIM

I ask the product support team to enable DKIM for the exact From domain. Confirm availability for your specific application and sending route before assuming the same DKIM configuration applies across every Next Gen product.
  1. Get the selector. Request the complete DKIM hostname, record type and value. The selector must come from support; do not assume it is default, selector1 or nextgen.
  2. Publish the record. Add the supplied TXT public key or CNAME target at the exact selector hostname. Check whether your DNS editor automatically appends your domain.
  3. Enable signing. Ask support to confirm that outgoing messages now use your domain in the DKIM d= value. Publishing a public key alone does not activate signing.
  4. Check a real message. Trigger an application notification, then inspect its DKIM-Signature and receiver Authentication-Results. Require dkim=pass and domain alignment to the visible From domain.
For a From address of forms@example.com, d=example.com satisfies both relaxed and strict DKIM alignment. A signing subdomain such as mail.example.com satisfies relaxed alignment, but not strict alignment with example.com.
I aim for both SPF and DKIM to work. DKIM is especially useful when forwarding changes the connecting IP and breaks SPF, provided the signed content remains intact.
SPF check
The receiver checks the connecting IP against the envelope sender's SPF authorization. A passing provider-owned Return-Path does not establish SPF alignment with your From domain.
DKIM check
The receiver validates the signature against the selector's DNS key. DMARC can pass through DKIM when a valid signature's d= domain satisfies alignment with your From domain.
Keep the private signing key with the sending system. For a key rotation, retain the previous public selector until support confirms that signing has switched and messages signed with the old key have cleared delivery queues.

Set up DMARC

Publish DMARC for the domain in the visible From address. I check the existing record before editing it because a domain has one DMARC policy shared by all its sending systems.
  1. Find the existing policy. Look up TXT at _dmarc.example.com. Preserve an existing quarantine or reject policy and its reporting destinations.
  2. Start monitoring if absent. For a domain without DMARC, create one TXT record at _dmarc.example.com with the monitoring value below.
  3. Use a working report address. Replace dmarc@example.com with a mailbox or reporting destination you control. For an external reporting service, complete any required external report authorization.
  4. Keep the record unique. Edit the existing DMARC TXT record rather than publish another policy record at the same hostname.
Initial DMARC TXT value at _dmarc.example.comtext
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Use our DMARC record generator to prepare the TXT value. The example address is a placeholder, and p=none requests monitoring rather than rejection of failing messages.
Enter the From domain in the DMARC checker below after saving DNS. If your editor adds the zone automatically, enter _dmarc as the host rather than accidentally creating _dmarc.example.com.example.com.

DMARC checker

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

?/7tests passed
A valid policy does not prove that Next Gen signs messages correctly or uses the intended Return-Path. It confirms the receiving server can find and interpret your DMARC instructions.
Use the live message checks next to confirm authentication. Aggregate reports then show whether other sending routes using the same From domain also pass.

Verify and troubleshoot

I send the test through the same Next Gen workflow used in production. A message sent manually through your ordinary mailbox tests a different sending route.
  1. Trigger the workflow. Send an application invitation, notification or other representative message to the test recipient. Repeat for each sending route and From domain.
  2. Read trusted results. Inspect Authentication-Results added by the receiving system, plus the visible From, Return-Path and DKIM-Signature domains.
  3. Separate pass and alignment. Confirm spf=pass and dkim=pass where configured, then confirm at least one passing method satisfies DMARC domain alignment.
  4. Escalate with evidence. Give support the delivery time, message ID, connecting IP, complete headers and failing DNS hostname. Remove sensitive message content before sharing.
The email tester below is the quickest configuration check. It supplies a recipient address; send an actual Next Gen message to that address to receive the authentication diagnosis.
Check that the results name the expected Return-Path and DKIM signing domain. A general tests-passed score is useful, but the domain-level SPF, DKIM and DMARC results determine whether this setup works.

Email tester

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

?/43tests passed
After a DNS change, wait for the previous record's cache lifetime to expire and send a fresh message. An old message keeps its original authentication results.
I use the result patterns below to decide whether the next change belongs in DNS, the application configuration or the sending system.

Result

Likely issue

Next check

SPF fail
Sender unauthorized
Return-Path SPF
SPF permerror
Invalid SPF
Duplicates or lookups
DKIM fail
Key or signature
Selector and signing
DMARC fail
Domain mismatch
From versus auth domains
DMARC pass
Auth accepted
Other sending routes
For DNS checks, query the exact hostnames support provided. Replace selector in the DKIM query below with the selector from a real message; it is an example name, not a Next Gen default.
A DKIM CNAME and its target need separate inspection when troubleshooting delegation. Keep the full public key intact if the DNS interface displays it in multiple quoted chunks.
Example DNS verification commandsbash
dig +short TXT bounce.example.com dig +short CNAME selector._domainkey.example.com dig +short TXT selector._domainkey.example.com dig +short TXT _dmarc.example.com
If authentication passes but delivery still fails, inspect the SMTP rejection and application delivery logs. DMARC success does not guarantee inbox placement.

Get alerted when it breaks

Our platform, Suped, turns ongoing DMARC monitoring into source-level investigation and issue notifications. For Next Gen mail, use it to catch changes in authentication after a key rotation, DNS edit or sending-route change.
  1. Enable issue notifications. For a domain already reporting to Suped, open Notifications and enable Issues detected. Confirm the notification recipients.
  2. Review new sources. Enable Sending sources need verification. Confirm ownership of a new sending source before marking it verified.
  3. Investigate failures. Filter the Data view by source or IP, open a failing record, and compare SPF, DKIM and DMARC results with the Next Gen support configuration.
  4. Confirm the repair. Follow the issue's steps to fix, retest a live Next Gen message, and check subsequent report data. Use DMARC summary emails for recurring review.
Suped's notifications depend on the data available to it. DMARC aggregate reports arrive on receiving providers' schedules, commonly daily, so authentication incidents appear after that reporting delay.
Keep application delivery alerts enabled as well. SMTP failures in Next Gen's sending logs are the immediate evidence when a particular notification is rejected.
Verify a source before authorizing it
A familiar name or reverse DNS hostname does not prove a source is yours. Confirm the application owner and intended sending route before adding SPF authorization or treating failed traffic as legitimate.
For a confirmed Next Gen incident, attach the failing record details to the support request. That gives the product team the sending IP and authentication domains needed to investigate.

Secure your domain with p=reject

I move to p=reject after every authorized sender has a working DMARC authentication path and the reports cover a representative operational cycle. Include infrequent workflows such as scheduled notifications before enforcing the policy.
  1. Inventory all senders. Review every source using the From domain, including systems unrelated to Next Gen. Do not judge readiness using Next Gen traffic alone.
  2. Fix legitimate failures. Confirm SPF or DKIM passes with domain alignment for each authorized route. Prefer both where supported, and retest after changing the Return-Path or signing key.
  3. Stage enforcement. Change the existing policy to p=quarantine, review legitimate failures over a representative sending cycle, then change it to p=reject when those failures are resolved.
  4. Review subdomains. Check explicit subdomain policies and any sp= setting. A root-domain change also affects subdomains that inherit its policy.
  5. Keep reporting active. Retain a working rua destination and incident owner. If legitimate traffic breaks, repair that sender or make a deliberate policy rollback while investigating.
Suped helps establish readiness by showing verified sources, authentication failures and the records behind each issue. Use our Hosted DMARC to manage policy changes and staging through the dashboard after its DNS setup is complete.
The value below replaces the monitoring policy; it is not an additional TXT record. Use your real reporting address and preserve other intentional settings in your existing policy.
Final DMARC TXT value after sender verificationtext
v=DMARC1; p=reject; rua=mailto:dmarc@example.com
A reject policy asks receivers to reject messages that fail DMARC. Receiver handling still depends on local policy, so keep monitoring actual authentication results and delivery errors after the change.
Retest Next Gen messages after signing-key rotations or application migrations. Keep the approved Return-Path, selector inventory and support confirmation with the domain's DNS change records.

Frequency asked questions

Get the authorization value from your Next Gen product support team. There is no verified universal include value established for this setup. Publish the account-specific SPF or delegation records at the hostname actually used by your Return-Path, and preserve existing authorized senders.

Yes. DMARC passes if a valid DKIM signature has domain alignment with the visible From address, even when SPF alignment fails. Confirm DKIM on a real message from the affected application. A passing DKIM signature using only a provider-owned domain does not satisfy alignment with your own From domain.

Keep an existing reject or quarantine policy while setting up Next Gen. Enable and verify the sender before switching production traffic to your From domain. Start with p=none only when the domain does not already have an enforcement policy.

Check authoritative DNS after saving, then allow previously cached answers to expire according to their TTL. Send a fresh application email after the change is visible. DMARC aggregate reports follow the receiver's reporting schedule, so they do not provide immediate confirmation of a DNS edit.

Next Gen uses ngwebsolutions.com for its application infrastructure, but a matching reverse DNS hostname alone does not authenticate a message or identify your authorized account. I check the actual connecting IP's PTR result, confirm the sending route with support, and compare the message's SPF and DKIM domains. Do not assume every Next Gen sending route has the same rDNS suffix.
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