# acme-dns/acme-dns

Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely.

Repository: https://github.com/acme-dns/acme-dns
Canonical: https://ross.abutalabs.com/products/acme-dns
Language: Go
License: MIT
License Family: permissive
Topics: acme-challenge, acme-dns, dns-server, tls-certificate, letsencrypt
Last push: 2026-06-08T14:11:46+00:00

## Health v2 (maintenance only)
Score: 83/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 86, release rhythm 69, longevity 100
- inputs: {"age_days": 3580, "days_push": 86, "days_rel": 209, "gap_med": 0.0, "n_releases_24m": 3}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2814, forks 304 (observed 2026-08-28T04:07:23.786710+00:00)

## What it is
acme-dns is a simplified DNS server with a RESTful HTTP API designed to automate ACME DNS challenges for Let's Encrypt and other ACME certificate authorities. It limits API credentials to TXT record updates on dedicated subdomains, so leaked keys have minimal security impact.

## Use cases
- automate letsencrypt dns-01 challenges
- renew tls certificates automatically without exposing dns provider api keys
- self-host a dns server for acme challenges
- issue wildcard certificates via dns challenge
- secure certificate automation for many servers
- serve custom dns records alongside acme challenges

## When to choose
- your dns provider has no API or its API keys grant too much power
- you need automated, unattended certificate renewal with dns-01
- you want wildcard certificates without storing powerful dns credentials on servers

## When to avoid
- http-01 challenges suffice for your setup
- you cannot delegate a subdomain via CNAME from your zone
- you need a full-featured authoritative dns server

## Facets
- artifact type: service
- maturity: active
- function: networking, http-server, api-framework, security, self-hosted
- domain: security, networking, self-hosted, developer-tools
- platform: go, self-hosted, cross-platform
- tags: acme, letsencrypt, dns-challenge, txt-records, tls-certificates, certificate-automation, automation, linux, docker

## Member repositories
- acme-dns/acme-dns (main) score 83

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:07:23.786710+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T08:13:28.311861+00:00, confidence not recorded.
  - readme: https://github.com/acme-dns/acme-dns (fetched 2026-08-28T04:07:23.786710+00:00, sha 1dcb5a6c0d1e)
- Data as of 2026-08-30T08:39:29.467469+00:00.