From IP address to HTTPS in a minute.
DNSMint gives any server a real hostname with one API call. Point Caddy at it, the certificate issues itself, and traffic flows straight from your users to your machine.
$ curl -X POST https://dnsmint.com/api/v1/hostnames \ -H "Authorization: Bearer $DNSMINT_KEY" \ -d '{"ip": "34.120.50.10"}' { "hostname": "q7k4m2.pool-3.mintzone.net", "ip": "34.120.50.10", "record_type": "A", "status": "live" } $ dig +short q7k4m2.pool-3.mintzone.net 34.120.50.10
Machines now create machines
Agents rent a VM, run a job, and tear it down before lunch. Every one of those machines needs a URL the outside world can reach: an MCP server your customers connect to, a webhook receiver, an inference endpoint, a browser the agent drives remotely. Each of those URLs has to be HTTPS, because every modern client insists on it.
Getting a machine online used to be a human ritual. Buy a domain, configure the zone, point a record, wait for propagation, wire up certificates. Software that creates infrastructure at 3am cannot file that paperwork. DNSMint compresses the whole ritual into one API call that a program makes by itself.
DNSMint treats the machine as the customer. There is nothing to own before the first hostname, every step from key to certificate is an API call, and scoped tokens, hard caps, and self-expiring names make it safe to hand the whole loop to automation.
How it works
- 1
Create an API key
Sign up and mint a key. Agents and CI pipelines can complete this step on their own.
- 2
Register an IP
POST the address and your hostname comes back in the same response. IPv4 and IPv6 both work.
- 3
It resolves everywhere
Our nameservers answer worldwide within seconds, and the API flips the record to live the moment it is served, so your tooling knows exactly when to proceed.
- 4
HTTPS turns on
Point Caddy or certbot at the name and Let's Encrypt issues a free certificate automatically. Private IPs and wildcards go through the built-in DNS-01 API.
What runs on minted names
MCP servers
Agent platforms expose tools over HTTP. Each customer's MCP server boots, registers its IP, and greets the world with its own hostname and certificate.
Agent-spawned compute
An agent rents a VM and hands back a working HTTPS URL in the same run. When the machine quietly dies a week later, the name retires itself.
Preview environments
CI mints a hostname per pull request. The name stays alive exactly as long as the branch does, then cleans up after itself.
Device fleets
Thousands of boxes on changing addresses, each holding a certificate for its own name. DNS-01 issuance works even when the devices live on private networks.
Webhook receivers
A real HTTPS endpoint for a test, minted in seconds and gone when you stop renewing it.
Self-hosted services
Home Assistant, a NAS, or a game server gets a proper name and a real certificate, with the domain and DNS handled for you.
What you get
The domain is included
Your first hostname requires owning exactly nothing. The domain arrives with it, already registered, delegated, and defended, and the nameserver ops are our job. On paid plans the domain is exclusively yours, with certificate rate limits to match.
Direct connections
DNSMint's job ends at the DNS answer. Your users connect straight to your server: your bandwidth, your TLS keys, your latency. There is no proxy tier to pay for, tune, or wait on.
Certificates for every network
Public servers get certificates the standard way. Machines inside your VPC get them through our DNS-01 API, which publishes the validation record that public CAs check. Both paths finish in about a minute.
Unlimited by default
DNS lookups, API reads, and renewals are unlimited on every plan. You pay for names and domains, so a traffic spike costs you exactly nothing.
Safe to hand to an agent
Keys, hostnames, renewal, release: every step is an HTTP call an agent can make alone. Scoped tokens confine each ACME client to one name, caps bound the blast radius, and abandoned names expire on their own.
Works with your stack
Caddy, Traefik, certbot, lego, and cert-manager all work unmodified: the DNS-01 API speaks the acme-dns protocol they already support. For most setups the integration is one line of config.
Free to start, month to month after
25 hostnames free. Your own domain from $9.99. Private networks and teams from $29.99. Queries stay unlimited on every plan.