IONOS termination made easy - cancel hosting, domain & more

Cancel IONOS Hosting succeeds completely online today: I cancel my hosting, domain or construction kit directly in the Control Center, back up my data and adhere to deadlines. In this guide, I show you the necessary steps, explain notice periods and provide practical tips for a smooth switch.

Key points

• Deadlines know: Terminate products in good time and avoid automatic renewal.
• Data backup: Export websites, emails and databases in advance.
• Domain Guard deactivate beforehand, otherwise the termination will stop.
• Online cancel: Conclude a clean contract in the Control Center.
• 30 days Use the money-back guarantee for new contracts.

Notice periods briefly explained

I check before every Termination the term of my tariff so that no further renewal takes effect and I save costs. IONOS links the term to the respective product, so I look specifically at my contract. Web hosting and domains have longer terms, while cloud or VPS products are usually billed on a monthly basis. For website builders, I recognize different minimum terms depending on the tariff. This overview helps me to find the right Date to choose.

Product	Minimum term	Term of notice	Note
Web hosting	12 months	No later than 1 month before the end of the term	Otherwise extension by 12 months
Domain	12 months	At the latest 6 weeks before expiry	Short reactivation period possible after deletion
VPS/Cloud Server	Flexible	7 days at the end of the month	Monthly cancelable
Homepage construction kit	1-12 months	30 days	Varies depending on tariff

I keep a Buffer of a few days so that the confirmation arrives on time. If the end date falls on a public holiday or weekend, I plan the application early enough. That way I avoid extensions and unnecessary additional costs. As soon as I know the deadline, I set the date for the move. Then I prepare the data backup and the actual move. Termination process before.

Step-by-step: Terminate contract, hosting or domain with IONOS

I report to IONOS Control Center and open "Contracts & subscriptions". There I select the relevant contract or the specific domain. The "Cancel contract" or "Manage products" button starts the process. I read the information carefully and check the term. This allows me to keep track of Options and dates.

I wear the Reason for termination and confirm the desired end date, if the interface offers this step. Alternatively, I deactivate the automatic renewal for individual domains. As a result, the domain expires and is deleted after a grace period. If Domain Guard exists, I deactivate the protection beforehand. This is how I prevent blocks during the Termination.

After I have confirmed everything, I am waiting for the e-mail with the final Termination date. If it doesn't arrive, I actively ask the support team. Mails sometimes end up in spam - I check the mailbox immediately. The appointment is only saved once it has been confirmed. I save the message locally as Proof.

Cancel or transfer domains separately

I decide whether I want to use the Domain or transfer to another registrar. For the move, I request the AuthCode in the Control Center and start the transfer with the new provider. This ensures that my website remains accessible. A clear sequence of steps is provided by the Domain transfer instructions. If I simply let the domain expire, I deactivate the automatic Extension.

After the deletion I can buy some domains for a few days reactivate, then the address is free. Please note, however, that email inboxes and forwarding will no longer work. For projects with ongoing traffic, I plan the transfer in good time and lower the TTL in advance. This speeds up the DNS changeover and reduces downtime. Good planning saves me a lot later on Stress.

Back up data before canceling

I secure website files, Databases and emails completely before I end the contract. For WordPress, I use a backup plugin or export databases directly via phpMyAdmin. I back up mailboxes via IMAP download or with the export functions of my client. I also download log files and configurations. A structured checklist helps me to do nothing to overlooked.

If you are planning to change provider, read my tips on Provider change and data backup. This is how I implement backups, tests and relocation in a clear sequence. I keep a local snapshot and a copy in the cloud. After the move, I test the front end, login and contact forms. Only when everything is up and running do I carry out the final Termination.

Special termination, revocation and contract change

I differentiate between ordinary termination, extraordinary termination (e.g. in the event of significant changes to services) and revocation. For new customers, there is also a 30-day money-back option. As a consumer, I can generally declare a withdrawal within 14 days if I have not expressly agreed to the immediate commencement of the service. In special cases (price adjustments, loss of service, longer outages), I check whether extraordinary termination is possible. I document evidence (tickets, logs) and adhere to the specifications in the Control Center. If in doubt, I clarify legal issues with expert advice, because this is not a Legal advice.

