Manage your domains and DNS without leaving the terminal, built for developers who live in their terminals and CI pipelines. What you can do: create, update, and delete DNS records; register domains and manage renewals; issue and manage SSL/TLS certificates; run it in CI with API token auth and structured output. Built in Go, it uses the same foundation as our official client libraries and Terraform provider. Read our announcement: https://blog.dnsimple.com/2026/05/announcing-the-dnsimple-cli/

Free Options

Launch tags:Developer Tools•Artificial Intelligence•GitHub

Launch Team

getviktor.comAn AI coworker that actually does the work

Promoted

Hunter

📌

DNSimple has always positioned itself as the DNS provider for developers, and a CLI is a natural fit with that identity. It meets our core audience exactly where they spend their time, in the terminal. The proof is in the wild: several unofficial DNSimple CLIs have been built by the community over the years, well before this official release. Our goal with the CLI is to make pragmatic access to the DNSimple API as easy as possible. The DNSimple API is one of the most complete in the industry, covering everything from domain registration to DNS records and certificates. It's great when you're building a system on top of it, but it's not the right shape for the everyday task of inspecting a zone, fixing a record, registering a domain, or scripting a quick automation. A CLI is, and it takes our automation story to the next level by exposing the full surface of the API behind a single, consistent command. In the past few months, it has become evident how powerful the combination of a CLI and an AI agent can be. Debugging is more approachable, repetitive work across many resources collapses into a single instruction, and complex workflows can be composed conversationally. We wanted DNSimple to be a first-class citizen in that world, without sacrificing the experience for people who just want to type a command and read the output.

Report

8d ago

Since this shares a foundation with your Terraform provider — where's the line you'd draw between reaching for the CLI versus just declaring records in Terraform? Anything that lives in version control I'd default to the provider, so I'm trying to picture the CLI's home turf: one-off changes, incident response, scripting renewals?

Secondly, The "structured output for CI" line is the part I'd lean on hardest. Is that stable, documented JSON I can pin a script to, or is it formatted-for-humans output that'll shift between releases and quietly break my pipeline? CLI tools live or die on whether their machine output is a contract.

Report

1h ago