Domain expiration can silently shut down your website. This checklist walks you through verifying your renewal settings, ensuring your contact information is current, and confirming that auto-renewal is active to keep your site online without interruption.

Scenario: A Personal Blog Owner Discovers an Expiring Domain

This is an imagined but concrete situation: a personal blogger keeps a small site about backyard birds and has just noticed a renewal notice in his inbox while preparing a post about winter feeders. He is not sure whether the message is real, and he does not want the site to vanish during a busy week.

His first concrete move is to write a short "domain facts" note in the same text file where he drafts posts. He gives it three headings: Identifier, Registrar and Account, and Dates. Under Identifier he records the exact written form he chose, including capitalization and the suffix, as he typed it on his own invoice — for example, "BackyardFeederNotes.example" and a second candidate, "feeder-notes.example". He marks the first as the one he believes is active and the second as "not registered, check later". Under Registrar and Account he notes the login email he used and nothing more sensitive. Under Dates he writes the observed expiry date from the notice and a second column for "renewal window opens", leaving the second blank rather than guessing. Writing the name twice — once as a display label and once with the suffix separated — helps him see whether the notice matches the spelling he actually chose.

Next he builds a tiny comparison table with three columns: Notice details, My record, and Difference. In the Notice details row he copies only what the message states, such as the suffix and the month of expiry. In My record he writes what his own note says. The Difference column holds his open questions: "suffix matches", "month differs by one". This is his own example, not a report of a real message.

To check where the domain points, he plans a simple lookup step: open his domain settings page and compare the listed name servers with the two host names he wrote down when he first set up the blog. If the values differ, he notes the difference and stops rather than changing anything. He also makes a calendar entry for a weekday morning two weeks before the stated expiry, labeled "renew or ask", with the note "do not act on a link in the message; log in directly".

Finally he drafts a short message to himself listing what he still does not know: whether auto-renew is on, which payment method is attached, and whether the contact email is current. He writes one question per line and leaves space for the answer, so the next step is a single, unhurried login rather than a rushed click. These entries are his own example format, not advice about any provider's interface or policy.

Step 1: Locate Your Domain Management Console

The cited official guide places domain management inside the account: after signing in, the domain management console is where you can view the expiry date, renew or redeem, transfer out, and modify DNS records. This console is the starting point the guide names for those listed actions.1

The guide describes the console in general terms rather than listing separate menus. It does not state additional steps for locating a particular domain or for confirming auto-renew, so those details should not be assumed from this source.1

You can start with the renewal message itself: open it beside your own domain-facts note and trace one identifier—your exact registered name, including the suffix—back to the account where you last paid. If the note already holds a login page and account label, that is your first candidate console; treat the message as a pointer, not as proof of where the domain lives.

To follow the trail, open that account in a new tab rather than clicking anything in the message. Look for a list of domains you own, then find the row matching your recorded identifier character for character. A near match with a different spelling or suffix is a separate registration, so consider writing it in the note as a second entry before assuming it is yours. If the account shows no matching row, the note's next candidate—an older host or a second registrar account—becomes the place to look, and you can record which candidate failed so you do not repeat it.

Here is a filled example of the fields you might keep for that search, using the bird-blog situation: Identifier: winterfeeders.example, suffix included; Candidate account label: the one used at first registration; Status: matching row found or not found; Last checked: today's date; Next candidate: the older host account. When a later renewal notice arrives under a different name, add a second block with the same fields rather than overwriting the first, so the history of which account holds which domain stays readable.

Before you commit to a console, you might compare two candidate rows side by side: one where the domain name matches but the contact address is unfamiliar, another where the contact address matches but the name looks slightly off. Record the reason you trust one over the other in plain words—for instance, "contact matches my usual mail" or "name differs by one character." That sentence is often enough to keep a future renewal from being chased in the wrong place, and it leaves you a clear next step: return to the chosen console and check what the renewal setting currently says.

Step 2: Verify the Current Expiration Date

Open the cited official guide and follow its account-management route: after signing in, go to the domain management console to view domain expiration dates. The guide lists this as one of the available console actions, alongside renewal/redemption, transfer-out, and changing DNS records; it does not describe any further verification steps.1

The guide also ties the registered email address to expiration reminders, stating that important notices such as domain expiration alerts and transfer authorization codes are sent there. Use the address you actually monitor when checking the account, since the guide does not specify a separate lookup tool or comparison method.1

Go back to your domain-facts note and add one line that records the expiration date exactly as it appears in your account, including the year and the time zone if one is shown. Note where you read it—account dashboard, renewal page, or a confirmation email—because two places can disagree and you will want to know which one you trusted.

A small dated log helps here. Consider a three-column entry: Date checked, Source, and Date shown. A filled example from the bird-blog case might read: 14 January, account dashboard, 3 March next year. A second row might read: 14 January, renewal email footer, 2 March next year. The one-day gap is exactly the kind of difference worth resolving before you decide anything.

When the dates differ, treat the shorter one as your planning date and jot a note about why. You might write: "Using 2 March because the email is older; will confirm on dashboard." That sentence costs little and prevents a later argument with yourself about which figure you saw.

You can also compare the date to the calendar you actually keep. If the shorter date falls in a week when you travel or publish heavily, mark it now as a week you would rather not spend troubleshooting a dead site. That is a personal scheduling choice, not a rule about when renewals must happen.

