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 collapse the whole ordeal into a single DNS record you add once and never think about again.
You prove you control a domain exactly once, by adding a single record. From that moment on, AutoCertify requests a publicly-trusted certificate, installs it, watches it, and renews it well ahead of expiry — automatically, forever. Merchant-simple on the surface, seriously programmable underneath.
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 on WordPress, Shopify, Wix, Squarespace or ClickFunnels — who just saw “Not Secure” on their own custom domain and has no idea what a CSR is. They add one record and watch it go green.
The web person a client hands the job to. A scoped invite link, one CNAME to _acme-challenge, done — no account sharing, no server access, no renewal cron jobs to babysit ever again.
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.
A domain reads “secured” only when a publicly-trusted certificate is genuinely live. AutoCertify never fakes an active state, never self-signs, and never marks something done that isn't.
You should touch DNS exactly once. Delegated validation means every renewal after that happens on its own — the best certificate is the one you forget you have.
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.