Sometimes a Contract change the better solution than canceling. I check whether downgrading to a smaller plan, changing the term (e.g. to monthly) or removing individual add-ons already fulfills my goals. This way, I avoid the expense of moving if the basis still fits.

Cancel individual services vs. terminate the entire contract

In my account, I make a precise distinction as to whether I use a single Product (e.g. a domain or an SSL certificate) or terminate the entire contract. Package tariffs often combine several services: Web space, databases, mail, SSL, possibly a construction kit. If I cancel the package completely, all of the included services are no longer available. If I only want to move one domain, I can leave the hosting running or rebook it separately. This way, email inboxes and FTP access are retained until the move has been completed.

Additional services such as SiteLock, CDNdedicated IPs, malware scanners, SSL certificates or Microsoft 365 subscriptions are checked separately. These can have their own terms and billing. I terminate them specifically so that no "hanging" subscriptions continue to run.

Domain transfer: blocking periods, DNSSEC and timing

Before changing the registrar, I equalize the technology: I deactivate Domain Guardif necessary, remove the transfer lock and request the AuthCode. I am aware of lock periods - many gTLDs are locked for 60 days after a new registration, change of ownership or previous transfer. With .de domains, things run much faster; here I need the AuthInfo and start the transfer quickly.

Use my domain DNSSECI delete the DS entries before the transfer or prepare the appropriate keys with the new provider. Otherwise there is a risk of resolution errors after the move. For the DNS cutover, I set the TTL of my zones to a low value a few days beforehand (e.g. 300-600 seconds). This gives me flexibility during the changeover and allows me to correct problems quickly.

I am also planning a Freeze for dynamic content: For CMS and stores, I stop order processes before the final dump or switch to a short maintenance mode. Then I transfer the last delta (uploads, database diff) to the target system, check sessions, caches and image paths and only then go live.

Email migration without data loss

I migrate mailboxes in a structured way: First I set up mailboxes at the target, then I test IMAP access. I copy folders via client or use migration tools. Before the MX switch, I lower the TTL and check the SPF, DKIM and DMARC at the destination. I avoid double deliveries by setting temporary forwarding or testing the dispatch via the new system before I change MX.

For productive teams, I inform the users at an early stage, plan a Maintenance window and set up temporary parallel access if necessary. I document SMTP ports, authentication, sender domains and signatures. After the changeover, I check bounces, spam quotas and reputation and adapt SPF mechanisms (include, a, mx) to the new infrastructure. This ensures that deliverability and sender trust are maintained.

Technology checklist before switching off

