Rackhost in Hungary: WordPress pricing and DNS cutover

Who Rackhost may suit

This profile is based on published offers and documentation. No new hosting benchmark or support test was performed for this translation.

Plans, prices and renewals

Prices retain the market, currency and billing period described in the French source. Translation does not update a commercial quote. Confirm the final price, taxes and options before ordering.

Languages and support

Website and documentation

Local offer and documentation mainly in Hungarian.

Control panel

Rackhost account documented in Hungarian and English.

Support

Continuous written support advertised for the range. WordPress support in English or French to confirm.

Rackhost in Hungary: prepare WordPress with its domain

Rackhost offers eight WordPress plans in Hungary in the most recent record, with automated installation. The page sets a decisive constraint for an existing site. Domains associated with WordPress plans must be managed in the Rackhost system, and subdomains cannot be added. This rule makes the domain part of the hosting choice.

The fictional Szeged workshop wants to move its site while retaining email. Its domain receives inquiries, verifies senders and opens the catalog. The team prepares a candidate DNS zone and compares it with a reference zone. It accepts the web-entry change planned by migration and rejects a zone that has lost an email record. The local test lets this decision be replayed with fictional names and addresses.

This profile examines what the annual price includes, documented restoration fees and access required to move the site elsewhere. Before choosing a plan, the workshop must verify it can entrust domain management to Rackhost, preserve email entries and keep an independent WordPress copy. These three actions have separate schedules and owners.

Calculate initial cost and renewal in forints

In the official-page record of November 10, 2026, WP Mini 2 GB costs 990 HUF excluding VAT for the first year, with 1,257 HUF including VAT displayed. The note states 16,000 HUF excluding VAT per year after the first year, or 20,320 HUF including VAT. An older indexed version displayed renewal at 15,000 HUF excluding VAT and 19,050 HUF including VAT. Compare forint amounts for the same reference and date the quote. Even for a small site, Mini’s entry price must be assessed with next-cycle and domain costs.

Displayed annual tax-exclusive prices for other levels are 24,000 HUF for Midi, 33,000 HUF for Maxi and 45,000 HUF for Mega. The 50, 80, 120 and 150 GB levels display 55,000, 80,000, 100,000 and 120,000 HUF excluding VAT. Corresponding VAT-inclusive totals are 30,480, 41,910, 57,150, 69,850, 101,600, 127,000 and 152,400 HUF. They match the 27% VAT applied in the Hungarian table. The record gives no separate second price list for these seven references. Their public annual price is a reference, and the renewal pro forma specifies the amount due.

The workshop must add the domain to its calculation. For .hu, the separate list displays 490 HUF excluding VAT and 622 HUF including VAT for one-year registration, 4,400 HUF excluding VAT and 5,588 HUF including VAT for transfer with a one-year extension, and 2,900 HUF excluding VAT and 3,683 HUF including VAT for a one-year extension alone. In the fictional case where Mini and transfer are billed together at these prices, the two lines total 6,845 HUF including VAT. Domain renewal depends on its own expiry date. Distinguish registrar change from DNS delegation, then check dates before transfer. Any assisted-restoration or reactivation cost is another line. To compare Mini with a larger plan, add two hosting cycles and domain and recovery items actually needed. Renewal is manual by default. Rackhost documents an option to enable in the account for renewal with sufficient credit balance.

Read quotas, panel and location

Card volumes combine two items. Mini advertises 1 GB for Web and 1 GB for email. Midi gives 5 GB each, Maxi 10 GB each and Mega 20 GB each. Higher levels display 30, 50, 80 and 100 GB for Web with 20, 30, 40 and 50 GB for email. For a 2 GB site with lightly used email, Mini’s combined volume does not establish available file space. The comparison also gives one 500 MB database and 25 GB transfer for Mini, versus three databases with a displayed size of 750 MB and 50 GB transfer on Midi. Confirm database-limit scope in the quote or panel.

The WordPress profile mentions one, three, five and ten domains for the first four levels. It excludes adding an external domain or subdomain on this range. Standard-hosting help documents another workflow for external domains. The workshop must ask whether its registrar and DNS configuration meets the WordPress plan criterion and how to prepare a verification target without using a subdomain on this range. Assess this constraint before initiating transfer.

Rackhost presents facilities in Budapest and Szeged, including a site in the Budapest Internet Exchange building. These are provider locations. Consulted documentation does not assign the chosen WordPress plan to a precise facility or confirm backup location. The quote or service data must specify that assignment if the workshop needs it.

Distinguish maintenance, languages and AI

The page presents WordPress installed through a one-click workflow and an SSL certificate activatable from the account. The table mentions PHP 8.1. Confirm the version actually available for installation and the ability to choose a recent version compatible with used plugins. The cards do not establish automatic updates for core, theme and all plugins. The workshop remains responsible for validating catalog, form and access after every change.

The local table and most consulted guides are in Hungarian. The Rackhost account can switch to English through user data. The table advertises continuous written support. The contact page distinguishes customer-service details from data-center on-call support. Confirm the language of WordPress support requests and advertised restoration-handling timeframe. If migration affects the domain, prepare the account identifier and a contact address that works even during cutover.

Rackhost describes WordPress plugins using AI in a help-center article. The table does not associate a generative tool or credits with these plans. Assess cost, language and portability of selected plugins separately. Domain and email preparation here relies on records known to the workshop and its email service’s documented settings.

Verify backups and exit routes

