Web Development Company in Pune: Domain, DNS and SSL Renewals — How to Stop Your Website Going Down for Reasons That Have Nothing to Do With Code

Web Development Company in Pune: Domain, DNS and SSL Renewals — How to Stop Your Website Going Down for Reasons That Have Nothing to Do With Code

The most common reasons a business website suddenly disappears are not hacks or bad code; they are a lapsed domain registration, a changed DNS record or an expired SSL certificate. All three are administrative, all three are preventable, and all three tend to be owned by someone who left the company years ago. A good web development company in Pune will ask three questions in the first week of any project: who owns the domain, who controls the DNS, and who is notified when the certificate is about to expire. If you cannot answer those today, this guide shows you how to find out and how to fix the gaps.

You do not need to be technical. You need a one-page register of what you own, where it lives and when it renews, plus a few automatic safeguards. The rest of this article explains the three moving parts in plain language, the failure stories we see most often, a monthly and yearly routine, and what to put in a contract so a developer or agency cannot accidentally become the single point of failure.

The three things that keep a website reachable

Think of your website as a shop. The domain name is the shop's registered address, DNS is the signboard that tells visitors which building to walk into, and the SSL certificate is the licence on the wall that tells visitors the shop is who it says it is. If the address registration lapses, DNS stops working. If DNS is wrong, visitors arrive at the wrong building or at none. If the certificate expires, browsers show a full-screen warning that most customers will not click through.

The domain name (registration)

A domain such as yourbusiness.com or yourbusiness.in is rented, not bought. You pay a registrar for a registration period, usually one to ten years, and the registration must be renewed before it ends. The person or company listed as the registrant is the legal holder of that domain. If your developer registered it in their own name "to save you the hassle", they, not you, are the holder.

DNS (the directory)

The Domain Name System turns a name into instructions: which server hosts the website, which service receives email, and which third-party tools are verified for your domain. These instructions are stored as records. The ones a business owner should recognise are:

• A and AAAA records, which point the domain to a web server's address.
• CNAME records, which point one name at another, often used for the "www" version or for services such as a store platform.
• MX records, which decide where email is delivered.
• TXT records, used for ownership verification and for email authentication (SPF, DKIM, DMARC).
• CAA records, an optional record that states which certificate authorities may issue certificates for your domain.

DNS is usually hosted by your registrar, your web host, or a separate provider. Where it lives matters, because that is the one place where a mistake can take down both website and email at the same moment.

The SSL/TLS certificate

The certificate lets the browser connect over HTTPS. It is issued for a limited period and must be renewed. Many hosts renew it automatically; some do not, and some automatic renewals fail silently when DNS or server settings change. When a certificate expires, browsers show a security warning and most visitors leave. Search Console, ad platforms and payment pages can also behave badly in the meantime.

Why this goes wrong so often

None of this is hard, but it falls between roles. The marketing manager thinks IT handles it. IT thinks the agency handles it. The agency thinks the client paid for the domain. The invoice goes to an email address nobody checks. Nothing breaks for twelve months, and then on the day of a campaign launch the site does not load.

These are the patterns we see repeatedly on Indian business and NGO sites:

• The domain is registered under a founder's personal email, and that person has changed jobs or the mailbox no longer exists.
• The developer or a former agency is the registrant, so the company cannot transfer or renew without their cooperation.
• Renewal reminders go to a spam folder, or to an address on the very domain that has just expired, so nobody ever sees them.
• A card on file has expired, so "auto-renew" is switched on but the charge fails.
• A DNS change for one purpose breaks another: someone edits records to verify a tool and accidentally deletes the MX records, and company email stops.
• A certificate was installed by hand once and never renewed, because no automation was ever set up.
• Nobody knows where DNS is hosted, because the nameservers were changed during a past migration.

If you recognise more than one of these, you are in good company. The fix is organisational first and technical second.

Step 1: Find out who owns what

