Opens in a new tab.

Our approach: Assess, find the gaps; Fix, put it right; Manage, keep it working; Assure, prove it stays that way.

← All insights DIGIPEST / INSIGHT

Website and email security basics for small organisations

The practical controls that protect business websites, domains and email from common configuration and impersonation risks.

3 min readBy DigiPest

A website and an email domain are part of an organisation’s identity. If either is poorly protected, attackers may be able to impersonate the organisation, intercept administration, publish malicious content or exploit trust in its name.

Security does not come from one hosting brand, certificate or filtering service. It comes from maintaining several connected controls and knowing who is responsible for each one.

Protect the domain first

The domain controls where the website and email are found. Losing the registrar or DNS account can undermine protections elsewhere.

Use a named organisational account rather than a supplier’s or employee’s personal account. Enable strong MFA, protect the recovery method and restrict administrative access. Record renewal details and make sure more than one authorised person can recover the account.

Review DNS records periodically. Remove entries for abandoned services and confirm that changes are monitored or at least recorded.

Use HTTPS consistently

HTTPS protects information while it travels between a visitor and the website and helps the visitor confirm which domain they reached. Redirect HTTP requests to HTTPS, use a valid certificate, and ensure scripts, images and other resources also load securely.

A certificate does not prove that a site itself is trustworthy or free from vulnerabilities. It secures the connection. The server, application, accounts and content still need protection.

Modern TLS configuration evolves over time. Prefer maintained server defaults and test the public configuration rather than relying on settings copied from an old guide.

Keep the web stack small and maintained

Every plugin, theme, library and administration route adds something to maintain. Remove components that are not needed and apply security updates promptly.

Use separate named administrator accounts, protect them with MFA where supported and avoid routine browsing or email from privileged accounts. Restrict administrative interfaces when practical and keep reliable backups of content and configuration.

Add appropriate security headers, secure cookie settings and a clear vulnerability-reporting route. The NCSC’s Web Check overview describes common checks including TLS, HTTPS redirection, headers, cookies and supported software.

Protect business email accounts

Email is both a communication channel and a recovery route for other services. Use passkeys where supported or unique passwords with MFA. Remove old accounts and forwarding rules, review privileged roles and make suspicious sign-ins visible to someone who can act.

Staff should know how to verify an unusual payment or bank-detail change through a separate trusted channel.

Stop other people sending as your domain

SPF, DKIM and DMARC work together to make domain impersonation harder:

  • SPF identifies systems authorised to send mail for the domain.
  • DKIM adds a cryptographic signature to outgoing messages.
  • DMARC tells receiving systems how to handle messages that fail checks and provides reports.

These records must reflect every legitimate sender, including marketing, invoicing and support platforms. Start by discovering and correcting legitimate sources, then move towards an enforcing DMARC policy. Do not copy another organisation’s DNS examples.

The NCSC provides email security and anti-spoofing guidance and a public email security check .

Treat newsletters as a separate sending service

Bulk email should normally use a reputable service configured to authenticate the organisation’s domain. Maintain the subscriber list lawfully, make the sender recognisable and provide a working unsubscribe route.

Adding a newsletter platform changes the authorised email sources, so review SPF, DKIM and DMARC rather than assuming the platform’s default setup is sufficient.

Put monitoring and ownership around the controls

Certificates, domains, software and third-party services all change. Assign ownership, record renewal and support dates, monitor failures and review configuration after introducing or removing a supplier.

A secure website and email domain are maintained services, not one-off installations. The most important question is often not which product is present, but who will notice when its protection stops working.