Suped

How to set up DMARC/DKIM/SPF for Netvigator

Published 22 Nov 2026
Updated 22 Nov 2026
11 min read
Summarize with
Netvigator email authentication setup with SPF, DKIM, and DMARC.
To set up SPF, DKIM, and DMARC for a domain you own using Netvigator, obtain the SPF authorization and DKIM signing details for your service, publish the supplied DNS records, and enable signing on the outbound mail system. Publish DMARC with p=none, test actual messages, then move to p=reject after legitimate sending sources pass. Keep an existing quarantine or reject policy.
For an address ending in @netvigator.com or @hkstar.com, Netvigator controls the domain's authentication records. You cannot configure those records through your personal mailbox. I check that distinction first because the DNS steps below apply only to a domain you control.
Netvigator's public 'Email service tips and tutorials' documents mailbox settings and authenticated SMTP. It does not document a universal custom-domain SPF include, DKIM selector, or domain verification wizard. Obtain those account-specific details before editing DNS.

Add your domain

Standard Netvigator personal email has no documented custom-domain onboarding process. For a customer-owned domain, confirm provisioning with Netvigator before treating the mailbox as a custom-domain sending service.
  1. Check ownership: Identify the domain after @ in your visible From address. Skip custom-domain DNS changes for @netvigator.com and @hkstar.com mailboxes.
  2. Confirm provisioning: Give Netvigator your custom domain and service account details. Confirm that the service authorizes outgoing mail using that domain.
  3. Verify ownership: If Netvigator supplies a TXT or CNAME challenge, publish its exact name and value at your authoritative DNS host, then ask Netvigator to verify it. There is no universal verification token.
  4. Request settings: Obtain the outgoing server, envelope sender domain, supported custom Return-Path configuration, SPF authorization, and custom-domain DKIM instructions.
Domain ownership verification does not activate DKIM or change the SMTP envelope sender. Confirm those separately, and keep existing MX records unless your service provisioning instructions explicitly require a mail routing change.
A different From address in a webmail identity is insufficient proof that the service authenticates your domain. Use the relevant account type below to decide who changes DNS.
Netvigator-owned address
Netvigator publishes the domain's SPF and DMARC records and controls its outbound signing. Use your issued mailbox credentials and report authentication failures to Netvigator.
Customer-owned domain
You control the domain's DNS. Netvigator must confirm the supported sending configuration and supply any provider-managed signing records. Publish your DMARC policy only after checking the existing policy.

Set up SPF

Publish SPF at the domain used in SMTP MAIL FROM, normally visible in the delivered Return-Path header. For custom-domain sending, request a Return-Path under your own domain and confirm it in a delivered message.
  1. Find the domain: Send a baseline message and inspect Return-Path or the receiver's smtp.mailfrom result. If it uses bounce.example.com, check SPF there.
  2. Get authorization: Ask Netvigator for the supported SPF include or outbound IP ranges for your actual relay service. Do not guess an include using the SMTP hostname or copy Netvigator's entire corporate SPF policy.
  3. Merge the record: Edit the existing v=spf1 TXT record at that DNS name. Add only the confirmed authorization before its final all mechanism, preserving other legitimate senders. Publish one SPF policy per name.
  4. Check the limit: Keep SPF evaluation within 10 DNS-lookup-causing terms, including nested includes and redirects. Avoid +all.
For personal Netvigator mailboxes, the published SMTP settings are smtp.netvigator.com, port 465, SSL/TLS, authentication enabled, and your full issued email address as username. Use the settings supplied for your business service if they differ.
Enter the actual envelope sender domain in the SPF checker below. A valid SPF record at example.com does not supply SPF for bounce.example.com, and SMTP login success does not prove SPF passes at the receiver.

SPF checker

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

?/16tests passed
After publishing, wait for the previous DNS TTL to expire and send another message through the same Netvigator relay. Confirm spf=pass and compare the authenticated envelope domain with the visible From domain.
If your particular service keeps a Netvigator-owned Return-Path, adding Netvigator to your own SPF record will not fix that mismatch. No SPF addition to your domain is needed solely for that route. Expect SPF alignment warnings and require passing DKIM with a signing domain that matches your From domain for DMARC to pass.

Set up DKIM

