Documentation

RHost Documentation

Everything you can do with RHost — register a domain, run its DNS, and deploy apps, databases and static sites from Git, on our platform or a server you already own.

Introduction#

What is RHost?#

RHost is a business platform that brings your domain, DNS, apps and data together under one account. Register a domain or bring one you own, run its DNS, and deploy web services, workers, cron jobs, static sites and managed databases straight from Git — paying only for what you switch on.

Think of it as two things working together. First, a domain & DNS platform: buy a new domain through RHost, or bring one you already own, and manage all its DNS from one dashboard. Second, a hosting platform: deploy web services, workers, cron jobs, static sites and managed Postgres, MySQL or Redis straight from Git — on RHost's own infrastructure, or on a server you already own. You pay only for what you switch on.

One account covers all of it. You and the people you invite sign in once, and the same console carries your domains, your DNS, everything you have deployed, and the bill for it.

RHost's DNS is powered by PowerDNS — a proven, high-performance open-source nameserver used by some of the world's largest DNS operators. Changes you make in the dashboard are reflected in the DNS within seconds.

How it works#

The flow to get your domain live on RHost is straightforward:

  1. 1

    Add your domain

    Enter your domain name in the Domains dashboard. RHost immediately creates a DNS zone and seeds it with default SOA and NS records.

  2. 2

    Set up your DNS records

    Add all the records your domain needs — A, AAAA, MX, CNAME, TXT, and so on. If RHost can auto-import your existing records from your current provider, it will do so automatically.

  3. 3

    Point your nameservers

    Log in to your domain registrar and update the nameservers to RHost's nameservers. Once propagated, all DNS queries for your domain will be answered by RHost.

Platform nameservers#

When adding a domain to RHost, you will need to update your nameservers at your registrar to point to the following:

NameserverRole
ns1.rwa-host.rwPrimary nameserver
ns2.rwa-host.rwSecondary nameserver

Both nameservers read from the same database. Changes you make are immediately available on both ns1 and ns2 — there is no zone transfer delay.

Getting Started#

Create an account#

Navigate to rhost.rw/auth/signup and complete the three-step registration form:

  • Step 1 — Personal information: first name, last name, email address, and optional phone number.
  • Step 2 — Organisation details: company name, address, city, and country (all optional).
  • Step 3 — Password: choose a strong password, confirm it, and accept the terms of service.

You can also sign up using your Google or GitHub account via the OAuth buttons on the signup page. After registration, a verification email will be sent to your address.

Turn on two-factor authentication after registering. Settings → Security offers three: a passkey, an authenticator app, or a code emailed to you — see Account Security below.

Your account#

Your account groups your domains, DNS zones, and team members together — every domain belongs to your account. It's created automatically when you sign up; there's nothing to set up.

Team members can be invited to your account with their own roles and permissions.

Add your first domain#

Once you have a workspace selected, navigate to Domains in the sidebar. In the Add a domain you already own panel, type your domain name and click Add domain.

RHost will immediately:

  • Create a DNS zone for your domain.
  • Seed the zone with default SOA and NS records.
  • Attempt to auto-import your existing DNS records from your current provider.

You will be redirected to the domain detail page where you can review imported records, add new ones, and eventually point your nameservers to go live.

Buying a Domain#

Search & availability#

To register a brand-new domain, go to Domains → Register and type the name you want. RHost checks availability live against the global registry (via RDAP) and shows you which extensions are free, which are taken, and the yearly price of each.

  • Available — free to register right now, with its price shown per year.
  • Registered — already owned by someone else. If you own it elsewhere, you can add it as an external domain or transfer it in instead.
  • Unsupported — the extension (TLD) is not one RHost sells yet.

Prices vary by extension — for example .com, .rw, and .io each have their own yearly rate. The price you see at search is the price you pay at checkout.

Registering a domain#

Pick one or more available domains and continue to checkout. You'll choose a registrant contact (the legal owner of the domain — see below), then pay securely by card. As soon as payment succeeds, RHost:

  • Registers the domain in your name.
  • Creates its DNS zone and points it at RHost's nameservers automatically — no manual nameserver step needed for domains bought here.
  • Adds it to your Domains dashboard, ready for records.

Registered vs external domains#

RHost handles two kinds of domain. The difference is only about where the registration lives — both get the full DNS dashboard.

