Old domains, dangling subdomains, and expiring certificates all fail without a sound. Here's how to find yours before someone else does.
------------------------------------------------------------------------------------------------------------------
TL;DR: Old web addresses don't stop working just because nobody's paying attention to them, and every so often they start working for a stranger. Once a lapsed domain clears its grace period, anyone can register it, and a subdomain still pointed at a canceled cloud service can be claimed by whoever sets up the same name. Expiring certificates bring their own headaches, and they're about to expire a lot more often as maximum lifetimes shrink toward 47 days by 2029. A basic inventory with a named owner, auto-renewal, and a regular cleanup heads off most of it.
------------------------------------------------------------------------------------------------------------------
Most companies have more domains than they think. There's the main website, sure, but also the one from the old company name, the campaign site from that trade show, the misspelling somebody bought just to be safe, and a handful of subdomains spun up for projects that wrapped years ago. They're cheap, they don't cause trouble, and so nobody thinks about them. Until somebody else does.
Think about what happens when you give up an old cell number. The carrier sits on it for a while, then hands it to someone new, and that person starts getting your car's service reminders, your kid's school alerts, and the occasional login code from an account you forgot to update. They didn't steal anything. They just picked up a number you weren't using anymore, and everything still pointed at it came along for the ride. Domains work almost exactly the same way.
And this isn't some fringe problem. When researchers at Palo Alto Networks' Unit 42 went looking, they turned up 317,000 hijackable "dangling" domains in a single month of data, including about 38,000 tied to some of the most-visited websites in the world. If big companies with full security teams lose track, a 40-person shop isn't exactly beating the odds.
The timing matters, too. Companies spin up and shut down cloud services faster than ever, and the rules for website certificates are changing in a way that'll make them expire far more often over the next few years. More moving parts, shorter lifespans, and the same one person keeping track of it all is a recipe for things falling through the cracks.
Nobody needs to become a DNS expert to fix this. It mostly comes down to knowing what you own, who's responsible for it, and what happens when you stop using something.
Table of Contents
- How Companies End Up With Domains Nobody Remembers
- What Happens When a Domain or Subdomain Gets Left Behind
- Lookalike Domains and the Email Problem
- Certificates Are About to Expire a Lot More Often
- A Domain Inventory You Can Start This Week
- Keep Track of Your Old Numbers
- Key Takeaways
- Frequently Asked Questions
How Companies End Up With Domains Nobody Remembers
Ask an owner how many domains the company has and you'll usually get a confident "one," then a pause, then "well, there's the old one too." The real number is almost always higher. A marketing agency registered a domain for a campaign and kept it in their account. A web developer built the site under his own login because it was faster than waiting on anyone else. The office manager bought the .net version during a rebrand and tied it to her email. Fast forward five years, and the agency's out of business, the developer moved to Arizona, and the office manager retired. The renewal notices for all three go to inboxes no one checks.
Subdomains are worse, because they're even easier to make. Spin up a customer portal, a help desk, a landing page for a promotion, or a test server for a week of troubleshooting, and each one gets a small DNS record pointing at a service somewhere else. When the project's over, somebody cancels the service. Hardly anyone deletes the record. That leftover record is where the trouble starts.
Most of this can be found by anyone who looks, and certificate logs make it even easier by listing every subdomain that's ever had a certificate.
To be fair to everyone involved, there's no villain here. Domains and DNS records don't show up on anybody's job description, so when people change roles or leave, the information goes with them. The domains don't care. They keep renewing or lapsing right on schedule, whether anyone's watching or not.
What Happens When a Domain or Subdomain Gets Left Behind
A domain doesn't vanish the day it expires. ICANN, the nonprofit that oversees domain names, requires registrars to send renewal reminders about a month out and again a week out. After expiration, there's a 30-day redemption window, plus about five more days before the name is released. After that, it's first-come, first-served. If those reminders are going to the guy who retired, the clock runs out, and nobody hears it ticking.
Whoever registers it next gets everything still aimed at it. That includes email sent to old addresses, password reset links for any account still tied to one of them, and old links from customer sites and search results. That's domain hijacking at its least dramatic. Nobody broke anything; they just bought a name you stopped paying for.
Subdomains have their own version, and it's sneakier. Microsoft lays out the pattern plainly. A company points a subdomain at a cloud service, later deletes the service but leaves the record in place, and an attacker sets up a service with the same name in their own account. Now your subdomain shows their content. They can even get a valid certificate for it, so the padlock appears and everything looks legit. Microsoft lists phishing, stolen login cookies, and, when a mail record is involved, intercepted email among the possible results.
REN-ISAC, a security group that serves colleges and universities, has seen attackers use taken-over subdomains to host spam pages that end up indexed under the victim's domain. There's nothing quite like having search engines vouch for junk with your name on it.
Lookalike Domains and the Email Problem
Not every domain problem involves something you used to own. Sometimes it's a domain you never owned that looks a lot like yours. Swap an "rn" for an "m," add a hyphen, change .com to .co, and you've got an address that survives a quick glance in a busy inbox. That's the raw material for the vendor fraud email from earlier in this series, where a "supplier" asks you to update their banking info from an address that's one character off.
You can't register every possible misspelling, and there's no point trying. Grabbing the two or three most obvious versions of your main domain is cheap insurance, though, and it keeps those particular names out of someone else's hands.
The bigger lever is making your real domain hard to fake, and three email settings handle that. SPF (Sender Policy Framework) lists which servers are allowed to send mail for your domain. DKIM (DomainKeys Identified Mail) adds a digital signature showing a message wasn't tampered with. DMARC (Domain-based Message Authentication, Reporting and Conformance) tells receiving servers what to do with mail that fails those checks, and sends you reports on who's trying to send as you. CISA (the Cybersecurity and Infrastructure Security Agency) and its federal partners recommend setting DMARC to "reject," so spoofed messages get turned away before they reach anyone's inbox.
None of that stops lookalikes, since those aren't your domain. What it does stop is someone sending mail as your exact address. Plenty of small businesses set up SPF and called it a day, or left DMARC on "do nothing" because somebody worried it would break the newsletter. That's understandable, and it's usually an afternoon's fix for someone who knows where to look.
Certificates Are About to Expire a Lot More Often
A website certificate is what puts the padlock in the browser and tells visitors they're on the real site. Certificates expire on purpose, which sounds like a design flaw until you hear the reasoning, and when one lapses, the site throws up a full-page warning that sends customers backing away slowly. Internal tools break, too. A payment portal, a remote access page, or a vendor integration can stop cold on a random weekday morning because a certificate ran out at midnight and nobody noticed.
For years, that came up about once a year per certificate, so plenty of companies handled renewals with a calendar reminder and good intentions. That's changing. The CA/Browser Forum, the industry group that sets the rules for publicly trusted certificates, voted in 2025 to shrink its maximum lifespan in stages. It dropped from 398 days to 200 in March 2026, falls to 100 days in March 2027, and lands at 47 days in March 2029. By the end of that schedule, a certificate managed by hand needs attention roughly every six weeks.
The logic behind it holds up; shorter lifespans limit the damage if a certificate's key is ever stolen or issued by mistake. Still, nobody's going to enjoy renewing certificates by hand every six weeks, and nobody should have to. Certificate expiration monitoring and automatic renewal stop being nice extras and become the only sane way to run things.
There's a security angle beyond outages, too. Every time staff clicks past a certificate warning on an internal site to get their work done, they get a little more comfortable clicking past warnings in general. That habit is exactly what makes a fake login page work.
A Domain Inventory You Can Start This Week
This doesn't require a security platform. It takes a spreadsheet and somebody stubborn enough to fill it in. Start with four columns and work your way across.
- Every domain the company pays for, including the old brand and the misspellings, with the renewal date next to each one.
- Which registrar holds it, which login controls it, and whose email gets the notices. If the answer is a former employee or an agency you stopped using, that's your first project.
- Every subdomain you can find, from your own DNS records and a certificate transparency search, plus what each one points to and whether that service still exists.
- Every certificate, when it expires, and whether it renews on its own.
Then make three changes. Turn on auto-renew for anything you intend to keep. Move registrar accounts under a company-owned login with multifactor authentication switched on. And turn on registrar lock, which blocks a domain from being transferred away without extra verification.
That last one matters more than it sounds. Some domain thefts never involve an expiration at all. Someone calls the registrar's support line, claims to be the account holder, and rattles off names and titles from your website until the rep resets access. That kind of phone-based con is a whole category on its own, and the next post in this series digs into how attackers use your org chart to pull it off.
Last, decide on purpose what to retire. Delete DNS records for services you've shut down, and only let an unneeded domain lapse once you're sure nothing still points at it.
Keep Track of Your Old Numbers
Domains, subdomains, and certificates all tend to fail the same way, slowly and without anyone noticing. A domain registered by an agency or a former employee lapses after the reminders go to a dead inbox, and whoever buys it next inherits your old email and links. A subdomain left pointing at a canceled cloud service gets claimed by someone else, with a valid certificate and all. Lookalike domains feed vendor fraud, while loose email settings let people send as your real address. And certificates, which used to need attention once a year, are headed toward a 47-day lifespan that no calendar reminder will keep up with.
For a lot of owners, the frustrating part is that nobody ever handed them a list. The registrar login is in somebody's old email, the DNS records were set up by a developer who's long gone, and the first sign of trouble is a customer asking why your website says it isn't secure.
CNWR handles this kind of housekeeping as part of running IT properly. That means knowing which domains and records a company has, keeping certificates renewing on schedule, getting SPF, DKIM, and DMARC configured so your domain is hard to impersonate, and clearing out records for services that are long gone. It isn't flashy work, but it's the kind that keeps a stranger's page from showing up under your name.
If you're not sure how many domains your company owns or who controls them, connect with CNWR and schedule a call. Carriers recycle old phone numbers every day, and the internet recycles old domains the same way, so make sure yours aren't on the list.
Key Takeaways
- Domains and subdomains keep working after people forget about them, and anyone can claim one that's left behind.
- An expired domain opens up to the public roughly 35 days after it lapses.
- Deleting a cloud service without deleting its DNS record invites a subdomain takeover.
- SPF, DKIM, and DMARC make your real domain much harder to spoof.
- Certificate lifetimes are shrinking to 47 days, so renewals need to run automatically.
- A simple inventory and company-owned registrar accounts prevent most of these problems.
Frequently Asked Questions
1. What happens to email when a domain expires?
Mail sent to that domain stops reaching you, and once someone else registers it, it starts reaching them. That can include customer messages, vendor invoices, and password reset links for any accounts still tied to those addresses. Before letting a domain go, update every account that uses it and give it plenty of time, since some old contacts never get the memo.
2. Should we buy common misspellings of our domain?
The two or three most obvious ones, yes; every possible typo, no. A handful of close variations is cheap and keeps those specific names away from scammers, but there are endless ways to misspell a domain, and buying them all turns into an expensive hobby. Strong email authentication on your real domain does more good than a pile of misspellings.
3. Who should own our domain registrar account?
The company should, through a login tied to a shared business account rather than one person's email. Turn on multifactor authentication, keep at least two people with access, and make sure renewal notices go to an address someone checks. An agency or developer can manage it day to day, but ownership shouldn't leave with them when the relationship ends.
