DNS Security for Business Websites: SPF, DKIM, DMARC, DNSSEC, and Registrar Controls
DNS securitydomain protectionemail authenticationDNSSECwebsite security

DNS Security for Business Websites: SPF, DKIM, DMARC, DNSSEC, and Registrar Controls

SSecuring.website Editorial Team
2026-11-14
7 min read

A practical DNS security checklist covering registrar access, DNSSEC, SPF, DKIM, DMARC, monitoring, recovery, and recurring reviews.

DNS is part of your website’s security boundary, not just a technical configuration. This guide provides a practical checklist for protecting a business domain against spoofed email, unauthorized DNS changes, domain hijacking, and avoidable service disruption. Use it to establish a baseline, record expected settings, and create a recurring review process for your registrar, DNS provider, website host, and email platform.

Overview

A business domain usually depends on several connected systems: a registrar holds the domain registration, an authoritative DNS provider publishes records, a hosting platform serves the website, and one or more email providers send messages using the domain. A weakness in any of these areas can affect availability, trust, or data protection.

DNS security best practices should therefore address both access control and record integrity. Registrar MFA helps prevent unauthorized account access. A domain lock can make certain unauthorized transfers more difficult. Restricted nameserver permissions reduce the number of people who can redirect the domain. DNSSEC can help DNS resolvers detect tampered responses when it is correctly deployed and supported throughout the resolution path. Email authentication records help receiving mail systems evaluate whether messages claiming to come from your domain are legitimate.

Start with an inventory. Record the registrar, authoritative nameservers, DNS provider, hosting provider, email provider, certificate-management method, and every person or system that can change them. Store the inventory in a controlled location and update it when a provider or administrator changes.

For broader infrastructure checks, pair this guide with the DNS and Hosting Security Checklist. DNS controls should also be included in your wider website security and compliance audit.

What to track

1. Registrar and account protection

  • Use a dedicated business-owned registrar account rather than a personal account.
  • Require MFA, preferably using a method resistant to password reuse and phishing.
  • Use a unique, long password and store recovery information in an approved password manager.
  • Review administrators, delegates, API keys, recovery addresses, and notification contacts.
  • Enable the registrar’s domain lock or transfer protection where appropriate.
  • Confirm that renewal notices and security alerts go to monitored organizational addresses.

Keep an offline or separately controlled record of the registrar, account owner, renewal process, and emergency contacts. Do not rely on one employee’s inbox or device for recovery.

2. Nameserver and DNS permissions

Confirm that the registered nameservers match the DNS provider you intentionally selected. Unexpected nameservers are a high-priority finding because they can redirect web traffic, mail, verification records, and other services.

Limit DNS administration to the people and automation that require it. Review role permissions, service accounts, tokens, and integrations. Separate read access from write access where the provider supports it, and require approval for changes to nameservers, MX records, TXT records, and the website’s primary address records.

Maintain a baseline of expected records, including A, AAAA, CNAME, MX, TXT, CAA, and any provider-specific records. The baseline should identify the purpose and owner of each record, not merely its value.

3. DNSSEC and certificate controls

DNSSEC adds signed DNS data so validating resolvers can detect certain forms of alteration. Treat it as a controlled deployment: confirm that the DNS provider supports it, document the signing configuration and key-management responsibilities, and verify that the domain remains resolvable after activation or key changes. A broken DNSSEC chain can make a domain appear unavailable to validating users, so include it in change testing and recovery procedures.

Use CAA records where they fit your certificate-management model to restrict which certificate authorities may issue certificates for the domain. Confirm that automated certificate renewal still works after any CAA change. Track certificate expiry, issuing authority, covered hostnames, and the person or system responsible for renewal.

4. SPF, DKIM, and DMARC

SPF identifies authorized sending services in a DNS TXT record. DKIM adds a cryptographic signature to outgoing messages, with the public key published in DNS. DMARC tells receiving systems how to evaluate messages that claim to use your domain and provides reporting options. These controls work together, but they do not replace mailbox security or protection against every type of phishing.

  • SPF: Keep one authoritative SPF policy for the domain and include only services that genuinely send mail. Remove obsolete providers after a carefully tested transition.
  • DKIM: Confirm that each active sending platform signs messages and that its public selector record is present. Track selectors during provider changes.
  • DMARC: Start with a monitoring-oriented policy when you need visibility, review reports, correct legitimate sending sources, and then consider a stricter enforcement policy based on your operational confidence.
  • Alignment: Check that the visible From domain aligns with the authenticated SPF or DKIM domain according to your chosen DMARC settings.