Registered with RHostExternal (registered elsewhere)
You buy and renew the domain here; billed yearly.You keep it at your current registrar; you renew it there.
Nameservers are pointed automatically.You point the nameservers to RHost yourself.
Included in the registration price.A small yearly managed-DNS-hosting fee applies.

Domain contacts#

Every registered domain needs a registrant contact — the person or organisation that legally owns it. Manage these under Contacts. You can reuse one contact across many domains, and update details (address, phone, email) in one place.

RHost keeps your personal contact details private in public WHOIS/RDAP lookups. Registrant information is redacted so your name, address, and email are not exposed to the public internet.

Transferring a domain in#

To move a domain's registration to RHost, open Domains → Transfer in, enter the domain and the authorization (EPP) code from your current registrar, and submit. You can track the request's status and cancel it while it is still pending. Transfers follow the standard registry process, so they can take a few days to complete.

Domain Management#

Adding an external domain#

An external domain is a domain you registered at a third-party registrar (Namecheap, GoDaddy, Cloudflare Registrar, etc.) that you want RHost to manage DNS for. You do not need to transfer your domain registration — only the nameservers need to change.

Enter just the root domain (e.g. example.rw) without a trailing dot or any subdomain prefix. RHost normalises the input automatically.

If you add a domain that is already managed by another DNS provider, do not update your nameservers until you have fully configured all your records in RHost. Switching nameservers before your records are ready will cause downtime.

Domain lifecycle#

Every domain in your inventory has two status indicators:

BadgeMeaning
ActiveZone exists and is configured in RHost. DNS records can be managed.
Nameservers not pointedZone is ready but the domain's nameservers at the registrar still point elsewhere. Queries will not reach RHost yet.
LiveNameservers are confirmed to be pointing to RHost. The domain is fully live.
SuspendedDomain has been suspended. Contact support.

Pointing nameservers#

Once your DNS records are fully configured, the final step is to update your nameservers at your registrar. The exact steps depend on your registrar but generally follow this pattern:

  1. 1Log in to your domain registrar's control panel.
  2. 2Navigate to your domain's management page.
  3. 3Find the Nameservers or DNS section.
  4. 4Switch from the default nameservers to custom nameservers.
  5. 5Enter ns1.rwa-host.rw and ns2.rwa-host.rw.
  6. 6Save the changes.

After saving, use the Check nameservers button on the domain detail page to confirm that RHost can see the NS change. Propagation typically takes between 30 seconds and 48 hours depending on your registrar and the TTL of your previous NS records.

To minimise propagation time, lower your NS record TTL to 300 seconds (5 minutes) at your current provider at least 24 hours before switching. This means resolvers around the world will refresh their cache within 5 minutes of your change.

Expiry alerts#

RHost can notify you before a domain expires so you can take action in time. To configure alerts:

  1. Open a domain's detail page.
  2. Click Expiry alerts in the header.
  3. Choose which days before expiry you want to be alerted (e.g. 90, 30, 7, 1 days).
  4. Toggle email and in-app notifications on or off independently.
  5. Use the Send test email button to verify delivery.

Expiry alerts are sent daily at 08:00 UTC. If you configure an alert for 30 days before expiry and today is exactly 30 days before the expiry date, you will receive the notification that morning.

DNS Records#

Record types reference#

RHost supports all standard DNS record types. Below is a reference of the most commonly used ones:

TypeDescriptionValue example
AMaps a hostname to an IPv4 address.192.168.1.1
AAAAMaps a hostname to an IPv6 address.2001:db8::1
CNAMECanonical name — aliases one hostname to another. Cannot coexist with other records at the same name.www → example.rw.
MXMail exchange — specifies the mail server responsible for accepting email for the domain. Requires a priority value.10 mail.example.rw.
TXTArbitrary text data. Used for SPF, DKIM, DMARC, site verification, and other purposes.v=spf1 include:_spf.google.com ~all
NSNameserver records — delegates a zone to a set of nameservers. Locked by RHost and cannot be edited directly.ns1.rwa-host.rw.
SOAStart of Authority — metadata about the zone (primary NS, contact email, serial, refresh intervals). Managed automatically by RHost.ns1.rwa-host.rw. hostmaster.example.rw. 1 …
SRVService locator — specifies host and port for a specific service. Requires priority, weight, and port.10 20 5060 sip.example.rw.
CAACertification Authority Authorisation — restricts which CAs can issue SSL/TLS certificates for the domain.0 issue letsencrypt.org
PTRPointer record for reverse DNS lookups. Maps an IP address back to a hostname.example.rw.

