Last updated: Oct 07, 2026
Prove that you control a domain's DNS by publishing a TXT record, and keep that proof up to date.
Verifying a domain is proving that you can change its DNS. Domain Stabilizer gives you a code, you publish it as a TXT record in the DNS of the domain, and the screen checks that it is there.
To get there, open a domain and choose Verify domain in its menu.
The account Owner can always generate the code and run the check. Other roles can if their role includes operating domains.
At the top, the title with a mark for the state of the domain, and under it three numbered blocks.
Blocks 2 and 3 are dimmed until a code exists.
When the code is found, the state changes to Verified and the two dates appear. If it is not found yet, the screen says what it sees in the DNS; wait a few minutes and press the button again.
The check looks at the domain exactly as it is written in the console. The record has to be on that name, not on a name under it.
Do this when the state is Verification expired, or earlier, when the expiry email arrives.
From step 2 until the check passes, the domain counts as not verified. A domain under continuous stabilization is not affected in the meantime. Renew when you can reach the DNS, so the gap is short.
The check found no TXT record starting with dhs-verify= at the root of the domain. The usual causes, in this order:
You generated a new code and the record still has the old one. Edit that TXT record in the panel of your DNS provider, put the new value, save, and press Verify now.
The record published here belongs to another domain of your account; the message names it. Each domain has its own code. Open this domain's screen, copy its value, and put it in this domain's DNS.
There is a record with that prefix, and its value is not this domain's code. Two causes:
The verification lapsed and the code in block 1 is the old one, which no longer counts. Follow Verify domain: generate a new code first, then publish it and check.
The domain's DNS did not answer in time. Nothing was changed. Wait a moment and press Verify now again. If it keeps happening, check that the domain exists and that its DNS answers.
The Continuous stabilization screen and the dashboard show a notice with the Verify domain button when the domain is not verified. That covers a domain never verified, one whose verification expired, and one where a new code was generated and not checked yet. Press the button, complete the check, and go back.
Generating a code and running the check need a role that includes operating domains. If yours does not, the request is refused and the screen shows an error instead of the result. Ask the account Owner to do it, or to change what your role includes.
The warning goes to one address: the billing email of the account if it has one, and otherwise the person who created the account. It is not sent to every member. The date is always on this screen, in Expires.
Domain stabilization: DMARC, SSL, DNS, MX, blacklists and uptime — exact fixes and evidence of the work.
© 2026 Domain Stabilizer. All rights reserved.