Alternative DCV Checker

Alternative DCV Check

domain(s) checked

DNS OK {{ dnsOk }} HTTP OK {{ httpOk }} HTTPS OK {{ httpsOk }} Errors {{ errorCount }}

Inputs: CSR (optional)

Domains (comma or newline separated)

Unique value / token:

Check DNS:

Enabled

DNS type

DNS name template:

DNS resolver

Check HTTP:

Enabled

Check HTTPS:

Enabled

Path:

Follow redirects

Enabled

Validate TLS

Enabled

Timeout (ms)

Concurrency

Max domains

Domain	DNS	HTTP	HTTPS	Notes	Copy
{{ row.domain }}	{{ formatCheckCell(row.dns) }}	{{ formatCheckCell(row.http) }}	{{ formatCheckCell(row.https) }}	{{ row.notes \|\| '' }}
No results.

Tags: DNS , Devops , Diagnostics , HTTP , PKI , Security

Export to PDF Fullscreen

Include query parameters

Embed:

Customize embed code

Include query parameters

Wrap embed in collapsible toggle

Collapse panel by default

Hide card frame (bare iframe)

Loading behavior

Width

Height

Aspect ratio (width : height)

Max height (optional)

Collapsible heading

Collapsible description (optional)

Allow fullscreen

Referrer policy

Sandbox tokens

Alternative DCV Checker

Domain Control Validation (DCV) can be done via DNS records or HTTP/HTTPS file checks. This tool helps validate that your DNS answers and web endpoints contain the expected unique token for each domain.

How To Use

Paste a CSR to extract CN/SAN domains, or enter domains manually.
Enter the unique token/value provided by your CA.
Enable DNS and/or HTTP/HTTPS checks and set the record name template and path your CA expects.

Notes

This tool cannot infer your CA-specific DCV record names automatically; use the exact DNS name and HTTP path your CA provided.
HTTPS checks may require disabling TLS validation while you are still provisioning the certificate.