Business identity

Business Email and Domain Foundation

The domain, DNS and mailboxes form the foundation of your business identity. Before changing providers, know who can recover them.

Document our domain and email foundation See useful links

When the foundation is unclear

Start with the domain the business must be able to recover

The registrar sends renewal notices to a former mailbox.

Nobody knows which account can authorize a DNS change.

The email provider is known, but the DNS or recovery account is not.

A marketing platform sends as the domain without being documented.

The underlying question

A business domain should not depend on one mailbox

This review focuses on the specific email foundation: domain, registrar, DNS, mail provider and recovery access. It complements the broader IT Ownership Register, which also covers the business’s other systems and vendors.

Concrete situations

  • The domain is registered through a former employee’s personal account.
  • MX points to one provider while another service still sends using the domain.
  • The DKIM selector or DNS-account owner is not recorded anywhere.
  • A renewal address exists, but nobody can confirm who watches it.

Connect the domain to its services

What needs documenting before a change

  • The registrar, expiry date, recovery account and people authorized to act.
  • DNS, MX and the services using the domain to receive or send email.
  • Visible SPF, DKIM and DMARC signals, without treating their presence as complete proof.
  • Dependencies on a provider, former mailbox or private account.

You receive

A foundation the business can take back

  • A clear record of the domain, DNS, email and responsibilities still to confirm.
  • A list of access and renewal tasks that should not depend on one person.
  • Questions to resolve before a migration, provider change or DNS update.
  • A distinction between the email foundation and the broader IT ownership inventory.

A verifiable foundation

What is included and what needs a separate plan

In this review

  • A guided review of supplied domain, DNS and mail information.
  • Bounded public checks and a record of unknowns.
  • A next step for documenting or confirming operational ownership.

Planned separately

  • Authorized access, account recovery and DNS changes.
  • Mailbox migration, device configuration or provider change.
  • Detailed email-trust repair when multiple senders need analysis.

Scope, deliverables, and pricing are confirmed before work begins. Additional work requires approval.

The right access before the right setting

Documentation comes before the change

We confirm the scope, evidence, customer responsibilities and any licences or third-party costs before changes are considered.

What the domain owner confirms

  • Provide available registrar, DNS and mail-provider information.
  • Name the people who can confirm operational ownership.
  • Authorize access, transfer or technical changes separately.

A useful next conversation

Document our domain and email foundation

Tell us what is happening. Initial contact confirms the right scope and requirements; it does not authorize a change.

Document our domain and email foundation