Creating records#

Navigate to a domain's DNS Records tab and click Add record. Fill in the record modal:

  • TypeSelect the DNS record type from the dropdown.
  • NameThe hostname. Use @ for the zone apex (root domain), or enter a relative label like www, mail, _dmarc. RHost will automatically append the domain name.
  • ValueThe record's content. For A records this is an IPv4 address; for CNAME it is the target hostname ending with a dot; for MX it is the mail server hostname.
  • TTLTime To Live in seconds. Controls how long resolvers cache this record. Default is 300 seconds. Lower values allow faster changes but increase DNS query load.
  • PriorityOnly visible for MX and SRV records. Lower numbers have higher priority.

Newly created records are immediately active and served by PowerDNS. There is no confirmation step for manually created records — only auto-imported records require confirmation.

Editing and deleting records#

Hover over any record row in the DNS tab and click the edit (pencil) icon to modify it, or the delete (trash) icon to remove it.

SOA and NS records are locked and cannot be edited or deleted. These records are managed by RHost to ensure zone integrity.

Deleting an A or MX record that is actively in use will immediately stop DNS resolution for that hostname. Always confirm records are no longer needed before deleting them.

Pending vs active records#

When RHost auto-imports records from your existing DNS provider, they are created as pending. Pending records are stored in the database but are disabled in PowerDNS — resolvers will not serve them until you confirm.

This gives you the opportunity to review the imported records before they go live. In the DNS Records tab:

  • Pending records are shown with an amber Pending badge.
  • Click Confirm All to activate all pending records at once.
  • Or select individual records and confirm them one at a time.
  • Once confirmed, records are immediately served by PowerDNS.

History and rollback#

Every create, update, and delete action on DNS records is logged in the domain's History tab. Each entry shows:

  • The action type (created, updated, deleted).
  • The record type and name.
  • The old and new values (for updates).
  • The email address of the user who made the change.
  • A timestamp.

Click Rollback on any history entry to instantly revert that record to its previous state. Rollbacks are themselves logged in the history.

Zone Management#

Importing a zone file#

RHost supports importing BIND-format zone files (.zone files). This is useful when migrating from another DNS provider that can export zone files.

Navigate to the Import / Export tab and paste or upload your zone file. RHost will:

  • Validate the zone file format (must include SOA and at least two NS records).
  • Delete existing non-locked records of the same types found in the import.
  • Stage all parsed records as pending (disabled) for your review.
  • Leave SOA and NS records untouched (they are locked).

After the import, go to the DNS Records tab and click Confirm All to activate the imported records.

A valid BIND zone file looks like this:

bind zone file
$ORIGIN example.rw.
$TTL 300

; SOA
@  IN  SOA  ns1.rwa-host.rw. hostmaster.example.rw. (
            2024010101 ; serial
            10800      ; refresh
            3600       ; retry
            604800     ; expire
            300 )      ; minimum TTL

; Nameservers
@  IN  NS   ns1.rwa-host.rw.
@  IN  NS   ns2.rwa-host.rw.

; A records
@     IN  A    192.168.1.1
www   IN  A    192.168.1.1
mail  IN  A    192.168.1.2

; MX record
@  IN  MX  10  mail.example.rw.

; TXT record (SPF)
@  IN  TXT  "v=spf1 ip4:192.168.1.0/24 ~all"

Exporting a zone file#

To export your zone as a BIND-format file, navigate to Import / Export and click Export zone file. The exported file contains all active records for the zone and can be imported into any BIND-compatible DNS server.

The SOA serial number is automatically incremented each time you export the zone file. This ensures that secondary nameservers correctly recognise the zone as newer.

Zone file editor#

For advanced users, RHost provides a full zone file text editor. Navigate to Import / Export → Open zone editor. You can edit the raw zone file directly and save — changes are parsed and staged as pending records, following the same import flow.

The zone editor is a power-user feature. Syntax errors will be rejected with a clear validation message, but always double-check your edits before saving. Incorrectly configured records can disrupt your site, email, or other services.

DNSSEC#

What is DNSSEC?#