Finally, decide how often you will re-check. A monthly glance at the same dashboard row is one option; checking only when a notice arrives is another. Write your choice into the note so the next check has a defined trigger and you are not relying on memory during a busy week.

Step 3: Confirm Contact Information Accuracy

Open the contact template you use for the domain in NamesLink and check that the holder name, email address, phone number, and full address are current, since the source notes that inaccurate or incomplete registration information can lead to a domain being suspended or deleted. Make sure the email is one you actually read, because renewal reminders and transfer authorization codes are sent there. To verify by hand, compare each field in the template against your own records and update anything that has changed.1

Step 4: Enable Auto-Renewal Settings

GoDaddy 's registration FAQ states that a domain registration lasts up to 10 years, and that to continue registration you must renew the domain before it expires—by turning on auto-renew or renewing manually. In that same section, the page presents turning on auto-renew as one of the two stated ways to keep a registration active.2

The page also includes a related step: make sure auto-renew is turned on so you continue to hold the domain registration. This is given as guidance alongside the statement that every domain must carry current, correct registrant contact information, an ICANN requirement the page says all registrars must follow.2

The page does not describe where the auto-renew control sits, what it costs, or how payment is handled. Those details would come from your actual account, not this FAQ.2

For the bird-blog case, you can turn the unresolved note you drafted earlier into a small auto-renew worksheet before you touch any settings. Use three columns: Setting, What I see, and My next step. A filled row might read: Setting: auto-renew; What I see: a toggle whose current position I cannot confirm; My next step: sign in to the account I identified in Step 3 and record the toggle state. Add a payment-method row and a contact-email row in the same way, leaving “What I see” blank until you have actually looked. This keeps a plan separate from a confirmed fact.

When you do sign in, you might compare the toggle label with the renewal wording in the notice rather than assuming they mean the same thing. Another conditional example: if the notice names an expiration date and the account shows a different one, note both in the worksheet and use the earlier date as your planning date, as you decided when comparing dates. If the toggle appears off while a payment method is listed, that is a question to record, not a conclusion. You can write: “Toggle appears off; payment method listed; ask which one governs renewal.”

A short checklist you can keep beside the worksheet might ask: Does the toggle state match my note? Is a payment method present, and is it one I still use? Is the contact email one I can open today? Which date did I choose as my planning date, and why? Filled example answers for the bird blogger could read: toggle state recorded on 14 January; payment method is the card he uses for hosting; contact email is the one he checks weekly; planning date is 2 March because the notice showed an earlier date than the account. These are his own records, not verified facts about any service.

You can also decide how to treat the worksheet afterward. One option is to add a single line to the dated log you started, such as “Auto-renew checked, toggle state copied, payment method noted.” Another is to leave a reminder for yourself to re-open the same account row on the day you chose. Either choice is yours; the aim is that the next time a notice arrives, your own note shows what you already confirmed and what still needs a look.

Step 5: Review Billing Method Validity

At the Billing stage described in this Namecheap registration guide, if Whois and DNS settings are fine and it is the first time you pay for the order, you specify the payment method. The options listed are Secure Card Payment, PayPal, or Account Funds. Secure Card Payments accept Visa, MasterCard, American Express and Discover, using a saved card or a new one with the card holder's name, the 16 card number digits, the 4 expiration digits (MM/YY), the 3 CVC digits and the billing address. The guide also states that on this same page you can review the auto-renewal settings and the billing contact information related to the order, and save them as default for all future orders.3

For the billing step, you can return to the worksheet you started and extend it rather than opening a new document. Add one column after the toggle state: Payment method on file. In the bird-blog example, that cell might read “card ending 4417, expires 09/26,” copied from the account page rather than from the notice. A second column, “Still valid?”, lets you mark yes, no, or unsure without forcing a decision yet. If the ending digits differ between your note and the account, that difference is worth circling before you change anything.

You might also record what the payment method is tied to. Some owners keep one card for several domains and a different one for hosting; if that is your setup, note which group this domain belongs to. A filled line could read: Domain: winterfeeders.example; Payment method: card ending 4417; Used for: this domain only; Last updated: 14 January. This is a made-up example, but it shows how a single row can answer the question “if this charge fails, what else is affected?” If the answer includes other domains, consider listing them in the same row so a later review does not miss them.

Before you plan any change, you can compare two candidate next actions and write down why you prefer one. Option one: leave the current method and set a reminder to review it in three months. Option two: update the method now and add a dated log line. Your reason for choosing might be “expiry date is close” or “I no longer use that card.” Neither choice is required; the point is to make the reasoning visible so a future you can pick up the thread.

Frequently asked questions

What headings should I give my short domain-facts note in my draft file?

His first concrete move is to write a short "domain facts" note in the same text file where he drafts posts. He gives it three headings: Identifier, Registrar and Account, and Dates.

What columns should I use when I build a tiny comparison table for the notice?

Next he builds a tiny comparison table with three columns: Notice details, My record, and Difference. In the Notice details row he copies only what the message states, such as the suffix and the month of expiry.

What can I add to my domain-facts note to record the expiration date as shown in my account?

Go back to your domain-facts note and add one line that records the expiration date exactly as it appears in your account, including the year and the time zone if one is shown.