DKIM needs both a published public key and an outbound system using the matching private key. Netvigator's personal mailbox documentation does not establish support for signing with a customer-owned domain. Confirm this for your service.
  1. Request signing: Ask Netvigator whether it can sign with your custom domain. Obtain the selector and exact TXT public key or CNAME target; request a 2048-bit RSA key where supported.
  2. Publish DNS: Add each supplied record at the exact selector name under _domainkey. Avoid appending your domain twice if the DNS editor adds it automatically.
  3. Activate signing: Have Netvigator verify DNS and enable custom-domain signing. If you operate the outbound server, configure signing there with its own matching key pair.
  4. Verify delivery: Send a fresh message. Check dkim=pass in the destination's Authentication-Results and inspect d= and s= in DKIM-Signature. The signing domain must match your visible From domain under your DMARC matching mode.
Use the selector from Netvigator's instructions or an actual signature. The commands below are lookup templates: replace SELECTOR and example.com before running them.
Look up the supplied DKIM selectorbash
dig +short TXT SELECTOR._domainkey.example.com dig +short CNAME SELECTOR._domainkey.example.com
A passing signature with d=netvigator.com does not authenticate a From address at example.com for DMARC. I check the signing domain as well as the cryptographic result.
If Netvigator cannot sign with your domain, use a sending system you control that signs before relaying, and verify the signature survives delivery. Otherwise, use a sending route that supports your domain's DKIM before enforcing DMARC.
A DNS key does not enable signing
Do not publish a random DKIM key and expect Netvigator to use it. The outbound signer needs the matching private key. For provider-managed signing, publish only the values Netvigator supplies.

Set up DMARC

For a new deployment on a domain you control, start with p=none. If the domain already uses p=quarantine or p=reject, keep that policy and repair Netvigator authentication without weakening existing protection.
  1. Inspect DNS: Look up TXT records at _dmarc.example.com and check the effective policy for your exact From domain before adding a record.
  2. Build the record: Use the DMARC record generator to prepare the policy and reporting destination.
  3. Publish once: Create or edit one TXT policy at _dmarc in the example.com DNS zone. Use the monitoring value below only when there is no existing enforcement policy.
  4. Keep reporting: Replace dmarc@example.com with a mailbox you control that accepts aggregate reports. Keep existing working reporting recipients when editing a policy.
Initial DMARC TXT value at _dmarc.example.comtext
v=DMARC1; p=none; rua=mailto:dmarc@example.com
The record above is an example, not a reporting address for your account. Replace the example domain and mailbox before publishing. For a reporting destination outside your domain, confirm that the recipient has published the required reporting authorization.
Check the exact From domain below and confirm that the intended DMARC policy is discoverable. Leave strict matching settings unchanged unless you have tested them; new records use relaxed SPF and DKIM domain matching by default.

DMARC checker

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

?/7tests passed
A valid DMARC DNS record does not prove that Netvigator mail passes DMARC. The receiver must authenticate a matching SPF domain or a matching DKIM signing domain on an actual message. p=none requests monitoring without quarantine or rejection based on that policy.
Reports generally arrive on a daily cycle, often within 24-48 hours after mail is sent. Reporting depends on receiving providers, so use a fresh test message for immediate configuration checks.

Verify and troubleshoot

I test each real sending route separately, including webmail and any application using Netvigator SMTP. A forwarded copy tests a different delivery path.
  1. Open compose: In Netvigator's documented classic webmail, open Mail and click New Message. If a From selector is shown, choose the identity being tested.
  2. Send a test: Use the email tester below to obtain its destination address. Send a new message directly to that address with the subject Netvigator authentication test.
  3. Inspect results: Read SPF, DKIM, and DMARC results alongside the authenticated domains. Check the destination's trusted Authentication-Results, rather than headers inserted by the sender.
  4. Repeat per route: Test the normal message format for each application and keep the sending time, source IP, Return-Path, and DKIM selector for support investigations.
Netvigator's public classic-webmail help documents Mail, New Message, the optional From selector, To, Subject, and Send. The illustration below recreates that compose workflow; the appearance differs between webmail versions.
Illustrative Netvigator classic-webmail compose screen for sending a test message.
Illustrative Netvigator classic-webmail compose screen for sending a test message.
The email tester prompts you to send a message and then diagnoses the delivered email. This checks the real sending IP and signing behavior, which DNS lookups alone cannot verify.
Use the actual test destination supplied by the widget. Send directly through the Netvigator account or relay you are configuring, then review the authentication results before changing the DMARC policy.

Email tester

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

?/43tests passed
For SPF permerror, check duplicate SPF policies and the DNS lookup limit. For DKIM failures, check the selector's DNS record, whether signing is enabled, and whether a relay changed signed content. For a timeout or missing record, recheck authoritative DNS after the previous TTL expires.
The compact checks below use 'matches' to mean the authenticated domain matches the visible From domain under the configured DMARC mode. A technical pass using an unrelated provider domain is insufficient.