DNSSEC (DNS Security Extensions) is a suite of specifications that adds cryptographic authentication to DNS responses. Without DNSSEC, an attacker who can intercept DNS traffic could forge responses and redirect your visitors to malicious servers — a technique called DNS cache poisoning.

When DNSSEC is enabled, each DNS response includes a digital signature. Validating resolvers check this signature against a chain of trust anchored at the root DNS zone. If the signature does not match, the resolver discards the response and the domain is unreachable from that resolver.

Enabling DNSSEC#

Navigate to the DNSSEC tab on your domain's detail page and click Enable DNSSEC. RHost will:

  • Generate a KSK (Key Signing Key) using ECDSA P-256 SHA-256 (algorithm 13) — the recommended modern algorithm.
  • Sign all records in the zone.
  • Provide you with DS (Delegation Signer) records to add at your registrar.

DNSSEC is only effective once you have added the DS records at your registrar. Until the DS records are in place, DNSSEC is signed but not validated — resolvers will not enforce it. Publishing DS records without correct NSEC/RRSIG records will break resolution for validating resolvers.

DS records#

After enabling DNSSEC, the DS records panel will display the DS record(s) you need to add at your registrar. They look like this:

ds record
12345 13 2 ABCDEF1234567890ABCDEF1234567890ABCDEF1234567890ABCDEF1234567890

The fields are: Key Tag, Algorithm (13 = ECDSA P-256), Digest Type (2 = SHA-256), and the Digest itself.

Copy these values into your registrar's DNSSEC DS record configuration. Once the parent zone (e.g. the .com registry) publishes the DS record, the chain of trust is complete.

Apps#

What an app is#

An app is a container RHost runs for you and keeps running. It can come from a Git repository, which RHost builds for you, or from a container image you already have. There are four kinds: a web service that answers on a URL, a private service reachable only by your other apps, a worker with no URL at all, and a cron job that runs on a schedule instead of staying up.

You do not need a Dockerfile. If your repository has one, RHost uses it; if it does not, RHost detects the language and builds the image for you.

Creating one#

Go to Apps → New. The form asks four things in order: what you are building, where the code is, how to configure it, and what to call it. Connect a Git provider the first time and RHost remembers it.

If your code lives in a subfolder of a larger repository, set Root directory to that folder — for example apps/api. Leave it as . to build from the repository root.

Domains and ports#

Every web app gets a free address straight away. To use your own, add it under Settings → Domains: RHost checks whether the domain is one it already manages, and if it is, offers to add the DNS record for you. If it is not, you are shown the exact record to add at your own provider, and RHost watches for it to appear.

Container port is the port your app listens on inside its container — not the port visitors use. Get this wrong and the edge cannot reach your app: you will see a 502 or 503, and the message names the port it tried.

An app's overview: a preview of the live site beside its source, container port, container name and creation date.
The top of an app's page: a screenshot of the live site beside the facts about it. Everything you can change lives under Settings.

Environment variables#

Set them under Settings → Environment. Changing one redeploys the app, because a running container cannot be handed new values. Variables marked available during build are also passed to the build step, which is what you want for anything a bundler reads.

Deploys#

Deploy history#

The Deployments tab lists every attempt, newest first, numbered from the first one. Each row shows whether it succeeded, the commit it built, when it ran and how long it took — which is the quickest way to notice a build getting slower.

The deployments table: status, deployment number and commit, when it ran, and how long it took.
Deploy history. The menu on each row opens the build log; the newest row can be redeployed, and earlier successful ones rolled back to.

Redeploy and roll back#

Redeploy builds the app again from wherever it comes from now, and is offered on the newest deployment. Roll back puts an earlier image back and is offered on previous successful deploys, for as long as the server still holds them — the last five.

Neither one risks what is live. A new version starts beside the running one and only replaces it once it is healthy; if it never becomes healthy, the old version keeps serving and the deploy is marked failed.

Rolling back returns the code, not the data. A newer version that changed your database schema has already changed it, and an older image may not understand the new shape.

Auto-deploy#

On by default for Git apps: pushing to the tracked branch deploys it. Turn it off, or switch branches, under Settings → Build & deploy.

In a monorepo, an app with a Root directory set skips a push that changed nothing under that folder — no filter needed. Build filters handle the rest: one glob per line, and a push whose every changed file matches is skipped.

