For a subdomain, use a CNAME record: www → host.rkzhosting.com. This is our recommended setup because we can keep it working if our infrastructure changes.
For the root or apex domain (@), use an A record to 51.79.164.219. If your provider supports ALIAS, ANAME, or CNAME flattening, you may instead point @ to host.rkzhosting.com.
You keep your domain and DNS with whichever provider you already use — we never take over your nameservers.
Add an A record for @ pointing to 51.79.164.219. A records are supported for root domains by virtually every DNS provider.
You can also use www.yourdomain.com with a CNAME to host.rkzhosting.com and redirect one hostname to the other, so visitors always see a single address.
The check itself runs in a few seconds. If you just changed your DNS record, it may not have propagated yet — that can take anywhere from a few minutes to a few hours depending on your provider. You can rerun the check as many times as you like at no cost.
For the broadest compatibility, configure both: www → host.rkzhosting.com (CNAME) and @ → 51.79.164.219 (A record). Then redirect one hostname to the other at your registrar or in your website settings.
Once you complete payment, Core provisions your hosting space and requests your public HTTPS certificate automatically (Let's Encrypt) — this typically takes a few minutes. Occasionally the certificate doesn't issue on the first try (usually because DNS hadn't fully propagated yet) — if that happens, My Portal shows a one-click "Enable SSL" retry next to that site.
HTTPS is issued and renewed automatically for every connected domain via Let's Encrypt, as part of provisioning — normally nothing for you to set up. If issuance doesn't succeed right away (usually because DNS hadn't fully propagated at that moment), My Portal shows that site as "No SSL" with a one-click "Enable SSL" button to retry it — no need to touch HestiaCP directly.
Once issued, renewal is fully automatic — normal Let's Encrypt behavior applies (renews before it expires, nothing for you to do).
Automatic HTTPS doesn't replace secure passwords, keeping your site's software updated, or backups — those still matter for every website, and are on you to stay on top of.
No. RKZ Hosting is web and database hosting only — we don't run mail servers. Most beginners use a free Gmail address or a separate email provider (like Google Workspace or Zoho Mail) alongside their website, and that continues to work fine since your domain's other DNS records stay with your existing DNS provider.
Yes. Once your domain is connected, select Control Panel in My Portal's navigation and sign in to HestiaCP using your panel credentials. From there you can use the file manager, quick-install templates, and your databases directly. If you need a new panel password, select Reset panel password on your hosting account in My Portal.
Your account keeps up to 5 backups on a recurring schedule, manageable from HestiaCP. We recommend downloading a copy periodically for your own records — backups protect against server issues, not against you deleting your own files.
Yes. Your first 3 sites share one account and one subscription, but a 4th (or 7th, or 10th) site isn't blocked — ordering it automatically provisions a separate account with its own fresh storage and its own PayPal subscription, with room for up to 3 more sites again.
There's no single-account storage upgrade — additional space always comes from an additional account rather than expanding an existing one.
Yes — My Portal includes an AI Site Builder that turns a short description into a real starter site (plain HTML/CSS, no page-builder lock-in) for a domain you've already connected. It's built for straightforward informational sites — landing pages, portfolios, business info, menus — not online stores, logins, or checkout.
You can describe changes in a chat box to adjust wording, colors, or layout before publishing. Publishing replaces whatever's currently live on that domain.
PayPal only, which also supports most major debit and credit cards without needing a PayPal account.
Sign-ups and checkout are restricted in a small number of regions for payment and fraud-prevention reasons. If you're in a restricted region, you'll see a notice explaining this instead of the site.
Turning off auto-renew from My Portal is the reversible option — billing pauses, and you can turn it back on any time before your account is suspended, with no new charge until you do.
Cancelling directly in PayPal is final on PayPal's end — PayPal doesn't support un-cancelling a subscription. Coming back after that means approving a fresh subscription from My Portal ("Resubscribe") rather than a simple resume. Either way, your sites stay live for the rest of whatever period you already paid for.
Once the period you already paid for ends with nothing renewing it, your account is automatically suspended — your files and databases stay exactly as they are, just not publicly served. Turning auto-renew back on or resubscribing at any point restores everything immediately.
Permanent deletion is a separate, manual administrative step after suspension. We keep deletion separate from billing so an account is not irreversibly removed by an unattended timer.