The WordPress comparison states regular backups. Cadence, point count, mailbox scope and time to make them available remain to be clarified for the selected plan. The page publishes assisted restoration at 10,000 HUF excluding VAT, or 12,700 HUF including VAT per intervention. It separately displays recovery of deleted hosting at 12,000 HUF excluding VAT, or 15,240 HUF including VAT. Ask whether the price covers one installation, a database, a downloadable archive or intervention on the site. Billing help lists WordPress among services suspended seven days after expiry. While the account is only suspended, help states reactivation without extra fees after payment clears. After thirty days unpaid from the due date on the payment request, it describes service deletion. Reactivation may then provide empty space. Recovery of files, the database or email depends on an existing copy. Help mentions a general thirty-day window and restoration charges separate from service payment. Confirm a usable copy exists for the necessary date, files and database.

Rackhost excludes phpMyAdmin from WordPress hosting in its own MySQL import guide. Its WordPress guide describes migration with All-in-One WP Migration. It presents export to a file, downloading and import at the destination. When the archive exceeds 1 GB, that guide directs users to standard Web hosting. The workshop must measure package size and confirm the method’s effective limit on its installation. Ask what alternative file and database export channel is accessible with the plan, and try opening a package outside Rackhost before choosing hosting based on a promotional price.

The site, email and DNS zone each have an exit method. A site archive must allow pages to be read, media to open and a form to be submitted in an isolated environment. A zone export must preserve record targets and priorities. For email, document mailbox, alias and forwarding-rule locations. In the Szeged case, they remain with the current provider. The site archive and domain record are kept separately with dates and the person able to restore them.

Practice comparing two DNS zones locally

Guidance for preparing a targeted restore. — Illustration by BlogPasCher.Open full-size illustration ↗

The ZIP in “Prepare your site” contains EXERCICE-RACKHOST.cjs and RESULTAT-RACKHOST.json. Run the script from its folder with Node.js. The delivered result was obtained with Node 22.16.0. The program keeps six reference records in memory, creates the expected zone and compares three variants with that target. Names end in .test, and both IPv4 addresses are reserved for examples. The trial runs without a connection or email.

The workshop replaces only the root A record, from 192.0.2.19 to 203.0.113.44. The www CNAME remains associated with the same name. The record contains the MX server and priority, SPF policy in a root TXT, DMARC TXT under _dmarc and DKIM selector under mail2026._domainkey. Comparison covers name, type and value. The test accepts the complete target. It rejects a variant missing MX and the DKIM selector, another retaining the old web IP and a third adding a second SPF policy in the test data. The reference zone remains intact.

Compare referenceRecords and intendedRecords. The changed entry corresponds to the migration instruction. For controls, examine issues. The response helps identify email loss before being persuaded by site rendering. The comparison is deliberately designed for these six entries. A real zone can contain several MX records, TXT records for distinct purposes and other types. The script validates neither delegation nor DNSSEC, cache delays or mail-server operation. It serves as a model for writing a decision rule using the workshop’s own inventory.

The Rackhost guide places editing in DNS zónák, then Rekordok szerkesztése. It states that an MX may be added automatically when adding the email domain to the account. A workshop keeping mailboxes elsewhere compares the actually published value with the one supplied by its email service. It retains the DKIM selector used for outgoing mail, with its provider’s type and value.

node .\EXERCICE-RACKHOST.cjs

Prepare WordPress and email migration

Separate three operations in the schedule. The WordPress copy moves site content and settings. DNS delegation specifies which servers publish the zone. Registrar transfer moves management of the domain registration. For the WordPress plan, ask Rackhost which exact state satisfies the domain-management constraint. The .hu transfer guide describes its own workflow. The workshop must check when it can enter records and when Rackhost can associate the domain with the plan.

Before the change, record authoritative servers, records and cache durations. Include any site IPv6 addresses and validation TXT records used by providers. If the domain is signed, define with the registrar how to coordinate delegation and affected signature records. On the WordPress target, check the certificate for the bare domain and www, then redirects and catalog links. Retain the ability to restore the old site address if target content or certificate fails. Caches may retain the old answer until its lifetime expires.

For mailboxes staying in place, record the email provider’s configuration and compare its values with candidate-zone records. After the change, verify authoritative-server responses. During a real cutover, use authorized test mailboxes to check receipt, sending and authentication headers. For the site, open both domain names and submit a fictional inquiry to verify its path. The team retains control of the previous site until both workflows succeed and inquiries received during the period can be reconciled.

Decide before moving the domain

Mini may suit the Szeged catalog if the site and temporary files fit within the Web quota, the database respects the displayed limit and Rackhost can associate the domain during the planned window. Automated installation, SSL and separate quotas facilitate scoping. Mandatory domain management and limited database access make rehearsal particularly important for an already-live site. In the quote, keep hosting, domain and assisted-restoration lines separate, with the next payment amount and intended transfer date.

Before cutover, the team must be able to open the restored catalog, check the certificate, locate every email record and identify who can restore the previous address. The test accepts only a zone containing the new web destination and every expected record. If the authoritative response has another value, record the difference before changing other services. If transfer involves changing nameservers, keep a record of expected responses on old and new servers to track transition.

The workshop chooses a window when one person can observe WordPress and another check email. The log retains times and results for both site names, a test send and receipt, and any changes on the old installation during transition. If the destination zone loses an email record, suspend cutover and restore the expected value before resuming. The old installation can stop after both workflows succeed and the independent copy has been verified.

Prepare your site

• 25 WordPress backup tools by recovery need
• HTTPS certificate does not cover your WordPress domain: fix the name and destination
• WordPress migration, staging and imports: choose the right tool
• Download the DNS-comparison exercise