Spend thirty minutes on this. You are building a register with five facts per domain.

Look up the registrar and registrant

Use a public lookup service (a WHOIS or RDAP lookup is available from your registry or from ICANN's lookup tool) and search your domain. You will normally see the registrar, the creation and expiry dates and the nameservers. Contact details may be hidden behind a privacy service, which is fine, but the registrar account itself must be one you can log in to.

Then ask your developer or whoever set up the site for the answers to these questions in writing:

• Which registrar holds the domain, and what email address is the account under?
• Who is the registrant organisation or person?
• Is the domain set to auto-renew, and which payment method is attached?
• Where are the nameservers pointing, and who can log in there?
• Which other domains and subdomains do you own, such as old campaign sites, regional versions or typo variants?

Make the company the registrant

The registrant should be your legal entity, with an administrative contact that is a role-based address (for example domains@yourcompany) forwarding to two or more people, not one individual. If the domain is currently in someone else's name, ask for it to be transferred or for the registrant details to be updated. Changing registrant details or transferring between registrars may trigger a temporary transfer lock under registrar policy, so do not plan this for the week of a launch. Your registrar's help pages explain the rules that apply to your domain extension.

Check the account recovery path

For each account (registrar, DNS host, web host, certificate provider if separate), write down the login email, whether two-factor authentication is on, and who holds the recovery method. If the only recovery phone number belongs to a former employee, fix it now.

Step 2: Build a one-page asset register

A spreadsheet with the following columns is enough. Keep it somewhere the business owns, such as a shared drive, and store passwords in a password manager rather than in the sheet.

Review it every quarter. It is also exactly the document a new developer, agency or auditor will ask for, so it pays for itself. We make the same point in our website handover and ownership checklist, because handovers are the moment when this information most often gets lost.

Step 3: Make domain renewal boring

The aim is that renewal happens without anyone remembering it.

• Turn on auto-renew at the registrar, and attach a payment method that is not about to expire. A company card tied to one person's employment is a risk; use a method owned by the company.
• Renew for several years if your budget allows. Longer registrations reduce the number of renewal events that can fail. This is a decision about cash flow, not about search rankings, and you should not expect any ranking benefit from it.
• Add two or more reminder recipients, including a shared mailbox on a different domain from the one being renewed.
• Keep a calendar reminder 60 days before expiry as a backstop to the registrar's emails.
• Do not let the domain drift into grace periods. After expiry, many registries hold a domain for a period during which only the existing holder can renew, usually at a higher cost, before it is released. Rules differ by extension, so check your registrar's policy. A site can go down on day one of expiry even though the domain is technically still recoverable.
• Enable the registrar's transfer lock so the domain cannot be moved without an authorisation step.

Domains for campaigns and old projects

Old microsites are a hidden risk. A forgotten domain that expires can be registered by someone else, and any links, emails or QR codes still pointing at it then lead to a stranger's page. Either keep every domain you have printed or published, or redirect and retire it deliberately.

Step 4: Treat DNS as a controlled document

DNS errors are quiet and total. A single mistyped record can break email for an entire company, and nothing shows an error until the first customer complains.

Know where DNS is edited

There should be exactly one place where your authoritative DNS is edited. Your registrar's nameserver settings will tell you where. If the nameservers point to your host or to a separate DNS provider, that is where changes must be made, and changes made at the registrar's own DNS panel will have no effect.

Back up the records before every change

Export or screenshot the full record list before touching anything, and paste it into the asset register. Almost every DNS recovery we have seen was a matter of putting back what was there before.

Change one thing at a time, and lower the TTL first

Each record has a TTL (time to live), which is how long other systems may cache it. If you are going to change a record, such as moving a site to a new host, lower the TTL a day in advance so that the change takes effect quickly and can be reversed quickly. After the change is stable, raise it again.

Protect email records

Email problems are often DNS problems. When you add or change a mailing tool, you may be asked to add TXT records for SPF, DKIM or DMARC. Add to the existing SPF record rather than creating a second one, since a domain should have only one SPF record. Our guide to SPF, DKIM and DMARC for business email covers this in more depth.

Consider a CAA record

A CAA record is optional, but it lets you state which certificate authorities are permitted to issue certificates for your domain. It is a small hardening step. Only add it if you know which authority your host uses, otherwise you can block your own renewals.

Step 5: SSL certificates without surprises

Know how your certificate is issued

There are three common arrangements:

1. Issued and renewed by your host (many managed WordPress hosts, store platforms and CDNs do this). Check that the dashboard shows renewal as automatic and the date of the last renewal.
2. Issued by a free certificate authority through an automated tool on your server. Free certificates are short-lived by design, which is why automation matters. If the renewal task stops running because of a server change, the certificate will lapse without warning.
3. Bought manually and installed by hand. This is the highest-risk arrangement, because a person must remember to repeat the process.

Certificate lifetimes are getting shorter

The browser and certificate-authority industry has agreed to reduce the maximum lifetime of public certificates in stages, with the first reduction taking effect in March 2026 and further reductions scheduled for the following years (see the CA/Browser Forum's ballot SC-081 for the schedule). The practical consequence is that a manually installed certificate that used to be a yearly chore will become a much more frequent one. If your site depends on someone remembering to install a certificate, now is the time to move to automated renewal.

Check it yourself

You do not have to wait for a warning. Click the padlock icon in your browser's address bar and view the certificate details to see its expiry date. A developer can also check from the command line. This example reads the dates from a live site:

echo | openssl s_client -connect yourdomain.com:443 -servername yourdomain.com 2>/dev/null | openssl x509 -noout -dates

Run it for every public hostname, including "www", subdomains for your store or donation page, and any regional or campaign domains.

Watch for mixed content and redirects after a change

After a certificate is renewed or replaced, load a few key pages and check for the padlock, make sure the plain-HTTP address redirects to HTTPS, and confirm there is no mixed-content warning. If you use HSTS, a mistake can lock visitors out of the site entirely, so read our guide to HTTP security headers and HSTS before enabling it.

Step 6: Add monitoring so you hear about it first

Automation reduces the chance of failure, and monitoring tells you if it fails anyway. For most business sites, a small set of checks is enough:

• Uptime monitoring that loads your home page and a few key pages every few minutes and alerts two people by email or WhatsApp.
• Certificate expiry monitoring, which many uptime tools include, alerting you 30, 14 and 7 days before expiry.
• Domain expiry monitoring, alerting you 90, 60 and 30 days before expiry.
• DNS change alerts, available from some DNS providers, so unexpected edits are noticed.
• Google Search Console and Google Ads emails going to a monitored mailbox, because they often flag certificate and site-access problems first.

Test that the alerts actually arrive. An alert that goes to a dead inbox is worse than none because it gives false confidence.

A realistic example (hypothetical)

Consider a Pune services company whose site was built six years ago by a freelancer. The domain is registered under the freelancer's email, hosting is paid by the company, and the certificate is a free one installed with a scheduled task on the old server.

Nothing is wrong until the company moves hosts for speed reasons. The new host's team copies the site files and points DNS at the new server but does not recreate the scheduled certificate task. Ninety days later, the certificate lapses on a Friday evening, and Monday's enquiries drop to zero. Meanwhile the registrar's renewal email goes to the freelancer, who has moved to another city.

None of those failures is dramatic, but together they cost days. The fix would have been four things done once: moving the registrant to the company, enabling automatic renewal on a company-owned card, using host-managed certificates, and adding uptime and expiry alerts. This is a composite scenario for illustration, not a client case.

What to put in your contract or handover document

When you appoint or change a developer, agency or hosting provider, ask for the following in writing:

• The domain is registered in the client's legal name and the client holds the registrar login.
• The agency may be given delegated access, but the client can revoke it.
• DNS access is documented, with a named person on the client's side.
• Certificate renewal is automated, and the method is described.
• A renewals calendar is part of the handover document, listing domain, hosting, certificate and any paid third-party services.
• Handover includes an export of all DNS records.
• A named person is responsible for responding to expiry alerts, and there is an escalation contact.

If you are interviewing a web development company in Pune, these questions also reveal a lot. A team that answers them clearly has done this before; a team that is vague is telling you something. Our broader guide to what a website maintenance plan should include lists the other recurring tasks worth confirming.

Common mistakes to avoid

• Letting the web host register the domain on your behalf without confirming you are the registrant.
• Using a single personal email address as the registrar contact.
• Moving nameservers during a redesign without exporting existing records.
• Turning on auto-renew but never checking whether the card on file is valid.
• Assuming the host renews certificates for every subdomain.
• Making DNS edits late on a Friday with no export and no TTL planning.
• Keeping passwords in a chat group rather than a password manager.

A simple yearly and quarterly routine

Quarterly (about thirty minutes):

• Open the asset register and confirm every date is still correct.
• Check expiry dates for domains and certificates against the live source.
• Confirm payment methods are valid.
• Confirm alerts reach the right people.
• Review who has access to registrar, DNS and host accounts and remove anyone who has left.

Yearly:

• Review every domain you own and decide whether to keep it.
• Update the register with any changes to hosting, CDN or email providers.
• Check that registrant details still match your registered business details.
• Run a recovery drill: could a new person restore access to every account using only the register and the company's password manager?

Frequently Asked Questions

What happens if my domain expires?

Your website and email stop working once the registration lapses and DNS records are removed or parked. Many registries then offer a limited period in which the existing holder can still renew, often with extra fees, before the domain is released for anyone to register. Rules vary by extension and registrar, so check yours and renew well before the date.

Who should be the registrant of my business domain?

Your company or organisation, not a developer, agency or individual employee. The registrar account should use a role-based email address monitored by more than one person, so the domain does not depend on a single mailbox.

How do I know when my SSL certificate expires?

Click the padlock in your browser's address bar and view the certificate details, or use an uptime monitoring tool that checks certificate expiry and alerts you 30, 14 and 7 days beforehand. Your host's control panel may also show the date and whether renewal is automatic.

Can a DNS change break my email?

Yes. Email delivery depends on MX records, and authentication depends on SPF, DKIM and DMARC TXT records. Deleting or overwriting them while editing DNS for something else can stop email being delivered or send it to spam. Export your full record list before any change and edit one record at a time.

Is it better to let my web host manage my domain?

It is convenient but risky if the host registers it in its own name or you cannot log in to the registrar account. A host can manage renewals on your behalf, provided you are the registrant, you have access, and you can transfer the domain away if you need to.

Sources: ICANN Lookup (registration data), CA/Browser Forum: Ballot SC-081 on certificate validity, Let's Encrypt: Documentation on certificate renewal, web.dev: Security and HTTPS. Specific renewal, grace-period and transfer rules depend on your registrar and domain extension; confirm them in your registrar's current policy pages. TODO: confirm the current CA/Browser Forum validity schedule against the Forum's published ballot text before relying on exact dates.

Working with Govindani Infotech on domain, DNS and certificate hygiene

Govindani Infotech is a Pune-based website design and development company at 2nd Floor, Landmark Plaza, 206 Satara Road, Parvati Paytha, Pune 411009. When we hand over a project we include a written list of the domain, DNS and certificate arrangements so that the client holds the keys, and we are glad to review an existing site's setup in the same way.

If you are not sure who owns your domain or when your certificate lapses, send us the domain name on WhatsApp at wa.me/919201958278 or through our contact page, and we will tell you what a short review would cover before any price is discussed. You can also see how we approach site builds on our website creation page.

About the author: written by the Govindani Infotech web development team in Pune, drawing on our experience handing over business, e-commerce and NGO websites.