Skip to content
How it works

From “Not Secure” to a padlock — in four unhurried steps.

Publish both validation records and verify your hostname. Cloudflare manages the certificate; your compatible hosting route serves the site over HTTPS.

Before

After

Add your domain and AutoCertify checks it live as you go — you watch it move from pending → verifying → secured without ever guessing where things stand.

What actually happens, step by step.

Add the hostname, configure DNS, verify issuance and keep validation healthy. Each step explains what you control and what the provider manages.

  1. 1

    Add your domain

    Sign in and add the exact hostname you want to secure. Confirm that your hosting setup can route it through the configured Cloudflare for SaaS service; certificate validation alone does not change website traffic.

    shop.example.com Add domain

    No CSRs, no key files, no server access.

  2. 2

    Add two validation records

    Copy the delegation CNAME and workspace ownership TXT record into your DNS provider. Use the exact values from your dashboard, or send your developer a verification link to add both.

    1. Delegation CNAME Waiting for DNS
    Type
    CNAME
    Name
    _acme-challenge.shop.example.com
    Value
    shop.example.com.a1b2c3d4.dcv.cloudflare.com
    TTL
    300

    Example only · use your dashboard values

    2. Workspace ownership TXT Waiting for DNS
    Type
    TXT
    Name
    _autocertify-verify.shop.example.com
    Value
    autocertify-domain-verification=7f8c9a1b2d3e4f5061728394a5b6c7d8
    TTL
    300

    Example only · use your dashboard values

    Use the exact records from your dashboard, with its copy buttons and registrar instructions. These examples illustrate the required CNAME and TXT. Run a live check after both have propagated.

    GoDaddyNamecheapCloudflareSquarespaceWixPorkbun

    Rather hand it off?

    Send a verification link to your developer or DNS admin so they can add both records.

  3. 3

    Verify and request the certificate

    Run verification after both records propagate. Successful validation starts issuance automatically. Refresh status until Cloudflare reports both the hostname and certificate active, then confirm HTTPS through your configured traffic route.

    AutoCertify validates control and issues a publicly-trusted certificate through Cloudflare for SaaS. Refresh until the hostname and SSL are active, then confirm the site serves HTTPS through the configured traffic route.

  4. 4

    Keep validation healthy

    Cloudflare manages renewal while the hostname remains eligible and correctly configured. Keep both DNS records published. Recheck DNS and refresh certificate status from the dashboard or your integration to catch configuration changes.

    Provider-managed renewal Recheck DNS on demand Signed issuance events
The honesty guarantee

A domain reads “Secured” only when a real certificate is genuinely live.

AutoCertify never marks a hostname active until Cloudflare for SaaS confirms both the hostname and its SSL are live. No faked padlocks, no self-signed shortcuts, no “done” that isn’t. The status reflects the last provider check. Your hostname must also route through the service before that edge certificate can secure website traffic.

  • Publicly-trusted certificates via Cloudflare for SaaS Managed CA — never self-signed
  • Managed renewal through Cloudflare while validation and hostname eligibility remain intact
  • DNS rechecks, provider refresh and signed certificate-issuance events

2

Validation records: a CNAME and ownership TXT

DV

Domain-validated certificates via Cloudflare for SaaS

0

Private keys or CSRs to manage yourself

API

Domain, certificate and verification workflows

Start with your first hostname.

Start free — no card required. Add your hostname, publish both validation records and follow the steps to a managed certificate.

Secure a domain free Prefer the API? Read the quickstart