Do not copy authentication records from a vendor without checking the vendor’s current instructions. Syntax, hostnames, selectors, and required records can differ between providers.

5. Monitoring, backups, and recovery

Enable change notifications for registrar activity, nameserver changes, DNS edits, certificate events, and authentication-policy changes. Where possible, send alerts to more than one monitored contact and retain an audit trail.

Export or record the authoritative DNS zone before major changes and after a known-good review. A backup is useful only if someone knows where it is stored, who can restore it, and how to distinguish current records from deprecated ones. Document the sequence for restoring DNS, hosting, certificates, and email when a provider is unavailable.

Cadence and checkpoints

A recurring review is more reliable than a one-time configuration exercise. Use the following schedule as a starting point and adjust it to the importance of the domain and the frequency of change.

CadenceCheckpointsEvidence to retain
MonthlyReview DMARC reports, unexpected DNS changes, failed certificate renewals, and new registrar or DNS alerts.Report summary, alert review, tickets for anomalies.
QuarterlyReview administrators, MFA status, API keys, nameservers, domain locks, DNS records, SPF sources, DKIM selectors, and recovery contacts.Access review, approved record inventory, screenshots or exports.
After a changeTest website resolution, HTTPS, email sending and receiving, authentication records, redirects, and critical subdomains.Change request, test results, rollback decision.
AnnuallyExercise domain recovery and confirm that the organization can reach the registrar, DNS provider, host, email provider, and certificate contacts.Recovery exercise notes and remediation actions.

For a small business, a documented quarterly review may be sufficient for stable domains, provided alerts are monitored between reviews. High-change SaaS environments or domains supporting critical services may need automated monitoring and more frequent validation.

How to interpret changes

Not every DNS change is malicious. A new TXT record may support a legitimate email, analytics, or service-verification workflow. A new CNAME may reflect a hosting migration. The important question is whether the change is authorized, understood, and documented.

Treat these findings as urgent until verified:

  • Nameservers changed without an approved request.
  • A new registrar administrator, recovery address, API key, or delegated user appears unexpectedly.
  • MX records point to an unknown mail service, or an established mail provider disappears.
  • SPF begins authorizing an unfamiliar sender, or a previously used sender was removed without a migration plan.
  • DKIM selectors, DMARC policy, CAA records, or DNSSEC settings change without a recorded owner.
  • The website, certificate, mail flow, or important subdomain stops resolving after a DNS change.

When a change is unexplained, preserve evidence before editing records: capture the current zone, review provider audit logs, identify the account that made the change, and contact the registrar or DNS provider through a verified support channel. If account compromise is plausible, use a known-safe device to reset credentials, revoke sessions and tokens, restore MFA, and review related hosting and email accounts. Escalate potential data exposure or service compromise under your incident response process; the incident response plan template can help organize roles and communications.

When to revisit

Revisit this checklist at least monthly for monitoring tasks and quarterly for access and configuration reviews. Perform an additional review whenever you change registrars, DNS providers, website hosts, email platforms, certificate automation, or domain ownership details. Also review it after an employee with administrative access leaves, a security alert is received, a domain is acquired, or a subdomain is launched.

Make the next review actionable:

  1. Export the current DNS zone and compare it with the approved baseline.
  2. Confirm registrar MFA, domain lock, recovery contacts, administrators, and API access.
  3. Validate nameservers, DNSSEC status, CAA records, certificates, and critical website records.
  4. Review SPF, DKIM, and DMARC results against current email providers.
  5. Test website and email behavior from outside your internal network.
  6. Record findings, assign owners, set deadlines, and retain evidence for the next review.

DNS security is a living control. A short, repeatable review after every infrastructure change—and on a defined monthly or quarterly cadence—helps prevent small configuration differences from becoming domain hijacking, spoofing, or prolonged service disruption.

Related Topics

#DNS security#domain protection#email authentication#DNSSEC#website security
S

Securing.website Editorial Team

Cybersecurity and Compliance Editors

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.