This guide outlines a yearly checklist for domain owners to prevent service interruptions. It focuses on verifying expiration status through WHOIS queries, ensuring auto-renewal is active in the management console, and reviewing current contact information. The steps rely on standard registrar interfaces and public lookup tools to maintain domain health without assuming specific provider features beyond general availability.
Setting the Stage: Why an Annual Domain Audit Matters
Suppose a freelance web producer is preparing a yearly review for a small site and has only a spreadsheet, a registrar account screen, and a folder of old setup notes. The producer creates three columns—item, current value, and next action—then fills a few rows to show how the audit works in practice.
The first row reads “Expiration date | 14 March next year | set a reminder 45 days before.” The second reads “Auto-renewal | on, charged to card ending 1234 | confirm the card still works.” A third row, “Registrant contact | old team mailbox | update to a monitored address,” shows why contact details belong beside renewal fields: a reminder sent to an abandoned inbox changes nothing. The producer records these values by reading the account page and the public registration record, labeling each cell “from account” or “from public record” so the origin stays clear.
For the site itself, a second small table lists the name in three working forms: “example-site.com,” “examplesite.com,” and “example-site.net.” The producer marks which form appears on printed material and which resolves to the live site, noting a check of the DNS records that point the name to hosting. This is not a claim that every spelling reaches the same place; it is a way to catch a stale note in the folder before it becomes a broken link. The choice between renewing the shorter form and retiring the longer one is recorded with a reason: “shorter form printed on business cards, so renew it; longer form parked, revisit next year.”
A final column asks whether the record matches the invoice, the invoice matches the card, and the card belongs to someone still reachable. Two fictional rows—one marked “confirmed” and one marked “outdated”—show how the sheet closes a loop rather than merely collecting facts. This imagined audit is drawn up to explain the shape of the task, and later sections go through each check in order.
Verifying Expiration Dates via WHOIS Lookup
A WHOIS query can be used to learn a domain's registrar, status, and expiration date. Alibaba Cloud's WHOIS lookup only supports suffixes for domains registered through Alibaba Cloud; for suffixes it does not cover, the page points to the ICANN official lookup or other WHOIS tools.1
The result includes an Expiration Date (UTC) field. The page advises renewing before that date to avoid service interruption or the domain being registered by someone else, and recommends enabling auto-renewal in the domain console. It also notes that an expiration date seen elsewhere may differ due to time zones or data caching delays, and that the date shown in the registrar's official console should be treated as the most accurate.1
When the expiration status deserves a closer look, the Domain Status field can hold several statuses at once, and the page provides a status-code reference for their meanings and suggested actions.1
For the expiration-date rows you already keep, you might add one field, “WHOIS check date,” and record what the lookup showed for the domain in its current form rather than for an older spelling. If your sheet lists “example-site.com” with a renewal date, you can write a separate archived row for “examplesite.com” and note whether the two records appear to describe the same registration or different ones. This keeps the current entry and the historical note from being blended into one value you later trust.
When a lookup result and your registrar screen disagree, consider treating that as a question to carry forward rather than an answer. A practical note might read: “Registrar shows 14 March; lookup shows 12 March; ask which record governs before setting the reminder.” You can also mark whether the record belongs to the site you are reviewing or to a similarly spelled name, since a small spelling difference changes which column the result should occupy.
You might close the row with a next action written as a dated intention, not a completed step: “Recheck in 30 days; confirm with account holder; keep old setup note attached.” The choice of how often to recheck is yours, and a glance at one row is enough to see whether the date, the name form, and the owner contact still line up before you move to the next entry.
Confirming Auto-Renewal Status in the Console
To turn on auto-renewal from the domain list, select the domain, then choose More and Open Auto-Renewal at the bottom of the page. Confirm the domain, then submit. The page states this should be done using the main account that holds the domain or a RAM user already authorized to manage domains.2
Billing begins on the 15th day before expiry, with one collection attempt per day until it succeeds or the domain expires. The charge draws from either the account balance or the credit limit, not both at once, so the page advises keeping the chosen source sufficient and setting a balance alert. If funds fall short before expiry, manual renewal is required.2
For the auto-renewal part of your own review, you can open the account screen beside your spreadsheet and note the switch state as you see it, rather than relying on last year's note. A row might read “Auto-renewal | on | confirm payment method before next term.” If the screen says off but an old note says on, you might write that discrepancy into the next-action cell instead of resolving it on the spot.
You could then check which payment method the screen associates with renewal and whether the contact address on that account still reaches someone who reads it. A second row might read “Contact email | old shared inbox | ask owner which address is current.” Keep these as observations from what the screen shows, separate from any assumption about what will happen at renewal time.
If you are preparing rather than completing the review, consider marking each row's status as “seen today” or “still to confirm” so future you can tell the difference. A sample third row: “Renewal notice setting | reminder email on | verify recipient before next term.” You can leave the last column dated, such as “recheck in March,” so the table records an intention rather than a finished action.
Reviewing Contact Details and Privacy Settings
In the Alibaba Cloud WHOIS documentation, the owner contact email appears as the Registrant E-mail field, but the page states that public WHOIS results no longer display registrant personal information, in line with ICANN registration data policy and GDPR. For a domain registered through Alibaba Cloud, the page suggests trying the on-page “contact by filling in information online” link to reach the owner. Registrar contact is separate: the Registrar Abuse Contact Email shown in the English information is for abuse reports such as phishing or fraud, not for routine contact detail review.1
The page also explains why stored contact details matter for updates. A clientUpdateProhibited status, whether set by the registrar or registry, blocks changes to the registrant, administrative, technical, and billing contacts as well as the DNS servers, though resolution records can still be set or modified; the page calls this a normal security state and says the update lock can be turned off in the domain console before modifying domain information. The page does not describe a separate privacy-setting control.1
For the contact-details area of your own review, you can add rows to the same spreadsheet rather than start a new document. A workable shape is “field, what the account shows, who currently relies on it, next action.” Two sample rows might read: “Registrant email | old team address | no one has checked since handover | confirm a reachable owner before renewal” and “Privacy setting | contact details hidden in public lookup | owner wants this kept on | recheck in six months.” These are demonstration rows; your entries depend on what your registrar screen shows, so note that you have seen the screen rather than assume the value.
You might also list each contact role separately, because a single address may serve billing while another serves technical notices. If a row names a person who has left, consider writing the question you still need answered, such as “who will receive notices now,” and leave the answer blank until you can confirm it. Marking entries as “seen today” or “still to confirm” keeps the difference visible on your next pass. The privacy choice itself is yours to make; the checklist only records which setting you intend to keep and when you plan to look again.
Checking Domain Locks and Security States
The registrar-side status explanation lists clientTransferProhibited as a normal security state that blocks transfers to another registrar; unlocking is needed first if a transfer is intended. It also recommends, for theft protection, enabling the transfer-prohibited and update-prohibited locks in the domain console when they are not already set.1
Two other statuses call for different follow-up: clientUpdateProhibited still allows resolution records to be set or changed even though registrant, contact, and name-server details cannot be modified, while inactive usually means no valid name servers were entered at registration, so correct address settings are required in the console or the name will not resolve.1
For the lock and security part of your own review, you can open the registrar account screen next to your spreadsheet and record the state you actually see, rather than recalling a setting from last year. A workable row might read “Transfer lock | on, as shown on account screen | confirm before any planned move,” with the middle column quoting the screen and the last column written as a dated intention. You might add a second row for whichever security switches appear there, noting only what is visible today.
If a lock appears off while your old setup notes describe it as on, consider treating the difference as a question to carry forward, not an answer. You can write a note such as “on in old notes, off on screen today; ask account holder before changing anything,” and mark the row “still to confirm.” That way, a later reader can tell what you observed from what you assumed.
You can also decide for yourself whether each lock needs a next action at all. Some rows may reasonably end with “no change planned,” while others earn a reminder date. Recording the difference honestly keeps the table useful without turning it into a list of tasks you have not yet done.
Documenting Findings and Scheduling Next Steps
You can turn the rows you have already filled into a short record that shows how each finding was reached, then leave the unresolved parts as dated intentions. In the same spreadsheet, consider adding a status column beside “next action,” with values such as “seen today,” “waiting on account holder,” or “no change planned.” That way a later reader can tell which entries reflect a screen you actually looked at and which ones are still open.
For a disagreement between an old setup note and the account screen, you might record both values rather than overwrite one. A workable example reads: “Auto-renewal — note says on, screen shows off — ask the account holder, then recheck in 30 days.” Writing the date and the person turns the row into something you can return to, not a resolved fact. You can apply the same pattern to a domain name spelled differently in an old invoice and a current account entry: keep the two spellings, note where each came from, and phrase the next step as a question to confirm.
You can also decide how far ahead each row deserves a reminder. A row connected to a renewal date might carry a reminder 45 days out, while a contact row with no immediate change could simply say “review at next yearly pass.” These intervals are your own choices; some rows may reasonably end with “no change planned,” and you can leave them there without forcing an action.
If you are preparing this review before checking everything, keep the status words honest. Mark a row “seen today” only after you have looked at the current screen or document, and leave it “still to confirm” otherwise. When you return, the mix of statuses and dated next actions gives you a clear place to resume without rereading every note.
Frequently asked questions
How can I add a WHOIS check date to the expiration-date rows I already keep?
For the expiration-date rows you already keep, you might add one field, “WHOIS check date,” and record what the lookup showed for the domain in its current form rather than for an older spelling. If your sheet lists “example-site.com” with a renewal date, you can write a separate archived row for “examplesite.com” and note whether the two records appear to describe the same registration or different ones.
What can I do if a lookup result and my registrar screen disagree?
When a lookup result and your registrar screen disagree, consider treating that as a question to carry forward rather than an answer. A practical note might read: “Registrar shows 14 March; lookup shows 12 March; ask which record governs before setting the reminder.”
How should I close a row with a next action?
You might close the row with a next action written as a dated intention, not a completed step: “Recheck in 30 days; confirm with account holder; keep old setup note attached.”