Domain expiration can lead to website downtime or loss of ownership. This article outlines simple, repeatable steps to verify your domain's status and ensure it remains active.
Assessing Your Current Renewal Status
Imagine a hypothetical independent publisher who has inherited a small portfolio of project domains and now wants a plain-language checklist for checking renewal status before anything lapses. Her working materials are a notebook page headed “Renewal Status Review,” a printout of her registrar dashboard, and a one-page domain list she maintains herself. The list has three columns: name as she writes it, registrar account label, and next renewal month. Two fictional rows show how she sorts them. The first row is “maple-draft-notes.example | account A | 11 March.” The second is “river-archive-index.example | account B | 02 August.” These are her own shorthand entries for an internal page, not confirmed registration dates or a claim that any outside system accepts those names. A third candidate shows a deliberate naming choice: she labels one line “maple-draft-notes-renewal-reminder” rather than a shorter alias, because the longer label tells her at a glance which project the reminder belongs to. That is the trade-off she records for this review: a longer, more descriptive internal label is easier to match to the right notebook page, even if a shorter alias would fit on one line.
For the checklist itself, she writes four concrete fields under the heading “Check on each account.” The first is “Dashboard renewal date,” with a line for the date shown on the registrar page. The second is “Auto-renew setting,” with two boxes, “on” and “off,” so she can note the current state without deciding yet whether to change it. The third is “Contact email on account,” where she copies the address she believes is attached to the account, because a stale address could mean missing a notice. The fourth is “Last verified,” with a date she fills in herself. A short example record demonstrates how the fields fit together: “maple-draft-notes.example | dashboard date 11 March | auto-renew off | contact email saved in notebook | last verified 14 February.” The second record follows the same layout: “river-archive-index.example | dashboard date 02 August | auto-renew on | contact email saved in notebook | last verified 03 July.” These are invented examples for explaining the layout, not screenshots or verified account details.
She also keeps a separate “discrepancy log” line for any mismatch between the dashboard date and her notebook month. If, for instance, the dashboard shows a different month than her list, she writes both entries side by side and marks the line “needs review” rather than guessing which one is right. That log is a note-taking aid, not proof of a registrar error. The purpose of this exercise is to make the current status visible and easy to compare later, while leaving the actual account checks and any renewal decisions for the next stage.
Locating Expiration Dates in Your Account
The cited official guide places expiration information inside the account area: after signing in, open the domain management console to view a domain's expiration time. The same console lists renewal or redemption, transfer-out, and DNS record changes as separate actions, so locating the date does not itself renew anything.1
For advance notice, the guide says a frequently used and valid email matters because expiry reminders are sent to the registered email address. This is presented as part of registration information upkeep, not as a guarantee of when a reminder arrives.1
You can start with one plain text file or notebook page that lists every domain you own, and beside each name jot where you last saw its expiration date: the account dashboard, a renewal notice, or only a memory of the signup email. That first pass does not need to be tidy; its purpose is to show which dates you can actually point to and which you are assuming.
For each domain, you might record the date exactly as it appears, the account or folder where you found it, and the month you last opened that page. If two places disagree, keep both versions side by side rather than choosing one. A dashboard line reading “expires 14 March” and a notebook note reading “renews in March” look similar but answer different questions, so the wording is worth copying as-is. Consider adding a short note on whether the date refers to the registration term ending or to an automatic renewal attempt.
If a domain appears only in an old confirmation email, you can mark it as unverified and leave the date field blank rather than guessing. That blank is useful: it tells you which names need a fresh look inside the account before you plan any reminder. Names registered through a separate profile or a colleague’s login deserve their own row, even if the domain name looks familiar.
You might also separate domains you intend to keep from those you are letting lapse, because the two groups call for different attention when you revisit the list. The file can stay simple: one row per domain, with columns for the name, the date seen, where it was seen, and the date you last checked. Filling in the last column is the habit that keeps the rest honest.
Setting Up Manual Check Reminders
Log in to your NamesLink account and open the domain management console, where you can check each domain's expiration date. Cross-check those dates against your own calendar or reminder list and set manual reminders well ahead of each expiration date.1
Verifying Contact Information Accuracy
Contact details should stay accurate because the cited official guide states that untrue or incomplete registration information may lead to a domain being suspended or deleted. During registration, it lists holder name or organization, email address, phone number, and full address (country, region, city, street, postal code) as the required details.1
The guide also places email validity under registration notes: reminders about domain expiration and transfer authorization codes are sent to the registered email address, so it recommends an address that is commonly used and valid.1
For contact accuracy, you can begin with the same notebook page or text file rather than a new system: take one domain from your list and copy the contact email and postal address exactly as they appear in the account record. Beside each copy, note the date you last checked it and the page where you saw it. You might add a third line for anything that looks stale, such as an address tied to an old office or an email you no longer read regularly.
To see how this works on a specific entry, suppose your notes list a project domain with an admin email ending in a former employer's host and a postal address from an old shared workspace. You could write the entry as: contact email, recorded as seen; postal address, marked as questionable; next step, consider whether the account holder still reads that mailbox. Nothing needs to be changed yet; the record simply shows which contact details deserve a second look before you rely on them for renewal notices.
When you revisit a contact, you might compare the email and address you recorded against the account page again and note any difference. For example, if the email field now shows a different mailbox from your earlier copy, you can add a short line reading “email changed since last check,” with both versions side by side. A blank or uncertain field is worth keeping visible rather than filling with a guess, since it tells you where to look next.
It also helps to note which contact route you actually monitor, such as a mailbox you open weekly, and which addresses you can no longer access. You can mark these as “read,” “forwarded,” or “unknown” for your own reference, then decide later whether to update the account record. Keeping the original text alongside your label lets you see what changed and when you first noticed it.
Reviewing Auto-Renewal Settings
To review auto-renewal settings, log in to your Porkbun account and reach the Domain Management screen; if already logged in, select ACCOUNT in the top-right corner and then Domain Management. Locate the domain and click the refresh/recycle icon to the right of the domain name under the RENEW column. A menu opens with sections labeled Auto Renewal and Manual Renewals. The page states that renewal happens automatically as the expiration date approaches only when a credit card is on file and auto-renew is turned on for that domain.2
Before you rely on any renewal assurance, take one domain from your list and open the account page where its auto-renewal setting should appear. Note two things in your own file: whether the toggle is on or off, and the exact date the dashboard shows for the next renewal. If you cannot find the setting at all, write “not located” rather than assuming it is enabled.
You might then compare that dashboard date with the date in an old confirmation email or your earlier notes. Suppose the account shows next renewal in March while an older receipt mentions January; record both lines, side by side, without deciding yet which is right. That mismatch is itself a useful flag: it tells you which entry deserves a second look before you treat the setting as settled.
Consider adding a short field for what the renewal depends on. For a domain you intend to keep, you could jot “card ending 1234, expiring 06/26” or “payment method removed last year.” This is a note to yourself, not a promise that the charge will succeed; it simply reminds you to check the payment route as well as the toggle.
For each entry, you can also mark one of three plain states: “on and confirmed,” “off,” or “unclear.” Keep the unclear group small by revisiting one entry at a time, and date each revisit. If you prefer, leave a line for the next check so the list does not quietly go stale.
Finally, decide how you will treat the confidence level you recorded. A “confirmed on” entry may need only a calendar reminder; an “unclear” or mismatched entry may deserve a follow-up question to the registrar before the renewal month approaches. You can choose the follow-up route that suits you, but writing the choice beside the entry keeps the decision visible when you return to it.
Finalizing Your Maintenance Schedule
You can now turn the notebook entries you have gathered into a maintenance schedule by choosing a review rhythm that fits how often you actually open each account. Consider starting with the domains marked “unclear” or with a mismatch between dashboard and notebook, because those entries need a nearer review date than the ones marked “on and confirmed.” You might assign each domain a review month—say March, July, and November—and write that month beside the entry, then set a single reminder for the earliest one. The choice of three or four reviews a year is yours; the point is that every entry gets a named month rather than a vague “check later.”
When you write the schedule, keep the fields small enough that you will actually fill them. A workable line might read: domain name, review month, current state, who to contact if something looks wrong. For one hypothetical entry you could write “project-site, July, unclear, check dashboard first.” For another: “portfolio-name, November, on and confirmed, no action unless reminder.” If a domain is one you are letting lapse, you might give it its own short line stating the month you will stop renewing and the month you will remove it from the list, so the decision stays deliberate instead of accidental.
You can also decide in advance what “done” looks like for each review. For a confirmed entry, done might mean you opened the account page, saw the same renewal date, and left the line unchanged. For an unclear entry, done might mean you replaced “unclear” with either “on” or “off” and wrote the date you checked. If an entry stays unclear after one review, consider moving its next review month forward rather than leaving it at the back of the list. Recording the outcome of each review, even as a single word, gives you a trail you can compare next time.
Finally, you might choose a place to keep the schedule that you already visit: the same notebook page, a pinned note, or a folder you open weekly. The schedule does not need to be elaborate; it needs a home you will return to. Before you close this task, pick the first review month from your list and note what you will open when that month arrives. That single dated line is the schedule beginning to work.
Frequently asked questions
How can I start recording the domains I own and where I last saw each expiration date?
You can start with one plain text file or notebook page that lists every domain you own, and beside each name jot where you last saw its expiration date: the account dashboard, a renewal notice, or only a memory of the signup email.
What should I write down for each domain when recording its expiration date and where I found it?
For each domain, you might record the date exactly as it appears, the account or folder where you found it, and the month you last opened that page. If two places disagree, keep both versions side by side rather than choosing one.
What should I do if a domain appears only in an old confirmation email and I don't have a verified date?
If a domain appears only in an old confirmation email, you can mark it as unverified and leave the date field blank rather than guessing. That blank is useful: it tells you which names need a fresh look inside the account before you plan any reminder.
How to Renew Domain Names - Porkbun Knowledge Base . Retrieved 2026-11-19. ↩︎