Add the generated ownership TXT record to prove you control the domain
Ownership verification proves you control the hostname before WebOptiva issues a certificate or routes traffic for it. WebOptiva never invents the record — it generates a deterministic TXT value for your domain, so you can create it once and re-check it as often as you like.
1. Open the setup workflow#
Select View on the domain card, then on the domain detail page choose the Setup category and the Setup workflow section. The panel heading is Setup workflow and its meta row shows Domain type, Root domain, and Next action — the fastest way to see what the domain is waiting for.
2. Read the ownership record#
In the group 1. Add the ownership record at your DNS provider the panel shows a record card labelled Ownership verification with three fields: Type (TXT), Name / host, and Target / value. The subtitle explains what it is for: This proves that you control the hostname. Use the copy buttons beside the name and value so nothing is mistyped.
3. Publish the record at your DNS provider#
Open the DNS zone for the root domain named in the meta row and create the TXT record with exactly those values. The panel reminds you that most providers append the root domain automatically, so paste the short host name rather than the fully qualified name. Leave MX, email, and unrelated TXT records untouched.
4. Ask WebOptiva to re-read public DNS#
Press Check DNS records. While it runs the button reads Checking public DNS…; when it finishes, the step status moves from Pending to Completed and the group gains a Done badge. Checking reads public DNS only and never modifies your records — and because DNS changes can take time to propagate, repeat the check if propagation is still in flight.
Expected result#
Step 2 of the workflow, Verify domain ownership (actor You), reads Completed. A mismatched TXT value leaves the step Pending with the record card still visible, so you can compare the published value against the expected one directly.
Why the value is deterministic#
The TXT value is derived from the domain itself, so it is identical every time you ask. What you copy on screen is the same value the onboarding API verifies — there is no second source of truth that could drift out of sync.