Frannie Lindsay

How to keep a domain portfolio organized

A domain portfolio is more than a folder of memorable names. It includes active websites, defensive registrations, campaign addresses, redirect domains, email hosts and names currently offered for sale. When those pieces live in separate registrar dashboards, a missed renewal or outdated redirect can interrupt campaigns, weaken brand consistency and create unnecessary work for a small Australian team.

A workable system answers four questions for every name: Who owns it, where is it registered, when does it need action, and what job does it perform? A spreadsheet is often enough for a small collection. As the portfolio grows, move the same fields into a domain-management platform or database without losing the underlying discipline of one verified record.

Australian conditions add useful structure. Many businesses meet .com.au before .au, and both extensions involve auDA rules that should be checked against the registrant and intended use. Compare prices in Australian dollars, including GST where charged, and make sure invoices match the legal entity holding the registration. Sydney, Melbourne and Brisbane offices may also share one portfolio across time zones, so ownership should never depend on who happened to log in first.

The practical method for keeping a domain portfolio organized is to treat every name as an asset with an owner, lifecycle and documented decision. The following approach covers records, classifications, renewals, redirects, performance reviews and sale opportunities. It also gives a parked name such as FRANNIELINDSAY.NET a clear place in the wider portfolio: a deliberate holding, an active sales property or a redirect source with a documented end date.

Establish a single source of truth

Start with a portfolio register that is treated as the authoritative source. It should be separate from registrar dashboards, website analytics and team chat. Every row represents one registrable domain; subdomains, redirects and email services are linked as dependencies unless they are independently registered.

Useful fields include the full domain name, portfolio ID, owner type, business contact, registrar and account reference, date registered, purchase price, renewal price, renewal date, auto-renew status, nameservers, DNS provider, registrar lock, privacy choices, payment method, purpose, risk tier, acquisition source, redirect destination and sale status. Add notes for disputes, trademarks, renewal commitments and the person authorised to approve a transfer. Consistent naming makes searching and sorting dependable.

Restrict edits to named roles and enable multifactor authentication on registrar accounts. A password manager can hold shared credentials without exposing them in the register. Where staff work across Australian offices, record a primary custodian and a backup for urgent renewals. Public status pages can explain a domain’s availability, but they should never contain passwords, private contact details or unverified ownership claims.

Classify assets by role and risk

Assign every domain one primary class and, where useful, a risk tier. Common classes include core brand, defensive, product or campaign, legacy or redirect, monetised, and available for sale. Core names receive the highest attention to DNS, security and renewals. Defensive names need a clear purpose so they do not become forgotten annual costs.

Risk tiers help teams act consistently. Tier one might contain revenue-critical domains under an Australian trading entity. Tier two could cover regional campaigns and future projects. Tier three may include low-cost experimental names. A held domain with no owner, review date or disposal decision is not organised, regardless of how attractive it looks.

Use a naming convention for rows and folders, but keep the domain itself unchanged. Combine the portfolio ID, category and short purpose, such as AU-CORE-SYD or AU-SALE-2025. Add a quarterly review date for low-activity holdings. This makes duplicate purchases easier to spot and gives a prospective buyer or internal manager an immediate understanding of the asset’s status.

Control renewals and ownership records

Build renewal control around a calendar rather than an annual bulk reminder. Review names due within 90 days, confirm auto-renew, check that the payment method has not expired, and place a second review 30 days before the charge. Multi-year registrations still need a yearly check because auDA eligibility, contact details or business ownership may change.

Ownership records deserve the same care. Domain registrant details can sometimes be exposed through public lookup services, and the Australian Privacy Act does not make every business record confidential. Use a monitored business email address, keep the legal entity name accurate, and restrict public contact details to what is necessary. The Spam Act 2003 also applies when a domain supports commercial email, so list and consent processes should be documented separately from domain administration.

Before transferring a name, reconcile the registrar account, invoice, legal owner and authorisation. Keep the receipt and GST record with the purchase file. After transfer, recheck nameservers, DNS, renewal settings and access rather than assuming every setting moved. If a company buys the name, compare its ABN and ASIC records with the registrant information and correct mismatches before the next renewal.

Map redirects and connected services

A domain becomes difficult to manage when its digital connections are invisible. Map which domains use each website, DNS account, certificate, analytics property and email provider. Keep a redirect register with the source domain, destination, campaign parameters, owner, launch date, expected end date and last test result. This prevents a legacy .com.au address from sending traffic to an unrelated page after a redesign.

Record special paths as part of that map. A monetised or campaign destination such as mobile slot references should have an explicit purpose, responsible owner and expiry or review date, rather than existing only as a redirect. The same rule applies to press-kit paths, retailer links, short campaigns and international landing pages.

Run connection checks after every major website change. Look for redirect chains, broken destinations, certificate failures and analytics duplication. Domain renewal, hosting renewal and certificate renewal are separate obligations with separate dates. For email, include SPF, DKIM and DMARC status in the review so a web portfolio does not conceal an unattended mail configuration.

Review performance and sale opportunities

Performance review should connect each class to a decision. Core domains can be judged on uptime, search visibility, lead quality and security. Campaign names need conversion and cost data, while defensive names may be judged by relevance and renewal cost. A domain offered for sale should instead have a valuation, target buyer type, asking approach and review date.

The parked page for FRANNIELINDSAY.NET shows the basic information a sales property can carry: the name is available, visitors can purchase it or seek a quote through messaging or email, and the page can present basic age and history signals plus links to other negotiable domains. Those details should be factual and easy to verify. A prospective purchaser should not have to infer the process from an unexplained form.

Direct outreach works best when the seller knows the name’s history, likely buyer and acceptable terms. Advice on approaching domain buyers can support a tailored LinkedIn message, followed by a concise email containing the domain, relevant history and a clear next step. Avoid excessive follow-up, disclose conflicts and check that a proposed transfer will not infringe an existing trademark.

Use repeatable portfolio routines

Automation should flag exceptions, while a person still approves meaningful spending. A weekly routine catches small changes; a quarterly routine tests whether the portfolio still matches the business. The following checklists create accountability without asking staff to repeat the same manual inspection every time.

During weekly and monthly reviews, focus on these checks:

During quarterly and ownership reviews, complete these checks:

Keep the system accurate over time

Choose a storage method that matches the portfolio’s size and staffing. A spreadsheet offers flexibility and portability. A domain-management platform provides broader visibility across registrars and connected services. A database or structured workspace supports custom fields, detailed audit histories and organisations with frequent staff changes.

Storage method Best suited to Main advantage Main limitation
Spreadsheet Small, stable portfolios Familiar, portable and quick to set up Reconciliation becomes manual as the portfolio grows
Domain-management platform Teams using several registrars Renewal and DNS status in one view Subscription costs and available fields vary
Database or structured workspace Large or frequently changing portfolios Custom fields, permissions and audit history Setup and access controls require ongoing maintenance

Whatever method is used, assign a person responsible for accuracy and schedule a formal review. Preserve exports of invoices, renewal records and sale correspondence so the information survives a change of platform or account. Remove stale rows only after checking that no website, mailbox, certificate or advertising account still depends on the domain.

Every name should have a named custodian, an accurate renewal date, a defined purpose and a recorded next action. That standard keeps domain administration controlled without making it a full-time job.