Use HTTP 410 if you want a website to disappear cleanly. Remove DNS only when you truly do not care about users, search engines, old links, email, or a tidy goodbye. A 410 status says, “This page is gone on purpose,” while DNS removal says, “Nobody is answering the door.” Google treats 404 and 410 as signals that a page should leave search results over time [source: Google Search Central].
TLDR: If you are retiring a website forever, keep the domain alive and serve HTTP 410 Gone for at least a few months. For example, if a small site has 1,200 indexed URLs, a 410 plan gives search engines a clear “delete this” signal for each URL. If analytics show that 62% of traffic still comes from old Google results, DNS removal will confuse people and bots. Use DNS removal only after traffic is near zero, email is moved, and you are done being polite.
DNS Removal vs HTTP 410: The Simple Version
Think of your website as a shop.
- DNS removal is like removing the street address from every map.
- HTTP 410 is like putting a sign on the door that says, “Closed forever. Thanks.”
Both can stop people from seeing the old site. But they do it in very different ways.
DNS is the system that turns example.com into a server address. If you remove DNS records, browsers cannot find the server. Visitors may see errors like “site can’t be reached”. Search engines may see connection failures. That is messy.
HTTP 410 is different. The server still answers. It just answers with a clear status code: Gone. That is much cleaner.
What HTTP 410 Actually Means
HTTP 410 Gone means the page used to exist, but it has been removed forever. Not moved. Not broken. Gone.
That matters because search engines love clear signals. A 404 says, “Not found.” Maybe it is a mistake. Maybe it will come back. A 410 says, “Nope. We meant this.” MDN describes 410 as a permanent removal signal [source: MDN].
Use it when:
- You are shutting down the whole website.
- You are deleting old product pages forever.
- You are retiring a blog, app, or campaign site.
- You do not have a useful replacement page.
Do not use it when:
- The content moved to a new URL.
- You want to keep ranking signals.
- You have a better page to send users to.
- The page is only gone for a short time.
In those cases, use a 301 redirect instead.
When DNS Removal Makes Sense
DNS removal is blunt. Like using a toaster to flatten a spider. It works, but wow.
It can make sense when the website has no value left. No traffic. No links. No email. No search presence. No customers typing the address from an old invoice. If the domain was used for a one week joke project in 2017, fine. Pull the plug.
But be careful. Removing DNS can break more than the website.
- Email may stop working if you remove MX records.
- Subdomains may die, including docs, apps, or support areas.
- APIs may fail if old software still calls them.
- Search engines get vague errors, not a clean retirement signal.
- Users get ugly browser errors, not a helpful message.
Honestly, it feels like the web version of ghosting. Fast, yes. Classy, no.
The Best Plan for Retiring a Website
The clean shutdown plan is simple.
- Back up the site. Save files, databases, images, logs, and invoices.
- Export analytics. Keep traffic history before the tool goes dark.
- Check email. Move mailboxes and keep MX records if needed.
- Set HTTP 410 on old URLs. Do this sitewide if the whole site is dead.
- Keep the domain renewed. Do not let someone else grab it.
- Watch logs for 30 to 90 days. See who still visits.
- Remove DNS later, only when you are sure.
That last point saves headaches. Expect to waste time on forgotten tools. Old CRMs love calling dead endpoints at 2:13 a.m. for no good reason.
How to Serve 410 for a Whole Website
You do not need a huge setup. You need a server that answers every request with 410.
Apache example
RewriteEngine On
RewriteRule ^ - [G,L]This tells Apache to return 410 Gone for all paths.
Nginx example
server {
listen 80;
server_name example.com www.example.com;
return 410;
}If you use HTTPS, keep the certificate working. Otherwise browsers may show a certificate warning before the 410. That is annoying. It adds one more scary screen users do not need.
Cloudflare Worker style idea
return new Response("This website has been permanently retired.", {
status: 410,
headers: { "content-type": "text/plain" }
});You can also serve a tiny HTML page with a friendly message. Keep it short.
Example:
This website has been permanently retired. Thank you for visiting. If you need help, contact support@example.com.
Should You Show a Goodbye Page?
Yes, if real people still visit.
A plain 410 works for bots. A human may need context. So you can return 410 and still show a small goodbye page. The status code is for machines. The message is for people.
Good goodbye page text includes:
- What happened.
- When it happened.
- Where to go next, if anywhere.
- A support email, if still active.
Bad goodbye page text includes a 900 word diary about company strategy. Nobody wants that. They came for an old recipe, invoice, PDF, or password reset. Be kind. Be brief.
What About SEO?
If there is a replacement website, do not use 410 for everything. Use 301 redirects from old pages to the best matching new pages. That helps users and may preserve ranking signals.
Use 410 when the content has no replacement.
Simple rule:
- Same content at a new URL? Use 301.
- Similar content exists? Use 301 if it truly helps.
- No replacement? Use 410.
- Temporary problem? Use 503, not 410.
Also, do not block the retired site in robots.txt before search engines see the 410. If bots are blocked, they may not see the status code. That defeats the point.
When Can You Finally Remove DNS?
After the quiet period.
Check server logs. Check analytics. Check support tickets. If almost nobody visits after 90 to 180 days, DNS removal may be fine. Large brands may wait a year. Tiny side projects may wait a month.
Before you remove DNS, ask:
- Is email moved?
- Are redirects no longer needed?
- Are legal pages saved?
- Are backups tested?
- Is the domain still renewed?
The Final Pick
Choose HTTP 410 first. It is cleaner. It is clearer. It is kinder to users and bots.
Choose DNS removal later, after the website has fully faded out. Do not start there unless the site is worthless and isolated.
A permanent shutdown should not feel like a server crash. It should feel like turning off the lights, locking the door, and leaving a neat sign behind.
