To avoid losing access to your restaurant website, identify who controls your domain, who renews its SSL certificate, and how each renewal is paid for. Record the dates and account contacts in one place, then check that a current staff member can get into each account before a renewal is due.
The domain is your website address. The SSL certificate helps secure the connection between a visitor’s browser and your site. They are separate responsibilities, even if one provider handles both. An expired domain can make your address stop working; an expired certificate can trigger browser security warnings or prevent visitors from reaching the site normally. Either problem can interrupt a guest trying to find your menu or place an order.
Find the dates, accounts, and billing owners
Start with the domain registrar: the company where the domain is registered. Look for the registration expiration date, renewal setting, payment method, and account holder. A website designer or marketing agency may have purchased the domain for you, so the person who manages your site may not be the person receiving the renewal bill.
Next, identify the website host and the provider responsible for the SSL certificate. The host may manage the certificate, or it may be handled through another service. Ask each provider to name the account where renewal is configured and the person authorized to make changes. Do not assume a website subscription includes domain or certificate renewal without checking the agreement.
Collect these details for both the domain and certificate:
- The provider and account login location.
- The expiration date and whether automatic renewal is enabled.
- The billing contact and payment method on file.
- The person responsible for checking renewal and the backup.
- The support contact and recovery process if the account becomes inaccessible.
Compare the information in the account with invoices and emails. An old invoice can point you toward a provider, but it does not prove that the account is still active or that the same card will pay the next bill. If an agency controls an account, ask whether the restaurant can be added as an authorized contact and what happens if the agency relationship ends.
Renewal responsibility is only one part of control. For questions about who holds the domain account and what happens when you change providers, read the related domain ownership guide.
Use a renewal ownership tracker
A tracker should assign an action, not just list dates. The following is a hypothetical example for a restaurant whose domain and certificate are managed by different providers. The dates and roles illustrate a process, not a Fleksa setup.
| Item | Renewal arrangement | Owner and backup | Next check |
|---|---|---|---|
| Domain | Expires October 15; auto-renew is on; card billed by registrar | Owner checks billing; manager is backup | September 1: confirm card and renewal notice contacts |
| SSL certificate | Expires September 30; host says it renews automatically | Manager checks with host; owner is backup | September 1: confirm renewal status and support contact |
| Account recovery | Separate registrar and host logins | Owner maintains access; manager holds authorized backup access | September 1: verify both recovery contacts |
In this example, the certificate needs attention before the domain, even though both checks happen on the same day. The owner should not mark the whole website as “renewed” when only the domain payment succeeds. After each renewal, record the new expiration date and who confirmed it.
Keep the tracker somewhere the owner and designated backup can reach. It can be a shared document or a page in an operations binder. Do not put passwords, card numbers, or recovery codes in an ordinary shared spreadsheet. Store sensitive access information separately in a secure tool, and make sure the backup knows how to reach it under your restaurant’s access rules.
If you have several locations or addresses that redirect to one site, give each domain its own row. Include any address printed on menus or signs, even if it only forwards visitors to the main website. Ask the provider whether that forwarding depends on a separate service or certificate, and add any confirmed dependency to the tracker.
Check notices, recovery contacts, and certificate duties
Automatic renewal is useful, but it still needs a working payment method and a place to send notices. A card can expire, an employee can leave, and an agency inbox can go unattended. Review the renewal and billing email addresses in each account. Use contacts the restaurant controls or monitors, and give an authorized backup a way to receive or see important notices.
Also check the account recovery email and phone number. These can be different from the billing contact. Ask the person leaving a role or changing vendors to transfer access before their last day, rather than relying on an old mailbox later. If a provider requires identity checks or account-holder approval for recovery, learn what the restaurant would need to supply and keep those instructions accessible.
For the SSL certificate, ask a direct question: “Who notices a failed renewal, and who fixes it?” A provider may handle the technical renewal while the restaurant still has to maintain an account, payment method, or domain setting. Ask what notice you will receive, where to see the current expiration date, and whom to call if the renewal fails.
Also ask whether the certificate covers every address guests use, including the main domain and any alternate address. A valid certificate for one address does not necessarily establish that every other address is covered. If a separate ordering page uses another address, identify who is responsible for that page as well.
There is a trade-off between convenience and control. Letting an agency manage everything can reduce routine work, but it can leave the restaurant dependent on one contact. Managing every account yourself gives you more direct access, but also puts reminders and payment updates on your staff. Either arrangement can work if the duties, backup access, and handoff process are clear.
Set reminders and practice account access
Set a calendar reminder well ahead of each expiration date, with a second reminder closer to renewal. The first gives you time to update billing or resolve an access problem. The second prompts someone to verify that renewal actually happened. Assign both reminders to a named person and copy the backup; a calendar entry without an owner is easy to ignore.
Practice the access process before a deadline. The account owner can sign in to the registrar and host, locate the expiration and billing screens, and confirm the recovery contacts. The backup can verify their own authorized access. Record any obstacle and the provider’s support route, then resolve it while the site is working.
Keep this practice read-only. Do not change domain settings, disable automatic renewal, or deliberately interrupt the certificate. A simulated check does not need a real card payment, guest message, or courier dispatch. If you need to test a change, agree on a safe procedure with the provider first. A successful login shows that someone can reach the account; it does not prove that a future payment or technical renewal will succeed.
If a renewal has already failed, contact the responsible provider promptly. Ask for the current status, the steps to restore service, and whether any additional charges apply. Avoid making several unrelated configuration changes while the provider is diagnosing the problem. Once service is restored, update the tracker with the cause, the new dates, and the person responsible for preventing a repeat.
Changes to your restaurant website or online ordering setup are a good time to repeat these checks. Before moving providers, agree on who keeps the domain account, who handles the certificate, and when each party’s access ends. Confirm the handoff in writing and check the site after the change; do not assume a migration will be uninterrupted.
Next step: Use the tracker to check your current domain and certificate arrangements. If you are considering a new website or ordering setup, ask Fleksa about its restaurant website, including current US availability and who would handle your domain and certificate renewals.
Frequently asked questions
Does renewing my website subscription renew my domain?
Not necessarily. Check the agreement and the domain registrar account to see who bills for the domain and whether automatic renewal is active.
How can I tell who renews my SSL certificate?
Ask your website host or provider who manages the certificate, where its expiration date is shown, and who receives a failed-renewal notice. Record the answer and a backup contact.
What should I do if my domain renewal notice goes to a former employee?
Have an authorized account holder update the billing, notice, and recovery contacts with the registrar. Then verify that a current owner or designated backup can access the account.
