A domain portfolio audit gives you a reliable view of ownership, renewal exposure, DNS dependencies, and registrar spending. This checklist shows how to build a reusable inventory, estimate annual costs, identify domains that need attention, and establish a quarterly review process for managing multiple domain names.
Overview
A domain portfolio is more than a list of names. Each domain may control a website, email service, redirect, development environment, brand protection strategy, or third-party integration. If the portfolio is not documented, an apparently unused domain can still support an important service, while an active domain can be missed at renewal time.
A domain portfolio audit is a structured review of four areas:
- Ownership: who controls the registrar account, registrant information, recovery email, and payment method?
- Renewals: when does each domain expire, is auto-renewal enabled, and what is the expected renewal cost?
- Infrastructure: which DNS provider, nameservers, website, email platform, redirects, and verification records depend on the domain?
- Business value: should the domain be retained, consolidated, transferred, monitored, or allowed to expire?
The goal is not to move every domain to one registrar or delete names that appear inactive. The goal is to replace assumptions with documented decisions. Keep a separate record of credentials in a password manager rather than placing passwords in the inventory spreadsheet.
For account security, review the controls described in the Domain Security Checklist. The portfolio audit should show where a domain is managed and who is responsible for it; it should not become a second, less secure credential store.
How to estimate
Start with one row per registered domain. Then calculate the expected annual portfolio cost using the renewal price for each domain, plus any optional services that are billed separately.
A practical formula is:
Estimated annual cost = domain renewal charges + privacy charges + email charges + DNS or related service charges + reserved contingency
Use renewal pricing rather than first-year promotional pricing when planning a budget. Record the currency, tax treatment, and billing interval so that totals are comparable. If a registrar displays different prices for registration, renewal, transfer, or redemption, keep those amounts in separate fields. A low acquisition price does not necessarily indicate a low long-term cost.
For each domain, assign a status such as active, redirect, development, reserved, brand protection, for review, or retire. This status helps distinguish a domain with no website from a domain with no purpose. A domain used only for email, redirects, certificate validation, or DNS records is still an active dependency.
To estimate the effect of a registrar consolidation, compare the current portfolio total with the projected total at the proposed registrar. Include transfer fees, renewal timing, privacy charges, and any services that would remain at the original provider. Do not treat consolidation as automatically cheaper; centralization can reduce administrative effort, but it also increases the importance of account security and recovery planning.
Inputs and assumptions
Create a spreadsheet or database with these fields. Mark unknown values explicitly instead of leaving cells blank.
Ownership and administration
- Domain name and top-level domain
- Registrar and registrar account owner
- Registrant organization or responsible business unit
- Administrative contact and recovery email
- Renewal payment owner and internal domain manager
- Account security status, including multifactor authentication where available
- Transfer lock status and transfer authorization requirements
Renewal and cost tracking
- Expiration or renewal date
- Auto-renewal status and the date it was last confirmed
- Current renewal price and currency
- Privacy protection status and separate privacy fee, if applicable
- Payment method reference, without storing full payment details
- Expected annual cost and next review date
DNS and active services
- Authoritative nameservers and DNS provider
- Website host, redirect destination, or hosting account
- Email provider and important MX, SPF, DKIM, or DMARC records
- Subdomains used for applications, APIs, staging, monitoring, or vendors
- Certificate validation, analytics, payment, search, and other verification records
- Last DNS review and the person who performed it
Use the domain-to-hosting guide when documenting how a domain connects to a website. If records are unclear, the DNS troubleshooting guide can help separate an ownership issue from a record or propagation issue.
Make three assumptions visible in the workbook. First, an expiration date is not the same as a safe deletion date. Second, auto-renewal is not a substitute for a monitored payment method and recovery contact. Third, a domain is not unused merely because its homepage does not load.
Worked examples
Example 1: Building a portfolio total
Suppose a small company records eight domains. Each row contains its renewal estimate, privacy cost if applicable, and any domain-specific email or DNS service. Add the costs by row rather than multiplying one assumed price across the entire portfolio. This matters because domains can have different renewal terms, optional services, currencies, or pricing categories.
Next, group the total by purpose: operating websites, email-only domains, redirects, brand protection, development, and review candidates. The grouping shows where spending is concentrated and makes the business decision clearer. For example, a domain with no website but active email records should be reviewed as an email asset, not as an abandoned website.
Example 2: Finding a hidden dependency
An inventory row labels a domain “inactive” because it has no public site. A DNS review shows an MX record pointing to the company’s email provider and a subdomain used by an internal application. The correct action is to change the status to active, identify the service owners, and document a retention reason. If the domain is later retired, the email and application dependencies must be migrated before cancellation.
Example 3: Evaluating a transfer
A portfolio owner considers moving several domains to a different registrar. Before starting, compare renewal costs, privacy treatment, account controls, transfer eligibility, upcoming expiration dates, and the effort needed to recreate DNS or update contacts. Keep DNS hosted where it is unless there is a specific reason to change it; transferring registration and changing DNS are separate decisions.
For the operational sequence, use the Domain Transfer Playbook. Schedule transfers with enough time to resolve account, contact, lock, or authorization issues, and avoid making unrelated DNS changes during the same window.
When to recalculate
Run a lightweight review quarterly and a deeper audit at least twice a year. Recalculate the portfolio cost whenever renewal pricing, privacy fees, service subscriptions, currency assumptions, or the number of domains changes. Also revisit the inventory after an acquisition, rebrand, website launch, hosting migration, registrar transfer, staff change, or agency handoff.
Use this quarterly checklist:
- Sort domains by renewal date and flag the next review window.
- Confirm the registrar account, recovery contact, payment method, and auto-renewal status.
- Check that registrant and business ownership records are accurate.
- Review nameservers and identify every active website, email service, redirect, and subdomain.
- Compare recorded renewal costs with current registrar information.
- Investigate domains marked unknown, inactive, or for review.
- Record decisions: retain, transfer, consolidate, migrate, or retire.
- Assign an owner and due date for every unresolved item.
Before allowing a domain to expire, check website traffic, email delivery, DNS records, certificates, redirects, integrations, and historical business use. If a domain is being retired, document the decision and complete a controlled migration first. The website migration checklist and backup and restore workflow provide useful companion checks for related infrastructure.
Keep the completed inventory in a controlled location, assign a review owner, and record the date of every material change. A domain portfolio audit becomes valuable when it is repeatable: the same fields, calculations, and decisions should still make sense at the next quarterly review.