Before your domain expires, it is critical to confirm its current status, ensure the billing method is active, and verify that all contact details are up to date. This guide outlines the necessary checks to prevent service interruption.
Assumed Scenario: Preparing for Domain Renewal
Picture an independent site owner preparing a small travel-notes project on a domain chosen for its readable spelling and a familiar, generic suffix. She keeps her renewal notes in a plain text file. Her checklist has three headings: Domain Status, Billing Method, Contact Record. Under each she writes candidates rather than final answers.
For Domain Status she lists three items with tentative names: "Registrar status" (is the domain active, expired, or in a grace or redemption period—terms her registrar account might show, which she intends to confirm there rather than assume), "Lock state" (client transfer prohibited or not), and "DNS nameservers as listed" (to compare later with what she configured). Her two invented example entries look like this: status: active — verify in account and lock: transfer lock — confirm toggle. They are placeholders she plans to replace after checking the actual dashboard, not records of anything already observed.
For Billing Method she writes "Payment on file," "Renewal term" (one year versus multi-year), and "Auto-renew setting." Two sample rows: card ending 4417 — expiring, plan to update and auto-renew: unclear — check before lapse. She adds a note to look for renewal notices reaching the contact address, since a missed message is the quiet failure mode she worries about.
For Contact Record she lists "Registrant email," "Alternate email," and "Phone or postal contact if the registrar requires it." Her placeholder rows read: email A — primary, confirm inbox and email B — backup, forwarding uncertain. The phone field stays blank with "decide later."
Her one worked choice: she keeps the transfer lock on for now and postpones any nameserver edit until renewal is confirmed, reasoning that an unrelated DNS change during a renewal window adds confusion without benefit. These entries are her own draft examples, written to show how each item gets classified and revisited; they are not verified facts, and the dashboard check itself is the next step.
Verifying Domain Status in the Console
The console shows the domain's actual stage and renewal window, so start by reading the status displayed there rather than assuming where the domain sits in its lifecycle. The page describes normal, grace, redemption, and pending-deletion stages as separate states with different fees.1
Renewal is blocked for domains that have not completed real-name verification; those must be verified first. A domain in an abnormal state, such as clientRenewProhibited, requires contacting the registrar to remove the restriction.1
After payment, check whether the expiration date in the domain list has actually been extended, and if not, look up the renewal order status in order management.1
For the Domain Status heading, she can replace her tentative “Registrar status” line with one dated entry that records what the console shows today and what each label would mean for her. A practical format is: date checked, status shown, what changes next, and by when. A filled example might read “12 May — active, expiry 3 June; renew before 27 May.” If her domain were already in a grace period, the same four fields would instead read “12 May — grace period; redemption possible after 3 June; renew now,” so the field structure stays constant while the values tell a different story.
She might also separate two questions she had merged: whether the domain is active and whether auto-renew is switched on. Those are different rows, and recording them separately keeps one answer from hiding the other. Her earlier decision to leave the transfer lock alone can sit as a short note under this heading rather than as a separate checklist item, since it belongs to the same moment of checking status.
For Billing Method, she can add a “last confirmed” date beside the card ending 4417 and its expiry, so a future glance shows how stale the note is. She can choose to write the renewal term and auto-renew setting as she last saw them, marked as unverified until she next checks. That way the checklist distinguishes what she remembers from what she has confirmed.
Checking Billing Method and Auto-Renew Settings
For auto-renew, the source describes a console path for an Alibaba Cloud domain: sign in to the domain list with the account that owns the domain or an authorized RAM user, select the domain, then choose the more menu and open auto-renew, confirm the domain, and submit. It states that the account balance or credit line must cover the renewal, and only one of the two payment methods is used.1
Deduction attempts begin 15 days before expiry, once per day, until payment succeeds or the domain expires. If the balance is insufficient, the source says to add funds and renew manually before expiry, or wait for the daily retry.1
For the billing row she already drafted, the next move is to split it into two dated entries: one for the payment method on file and one for the auto-renew setting. She can write “card ending 4417 — expires 09/27” and beside it “auto-renew: on, confirmed [date],” then leave a blank line for the next check. If she prefers, she might instead mark auto-renew as “off — decision pending,” which is just as valid a record and keeps the choice open.
She can also add a renewal-term note, such as “current term ends 14 March next year; multi-year option not chosen,” so the billing row answers both “how is it paid” and “how long does it cover.” Another sample line might read “alternate payment: none recorded,” flagging a gap without treating it as a failure.
For her worked choice, she can keep the auto-renew entry as a question rather than an answer until she has compared it with the renewal term. Recording “auto-renew on, but term ends sooner than expected” gives her something to resolve on the next pass, and the plain text file stays honest about what she has confirmed and what she has only assumed.
Confirming Contact Information and Real-Name Authentication
The contact record is only part of the check under Chinese mainland rules: every domain name must complete real-name authentication to resolve and be used, and a domain not authenticated is locked by the registry with a serverHold status, so the site cannot be reached. The material puts authentication in two steps: create an information template and get it verified, then associate the verified template with the domain.2
For the template itself, the holder name must exactly match the name on the uploaded credential, including characters and punctuation. The email address must be real and verified through the field, and the source suggests avoiding email addresses on new generic top-level suffixes. The contact person need not be the legal representative.2
You can treat the contact entries as a short personal log rather than a form to complete: open your draft and, beside “Registrant email,” note whether the address still receives mail and whether the record shows it as verified or unverified. If you list an alternate email, you might add why it exists, such as a forwarding inbox you check less often. That reason helps you decide later whether it still suits the entry.
Where the heading mentions real-name authentication, you could add a “last checked” date and a plain line describing what your own notes say about the authentication state, without copying identifiers. For example: “contact record checked 14 March; authentication note still marked pending in my file.” Keep that entry separate from the email row so a contact change does not silently look like an authentication change.
If these details sit in a plain text file, consider adding one short question per line, such as “does the registrant email still reach me?” or “is the authentication note current?” You can leave answers blank until you are ready. This keeps the contact section useful for renewal decisions without turning your notes into a finished record.
Reviewing WHOIS Data for Expiry Date Accuracy
For expiry-date accuracy, the provider's guide says to use the WHOIS domain information query: enter the domain and click to query, then check the domain status shown on the results page. The same page states that if WHOIS shows the domain has expired, the lock may be caused by that expiry, and it points to the redemption section for expiry-time details.3
The guide also lists the next steps by period: during the renewal grace period, renew promptly to extend the domain's validity; during the redemption period, redeem the domain at the higher price; if the domain has already been deleted, register it again. Keep the WHOIS-expired condition attached to those options rather than treating a lock itself as proof of expiry.3
You can begin with one WHOIS excerpt you have already saved and mark its date plainly, so the expiry line is read as a snapshot rather than a live fact. Add what you compared it against, such as the renewal date shown in your own notes, and note any mismatch without deciding yet which one is right.
Consider recording two fields for that excerpt: “date captured” and “expiry date shown.” A filled example might read “captured 3 June; expiry 12 March next year,” followed by a plain question: “does my renewal record agree?” You might leave the answer blank until you have looked.
If the excerpt lists a status such as active or pending renewal, you can copy that wording as it appears and keep your own interpretation separate. One sample line could read “status shown: active; my note: awaiting renewal confirmation,” which keeps the observation distinct from the judgement.
You might also note which contact field the excerpt displays, then check later whether that address still reaches you. Keeping these lines short and dated helps you revisit the same excerpt without retyping it.
Final Checklist Before Expiration Window
You can turn the three headings in your draft into a short, dated log by adding one entry per question you still have, rather than filling every line with an answer. For the Domain Status heading, consider writing today’s date beside each candidate and a plain note of what you actually see. An example line might read: “checked 3 June; console shows active; grace period not seen.” If you are unsure what a status label means, you could keep the wording as shown and put your own question beside it, such as “confirm whether this label means renewal is pending.”
For the billing entry, you might split the row into two dated lines: one for the payment method on file and one for the auto-renew setting. A filled example could read “3 June: card ending 4417, expiry next January” and “3 June: auto-renew setting unclear; compare with renewal term.” Adding a renewal-term line, such as “current term ends 14 March next year; multi-year option not chosen,” lets the same row answer both how payment is made and when it lapses. You can choose to leave the auto-renew item as an open question until it matches the term note.
For the contact record, you could treat each line as a personal check: beside “Registrant email,” note whether that address still reaches you, and add a “last checked” date. A sample line might read “registrant email — reaches me; checked 3 June.” If your notes mention real-name authentication, you might add a plain line about what your own record says and when you last looked, without turning it into a formal requirement.
Finally, you can date one saved WHOIS excerpt and record two fields: “date captured” and “expiry date shown.” A worked example might read “captured 3 June; expiry 12 March next year; status shown as active.” Keep your interpretation separate from the copied wording, and note which contact field the excerpt displays. These short, dated lines give you a usable snapshot without pretending to be live facts.
Frequently asked questions
How can I turn my draft headings into a dated log of the questions I still have, rather than answering every line?
You can turn the three headings in your draft into a short, dated log by adding one entry per question you still have, rather than filling every line with an answer. For the Domain Status heading, consider writing today’s date beside each candidate and a plain note of what you actually see.
How could I split the billing entry into two dated lines, one for the payment method and one for the auto-renew setting?
For the billing entry, you might split the row into two dated lines: one for the payment method on file and one for the auto-renew setting. A filled example could read “3 June: card ending 4417, expiry next January” and “3 June: auto-renew setting unclear; compare with renewal term.”
How can I treat the contact entries as a personal log, noting whether the registrant email still reaches me and adding a last-checked date?
For the contact record, you could treat each line as a personal check: beside “Registrant email,” note whether that address still reaches you, and add a “last checked” date. A sample line might read “registrant email — reaches me; checked 3 June.”
如何给域名续费-域名(Domain)-阿里云帮助中心 . Retrieved 2026-11-19. ↩︎ ↩︎ ↩︎ ↩︎ ↩︎
创建域名信息模板-域名(Domain)-阿里云帮助中心 . Retrieved 2026-11-19. ↩︎ ↩︎
解除域名锁定状态Clienthold、Serverhold-域名(Domain)-阿里云帮助中心 . Retrieved 2026-11-19. ↩︎ ↩︎