is-a.dev: A Free .is-a.dev Subdomain Service for Developer Personal Sites

What is-a.dev Is and Who It Is For

is-a.dev is a community-run service that provides free .is-a.dev subdomains to developers for their personal websites. The repository at is-a-dev/register is where the subdomain registry lives: each registered subdomain corresponds to a file in the domains/ directory, and the DNS configuration is managed through dnsconfig.js.

The service targets individual developers who want a professional-looking personal domain for a portfolio, blog, or project page. The appeal is that a subdomain like yourname.is-a.dev reads as developer-specific: the .is-a.dev pattern implies the site belongs to someone who is a developer.

The service is MIT-licensed and community-funded. It is supported by Cloudflare's Project Alexandria program for DNS management, and it accepts donations at donate.is-a.dev and sponsorships. The README notes that all current and past supporters are listed at is-a.dev/thanks.

How the Registration Process Works

Unlike services that provision subdomains through a web interface, is-a.dev registration uses a GitHub pull request workflow. The steps are:

1. Fork the is-a-dev/register repository. 2. Follow the documentation at docs.is-a.dev to add a file in the domains/ directory specifying your subdomain and DNS records. 3. Submit a pull request to the repository. 4. A maintainer reviews the PR. If changes are needed, the maintainer will request them. 5. Once the PR is merged, the DNS records are published within a few minutes.

The README contains one pointed warning: do not use AI to generate the pull request. The README states this "WILL always get it wrong and will delay you getting a domain." This is a practical note, not a policy prohibition: the structure of the domain file must match the service's exact format, and AI tools apparently generate submissions that fail validation.

If a requested subdomain change is not made after a maintainer requests it, the PR will be rejected. Once the PR is merged, the .is-a.dev subdomain is live and the registrant keeps it as long as the registration remains active.

Repository Structure and How DNS Is Managed

The repository has a clear structure:

- domains/: each file represents one registered subdomain, with the owner's DNS record configuration. - dnsconfig.js: the DNS configuration file used to manage records through Cloudflare. - tests/: validation tests that run against the domain files to check for formatting and configuration errors. - util/: scripts for managing reserved subdomains and checking reservation order.

The test suite uses the ava test framework and runs against JavaScript test files in the tests/ directory. When a PR is submitted, the CI runs these tests to validate the new domain file before a maintainer reviews it. Prettier is used for code formatting consistency across the domain files.

DNS is managed through Cloudflare's Project Alexandria program, which provides DNS infrastructure at no cost to the project. Cloudflare's DNS network handles resolution globally once a PR is merged and the records are published.

Terms of Service and Abuse Reporting

The repository includes a TERMS_OF_SERVICE.md file with the conditions under which subdomains are provided. The is-a.dev service has terms that govern acceptable use. The README notes that only critical announcements are posted on GitHub; everything else, including service updates and downtime notifications, is posted in the Discord server at discord.gg/is-a-dev-830872854677422150.

If a registered subdomain is found to be abused or violating the terms of service, anyone can report it by creating a GitHub issue using the report-abuse template. The issue should include relevant evidence. The maintainers can then review and take down the subdomain.

The README does not specify what types of sites are prohibited beyond referring to the terms of service. Reading TERMS_OF_SERVICE.md in the repository is the definitive source for what is and is not allowed under a .is-a.dev subdomain.

Limitations and Cases Where is-a.dev Is Not the Right Fit

The core limitation of is-a.dev is that it is a community-run service with no SLA. PR review times depend on volunteer availability. The README keeps track of this through Discord announcements, and there is no commitment to a specific turnaround time. An engineer who needs a subdomain on a deadline should not count on is-a.dev to deliver it in a predictable window.

The subdomain is tied to the service. If is-a.dev shuts down or changes its policies, registrations are lost. This is a fundamental risk of any free subdomain service rather than a specific criticism of this project, but it means is-a.dev is not appropriate for a business-critical domain.

The registration format is specific: the domain file must match the exact structure the service expects. The README's warning about AI-generated submissions highlights that the format is precise enough to trip up automated tools. Engineers who are not comfortable reading the documentation at docs.is-a.dev and following it carefully will encounter rejected PRs.

The service is also intended for personal developer sites. Using a .is-a.dev subdomain for a commercial product or a client site is a different use case than what the service is designed for.

is-a.dev vs. GitHub Pages Subdomains

GitHub Pages automatically provides a free subdomain at username.github.io for any repository set up as a GitHub Pages site. This is the most common baseline comparison for is-a.dev. The difference is control over the subdomain name.

A GitHub Pages subdomain is always username.github.io, where username is your GitHub account name. If your account name is not a natural representation of your developer identity, the subdomain reflects that. is-a.dev lets you choose any available subdomain under .is-a.dev, so you can claim something like firstname.is-a.dev or a project-specific name.

GitHub Pages requires no PR process: publishing a site to GitHub Pages is done through repository settings or a specific branch. is-a.dev requires submitting and waiting for a PR review. For developers who already have GitHub Pages set up and just want a different subdomain, is-a.dev provides an alternative without requiring changes to the underlying hosting.

The .is-a.bot Service and Related Projects

The is-a.dev organization also runs a .is-a.bot subdomain service, noted in the repository README with a link to github.com/free-domains/is-a.bot. This follows the same pull request-based registration model and is intended for bot projects rather than personal websites.

Both services are part of a broader pattern of community-operated free subdomain registries on GitHub, where the registry is maintained as a public repository and registrations are handled through pull requests. This approach makes the registration history transparent and auditable: the entire history of subdomain registrations, removals, and changes is in the git log.

The last push to the is-a-dev/register repository was on 2026-09-27, indicating that the service is actively reviewing and merging PRs. The MIT license on the repository covers the tooling and configuration code, not the registered subdomains themselves, which are governed by the terms of service.

Editorial conclusion

is-a.dev is appropriate for individual developers who want a memorable personal domain without paying for a top-level domain registration. The pull request process works well for engineers comfortable with GitHub but adds friction compared to services that provision subdomains through a web form. The service depends on volunteer PR reviews, so turnaround time is not guaranteed. Before submitting a registration, read the documentation at docs.is-a.dev carefully, since the README explicitly warns that AI-generated PR submissions are consistently incorrect and will be rejected. The DNS infrastructure is backed by Cloudflare through the Project Alexandria program.

Frequently asked questions

Official sources

1. is-a-dev/register on GitHub
2. Issues
3. License: MIT
4. Project website
5. README