SPF

DKIM

DMARC

Next step

Pass, matches
Fail
Pass
Repair DKIM
Pass, other domain
Pass, matches
Pass
Preserve signing
Pass, other domain
Pass, other domain
Fail
Fix domain matching
Permerror
Fail
Fail
Repair both methods
Authentication checks on a delivered Netvigator message.

Get alerted when it breaks

Suped is our platform for ongoing DMARC monitoring. For Netvigator sending, it brings source-level authentication results and detected issues into the same investigation workflow. One successful test does not catch a later relay change or expired DNS delegation.
  1. Enable notifications: Enable Suped's Issues detected and Sending sources need verification emails. Enable DMARC summary emails for regular review.
  2. Verify the source: Review Netvigator traffic in the source table. Confirm source IPs and authenticated domains against mail you actually authorize before marking a source verified.
  3. Investigate failures: Open the affected records in Data view, then use Detail view to inspect SPF, DKIM, DMARC, and rDNS checks. Follow the detected issue's fix steps.
  4. Confirm recovery: Compare DNS history with the failure's start time, correct the record or sending configuration, send another test, and check subsequent reports.
DMARC aggregate reporting has a delivery delay. Suped alerts on the information it receives; aggregate-report alerts are not an instant notification for every individual message. Keep the reporting destination working after setup.

Secure your domain with p=reject

Move a domain you control to p=reject after legitimate senders consistently authenticate with matching domains. Suped's source verification and record diagnostics provide the evidence for each policy change, including Netvigator traffic.
  1. Inventory senders: Review a complete normal sending cycle, including infrequent billing or application mail. Verify each legitimate source in Suped and investigate unrecognized traffic.
  2. Fix DKIM first: Require reliable custom-domain DKIM on Netvigator mail. Avoid relying solely on SPF at p=reject because forwarding commonly changes the sending IP.
  3. Stage enforcement: After resolving legitimate failures, move p=none to p=quarantine, review reports and delivery problems, then change the existing policy to p=reject. Keep a working enforcement policy if one is already published.
  4. Manage policy: Use Suped's Hosted DMARC for dashboard policy management after its DNS delegation is configured, or edit your existing TXT policy directly. Preserve reporting recipients and tested matching settings.
The value below illustrates the final policy using the same example reporting mailbox. Replace that address with your working destination; do not overwrite a production record's other intentional settings with this minimal example.
Final DMARC TXT example at _dmarc.example.comtext
v=DMARC1; p=reject; rua=mailto:dmarc@example.com
Check sending subdomains and their effective policies as well. An explicit policy on a subdomain can differ from the parent policy. Continue reviewing Suped reports after each change and investigate new legitimate failures promptly.
p=reject asks receiving systems to reject mail that fails DMARC. Receivers retain local handling discretion, so the policy is not a guarantee that every unauthorized message will be rejected.
Enforce after verification
Proceed when all identified legitimate sending routes pass tests, custom-domain DKIM is reliable, and report review shows no unresolved legitimate failures. Keep Suped notifications enabled while enforcing the policy.

Frequency asked questions

No. Netvigator controls DNS and authentication for netvigator.com. Use its authenticated sending service and ask Netvigator to investigate failures. You can publish a DMARC policy only for a domain you control.

Netvigator's public personal-email setup guide does not specify a custom-domain SPF include. Obtain the supported authorization for your service from Netvigator. Do not assume smtp.netvigator.com is an SPF include or authorize every Netvigator network address.

The public personal-mailbox instructions do not confirm custom-domain DKIM provisioning. Ask Netvigator for your service's signing support and selector records. If signing is unavailable, use a sending system that signs with your domain and verify delivery before enforcing DMARC.

Yes. DMARC passes when a valid DKIM signature has a signing domain that matches the visible From domain under the configured matching mode. If Netvigator uses its own Return-Path, editing your domain's SPF does not change that identity. Verify custom-domain DKIM instead.

The .netvigator.com suffix is associated with Netvigator's network. A hostname suffix alone does not establish that a message came through an authorized Netvigator mail relay; an ISP network also contains customer connections. Check the actual source IP, trusted Received headers, and SPF or DKIM results before verifying a source.

The DNS policy and a message's authentication result are separate. Messages fail when neither SPF nor DKIM passes with a matching domain. Common causes are an unrelated Return-Path, a provider-owned DKIM signing domain, missing DKIM signing, or broken DNS records. Send a fresh message through the actual Netvigator route to diagnose it.
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