• websiteFiles, media, .htaccess/NGINX rules, redirects (www/non-www, HTTP→HTTPS), caches, cronjobs, maintenance mode.
• DatabasesComplete dumps (incl. triggers/views), check character set (UTF-8), adjust connection data at destination.
• E-mailChange: IMAP export, aliases/forwarding, catch-all, autoresponder, MX/SPF/DKIM/DMARC.
• SSL/TLSReissue certificates (Let's Encrypt or paid certificates), keep private keys safe, check HSTS header.
• DNSLower TTL, inventory records (A/AAAA, CNAME, MX, TXT, SRV), synchronize DS/CAA entries.
• IntegrationsPayment providers, webhooks, API keys, OAuth callbacks, web analytics, consent tools.
• SecuritySFTP/SSH keys, application secrets (.env), rotate access tokens, delete old accesses.
• DocumentationPHP version, memory limits, upload limits, worker/queue configuration, scheduled tasks.
• MonitoringUptime checks, error logs, alerts, post-cutover tests (forms, login, checkout).

Legal matters, data protection and order processing

I note Data protection-obligations: If an order processing contract (AVV) for my hosting data is running, I also terminate it and - if offered - request confirmation of deletion. I check which data (backups, logs) will still be retained after the end of the contract and when they will be deleted. I secure personal data (e.g. store orders) in compliance with the GDPR, encrypt it and delete outdated copies after the move.

I export logs for my Verification documentation (e.g. security incidents, access histories) and comply with the retention periods. For business accounts, I clarify internally who has data sovereignty and designate those responsible for the cutover. In this way, I prevent disputes about access and responsibilities.

Billing, invoices and payment methods

I load my Invoices completely before the account is closed. I save PDF documents and payment receipts locally for accounting purposes. I check open items, credit notes and stored payment methods (SEPA, credit card, PayPal). For flexibly billed products (e.g. cloud), I pay attention to daily or monthly billing. In the case of annual packages, services often continue until the end date; there is usually no daily reimbursement.

Important: If I cancel Domainsfees may have already been incurred in advance. I plan for these costs and avoid double payments by scheduling the transfer so that no new extension is triggered.

Change of owner, contract transfer and customer account

Changes the Domain ownership (e.g. sale of the project), I separate the change of owner from the change of registrar: First I adjust the owner data, then I start the transfer. I pay attention to blocking periods that may arise due to changes to WHOIS data. For contract transfers, I clarify the necessary steps with support (proof of legitimacy, powers of attorney). This keeps the history clean and clarifies any subsequent questions about authorization.

Following the successful termination of individual contracts, I decide whether my Customer account remains (e.g. for domains or new projects) or is to be closed completely. Before closing, I export all documents and make sure that no active services are still connected.

Money-back guarantee and cancellation within the first 30 days

As a new customer, I will use the first 30 days the money-back guarantee. I start the cancellation process in the Control Center and select the appropriate option for the refund. The refund will be made to the original payment method. Additional services or domains may vary - I read the instructions carefully. This way I can be sure that Deadline correctly.

Avoid common mistakes

I never give notice to the last Pusherbecause emails, confirmations or queries take time. I double-check whether add-ons, mailboxes or subscriptions are still active that would otherwise continue to run. For domains, I check whether a move affects webmail usage. I document settings such as PHP version, cron jobs and redirects for the restart with the new provider. With this preparation, I prevent outages low.

Provider change without downtime

I move hosting and mails carefully so that the site is live. remains. First I copy files and databases, then I set up a staging environment. I then lower the DNS TTL and activate the new environment after a final test. For emails, I follow the compact instructions for E-mail server migration. I then change DNS entries and monitor the Propagation.

Comparison & alternatives to IONOS

I rate performance, Support and price-performance in direct comparison. For data-intensive projects, server power and I/O performance are the most important factors. For entry-level priorities, a solid package with clear limits is sufficient. A quick look at the services that my project really needs saves on fees. This table gives me a quick Classification:

Provider	Server performance	Support	Price-performance	Recommendation
webhoster.de	Very high	24/7	Very good	Test winner
IONOS	High	24/7	Good	–
HostEurope	High	24/7	Good	–
Strato	Medium	24/7	Sufficient	–

FAQ: Cancel IONOS Hosting, cancel domain & end contract

How do I find my termination date?

I start the termination in Control Center and read the end date displayed there. I also receive an e-mail with all the details. I save this message as a PDF. If there is no confirmation, I actively ask the support team. Clear documentation protects me from Misunderstandings.

What happens to my data after expiry?

The provider deletes files after the end date, Databases and emails. I then no longer have access to the account. That's why I export everything important in advance. I test the backups and keep at least a second copy. This is how I prevent final Data loss.

Can I reactivate a domain or a contract?

Sometimes I can use domains for short Time reactivate after deletion. With contracts, reactivation depends on the product and is often not possible. After reactivation, I have to set up mailboxes and applications again. That's why, when in doubt, I prefer to renew for a month. This ensures me a clean Relocation.

How do I use the money-back guarantee?

As a new customer, I cancel within 30 days in the Control Center. I select the refund and confirm everything as specified. The payment will be made to the original payment method. I note that domains and add-ons can be handled separately. A look at the notes saves me Surprises.

Summary for a quick conclusion

I meet deadlines, ensure Data and start the termination in the Control Center - this way I can end hosting, domain or construction kit without any hassle. I deactivate automatic renewal for individual domains or move them with AuthCode. I switch off Domain Guard before I cancel and check email migration and DNS. For new contracts, I use the 30-day money-back option. With this plan, I move stress-free and keep services reliable online.