> For the complete documentation index, see [llms.txt](https://docs.certinext.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.certinext.io/documentation/certificate-lifecycle-management/ordering-a-certificate/as-a-customer/ordering-ev-public-trust-certificates/phase-2-steps-via-email-and-emsign/domain-verification.md). # Domain Verification ### Action 6 - Domain Control Validation (DCV) Domain Control Validation is the process by which you prove to the Certificate Authority that you genuinely control each domain on your certificate. This is mandatory for ALL SSL/TLS certificates before issuance. ### Domain List When you expand Action 6 (Domain Verification), you see: • 'Total Domains: \[N]' - the count of domains requiring verification. • Each domain listed with a status icon (orange warning = pending, green = verified) and a 'Verify' button. • For EV SSL Certificate: 1 domain to verify. • For EV SSL Certificate UCC: one entry per domain - you must verify each domain individually.

ℹ INFO

Product Difference - Multiple DCV for EV SSL Certificate UCC

EV SSL Certificate UCC requires domain verification for EVERY domain listed on the certificate.

Total Domains: Shows the total count (e.g., "Total Domains: 4").

Each domain is listed individually with its own status icon, "CAA" button, and "Verify" button.

DCV must be initiated and completed for each domain separately by clicking "Verify" next to each one.

If the authorized domain name (base domain) ownership is proven, all sub-domains that have the same base domain name will be proven automatically (e.g., proving xyz.com automatically proves blog.xyz.com). Note: the reverse is NOT allowed.

### DCV Method - DNS TXT Record (Recommended) *Click the 'Verify' button next to a domain. A modal dialog appears.*

ℹ INFO

Technical Note

The DCV modal includes a note: "This is technical in nature. If you are not the right person, please contact your IT / Domain administrator." If you do not manage your DNS records yourself, forward the TXT record details (Host and Value) to your DNS administrator and ask them to create the record.

**DCV Method dropdown** The method used to prove domain ownership. 'DNS TXT Record (Most Preferred)' is the recommended and pre-selected method. Leave as 'DNS TXT Record (Most Preferred)' unless your DNS provider does not support TXT records. **Record Type** The type of DNS record to create: TXT. Always TXT for this method. **Host** The hostname for the DNS TXT record. This is the domain name itself (Copy button available). Copy this value exactly. Log in to your DNS provider's management panel, navigate to DNS settings for this domain, and use this as the Host/Name field when creating the TXT record. **Value** The unique verification token that must be entered as the TXT record's value (Copy button available). Copy this token exactly. Enter it as the Value/Content of the new TXT record at your DNS provider. Do not add any extra spaces or characters. For UCC: each domain gets its own unique Host and Value - do not reuse values between domains. **Verify Now button** Triggers the CA's system to check your DNS for the TXT record. ONLY click Verify Now after you have saved the DNS TXT record at your DNS provider AND allowed sufficient time for DNS propagation (15-30 minutes minimum, up to 48 hours). **Close button** Closes the modal without verifying. Click Close if you need to set up the DNS record first and return to verify later.

⚠ IMPORTANT

DNS Propagation

After creating the DNS TXT record at your DNS provider, changes may take anywhere from a few minutes to 48 hours to propagate globally (depending on your DNS TTL settings). It is best practice to wait at least 15-30 minutes before clicking 'Verify Now'. If verification fails, wait longer and try again. Do not delete the TXT record until verification succeeds.

### Domain Verification Success
After successful verification, a success popup appears: "Thank you for proving the domain ownership for \[domain]. Domain Verification is completed successfully." *Click OK to dismiss. The domain's status icon turns green.* *For EV SSL Certificate UCC: repeat the Verify process for each remaining domain until all show green / Completed.* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.certinext.io/documentation/certificate-lifecycle-management/ordering-a-certificate/as-a-customer/ordering-ev-public-trust-certificates/phase-2-steps-via-email-and-emsign/domain-verification.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.