Network Solutions
Network Solutions DKIM, SPF and DMARC: setup by email platform
Network Solutions DKIM depends on your email platform. See where to turn it on, which SPF record to publish and how to add DMARC safely.
Check your current setup:
Where DKIM is set up at Network Solutions
Network Solutions DKIM depends on the mail platform behind your mailbox: you turn it on in the DKIM Manager on Edge Desk, ProMail and Webmail 7.10.2, while Cloud Mail and Standard Email already include it. DKIM is a signature added to each message. The receiver checks it against a public key in your DNS to confirm that your domain sent the mail.
Existing DMARC policy: authenticating Network Solutions does not require resetting it. Keep one _dmarc record, preserve p, subdomain and alignment settings, and merge any needed rua address with existing destinations. The p=none example below is only for a new deployment without a valid record.
Network Solutions sells domains, hosting and several separate mail systems, so no single screen covers every customer.
| Your mail runs on | Where DKIM is handled | What you do |
|---|---|---|
| Edge Desk, ProMail, Webmail 7.10.2 | DKIM Manager in Account Manager | Turn it on (next section) |
| Cloud Mail, Standard Email | Included in the platform | Check the signature on a test message |
| Microsoft 365 | Microsoft Defender portal | Add two CNAME records in your DNS |
| Google Workspace | Google Admin console | Add one TXT record in your DNS |
| A newsletter, CRM or help desk service | That service's own settings | Add the records it gives you |
To find your platform, sign in at mail.example.com, using your own domain, and compare your webmail with the image in How to determine my email platform. If it matches, you have Cloud Mail. If it does not, you have Webmail 7.10.2. If your screen is OpenExchange, the Network Solutions DKIM article has no steps for it, so ask their support.
The plan name does not settle it. The Network Solutions service guide matches the Cloud Mail screen to Professional Email or Professional Email Plus, and the DKIM Manager steps also start from a Professional Email menu. Go by what your webmail looks like.
Turn on DKIM in the DKIM Manager
These steps apply to Edge Desk, ProMail and Webmail 7.10.2. On a multi-user account, only the account Admin can enable or adjust DKIM.
- Log in to your Account Manager and click Professional Email in the left navigation menu.
- On the Email page, select the mailbox and click Manage.
- Click DKIM Manager to open the DKIM Control Panel.
- Select Configure with auto-generated keys.
- Preserve the existing DMARC policy and alignment settings. Choose None only for a first policy. If DKIM Manager cannot preserve the current TXT and reporting addresses, do not apply the change until you inspect the generated record or resolve it with support.
- Type an address under the domain you are managing in the Send Reports to field. Network Solutions requires this. To send reports to an address on another domain, that domain has to publish a DNS report record (see Common problems).
If your domain is on Network Solutions nameservers, your DNS settings update automatically. If it is not, click View DNS TXT Record Information after you enable DKIM and give those records to your nameserver host.
Network Solutions does not say whether the policy you pick in step 5 creates a _dmarc record. Look up _dmarc.example.com before adding one by hand. Receivers discard every DMARC record at a name when they find more than one (RFC 9989 §4.10).
Network Solutions does not document the selector, the label that locates the public key in DNS. To find yours, send a message to a mailbox you control and paste its headers into the email header analyzer. Read s= and d= in the DKIM-Signature header. The key sits at selector._domainkey.example.com, which you can test with the DKIM checker.
DKIM on the other platforms
Cloud Mail and Standard Email
Network Solutions says Cloud Mail and Standard Email users do not need to set up DKIM. It does not say which domain signs the message, and that detail decides whether DKIM helps DMARC. DMARC only counts a signature whose d= domain aligns with the domain in your From address (RFC 9989 §4.4.1). Send a test message and read d=. If it shows a domain that is not yours, DKIM cannot pass DMARC for that mail, so SPF has to align instead.
Microsoft 365
Network Solutions sends Microsoft 365 users to Microsoft's own instructions. Microsoft says DKIM signing does not happen for mail from custom domains until you configure it. Get the two CNAME records for your domain from the Defender portal. Their hostnames are selector1._domainkey and selector2._domainkey. The values are specific to your organization, so copy them from the portal. The full steps are in DKIM in Microsoft 365.
Google Workspace
Generate the key in the Google Admin console. The default selector is google, so the TXT record goes at google._domainkey. After you publish the record, return to the Admin console and click Start authentication. The full steps are in DKIM in Google Workspace.
Another sending service
A newsletter, CRM or help desk signs with its own settings, and Network Solutions is only your DNS host. Add the CNAME or TXT records that service gives you, using the steps below.
Add DKIM, SPF and DMARC records at Network Solutions
These steps need your domain on Network Solutions nameservers. If your nameservers are elsewhere, add the records at that DNS host.
- Log in and select Domains on the left side of the page.
- Select the domain and click Manage.
- Go to the DNS tab and click +Add Record. To change an existing record, click its vertical ellipsis and select Edit.
- For a TXT record, set the record type to TXT. In Refers to, choose the root domain (
@) or Other Host for a name such as_dmarc, then enter that Host Name. Paste the entire value in TXT Value. - For a CNAME record, select Refers to, choose Other Host and enter the Host Name. Then enter the target your provider gave you in Alias to.
- Leave TTL at its default of 7200 (2 hours) and click Add. When editing a record, click Edit instead.
Some help pages show another route to these records, through Advanced Tools and Manage next to Advanced DNS Records. Use it if your account displays that layout.
SPF record for Network Solutions email
SPF lists the servers allowed to send mail for your domain. Network Solutions publishes these values for the root domain (@).
Professional Email bought from Network Solutions:
v=spf1 include:spf.registeredsite.com ~all
Cloud Mail:
v=spf1 include:spf.cloudus.oxcs.net ~all
Cloud Mail when you also use a Contact Form:
v=spf1 include:spf.registeredsite.com include:spf.cloudus.oxcs.net ~all
For Microsoft 365, Network Solutions gives include:spf.protection.outlook.com. For Google Workspace, it gives include:_spf.google.com.
Caution. Publish a single SPF record. If you already have one, edit it and add the new include: to it. Two SPF records make the check end in a permanent error (RFC 7208 §4.5), and Network Solutions warns that this can cause SPF authentication to fail.
The Network Solutions Gmail bounce article shows -all for Professional Email and Cloud Mail (include:spf.registeredsite.com include:spf.cloudus.oxcs.net -all). Do not copy that stricter ending before confirming every legitimate sender.
Its SPF article says ~all recommends marking non-compliant mail as suspicious, while -all recommends rejecting it. Start with ~all. Move to -all only after your DMARC reports show that every service sending for your domain passes.
The Cloud Mail DNS page lists SPF as optional. Publish it anyway, because the Gmail bounce article says adding it resolves most bounces.
DMARC record
DMARC tells receivers how you want them to treat mail that passes neither SPF nor DKIM in alignment with your domain, and it asks them to send you reports. Add a TXT record with Other Host and the Host Name _dmarc:
New policy only: use this starter value only when no valid DMARC record exists. For an existing record, keep its policy and merge the report address instead of pasting over the value.
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Replace the address with the mailbox that should receive the reports. With p=none you state no preference about failing mail and collect reports (RFC 9989 §4.7). Network Solutions recommends None first, then Quarantine, then Reject, and RFC 9989 §5.1.4 describes the same starting point. The DMARC generator builds the record if you want other options.
Caution. p=quarantine and p=reject can stop legitimate mail. Move up only after your reports show every sender aligned. Forwarded mail usually fails SPF while DKIM signatures generally survive, so RFC 9989 §7.4 requires valid DKIM on any domain that publishes p=reject. It also says domains whose users post to mailing lists should not publish p=reject.
Common problems
- SPF shows a permanent error. Look for two TXT records that start with
v=spf1, and merge them. Then count your lookups, because SPF allows 10 (RFC 7208 §4.6.4). When we checked on November 9, 2026,spf.registeredsite.comused 5 by itself and already includedspf.cloudus.oxcs.net. Listing both costs 7 lookups and adds no server. Run the SPF checker before you remove either one, because Network Solutions can change these records. - Mail to Gmail bounces. Read the bounce message first. Network Solutions says that in most cases adding an SPF record resolves it, so confirm the record exists on your root domain.
- DKIM passes but DMARC fails. The
d=domain in the signature does not align with your From domain. Turn on signing for your own domain at the provider that sends the mail. - The DKIM Manager is on but the record is missing. Your domain is probably not on Network Solutions nameservers. Copy the records from View DNS TXT Record Information to your DNS host.
- A TXT value breaks lookups. Some tools display values wrapped in quotation marks. Network Solutions does not allow a double quote at the start or end of a TXT value, and it says DNS responds with SERVFAIL if an invalid record is entered. Paste the value without the outer quotes.
- The lookup finds nothing. Network Solutions says advanced DNS updates may take up to two hours, and nameserver changes 24 to 48 hours. If the record is still missing, check the Host Name. The Network Solutions examples are short names such as
mailorautodiscover, so enter_dmarcand leave out your domain. - Reports never reach an address on another domain. When
ruapoints outside your domain, receivers look for a TXT record at that destination authorizing your domain (RFC 9990 §4). The destination has to publish it.