Running migrations before a deploy#

A pre-deploy command runs before each new version goes live — usually database migrations. If it fails, the deploy stops and the running version is left alone, so a bad migration cannot take your app down. When RHost spots migrations in your repository it offers the command as one click.

It can run inside your built image, or from a fresh checkout of your source. Choose source when your production image does not ship the migration tool.

Events and logs#

Events is the app's own history — deploys, domain changes, scaling, restarts — with the full detail of any one of them a click away. Logs is your container's output, searchable and filterable by level, and you can look back over a window rather than only forward from now.

An app's events: deploy succeeded, deploy failed with the error, and a domain attached.
Events. A failed deploy leads with the error itself rather than the word 'failed', and the full output opens in a panel.

Databases#

Creating a database#

RHost runs managed PostgreSQL, MySQL and Redis. Pick an engine and a size; you can change the size later.

Connecting to it#

Each database shows two host names. The internal one is how your other apps reach it, and it never leaves RHost's network — use this one wherever you can. The public one is for connecting from your own machine, and only exists while external access is on.

Who can connect#

A database that is public on your own server accepts connections from anywhere until you say otherwise, and only the password stands in the way. Add the addresses that need it under Who can connect — one IPv4 address or range per line — and everything else is refused by the firewall before it can try a password. Apps on the same server always keep their access.

Importing a dump#

Upload a .sql, .sql.gz or PostgreSQL .dump file and RHost restores it. The file is deleted from our server as soon as the import ends, and you are told when it finishes — it runs for minutes, so you do not have to sit and watch it.

Start from empty deletes everything in the database before restoring. There is no undo. Take a backup first if you are not certain.

pgAdmin, PgHero and phpMyAdmin#

Each database offers one-click admin tools — pgAdmin and PgHero for PostgreSQL, phpMyAdmin for MySQL, Redis Commander for Redis. They deploy as ordinary apps already pointed at the database, with their sign-in details shown on the card. Remove one like any other app when you are done with it.

Static Sites#

Building from Git#

A static site is built from your repository and then served as plain files — no runtime, nothing to keep alive. Give RHost the repository, a build command if it needs one, and where the build output lands.

The publish directory#

This is the folder your build writes into — dist, build and out are the usual ones. A build that produces nothing servable fails loudly rather than publishing an empty site.

Your Own Server#

Bring your own server#

You can point RHost at a server you already own and deploy to it with the same console — the same apps, databases, domains, logs and deploy history, running on your hardware instead of ours.

Connecting a server#

Go to Servers → Connect a server and run the one-line install command it gives you. It installs a small agent that dials out to RHost — you do not need to open any inbound port or hand over SSH keys. The server appears in the console once the agent connects.

Docker is the only requirement. RHost installs what else it needs and keeps your apps behind a web server it manages, with certificates issued automatically.

What you can run on it#

Everything you can run on RHost's own platform: web apps, private services, workers, cron jobs and databases. Apps on the same server reach each other by container name, and a database can expose an extra port to the outside world when you need it.

Projects#

Projects and environments#

A project groups the things that belong together, and each project has environments — Production to begin with, and whatever else you add. Anything that is not in a project yet shows up under Apps, where you can file it without redeploying.

Shared variables#

An environment group is a set of variables several apps share. Attach one, and its values fill in anywhere the app does not already define the same key — the app's own variables always win. Changing a group redeploys every app attached to it, so the change actually takes effect.

Account Security#

Two-factor authentication#

A second step after your password, set up under Settings → Security. There are three to choose from, and one is active at a time: a passkey, an authenticator app, or a code emailed to you. Setting up a new one replaces the previous.

Passkeys#

The strongest of the three, and the least work: your fingerprint, your face, or a security key. There is no code to type and nothing that can be phished, because the secret never leaves your device.

Register more than one — a phone and a laptop, say. A passkey lives on the device that made it, so a second one is what stops a lost phone becoming a lost account.

Authenticator apps#

Scan the QR code with any authenticator app and enter the six-digit code it shows. The codes rotate every thirty seconds and work with no signal and no network.

Backup codes#

Setting up an authenticator gives you ten backup codes. Each works once, in place of a code from the app, and they are shown exactly once — save them somewhere that is not the phone holding the authenticator. You can issue a fresh set at any time, which invalidates the old one.

