# SimpleACME > Delegated DNS-01 challenge automation with one permanent CNAME per challenge owner. No normal DNS-provider API token or inbound HTTP challenge endpoint. ## Product facts SimpleACME manages TXT challenge updates, not certificate issuance, private keys or installation. The customer's ACME client performs those tasks. Paid yearly access is required for /update. One single-domain demo can prepare DNS but cannot update it. Provider pause/cancel does not shorten the paid term; approved refunds and chargebacks disable updates. TXT activity is not proof of a completed certificate renewal. ## Documentation - [Service certificate guides](https://simpleacme.com/services) - [DNS provider directory](https://simpleacme.com/dns-providers) - [Self-updating sitemap](https://simpleacme.com/sitemap.xml) - [Published article RSS](https://simpleacme.com/blog/feed.xml) - [Service](https://simpleacme.com/) - [FAQ](https://simpleacme.com/faq) - [Client integration and MCP](https://simpleacme.com/developers) - [Traefik](https://simpleacme.com/integrations/traefik) - [win-acme](https://simpleacme.com/integrations/win-acme) - [Certbot](https://simpleacme.com/integrations/certbot) - [OpenAPI](https://simpleacme.com/openapi.json) ## MCP Endpoint: https://simpleacme.com/mcp Transport: Streamable HTTP, JSON responses, protocol 2025-11-25. Public read-only setup guidance and placeholder configuration generation. No credentials, registration or DNS mutation tools. Connect explicitly from a compatible client; availability does not imply automatic discovery by all AI systems. ## Public articles - [RFC 2136 and CNAME delegation are different DNS-01 controls](https://simpleacme.com/blog/rfc2136-cname-dns01): RFC 2136 and CNAME delegation are different DNS-01 controls. Practical diagnosis, a SimpleACME DNS-01 workflow, and checks for safe unattended renewal. - [ACME address already in use: remove the challenge port conflict](https://simpleacme.com/blog/acme-address-already-in-use): ACME address already in use: remove the challenge port conflict. Practical diagnosis, a SimpleACME DNS-01 workflow, and checks for safe unattended renewal. - [Nginx Proxy Manager and Tailscale: keep validation separate](https://simpleacme.com/blog/nginx-proxy-manager-tailscale-dns01): Nginx Proxy Manager and Tailscale: keep validation separate. Practical diagnosis, a SimpleACME DNS-01 workflow, and checks for safe unattended renewal. - [GoDaddy add-TXT failures: separate API access from DNS validation](https://simpleacme.com/blog/godaddy-add-txt-error): GoDaddy add-TXT failures: separate API access from DNS validation. Practical diagnosis, a SimpleACME DNS-01 workflow, and checks for safe unattended renewal. - [What to verify after an ACME certificate rotation](https://simpleacme.com/blog/certificate-rotation-checks): What to verify after an ACME certificate rotation. Diagnose the failure, use delegated DNS-01 where it fits, and verify renewal and deployment with SimpleACME. - [OPNsense and Nginx Proxy Manager need a clear certificate owner](https://simpleacme.com/blog/opnsense-npm-certificate-owner): OPNsense and Nginx Proxy Manager need a clear certificate owner. Practical diagnosis, a SimpleACME DNS-01 workflow, and checks for safe unattended renewal. - [Renew a private Synology NAS certificate without exposing HTTP](https://simpleacme.com/blog/synology-private-nas-renewal): Renew a private Synology NAS certificate without exposing HTTP. Practical diagnosis, a SimpleACME DNS-01 workflow, and checks for safe unattended renewal. - [A Docker renewal stack needs persistent state and a deploy step](https://simpleacme.com/blog/certbot-docker-renewal-stack): A Docker renewal stack needs persistent state and a deploy step. Practical diagnosis, a SimpleACME DNS-01 workflow, and checks for safe unattended renewal. - [pfSense ACME succeeds manually but does not renew automatically](https://simpleacme.com/blog/pfsense-acme-scheduler): pfSense ACME succeeds manually but does not renew automatically. Practical diagnosis, a SimpleACME DNS-01 workflow, and checks for safe unattended renewal. - [Troubleshoot pfSense certificate renewal one stage at a time](https://simpleacme.com/blog/pfsense-renewal-stage-troubleshooting): Troubleshoot pfSense certificate renewal one stage at a time. Practical diagnosis, a SimpleACME DNS-01 workflow, and checks for safe unattended renewal. - [Nginx certificates: when to move from HTTP-01 to delegated DNS-01](https://simpleacme.com/blog/nginx-http01-to-dns01): Keep HTTP-01 for a simple public Nginx site, or use SimpleACME DNS-01 when wildcard names, private services or complex challenge routing change the requirements. - [Why Certbot asks for a different challenge record again](https://simpleacme.com/blog/certbot-repeats-cname-prompt): Why Certbot asks for a different challenge record again. Diagnose the failure, use delegated DNS-01 where it fits, and verify renewal and deployment with SimpleACME. - [Automate wildcard validation without moving nameservers](https://simpleacme.com/blog/delegated-dns-not-nameserver-migration): Automate wildcard validation without moving nameservers. Diagnose the failure, use delegated DNS-01 where it fits, and verify renewal and deployment with SimpleACME. - [Wildcard and apex names can share a challenge owner](https://simpleacme.com/blog/wildcard-apex-same-challenge-owner): Wildcard and apex names can share a challenge owner. Diagnose the failure, use delegated DNS-01 where it fits, and verify renewal and deployment with SimpleACME. - [DNS-01 does not require your main DNS provider's API](https://simpleacme.com/blog/dns01-without-main-zone-api): DNS-01 does not require your main DNS provider's API. Diagnose the failure, use delegated DNS-01 where it fits, and verify renewal and deployment with SimpleACME. - [Wildcard renewal still needs working DNS validation](https://simpleacme.com/blog/wildcard-renewal-still-needs-dns): Wildcard renewal still needs working DNS validation. Diagnose the failure, use delegated DNS-01 where it fits, and verify renewal and deployment with SimpleACME. - [MikroTik certificates with an external DNS-01 client](https://simpleacme.com/blog/mikrotik-external-acme-client): MikroTik certificates with an external DNS-01 client. Diagnose the failure, use delegated DNS-01 where it fits, and verify renewal and deployment with SimpleACME. - [Namecheap domains: automate DNS-01 without a zone API token](https://simpleacme.com/blog/namecheap-dns01-without-api): Namecheap domains: automate DNS-01 without a zone API token. Practical diagnosis, a SimpleACME DNS-01 workflow, and checks for safe unattended renewal. - [Repair an existing Certbot renewal without creating duplicates](https://simpleacme.com/blog/certbot-existing-lineage-renewal): Repair an existing Certbot renewal without creating duplicates. Practical diagnosis, a SimpleACME DNS-01 workflow, and checks for safe unattended renewal. - [Manual DNS challenges need fresh TXT values on renewal](https://simpleacme.com/blog/manual-dns-txt-every-renewal): Manual DNS challenges need fresh TXT values on renewal. Diagnose the failure, use delegated DNS-01 where it fits, and verify renewal and deployment with SimpleACME. - [An ACME challenge CNAME does not move your website](https://simpleacme.com/blog/acme-cname-web-records): An ACME challenge CNAME does not move your website. Diagnose the failure, use delegated DNS-01 where it fits, and verify renewal and deployment with SimpleACME. - [Choose a challenge method for a mixed self-hosted stack](https://simpleacme.com/blog/choose-challenge-private-stack): Choose a challenge method for a mixed self-hosted stack. Diagnose the failure, use delegated DNS-01 where it fits, and verify renewal and deployment with SimpleACME. - [Trusted certificates for servers that are not internet-facing](https://simpleacme.com/blog/local-server-public-certificate): Trusted certificates for servers that are not internet-facing. Practical diagnosis, a SimpleACME DNS-01 workflow, and checks for safe unattended renewal. - [Pi-hole and Unbound interfere with DNS-01 checks](https://simpleacme.com/blog/pihole-unbound-dns01): Pi-hole and Unbound interfere with DNS-01 checks. Diagnose the failure, use delegated DNS-01 where it fits, and verify renewal and deployment with SimpleACME. - [Stop finding expired certificates by accident](https://simpleacme.com/blog/certificate-expiry-notifications): Stop finding expired certificates by accident. Diagnose the failure, use delegated DNS-01 where it fits, and verify renewal and deployment with SimpleACME. - [Certificate automation: give every renewal a clear owner](https://simpleacme.com/blog/certificate-automation-ownership): Certificate automation: give every renewal a clear owner. Practical diagnosis, a SimpleACME DNS-01 workflow, and checks for safe unattended renewal. - [Internal certificates when your DNS provider has no API](https://simpleacme.com/blog/internal-services-no-dns-api): Internal certificates when your DNS provider has no API. Diagnose the failure, use delegated DNS-01 where it fits, and verify renewal and deployment with SimpleACME. - [One renewal host, several certificate destinations](https://simpleacme.com/blog/multi-host-certificate-deployment): One renewal host, several certificate destinations. Diagnose the failure, use delegated DNS-01 where it fits, and verify renewal and deployment with SimpleACME. - [Make a certificate renewal job genuinely unattended](https://simpleacme.com/blog/unattended-renewal-job-design): Make a certificate renewal job genuinely unattended. Diagnose the failure, use delegated DNS-01 where it fits, and verify renewal and deployment with SimpleACME. - [win-acme renewals fail after port 80 is blocked](https://simpleacme.com/blog/win-acme-blocked-port-80): win-acme renewals fail after port 80 is blocked. Diagnose the failure, use delegated DNS-01 where it fits, and verify renewal and deployment with SimpleACME. - [Certbot in Docker: persistent DNS-01 renewals with bind mounts](https://simpleacme.com/blog/certbot-docker-dns01): Keep Certbot certificates, account state and SimpleACME credentials across container recreation. Plan a repeatable DNS-01 renewal and deployment workflow. - [Build a useful certificate inventory before automating](https://simpleacme.com/blog/certificate-inventory-single-domains): Build a useful certificate inventory before automating. Diagnose the failure, use delegated DNS-01 where it fits, and verify renewal and deployment with SimpleACME. - [One permanent CNAME for repeated certificate renewals](https://simpleacme.com/blog/permanent-cname-certificate-renewals): Understand how a fixed ACME challenge CNAME points to changing TXT authorization values, and how to preserve it across renewals and DNS migrations. - [Wildcard certificates with one permanent challenge CNAME](https://simpleacme.com/blog/wildcard-certificates-one-cname): Secure first-level subdomains using wildcard DNS-01 validation. Understand wildcard coverage, the apex name and permanent CNAME delegation with SimpleACME. - [Troubleshoot DNS-01 certificate failures in the right order](https://simpleacme.com/blog/troubleshoot-acme-dns01): Diagnose CNAME, authentication, DNS propagation, client and deployment failures separately. Use SimpleACME's TXT timeline as one part of the evidence. - [Certificates for private services without opening port 80](https://simpleacme.com/blog/private-services-without-port-80): Use public DNS validation for private dashboards, VPNs and management interfaces. SimpleACME removes the need for a public HTTP challenge endpoint. - [Let's Encrypt without a DNS-provider API: one CNAME is enough](https://simpleacme.com/blog/lets-encrypt-without-dns-api): Keep your DNS provider and automate DNS-01 through a delegated challenge record. Learn what SimpleACME changes and what your ACME client still handles. - [Windows certificates with win-acme and SimpleACME DNS-01](https://simpleacme.com/blog/win-acme-windows-dns01): Prepare DNS-01 validation for IIS and Windows services using win-acme, a permanent CNAME and SimpleACME's account-specific update credentials. - [Traefik DNS-01 with SimpleACME: prepare the account before renewal](https://simpleacme.com/blog/traefik-dns01-simpleacme): Connect Traefik's ACME-DNS provider to an existing SimpleACME registration. Keep the challenge CNAME and persistent account storage ready for automatic renewals. - [Certbot DNS-01 hooks without a DNS-provider API token](https://simpleacme.com/blog/certbot-dns01-hooks-simpleacme): Use Certbot authentication hooks with a delegated SimpleACME challenge record. Separate TXT updates, propagation checks and certificate deployment. - [Reduce DNS credential exposure in certificate automation](https://simpleacme.com/blog/secure-dns-validation-without-zone-api-keys): Compare full-zone tokens, scoped DNS credentials and delegated ACME challenge accounts. Learn where SimpleACME narrows the DNS write surface. - [HTTP-01 vs DNS-01: choose the easier certificate workflow](https://simpleacme.com/blog/http-01-vs-dns-01): Compare HTTP-01 and DNS-01 for public websites, private services and wildcard certificates. See when SimpleACME removes the DNS-provider API work.