Welcome
This is where you find out how to manage domains, DNS records and TLS certificates at regfish - by hand in the interface, or automated through the API. Both work on the same data, so you can switch between them at any time.
Where to start
Section titled “Where to start”You want to get something done. Change a record, turn on DNSSEC, set up DynDNS: that happens in the dash, the web interface to your account. How the interface is laid out shows its structure; the chapters below it walk through the most common tasks.
You want to automate something. Maintain records from a script, renew certificates without manual work, let a server keep its own IP up to date: for that you need an API key (here is how to create one) and Getting started.
You are looking for a specific workflow. The recipes are complete workflows that combine several API calls into one task - with rollback, waiting logic and the pitfalls you would otherwise only discover on the second attempt.
What you will find here
Section titled “What you will find here”The navigation separates two paths: the topic sections describe the interface, while everything technical sits under Automation, split by product area.
| Section | Contents |
|---|---|
| Domains | DNS records, DNSSEC, DynDNS, DNS Doctor, mail check, change history and forwarders |
| SSL/TLS certificates | Ordering, validation types, TLS organizations |
| Security | Domain guardian and certificate watch |
| The mail service: set up a mail program, webmail, spam and blocklists, calendar and contacts | |
| Customer account | Signing in, API keys, plans, account security, payment, team |
| Automation | All 41 endpoints and 15 recipes by product area, plus schemas and the MCP server |
| Tools | certbro for TLS certificates, DNS Doctor for diagnostics |
The API in brief
Section titled “The API in brief”Every call goes to one server and carries a key in the header:
curl -X GET 'https://api.regfish.com/dns/zones' \ -H 'x-api-key: $REGFISH_API_KEY'Responses are JSON and all share the same envelope: success, a code, and the actual payload
under response. Which permission a call needs is stated on every endpoint; if one is missing,
the API rejects the call and names the missing permission.
If you would rather dive straight in: Getting started.