Everything you need to secure a domain — and every domain after it.
Manage domain validation, request edge certificates and inspect provider status. Cloudflare for SaaS handles the managed certificate and renewal, while the dashboard and API keep the setup accessible.
Automatic certificate issuance
A valid certificate, issued at the edge and renewed by Cloudflare.
AutoCertify requests a publicly-trusted TLS certificate after domain control is confirmed. Cloudflare for SaaS manages the certificate and its renewal. Keep validation records in place and route the hostname through the configured Cloudflare service to serve your website over HTTPS.
- Publicly-trusted certificates issued through Cloudflare for SaaS — no self-signed shortcuts
- Provider-managed renewal, with certificate validity available in your dashboard
- Active status requires Cloudflare to confirm both the hostname and its SSL certificate
shop.example.com
Domain · added just now
- Type
- CNAME
- Name
- _acme-challenge.shop.example.com
- Value
- shop.example.com.a1b2c3d4.dcv.cloudflare.com
- TTL
- 300
Example only · use your dashboard values
- Type
- TXT
- Name
- _autocertify-verify.shop.example.com
- Value
- autocertify-domain-verification=7f8c9a1b2d3e4f5061728394a5b6c7d8
- TTL
- 300
Example only · use your dashboard values
Publicly-trusted certificate · active
Cloudflare for SaaS · provider-managed renewal
Custom hostnames & delegated DCV
Verify your hostname with a delegation CNAME and ownership TXT record.
The delegation CNAME lets Cloudflare validate the certificate, while a separate TXT record ties control of the hostname to your workspace. AutoCertify generates both records and checks them before issuance. Keep them published so future validation can use the same setup.
- A CNAME at _acme-challenge and a workspace-specific TXT at _autocertify-verify
- Works on apex domains and individual subdomains — add each hostname once, at any registrar
- Run a live DNS check to confirm both records before requesting a certificate
The two validation records
- Type
- CNAME
- Name
- _acme-challenge.shop.example.com
- Value
- shop.example.com.a1b2c3d4.dcv.cloudflare.com
- TTL
- 300
Example only · use your dashboard values
- Type
- TXT
- Name
- _autocertify-verify.shop.example.com
- Value
- autocertify-domain-verification=7f8c9a1b2d3e4f5061728394a5b6c7d8
- TTL
- 300
Example only · use your dashboard values
Publish the CNAME and ownership TXT using the exact values from your dashboard. These examples show their structure; keep both real records available for future checks.
Merchant self-serve
Built for the shop owner, not just the sysadmin.
Add your hostname, copy its CNAME and TXT records, and follow the instructions for your registrar. The dashboard shows validation and certificate status. A verification link lets your developer view the required records and run a check without sharing your account.
- Step-by-step, registrar-aware instructions with copy buttons — no jargon
- Invite a developer or DNS admin with a domain-specific link to add both records
- Separate DNS validation and certificate states show what still needs attention
Step-by-step for your registrar
Invite your DNS admin
A domain-specific link lets them add both records and check validation.
A programmable certificate API
Automate domain verification and certificate management over REST.
Provision domains, fetch validation records, trigger verification and refresh certificate status with an API key. Owner or admin sessions manage keys and webhook destinations. Platforms and agencies can integrate the same domain workflows into their own systems.
- REST endpoints for domains, certificates, verification links, usage and webhooks
- Bulk domain provisioning and idempotency keys for certificate issuance
- Signed cert.issued, cert.issue_pending and cert.issue_failed webhook events
curl --fail-with-body --silent --show-error \
-X POST https://api.autocertify.net/v1/domains \
-H "Authorization: Bearer $AUTOCERTIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "apex": "shop.example.com" }'
# 201 Created returns the domain with:
# validation.delegation — publish this CNAME
# validation.ownership — publish this TXT
# validation.status — DNS validation state
# cert.status — certificate state
#
# Use the returned DNS values and domain id.
# The quickstart shows the complete verification flow. Certificate status & DNS checks
Inspect validity, refresh provider status and recheck DNS.
Read certificate validity and validation results in one place. A refresh fetches the latest provider state; a domain recheck also validates DNS. Cloudflare manages renewal. For regular monitoring, schedule these checks in your integration and act on the returned status.
- On-demand checks for delegation, ownership and certificate state
- Signed issuance events for newly requested provider certificates
- A single dashboard for every domain, its status and its history
Your domains
4 total · 2 secured-
shop.example.com
Expires in 68 days
-
checkout.example.com
Expires in 71 days
-
go.acme-funnels.com
Checking DNS…
-
help.example.com
Add CNAME and TXT to continue
Provision domains in bulk over the API
Signed events report initial certificate issuance
Teams, clients & audit
Organize domains by client, with roles and a full audit trail.
Group domains by client, manage team roles, and review recorded domain, certificate and account actions. Organization-scoped queries keep workspaces separate; client labels help organize domains inside a workspace.
- Client records for organizing each customer's domains
- Team roles: owner, admin, operator and read-only
- Audit history for domain, certificate and credential operations
# Use a client UUID from POST /v1/clients/query.
curl --fail-with-body --silent --show-error \
-X POST https://api.autocertify.net/v1/domains/query \
-H "Authorization: Bearer $AUTOCERTIFY_TOKEN" \
-H "Content-Type: application/json" \
-d "$(jq -n --arg clientId "$AUTOCERTIFY_CLIENT_ID" \
'{ clientId: $clientId, page: { limit: 50 } }')"
# 200 OK returns matching domains in items.
# Each item includes clientId, validation and cert.
# total counts all matches; nextCursor pages through them. Start with one domain. Grow into the API when you’re ready.
Every capability here works from your first free domain. Nothing is faked — a domain reads “Secured” only when a real, publicly-trusted certificate is genuinely live.