research
Auditing whether domain registration contacts still belong to the company
A method for checking registrant, admin, and technical contacts against current company records, and for testing whether renewal notices still arrive.
Use this benchmark to size repeatable IT work, set the review cadence, and decide what stays with the technical owner before assigning the workflow to an IT virtual assistant.
Research playbook
On this pageJump to section
Key stats
Key takeaways
A domain registration record can keep pointing at a former employee for years because nothing breaks until a renewal or a recovery request. The registrant email may be a personal address, the admin contact may be an agency that no longer works for the company, and the technical contact may be a mailbox nobody reads. This audit checks whether each contact still belongs to the company and whether the renewal path works. The audit is a periodic check of records, not a legal opinion on ownership.
Question and scope
The audit asks whether the registrant, administrative, technical, and billing contacts for each company domain resolve to a current company-controlled person or mailbox. The unit is one domain registration record. The population is every domain in the company register plus any domain found in invoices or public records. The result describes the records at the audit date. Record the retrieval date and the source for every public record lookup.
Include domains used only for redirects and campaigns because they can still carry brand risk. Exclude domains owned by a client or another organisation, but note the relationship. Record the registrar and the registry for each domain. A scope that covers only the main website will miss the names that are easiest to forget. Note the domains that belong to a client and the contract that governs them.
Define the registrant record
List the fields that matter for ownership and recovery, including the registrant organisation, the contact name, the email, the phone number, and the postal address. Note which fields are public and which are masked by a privacy service. Record the registrar account that controls the record. These fields determine who can prove ownership. Record the registrar account and the legal entity shown in the record.
Check whether the registrant organisation matches the legal entity that operates the business. Note any domain held by a parent, a trading name, or an agency. Record the evidence used to confirm the match, such as a company registration number or an invoice. A match based only on a familiar name is not verified ownership. Attach the company registration document or the invoice used for the match.
Build the domain inventory
Export the domain list from the registrar accounts the company can access. Add the domains found in the website configuration, the mail records, and the finance invoices. Ask the marketing and account teams for campaign domains. Compare the lists and record the source of each entry. Keep the source column in the inventory so a single-source domain can be traced.
Mark the domains that appear in more than one source and the ones that appear in only one. Investigate the single-source domains before closing the inventory. Record the registrar account owner for each. An inventory with no source column cannot be checked later. Record the person who confirmed each entry, the date of the confirmation, and the source document used.
Verify contact details
For each domain, compare the registrant email with the company directory and the identity provider. Check that the mailbox exists and that a current employee can receive mail there. Verify the phone number against the company record. Mark any contact that points to a personal address or a departed employee. Test the admin and technical mailboxes with a message that asks for a reply.
Send a test message to the admin and technical contacts where the registrar allows it. Record whether the message arrives and who receives it. Check the billing contact against the finance system. A contact that looks correct but reaches a shared mailbox with no owner is still a gap. Record the mailbox owner and the route for a bounce or an auto-reply.
Check registrar access
List the people who can log in to each registrar account and the second factor that protects it. Confirm that the account uses a company-controlled email and a company-managed authenticator. Record any account that relies on a personal phone or an agency login. Access to the registrar is access to every domain in the account. List the second-factor method and whether it is tied to a company device.
Check whether the registrar supports role-based users and whether the company uses them, or whether everyone shares one login. Review pending transfer locks and authorization codes. Record who can unlock a transfer. The audit should show both the named users and the recovery route. Record the transfer lock status, the person who can unlock it, and the last date the lock was checked.
Test renewal notices
Confirm where the registrar sends renewal reminders and whether that address is monitored. Check the reminder schedule and the payment method on file. Ask finance whether the card or invoice route is current. A domain that renews automatically still needs a working notice path when the payment fails. Note the last invoice date and the payment method shown on it.
Review the last renewal invoice and the confirmation email. Note who received them and whether the domain was paid on time. Check the registrar grace period and the recovery fee. Record the test date. The renewal path is verified when a current employee can see the notice and act on it. Record the sender address and the mailbox where the notice arrived.
Review privacy and proxy settings
Note whether the domain uses a privacy or proxy service and who controls it. Check that the service still forwards mail to a current company address. Confirm that the underlying registrant details are correct even when they are masked. A proxy that hides a stale contact also hides the problem. Note the proxy provider and the forwarding address used for contact mail.
Review the contact details stored inside the registrar account, not only the public record. Check the transfer lock and the domain status flags. Record any setting that could block a legitimate transfer or recovery. The audit should distinguish public masking from internal neglect. Compare the internal record with the public record, note every difference, and assign the correction to an owner.
Report by risk
Group the findings by risk, starting with domains that carry mail, sign-in, or revenue. Then list domains whose registrant contact is a departed employee or a personal mailbox. Add the domains with shared registrar logins. Send the report to the domain owner and the finance contact. Add the registrar account owner, the renewal date, and the contact status to the risk view.
For each finding, record the required change, the owner, and the due date. Ask for a decision on domains that an agency manages. Keep the evidence with the report. A finding is closed when the registrar record and the company record both show the change. Record the evidence of the change, such as a screenshot or a confirmation email, and the date it was received.
Set a review cadence
Review the domain inventory and the contact fields every quarter. Recheck the registrar access after any staff change or agency change. Confirm the renewal notices at the same time. Add the review to the vendor and finance calendars so it is not dependent on one person. Assign the review to a named person and add a backup for leave periods.
Repeat the contact verification after a merger, a rebrand, or a website migration. Add any new domain to the inventory before it goes live. Keep the previous report for comparison. A quarterly check is short when the inventory is already complete. Record the date of the last full review, the domains added since, and the person who added them, so the growth is easy to audit.
Limits of the check
The audit verifies the records the company can see and the contacts it can test. It cannot prove that a registrar will accept a recovery request or that a proxy service will forward mail in every case. It also cannot resolve a legal ownership dispute. State these limits so the report is not read as a guarantee of control. Note the records that could not be verified and the reason.
Public records may lag behind registrar changes, so verify in the registrar console where possible. Note the retrieval date for every public lookup. Repeat the check after a transfer or a privacy setting change. The method is a periodic assurance step, not a one-time cleanup. Keep the previous reports so a change in contacts can be traced over time, and note the reason for each change.
Sources and next step
Use the NIST Cybersecurity Framework 2.0 and the CISA Cross-Sector Cybersecurity Performance Goals as primary references for the vault administrator, SaaS project account, domain contact, loaner handover, and mobile app measures discussed here. The NIST SP 800-53 Rev. 5 supports the access and audit record checks, and the GAO data reliability guidance supports the sampling and verification approach used in these methods. Apply your own policies, contracts, and system documentation when adapting the method.
Compare this study with the vault administrator audit and the SaaS project account study before combining them into one review cycle. If the measurement work is recurring and your technical owner can define the scope, review the service areas and contact ITVirtualAssistant to discuss a limited pilot.
Benchmark brief
What this research page must produce
A practical estimate for volume, review time, escalation rate, and assistant capacity.
A clear split between routine support, preparation work, and technical ownership.
What the auditing whether domain registration contacts still belong to the company data shows
Treat this as a planning benchmark, not a universal number. Compare the benchmark against your ticket volume, SaaS stack, documentation backlog, and support risk before assigning recurring work.
The useful output is a decision about capacity, not a static statistic. If the workflow is high volume and low judgment, an IT virtual assistant can absorb coordination and upkeep. If the workflow is low volume but high risk, keep it with the technical owner and use the assistant only for preparation, reminders, and documentation.
Workflow
Recommended operating workflow
Collect a baseline
Pull the last 30 to 90 days of examples related to auditing whether domain registration contacts still belong to the company, including completed work and unresolved exceptions.
Classify the work
Tag each item by routine admin, manager approval, technical decision, security risk, or vendor dependency.
Set the operating number
Use the median weekly volume and review time to decide how many assistant hours the workflow deserves.
Refresh the benchmark
Recheck the numbers quarterly so tool growth, new systems, and security requirements do not silently change the scope.
Decision rules
| Metric | Use it to decide | Manager action |
|---|---|---|
| Weekly volume | Whether the workflow is worth assigning as recurring assistant work. | Approve a weekly capacity target and backlog threshold. |
| Access sensitivity | Whether the assistant can work directly or only prepare review notes. | Set least-privilege permissions and removal dates. |
| Escalation rate | Whether the workflow is stable enough to delegate. | Rewrite the SOP when exceptions exceed the agreed threshold. |
Consolidated statistics
| Statistic | Figure | Source |
|---|---|---|
| Unit | One domain record | Study protocol |
| Fields checked | Four contact roles | Study protocol |
| Review cadence | Quarterly | Study protocol |
Sources
- NIST SP 800-81-2, Secure Domain Name System Deployment GuideDNS deployment and operational responsibility guidance.
- CISA Cross-Sector Cybersecurity Performance GoalsBaseline controls for domain and account ownership.
- NIST Cybersecurity Framework 2.0Asset management outcomes for public-facing services.
- GAO Assessing Data ReliabilityMethod for verifying registration records against primary sources.
Measurement checklist
| Field | What to capture | Owner |
|---|---|---|
| Volume | Weekly request count, backlog age, and repeat issue patterns | Assistant prepares, manager reviews |
| Risk | Access level, customer impact, security sensitivity, and approval needs | Technical owner |
| Cadence | Daily, weekly, monthly, or quarterly review rhythm | Manager |
| Evidence | Sample tickets, logs, screenshots, and before-after examples | Assistant collects, owner validates |
| Escalation | Triggers, approval path, response time, and stop-work rules | Technical owner |
How to read the result
A good research page should leave the manager with a working number and a clear boundary: what the assistant can do every week, what the assistant can prepare for review, and what must never move without the accountable technical owner.
Source and refresh note
This planning page is dated for 2026 and should be refreshed quarterly as tool stacks, ticket patterns, and security expectations change.
How should teams use this benchmark?
Use it to define task volume, access limits, review cadence, and escalation rules before assigning work.
Get free benchmark review