A domain request is a code contribution
is-a.dev offers a wonderfully legible address for a developer site: name.is-a.dev. The clever part is how little custom registration machinery sits between the applicant and the DNS data. Each subdomain is a JSON file in the public domains directory. A pull request proposes a new file or edits an existing one, automated checks validate it, and a maintainer decides whether it should join the registry. DNSControl translates accepted records for Cloudflare.
For a portfolio, this is nicer than a long hosting-provider URL and costs nothing. It also teaches a small but real slice of web operations. The applicant has to understand what an A, CNAME, or TXT record does, connect a custom domain at the host, and respond to review feedback. The result feels earned without requiring a registrar purchase.
The repository supports much more than one CNAME. Its configuration handles A, AAAA, CAA, CNAME, DS, MX, NS, SRV, TLSA, TXT, and a service-specific URL redirect. Nested names use dotted filenames, so the owner of alex.is-a.dev can request blog.alex.is-a.dev. Cloudflare proxying is optional. NS delegation exists, but the FAQ restricts it to approved cases because it hands the user much wider DNS control.
Registration is easy only after the site is ready
The quickstart begins with requirements, not Git commands. The website must be at least somewhat complete, must concern the applicant or a noncommercial software project, and must fit the terms. Placeholder pages and thin demos are poor candidates. Applicants fork the repository, create a lowercase JSON filename, add their GitHub username and DNS records, then open a pull request using the supplied template. The description must include a live preview link and screenshot.
That is not difficult for someone comfortable with GitHub, but it is more ceremony than filling in a registrar form. Vercel may require a second file for its TXT verification. GitHub Pages needs the custom domain configured after merge and HTTPS enabled. Other hosts have their own record values. The documentation covers Cloudflare Pages, Netlify, Railway, Firebase, Render, Replit, mail services, and several other common destinations, which greatly reduces guesswork.
Tests provide useful guardrails. The AVA suite checks filename shape, required owner and record fields, duplicate keys, reserved names, IP and hostname formats, conflicting records, nested-domain ownership, proxy rules, and restrictions such as pairing DS with NS. A green check does not guarantee acceptance. Maintainers inspect the site and terms compliance, and the contribution policy reserves the right to deny any request for any reason.
Review is the unpredictable step. The FAQ says volunteers handle the queue as a side project and gives no fixed turnaround. On August 16, 2026, GitHub showed about 100 open pull requests but only one open issue, with maintainers merging batches of registrations that day. Once a pull request is merged, the README says records should publish within minutes. Applicants still need to watch the pull request because ignored change requests lead to rejection.
The terms are narrower than the friendly name suggests
This is a service for individuals, developer groups, and noncommercial software work, not a free domain substitute for every website. Users must be at least 13 and register through an individual GitHub account. Commercial and political sites are prohibited. So are proxies and VPNs, general blogs unrelated to software development, course sites, conversational AI apps similar to major chat assistants, and several other high-abuse categories. Root subdomains generally cannot hide the site behind a login page.
The AI rule is especially strict. Using AI to build a compliant website is allowed, but using an AI coding tool to create or modify the registration pull request may cause closure, account restrictions, or removal of the author's existing domains. Whether one agrees with that policy or not, it is explicit. Applicants who routinely automate repository chores should do this one manually.
A free subdomain is also not property. is-a.dev retains the main domain and offers the service as-is, without promises of uptime, support, or permanence. It may deny a request or terminate a name at any time. Terms can change immediately when posted, with notices placed on the website or Discord. That governance is reasonable for a volunteer-run free service, but it makes the address unsuitable as the sole identity for a company, paid product, or critical account recovery flow.
Public Git history creates another tradeoff. Ownership and DNS data are supposed to be visible, which makes changes inspectable. Email is not required by the documented owner schema, so omit it unless a workflow truly needs it. The FAQ warns that sensitive data in a merged pull request cannot be retroactively removed. Never paste provider secrets or private verification material without confirming it is meant to become a public DNS record.
Healthy infrastructure, no release train
The project had about 10,984 stars and a fresh push on August 16, 2026. Pull requests were being reviewed, merged, and rejected throughout the same day. That combination is stronger evidence of health than a tag would be for a registry. GitHub's latest-release endpoint returns no release, which is unsurprising because the product changes through domain files, tests, terms, and DNS publishing workflows rather than packaged versions.
The code is GPL-3.0 licensed, the service has operated since 2020, and the repository includes CI, DNS publication, stale-request handling, a security contact, abuse reporting, and detailed terms. Cloudflare sponsors the infrastructure through Project Alexandria. None of that creates an uptime promise, but it shows a mature operating process around a very busy community resource.
is-a.dev is worth using for a public developer portfolio or qualifying hobby project. It looks good, costs nothing, supports real DNS configurations, and has documentation that anticipates common hosting mistakes. Keep a provider URL as a fallback, respect the narrow acceptable-use rules, and buy a domain when permanence or independent control starts to matter.