C
CertPilot
← All glossary terms

Domains

Domain governance register

A domain governance register records who owns each domain, why it exists, and how its lifecycle is reviewed.

Updated 24 July 2026

What it means

A domain governance register is a maintained record of operational context for domains. It records fields such as owner, purpose, lifecycle status, renewal decision, notes, and last reviewed date. The register sits beside technical domain checks rather than replacing them. It answers governance questions that DNS and SSL checks cannot answer on their own.

Why it matters

A domain can be technically healthy and still weak from a governance perspective. Nobody may know who owns it, why it exists, whether it should renew, or whether it belongs to an old client or project. Recording that context prevents domain portfolios from becoming unmanaged lists of hostnames.

How CertPilot uses the term

CertPilot's domain governance metadata is customer-entered. It does not come from WHOIS/RDAP ownership, and it does not affect technical health scoring. The fields support review queues, CSV import/export, and evidence reports so teams can explain domain ownership and lifecycle decisions clearly.

What to record

  • Domain owner and business purpose.
  • Lifecycle status and renewal decision.
  • Last reviewed date and notes.
  • Related client, website, system, or operational context.

What not to assume

  • Customer-entered owner is not WHOIS legal registrant data.
  • Governance metadata does not change SSL, DNS, or domain-expiry scoring.
  • The register does not renew or cancel domains automatically.

How to use this term in a review

Use Domain governance register when you need a shared operating definition in a management report, access review, renewal review, domain review, or evidence-pack discussion. The goal is not to turn a glossary term into a control by itself. The goal is to make the scope, source, owner, status, date, and follow-up clear enough that a manager or client can understand what was reviewed and what still needs attention.

  • Use the related pages to move from definition to workflow.
  • Keep evidence wording precise and avoid audit, legal, or certification overclaims.
  • Record limitations when the source is public, manual, customer-entered, or incomplete.