These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
Feature · Domains
Example screen with sample data
Domains
Domains records and operating decisions for the domain and service team.
OverviewDomain portfolio×
DNS & Domain Management · Domains
New
Domain portfolio
Domains
| Domain name | Registrar | Expires at | Auto renew | Owner | |
|---|---|---|---|---|---|
| Domain 232 | RGS-508 | 10 Oct | |||
| Domain 749 | RGS-154 | 06 Oct | |||
| Domain 789 | RGS-161 | 10 Oct | |||
| Domain 646 | RGS-697 | 05 Oct | |||
| Domain 201 | RGS-997 | 13 Oct |
6 of 6 records
Domain 232Domains · DMN-88612
RegistrarRGS-508
Expires at10 Oct
Auto renew✓
What you can do
Keep the working record connected
A domain nearing its expiration date is visible with its registrar and owner. The Domain Owner checks the renewal choice and gives the Portfolio Reviewer a complete record to review. A changed registrar or owner should be checked before the team relies on that entry for a DNS request.
The owner and registrar give the reviewer a way to verify the name before DNS work begins. A domain has no review status of its own, so the decision belongs in the team’s operating handoff. Check the current registrar and expiration date with the owner whenever either changes.
How the work is organized
- Ownership. Domain Owner checks registration details; Portfolio Reviewer makes the portfolio decision.
- Evidence. Compare the name, registrar, expiration, renewal choice and linked owner.
- Follow-through. Check the linked DNS entries after an owner or registrar change.
What to agree during setup
The reviewer checks the domain name against the intended portfolio, confirms who owns the next decision, and reads the expiration and renewal details together. This is an attributed portfolio decision. The name alone is not enough to tell the team who can authorize a change.
Rehearse an ordinary record and an exception with the people who will use this area. Check the linked owner or service before changing a status. If the outside information changes, compare it with the original request before the next handoff.
Check the handoff on an actual case
Start with a domain whose expiration is approaching. Compare the registrar, expiry and renewal choice with the owner who is expected to act. Then take a proposed record for that domain and confirm the reviewer has the same domain context before approving it.
Have the receiving operator repeat the check using the linked records. Review a mismatched owner, value or date with the decision owner before applying the same handling to more work.
For the exception, use a name whose registrar changed while its renewal date stayed the same. The Domain Owner should confirm the registrar and renewal choice against the current registration. The Portfolio Reviewer should confirm that the owner is still the right person for DNS decisions. If the owner changes, inspect existing linked entries before requesting another DNS update. This keeps a domain transfer from being treated as a routine record edit. The portfolio view helps the team find dates already due; it does not itself record a review decision. Agree how the reviewer communicates that decision to the person preparing the next entry.
What your team sees
- Domain portfolio — Names whose expiration date has arrived, with registrar, renewal choice and owner.
- Domains by owner — The current owner’s names and the dates that need attention.
Follow the work through
Follow the domain intake handoff and review the data model before migrating records.
What it keeps track of
Data model- Domains
- A record is one owned domain; the team uses this to track registration, renewal, and ownership.
Who uses it
Permissions- Domain Owner
- , Portfolio Reviewer.
Set up DNS & Domain Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.