You shut down an old website. The hosting is cancelled, the files are deleted, and as far as you’re concerned, the site no longer exists.
But months later, someone clicks one of its old URLs.
Will the redirect still work?
It can. A redirect doesn’t actually need the original website to stay online. What matters is where the redirect itself is being handled.
And that’s an important thing to check before you switch anything off.
Where does the redirect actually live?
A redirect might feel like part of a URL, but something still needs to receive the request and tell the browser where to go next.
If your redirects are configured inside your old hosting account, web server, or CMS, they depend on that infrastructure staying available.
Imagine you have:
oldbrand.com/pricing → newbrand.com/plans
The redirect works perfectly while the old hosting is active. Then you cancel the hosting.
Someone visits /pricing, but there’s no longer anything there to receive the request and return the redirect. The rule may still exist in an old configuration somewhere, but the infrastructure responsible for running it is gone.
The redirect goes with it.
The old website and the redirect are two different things
The good news is that the website itself doesn’t need to stay online.
A browser visiting oldbrand.com/pricing doesn’t need the old page to load first and then send it somewhere else. It only needs something at oldbrand.com to respond with the redirect.
That means you can remove the website while keeping a separate redirect layer running.
The flow can be as simple as:
oldbrand.com/pricing → redirect infrastructure → newbrand.com/plans
No old website in the middle.
This is particularly useful after a website migration or rebrand. There’s little reason to keep an entire old site running just because people might still visit its URLs.
You still need to keep the old domain
Removing the website is one thing. Giving up the domain is another.
If you want URLs on oldbrand.com to keep redirecting, you need to keep control of oldbrand.com.
That usually means continuing to renew the domain and keeping control of its DNS settings.
Once you stop owning the domain, you can no longer decide where requests to it should go. If someone else registers it later, they control what happens there.
So after a rebrand, you may be able to cancel the old hosting completely, but the old domain can still be worth keeping for years.
Backlinks, bookmarks, old emails, documents, social posts, and search results can continue sending people to it long after the original website has disappeared.
Move the redirects before cancelling your hosting
If your current redirects depend on the old website or hosting, move them somewhere else before shutting that infrastructure down.
A simple process looks like this:
Identify the old URLs that still need to redirect.
Decide where each one should lead.
Move those redirects to infrastructure that doesn’t depend on the old website.
Point the old domain’s DNS toward that infrastructure.
Test the old domain and important individual URLs.
Check that HTTPS versions work too.
Only then cancel the old hosting.
Don’t test just the homepage.
If you have redirects for /pricing, /about, /blog/article-name, or other important paths, open those old URLs directly and make sure each one reaches the destination you expect.
It’s much easier to fix a missing rule while you still have access to the old setup.
This is where Redirect Supply comes in
Redirect Supply is designed to handle redirects separately from the website itself.
You add the old domain to Redirect Supply and add the generated DNS records at your DNS provider. Once the domain has been verified automatically and its status changes from Pending to Connected, Redirect Supply can start handling requests for it.
You can then create rules such as:
oldbrand.com → newbrand.com
or:
oldbrand.com/pricing → newbrand.com/plans
Requests are handled through Cloudflare’s edge network, so the old hosting doesn’t need to stay involved.
The website can disappear. The redirect layer stays.
What if the old website is already gone?
If you’ve already cancelled the hosting, you may still be able to restore the redirects without bringing the old website back.
The important question is whether you still control the domain.
If you do, you can point its DNS toward new redirect infrastructure and recreate the rules there. You don’t need to rebuild the old site just to make its URLs work again.
If you no longer control the domain, the situation is different. You can’t create redirects for URLs on a domain you don’t control.
That’s why domain ownership is worth checking before shutting down an old website or letting an old domain expire.
Your redirects can outlive your website
A website might last a few years. Some of its URLs can stay in circulation much longer.
That’s why redirects are worth treating as something separate from the website they originally belonged to.
Before removing an old site, find out where its redirects are being handled. If they depend on infrastructure you’re about to cancel, move them first. Keep control of the old domain, test the important URLs, and then let the website go.
Redirect Supply gives those redirects somewhere to live after the original website is gone.
Your old site doesn’t need to stay online just to keep its old URLs useful.