With no authenticator and no backup codes left, getting back in means contacting support and proving who you are. Issuing a new set takes a few seconds and is worth doing before you need it.

Billing & Payments#

How pricing works#

RHost only charges for what you switch on. There are a few kinds of charge:

  • Domains — a yearly fee to register (or a small yearly managed-DNS fee for external domains).
  • Workspace — a monthly charge per mailbox, based on the storage per user you chose.
  • Add-ons — Meet and Forms, each a separate monthly charge.

If a promotion is running, the discount is shown right on the price (with the original struck through) and applied automatically at checkout.

Paying (checkout)#

All payments go through a secure checkout. You're redirected to enter your card details, and as soon as the payment succeeds RHost activates the service and brings you back to the dashboard. You never enter card numbers directly into RHost.

RHost will never ask you to send card numbers, passwords, or codes by email or chat. Enter payment details only on the secure checkout page you're redirected to.

Invoices & payment method#

The Billing page in the console lists your active services as a single tidy summary — the Workspace on one line, each add-on on its own — plus your total monthly cost. Your invoices appear there too, each with a downloadable PDF. Click Manage payment method to update your card or review past payments in the secure billing portal.

Cancelling a service#

You can cancel any service from where you turned it on: the Workspace from the domain's Apps tab (Cancel), an add-on from its card (Remove), or any line from the Billing page. Cancelling stops future charges and disables that service for the domain's users.

Team & Members#

Your account & team#

Your account is the home for everything you own — your domains, DNS zones, billing, and the teammates who help you manage them. It's created automatically when you sign up; there's nothing to configure.

ConceptDetail
ScopeAll your domains, records, and history live under your account.
Team membersInvite people to help manage your domains, each with their own role.

Inviting members#

To invite a team member to a workspace:

  1. 1Navigate to Settings → Workspace in the console.
  2. 2Click Invite member and enter their email address.
  3. 3Select their role (Owner, Admin, or Member).
  4. 4Click Send invitation.

The invitee will receive an email with a link to accept the invitation. They must have an RHost account (or create one) before the invitation can be accepted.

Frequently Asked Questions#

How long does DNS propagation take?#

Propagation time depends on two things: the TTL of the record being changed, and how aggressively resolvers respect TTLs. In practice:

  • Records with a TTL of 300 seconds (5 min) typically propagate globally within 5–15 minutes.
  • Records with a TTL of 86400 seconds (24 hours) can take up to 48 hours to propagate fully.
  • Nameserver changes (NS records) are typically slower — allow up to 48 hours even with a low TTL.

Before any major DNS change, lower your TTLs to 300 seconds at least 24 hours in advance. This ensures the old TTL has expired everywhere before you make the change.

The nameservers are not pointing — what should I do?#

If the Check nameservers button still shows "Nameservers not pointed" after waiting for propagation:

  • Double-check that you saved the nameserver change at your registrar. Log back in and confirm ns1.rwa-host.rw and ns2.rwa-host.co are listed.
  • Some registrars require nameservers to be registered (glue records) before they can be used. RHost nameservers are already registered — no glue records needed.
  • Wait the full 48 hours. Propagation for NS changes is legitimately slow with some registrars.
  • Use the DNS Propagation Checker tool to query your domain's NS record type from multiple resolvers and confirm what they are returning.

I confirmed my records but they are not resolving#

If your records are confirmed (active, not pending) but queries are still not resolving as expected:

  • Verify that your domain's nameservers are pointing to RHost (check the Live badge on the domain overview).
  • Ensure the record type and name are correct. Use the DNS Lookup tool to query your domain directly.
  • Check that you do not have a conflicting CNAME at the zone apex — CNAME records cannot coexist with other record types at the same name.
  • If you recently added the record, allow a few seconds for it to propagate through the packet cache.

Should I enable DNSSEC?#

Yes, if your registrar supports DS record management (most modern registrars do). DNSSEC adds a meaningful layer of security against DNS spoofing and cache poisoning attacks with minimal performance overhead.

The main caveat is that once you enable DNSSEC and add DS records at your registrar, you must not disable DNSSEC or delete the zone in RHost without first removing the DS records from your registrar. Leaving orphaned DS records at the registrar will cause DNSSEC validation to fail and make your domain unreachable from validating resolvers.

Still have questions?

Contact our support team or browse the console to explore features hands-on.

Go to console