When you close a project or retire a company website, cancelling hosting can look like the final administrative task. Yet the same account may hold messages, documents, DNS records and integrations that are still in use. A planned website closure separates what you can remove from what you need to retain. Before submitting a hosting cancellation request, work through these checks.
1. Separate your domain, web hosting and email service
Your domain is the address visitors use and often the part after @ in your email addresses. Web hosting provides the resources that run your website. Your email service handles sending, receiving and storing messages. These services may be managed together, but they are not interchangeable.
You can retire a website and keep its domain. You can also move email to another provider and close the web hosting account. The important step is to check technical dependencies and contractual terms rather than assume that each service operates independently.
- Identify the domain provider, registered holder, expiry date and access to domain management.
- Check where the DNS zone is managed and whether it depends on the account you intend to close.
- Establish where your mailboxes are hosted and who manages the service.
- Review active services and their renewal or cancellation terms.
If you keep a domain without a website, its renewal and contact details still need attention. The domain registration page is a starting point for information about this service, which is separate from web hosting.
2. List everything that depends on the hosting account
Look beyond the main website. An account may contain subdomains, test sites, customer files or automated processes that never appear in the website menu. Review both your service management settings and the configuration of connected applications.
- Websites and subdomains: secondary projects, campaign pages and customer portals.
- Databases: information used by the website or by external applications.
- Automation: scheduled tasks, imports, exports and report generation.
- Integrations: forms, notifications, webhooks and connections to invoicing or stock management applications.
- Public resources: documents, images or downloads linked from messages and other websites.
- Technical services: DNS, redirects and outgoing email sent through SMTP.
For each item, record whether you will close it, move it or keep it temporarily. Assign someone to handle the change and decide how it will be checked afterwards. For a company website, ask colleagues who use orders, forms or reports to confirm the list. Some dependencies may only be familiar to the people who use them.
3. Export your data and check that it is usable
A useful data export must remain accessible and understandable after the account closes. Do not assume an existing copy is complete or that it will remain available after cancellation. Check the export options and download your archives somewhere outside the hosting account you are closing.
What to include in your archive
- Website files, including uploads and configuration needed for a possible restoration.
- Databases and details of the application and software versions used.
- Exports of content, products, orders or other relevant records.
- Your DNS configuration and a list of integrations that would need setting up elsewhere.
- Email messages and contacts if you are closing the email service.
For WordPress, the application's content export does not necessarily replace a complete copy of the files and database. Distinguish between exports intended for reference and the material required for a technical restoration.
How to check the export
Open the archives, inspect representative files and confirm that the exports cover the period you need. If restoration matters, test it in a separate environment without making personal data publicly accessible. Keep copies in controlled locations, restrict access and protect sensitive information. Avoid leaving passwords or access keys in documents shared informally.
4. Retain necessary records, not every piece of data indefinitely
Closing a website does not automatically end obligations arising from the business activity behind it. Invoices, contracts, order documents and certain records of communications may need to be retained. Requirements depend on the type of record and the company's circumstances.
Work with the person responsible for accounting or a legal adviser to establish what you must keep and for how long. Do not apply one retention period to everything or assume that a full website archive is the only suitable approach.
- Separate required business records from technical copies and data you no longer need.
- Choose formats you can read without running the old website application.
- Record who can access the archive and where its instructions are stored.
- Arrange reviews and controlled deletion when retention is no longer justified.
If you are closing an online shop, check outstanding orders, returns, warranties and customer enquiries. Taking the website offline does not resolve these matters. Keep an appropriate contact route available for as long as necessary.
5. Plan for email continuity and domain retention
To maintain email continuity, prepare the move before deactivating the old service. An active domain does not automatically mean working mailboxes, and changing MX records does not transfer messages already stored on the old service.
- List mailboxes, aliases, forwarding rules and addresses used by applications.
- Prepare mailboxes with the new service and decide how to transfer messages, contacts and calendars where relevant.
- Check the DNS zone and its MX, SPF, DKIM and DMARC records against the chosen service's instructions.
- Update email clients and applications that send messages.
- Test sending and receiving with external addresses and check the message transfer before closing the old service.
Allow for DNS record updates when planning the change. If the DNS zone will disappear with the hosting account, move it and check it before cancellation. Also review accounts that use old email addresses for signing in, password recovery or notifications.
Keeping the domain can help preserve your project's identity and familiar email addresses. If you are changing registrar too, treat the domain transfer as a separate task: it does not automatically move the website, messages or DNS configuration.
6. Cancel hosting only after the final checks
Review the cancellation procedure and ask for clarification about the deactivation date, affected services and any subsequent access to data. Turning off automatic renewal is not necessarily the same as requesting immediate cancellation. For questions about your specific GazduireOnline.ro services, use the contact page before confirming cancellation.
If visitors need an explanation, consider a closure notice or a redirect to a relevant destination. Both require a working technical setup; retaining the domain alone does not provide them.
- Your exports have been downloaded and checked.
- Required records have a storage location and a person responsible for them.
- Email, DNS and remaining integrations have been checked.
- You have decided whether to retain or give up the domain.
- You have confirmation of the cancellation request and have checked the services that remain active.
The practical takeaway: close the hosting account after separating and checking everything that depends on it. Retiring your website can then remain a controlled decision rather than an accidental interruption to email, records or other services you still need.
