Browsers turned plain HTTP into a bright “Not Secure” warning — and rightly so. But for millions of custom domains living on builders, funnels and multi-domain fleets, earning a real certificate is still a mess of CSRs, key files and renewal cron jobs. AutoCertify exists to make that mess disappear.
HTTPS stopped being optional years ago. A missing certificate now means a scary interstitial, a “Not Secure” badge in the address bar and search engines quietly ranking you lower. For the sites a big platform already secures for you, that's a non-issue — the platform handles it.
The trouble is every domain that falls through the cracks: a custom domain pointed at a no-SSL page builder, a marketing funnel on its own URL, a fleet of client sites, an internal tool nobody wants to touch. Securing those the “proper” way means learning about certificate signing requests, generating keys, wrangling an ACME client and then remembering to renew every few months — forever.
So people either ship insecure, or pay a specialist, or set a calendar reminder and cross their fingers. None of that is acceptable in a world that punishes plain HTTP. We built AutoCertify to turn validation into clear DNS steps and certificate management into a repeatable dashboard or API workflow.
Publish the delegation CNAME and workspace ownership TXT, verify control, and request a publicly-trusted certificate. Cloudflare for SaaS manages the edge certificate and renewal. AutoCertify gives you the dashboard and API to inspect DNS validation and refresh provider status.
AutoCertify is built and operated by Pcnaid Inc., an independent software company based in Texas. We're a small team that would rather ship one thing that works flawlessly than a pile of features that mostly do.
The dashboard speaks plain language to the shop owner. The API speaks fluent REST to the platform. Nobody has to meet in the middle.
The person running a store or landing page who needs help securing a custom hostname. The dashboard explains the CNAME and TXT records, verification and certificate status; hosting must support the configured Cloudflare traffic route.
The web person a client hands the job to. A domain-specific verification link shows both required DNS records and lets them check validation without sharing the client's account. Cloudflare handles the managed certificate and renewal.
Teams securing hundreds or thousands of customer domains. The same platform that hand-holds a first-timer exposes a clean REST API, signed webhooks and bulk provisioning underneath.
These aren't slogans on a wall — they're the rules we hold the product to, especially when a shortcut would be easier.
Active status records Cloudflare's confirmation that the hostname and its certificate are active. Refresh to retrieve current provider state, and confirm the website's HTTPS connection through its configured traffic route.
A delegation CNAME and workspace ownership TXT record support repeat validation. Keep them in place while Cloudflare manages renewal, and recheck if your DNS or hosting configuration changes.
SSL is intimidating enough. Every screen is written for the shop owner having a bad morning, not the engineer who already knows what a CSR is.
The same platform that hand-holds a first-timer exposes a clean API for the team automating ten thousand domains. Simple on top, serious underneath.
It would be trivial to paint a green “Secured” badge the second you add a record and hope the certificate catches up. We don't. A domain reads “Active” only when a publicly-trusted certificate is genuinely live and both the hostname and its SSL are confirmed. No self-signed shortcuts, no faked states, no marking something done that isn't. If we can't show you a real padlock, we'll show you exactly where things stand instead.
Your first domain is free, forever — no card required. Have questions first? We're happy to help.