Domain Policy Basics
Home / Notes / Domain Policy Basics

Notes

Domain Policy Basics

A domain policy gives your business clear rules on what to buy, who controls it, and when it must be renewed. For South African companies, that matters because missed dates, staff changes and poor records can cost real money and cause avoidable downtime.

Start with ownership, not just registration

A domain should always be held in the name of the business, not an individual staff member. That sounds simple, but many firms in Cape Town, Bellville and Stellenbosch still let one person use a personal email and personal payment card to register names, then struggle later when that person leaves. A proper policy states who the legal holder is, who may approve purchases, and where the renewal notices must go.

Set one primary company contact and one backup contact. Keep the admin email on a shared business address that two or more trusted people can access. If your office in Claremont loses power during load shedding or a laptop fails, the renewal notice should still be reachable from a phone or another location.

  • Use a company email address for registrar communication
  • Record the legal owner, admin contact and technical contact
  • Keep payment details current and tied to the business
  • Store registrar logins in a secure password manager

Buy names that match your trading needs

A useful policy does not say yes to every available name. It sets rules for what gets bought and why. Start with your main trading name, then think about common misspellings, short forms, and names that protect a campaign or product range. If you work across Paarl, Somerset West and Cape Town, the same idea applies whether you are protecting a local service name or a national brand.

Do not chase every domain that looks interesting. Decide whether the name supports a live use, a planned launch, or basic protection against impersonation. This keeps the budget under control and helps the team answer one question quickly: does the name have a clear business reason?

  • Main brand name
  • Common spelling variations
  • Short, easy-to-type versions
  • Campaign or product-specific names
  • High-risk misspellings where customers often slip up

Renewal rules should be written before the deadline arrives

Most domain problems come from weak renewal habits, not from buying the wrong name. A policy should say how long each domain is held, who signs off on renewal costs, and when review happens. For example, renewals can be checked 60 days before expiry, then again at 30 days if payment has not gone through.

That buffer matters if a finance team changes card details, a director is travelling, or an email lands in junk. If your business depends on seasonal trade, a lapsed name during peak period can be a costly mistake. Some owners prefer longer renewal periods for key names, especially where a domain is linked to invoices, email accounts or customer bookings.

  • Set review dates 60, 30 and 7 days before expiry
  • Use automatic renewal for essential domains where possible
  • Keep a second payment method ready
  • Check that expiry notices reach more than one person
{

Use a simple hold-and-release rule for inactive names

Not every domain should stay on the books forever. A clear holding rule helps avoid waste and reduces admin. If a project is cancelled, the name can move into a review period before final renewal is approved. This gives management time to decide whether the domain still has value for future use, resale protection or brand defence.

For a small company in Claremont or a growing team in Bellville, a short quarterly review is usually enough. Look at live websites, email use, active campaigns and any names that have not been touched in 12 months. If no one can explain why a domain exists, it is probably due for review.

  • Keep active domains on a core register
  • Mark dormant names for review every quarter
  • Cancel unused names after management approval
  • Keep notes on why each domain was bought

Watch for expiring names that affect brand protection

A good policy covers more than your own portfolio. It should also include monitoring for names that are about to expire and may become available. This is useful when competitors, suppliers or typo variants could affect your customers. If an important name expires in South Africa, the release window can move fast, so a clean monitoring process is essential.

For example, a Stellenbosch retailer might want to track a short campaign name, while a Cape Town service business may want to watch for a common misspelling of its trading name. The goal is not to buy everything, but to know what is changing and whether action is needed.

  • Track expiry dates for key names linked to your brand
  • Set alerts for names that match your trading terms
  • Flag typo variations and campaign terms
  • Record who decides whether to backorder or let a name go

Make the policy practical for the people who use it

A policy only works if the team can follow it without confusion. Keep the rules short, clear and written in plain language. One page is often enough for the basics, with a second page for approvals and contacts. Include what happens if the main contact is unavailable, who may authorise transfers, and where the latest list of domains is stored.

A local example helps. Suppose a Somerset West company changes its finance manager and the renewal email is still going to the old inbox. If the business has a policy, the handover should catch that within days, not after the expiry date. That same process protects firms during office moves, mergers and staff turnover.

Useful items to include in the final policy:

  • Approved buying criteria
  • Renewal timetable and responsibility
  • Contact details for admin and backup users
  • Transfer approval steps
  • Review dates for dormant names
  • Instructions for alerts and reporting

A solid domain policy is less about legal jargon and more about discipline. It gives the business a routine that can be followed even when people are busy, offices are closed, or power cuts interrupt the day.

Questions we get asked

Who should own a company domain name?

The business should be the legal owner, with admin access controlled by trusted staff. Avoid registering key names in a person’s private account or private email.

How often should we review renewal dates?

Check domains at least 60 days before expiry, then again at 30 and 7 days. That gives enough time to fix payment issues or handovers.

Do we need a policy if we only have a few domains?

Yes. Even a small portfolio can be disrupted by a missed renewal, a staff change or a lost login. A short policy keeps the process clear and repeatable.

Planning something? Email the team.

domains@dropcatcher.co.za