How to Register a Free .is-a.dev Subdomain

To register a free .is-a.dev subdomain, you check availability on the is-a.dev homepage, then go to the is-a-dev/register repository on GitHub and follow the instructions there. Registration is handled through GitHub rather than a signup form on the website, so you need a GitHub account and some familiarity with the repository workflow (typically a pull request adding your subdomain's configuration file).

What is-a.dev offers

is-a.dev is a service that gives developers free .is-a.dev subdomains. According to the site, the project "is a free service for developers and will stay that way," and it accepts donations to keep running. It has also launched .is-a.bot subdomains, which are claimed through GitHub as well.

A subdomain is useful when you want a short, recognizable hostname for a personal site, portfolio, or project without buying a domain. You point the subdomain at infrastructure you already control (for example, a GitHub Pages site or your own server) by configuring DNS records in your registration file.

Step 1: Check whether your subdomain is available

On the is-a.dev homepage there is a Check Subdomain Availability tool. Enter the subdomain you want (the part before .is-a.dev) and submit it. The tool returns one of these results:

Check availability first so you don't spend time preparing a registration for a name that is already taken or reserved.

Step 2: Register through the GitHub repository

The site's instructions are explicit: "To register your own subdomain, visit the is-a-dev/register repository on GitHub and follow the provided instructions." The exact file format, required fields, and review process are defined in that repository, so read its README and contributing guidance before submitting.

At a high level, the workflow looks like this:

1. Sign in to GitHub (create an account if you don't have one).
2. Open the is-a-dev/register repository.
3. Read the repository's instructions for adding a subdomain.
4. Add your subdomain's configuration file, following the format the repository specifies. This is where you define the DNS records that point your subdomain to your hosting.
5. Submit your change as a pull request.
6. Wait for maintainers to review and merge it. Once merged, your subdomain becomes active.

The same GitHub-based process applies to .is-a.bot subdomains.

What to prepare before you submit

• The exact subdomain name you want, already confirmed as available.
• Your DNS target. Decide where the subdomain should point — for example, a CNAME to your hosting provider's hostname, or A/AAAA records to an IP address. The repository's instructions define which record types are accepted.
• A GitHub account in good standing, since the request is made as a pull request.

Common snags

• Skipping the availability check. If the name is owned or reserved, your pull request will be rejected. Check first.
• Guessing the file format. The repository is the source of truth for the configuration schema. Copy an existing entry as a template rather than inventing fields.
• Wrong DNS values. A merged registration with incorrect records will resolve to nothing or to the wrong place. Verify your target hostname or IP before submitting.
• Expecting instant activation. Because registration goes through a pull request, there is a review step; your subdomain works only after the change is merged.

After registration

Once your subdomain is live, you manage changes (updating DNS targets, for example) through the same repository. If you ever suspect a subdomain is abusing the service, the site provides a Report Abuse link. Documentation, Terms of Service, a contact link, a GitHub link, and a Discord server are all listed under Important Links on the homepage if you need help or want to check the rules.