Our sandbox installed is-a-dev/register in 6 seconds and passed its tests in 9 seconds at commit 204e47b. Use the service for a personal developer website if you can manage a pull request and keep the site portable. Avoid making it a hard-to-replace dependency for a team application: issue #26018 connects a portfolio-content dispute with nested services that a team already used.
What people use register for
Users in the supplied GitHub discussions used is-a.dev addresses for website redirects, personal portfolios and nested team services. These examples show why the destination matters as much as the address. A redirect can be convenient for a homepage, while a hostname embedded in another application creates a continuing dependency on the parent domain and its review process.
- GitHub user tejasag kept a Vercel-hosted website behind URL redirection after maintainer phenax explained the hosting conflict in the Vercel discussion in issue #489. Tejasag chose to leave that arrangement in place and consider a CNAME connection after finding another host.
- GitHub user Defective4 used services.defective.is-a.dev for team services. During a portfolio rewrite, they asked that the parent domain remain because the team's application made the hostname difficult to change. The nested-service report in issue #26018 explains the dependency.
- GitHub user Rayrsn used a redirect that carried /LinkInBio to a personal homepage. A maintainer requested a working root destination and later removed the domain from the broken list. The redirect discussion in issue #8171 records that outcome.
- GitHub user krishanunaskar removed a navigation button labeled Shop after a commercial-use report. The portfolio discussion in issue #26018 marks the domain fixed and includes a follow-up question about a differently labeled BuildByBit link.
For a personal homepage, keeping the underlying hosting address available gives you a practical route for moving links later. Defective4's example deserves more caution when choosing an address: changing a portfolio link and changing a hostname inside a team's application are different jobs. Decide which kind of dependency you are creating before requesting a nested name or sharing it with other users.
What happened when we ran it
Our October 25, 2026 run checked commit 204e47b: installation succeeded in 6 seconds and tests succeeded in 9 seconds. The recorded sandbox used 3 CPUs, 8 GB RAM and image label lab-node:22. These are our repository measurements. They describe the cost of running the recorded checks, while registration follows the separate fork, documentation and review process described by the README.
| October 25 repository check | Recorded result |
|---|---|
| Dependency installation | Succeeded in 6 seconds |
| Installed dependencies | 170 recorded, 35 MB on disk |
| Build | No build script or target, skipped |
| Tests | Succeeded in 9 seconds |
| npm audit | 0 known vulnerabilities across critical, high, moderate and low categories |
| Checkout | 17,884 files, about 1,293 source lines, 8.6 MB |
| Repository signals | 9 CI workflow files, a tests directory, no Dockerfile |
The separate November 16 hands-on attempt failed at its safety step because the repository lacked all four Compose filenames accepted by the runner: compose.yaml, compose.yml, docker-compose.yaml and docker-compose.yml. The error called the repository unsafe under its rule that a Compose file was required. The failed safety step identifies the missing prerequisite rather than a discovered exploit.
The November run summary says it deployed with the repository's own Docker Compose configuration, which conflicts with the failed prerequisite. The recorded outcome is therefore a blocked deployment attempt. The November run summary dates the attempt to November 16, 2026, and the teardown record reports teardown: ok. The October npm checks and November Compose prerequisite are separate results.
How the request and review process works
The README requires a fork, the documented configuration and a pull request that maintainers review. It tells applicants to watch for requested changes and make them. It also explicitly tells applicants not to use AI to generate registration requests. The is-a-dev/register README is the starting point for the process and links to the project's documentation.
The README says DNS records should publish within a few minutes after the pull request is merged. That timing starts after merge. In issue #18078, a user complained about waiting hours or days for changes, and a commenter explained that unpaid maintainers review requests in their free time. For a planned hosting change, prepare the destination and allow the pull request to reach approval before relying on the new record.
Where people get stuck: host ownership and review queues
Historical users encountered hosting conflicts after receiving an approved is-a.dev address. In issue #489, tejasag wanted to connect the address to Vercel. Phenax explained the existing URL redirect and advised using another host for the CNAME arrangement discussed there. Tejasag kept Vercel and the redirect. Redirection sends visitors onward; serving the site under the custom hostname is a different outcome.
| Report and source | What happened | Recorded response or outcome |
|---|---|---|
| Users in issue #6627 | GitHub sent notices that another user or organization had verified their domain | Maintainer wdhdev acknowledged the incident and said its cause was unknown |
| Reporter in issue #16295 | A GitHub Pages destination instead redirected to is-a.dev and returned an unexpected A record | Removing another domain and re-adding affected domains reportedly failed |
| Alex-idk in issue #8171 | A working redirect appeared on the broken list | Wdhdev checked it and removed the false positive |
| peme969 in issue #18078 | A request for NS records ran into delegation rules | Maintainers rejected convenience alone as justification |
Rayrsn's case in #8171 shows why the exact destination matters. The intended /LinkInBio path worked, while the destination's root deliberately returned a 403 response. A maintainer asked for the main page to redirect somewhere and subsequently confirmed that the domain worked. When responding to a broken-domain report, describe both the path visitors use and the root page's behavior so the reviewer can assess the same arrangement.
Issue #16295 records another failure: the reporter expected GitHub Pages content, received a redirect to is-a.dev, and saw an unexpected A record. Visiting that address returned a 403 forbidden error. Treat that report separately from a false positive in a redirect checker or a hosting account-ownership notice. The visible symptoms differ, so a remedy from one thread is a poor starting assumption for another.
Public contact details and later privacy changes
Issue #14802 includes phishing reports and later changes to how contact information was exposed. The readable thread records wdhdev reporting Raw API email redaction on July 29, 2024. On August 6, andrewstech reported OWL deployed and integrated into the Discord bot. These developments belong alongside the earlier reports when assessing the project's contact history, rather than treating the first complaints as the end of the story.
Several participants said they received similar messages. Xzonix reported that removing an email from the JSON file stopped further messages and suggested Discord; the same participant also reported receiving a message at a second address they had not supplied to is-a.dev. Phenax proposed accepting another reliable contact method and warned that previously published information had spread across forks and pull requests. The contact discussion in issue #14802 contains these distinct observations.
Wdhdev reported redacting all emails from the Raw API on July 29, 2024. The comment described the API as the suspected collection route and proposed watching whether the redaction changed the volume of scam messages. On August 6, andrewstech reported that OWL was fully deployed and integrated into the Discord bot, with 24 records using it. The readable issue #14802 thread supplies both dated updates.
API redaction and existing repository copies concern different places where information can appear. Choose contact details suitable for publication before including them in a public change, and follow the current documentation's accepted fields. An old comment suggesting a blank mail field is a participant's historical workaround, not a configuration example to copy into a new request without consulting the project's instructions.
Parent-domain content rules reach nested services
A portfolio review can put nested services at risk when their address depends on the portfolio's parent domain. In issue #26018, Defective4 said their website was down during a rewrite and that losing the parent would also affect services.defective.is-a.dev. They explained that the team's application made changing the domain difficult and asked for time to restore the portfolio.
The readable thread also records the enforcement follow-up. On September 22, 2025, the reporter said they intended to create a deletion pull request for Defective4's main and nested subdomains. Wdhdev said entries still unfixed could be removed, and the reporter closed the issue with a general fixed-or-removed summary. Keeping a useful destination available during a rebuild is therefore an operating concern for anyone placing other services beneath it.
Krishanunaskar's Shop link drew a separate content objection in the same issue. They said it pointed to their BuildByBit profile and removed the navigation button; the issue marked the domain fixed. Their later question asked whether a label such as BuildByBit Profile would still count as commercial. For a similar site, show reviewers the destination and ask about that actual use rather than assuming a different button label settles the content question.
Register vs alternatives: choose the job first
Choose is-a.bot for a robot website and evaluate Technitium DNS Server when you need to operate DNS infrastructure. The two projects answer different needs: one supplies a subdomain through reviewed requests, while the other is DNS server software. Cloudflare delegation and Railway also appear in the issue discussions, but those choices concern record management and website hosting rather than obtaining the same kind of address.
| Choice discussed | Why someone considered it | What the record actually supports |
|---|---|---|
| Personal Cloudflare management through NS delegation | peme969 wanted its features and easier DNS changes | In issue #18078, maintainers rejected convenience alone and said the project already used Cloudflare DNS |
| Railway instead of Vercel or Netlify | Participants needed a different hosting route | Issue #1150 recommends trying Railway; the user whose provider shut down said they would try it later |
| Bunny.net versus Cloudflare upstream | Contributors were discussing the registry's DNS provider | Issue #14153 discusses support, record limits, NS support and pricing concerns |
| Technitium DNS Server | Wdhdev explored running DNS infrastructure directly | In issue #14153, the maintainer reports personal testing and discusses infrastructure requirements |
The is-a.bot README describes a service for a robot's website. It says its registration process is the same as is-a.dev's, using the separate repository. It also reports problems with Vercel subdomain verification. The is-a.bot README therefore gives a reason to choose the suffix for the site's identity, alongside a hosting warning that deserves attention during that choice.
Technitium DNS Server is open-source authoritative and recursive DNS server software. Its README describes self-hosting DNS and provides installation routes. That makes it relevant when the task is running infrastructure for a namespace you control. For someone simply choosing a portfolio address, running a DNS server introduces a different task rather than completing the is-a.dev request on their behalf.
In issue #1150, a user said their hosting provider, foxxy.id, had shut down. Another participant suggested Railway, and the user said they would try it later. This example separates hosting continuity from the registry address: keeping an address useful still requires a destination host and, when its configuration changes, the corresponding registry update. An address choice alone does not keep the website running.
FAQ
Maintainers rejected convenience alone as a reason for NS delegation in issue #18078. The questions below come from the supplied GitHub discussions and cover that restriction, hosting conflicts, public contacts and broken-domain reports. Their answers name the reported outcome so a new applicant can distinguish a registration step from a hosting decision or a request for a maintainer's judgment.
Are other is-a.dev users receiving phishing emails at their published contact addresses?
Several participants in issue #14802 reported similar phishing messages. Xzonix also reported receiving one at an address they had not supplied to is-a.dev. Later in the thread, wdhdev reported Raw API email redaction, and andrewstech reported OWL deployment. The dated privacy developments and the earlier contact reports are described together above. Read the contact reports.
Could is-a.dev stop publishing owner email addresses and use another contact method?
Phenax proposed accepting another reliable contact method, including Discord or social accounts, in issue #14802. Wdhdev later reported removing emails from the Raw API, while andrewstech reported OWL integrated into the Discord bot. For a new request, use the project's documentation to choose the accepted contact fields rather than turning one historical suggestion into a current schema. Read the contact-method discussion.
Why does GitHub say my is-a.dev domain has been verified by another user or organization?
Multiple participants in issue #6627 reported that notice, and maintainer wdhdev said they were investigating and did not know why it happened. If you encounter a similar notice, preserve its exact text and the affected hostname when asking for help. That gives maintainers a concrete symptom to compare with the historical report. Read the verification incident.
Why does Vercel say my newly approved is-a.dev domain already belongs to another account?
Issue #489 records an ownership conflict and phenax's advice to retain URL redirection or use another host for the CNAME connection discussed there. Tejasag chose to keep the Vercel site behind the redirect. Decide whether sending visitors to the hosting address meets your needs before treating that workaround as the result you want. Read the Vercel ownership discussion.
Can Vercel and Netlify allow different accounts to use different is-a.dev subdomains?
Participants in issue #489 asked the providers to support subdomains across different accounts and reported problems involving Vercel and Netlify. Their question explains the desired behavior: separate users wanted separate subdomains beneath the shared parent. The concrete user outcome in that thread was tejasag keeping URL redirection to the Vercel website. Read the provider-support requests.
Why does my is-a.dev subdomain redirect to is-a.dev instead of showing my GitHub Pages site?
The reporter in issue #16295 described that redirect, an unexpected A record and a 403 forbidden response when visiting the returned address. The discussion also records unsuccessful attempts involving domain removal and re-addition. Include the intended destination, observed redirect and DNS response in a support request so the symptoms are clear. Read the GitHub Pages incident.
Why was my pull request to add NS records closed?
Wdhdev identified missing accepted reasoning in one request and an invalid mixture of NS and other records in another request discussed in issue #18078. The user later reported removing NS records and restoring A records. Explain the requirement behind a delegation request and follow the project's documented record rules when preparing the change. Read the delegation review.
Can I use Cloudflare simply because I prefer its DNS management?
Maintainers rejected easier management or convenience alone as sufficient justification in issue #18078. They also said the registry already used Cloudflare DNS. A preference for a personal dashboard was therefore different from the accepted need they required for NS delegation. Choose the registry workflow with that restriction in mind. Read the Cloudflare delegation discussion.
What we have not tested yet
The lab evidence contains repository checks and a blocked Compose attempt, without a completed registration or live-hosting exercise. We have not tested a fresh application, approval turnaround, public DNS propagation, TLS issuance, current Vercel or Netlify compatibility, or a hosting migration. The November attempt has no screenshot records or hands-on task answers. The October result supplies no test count, coverage figure or actual toolchain versions; lab-node:22 is an image label, not proof of runtime or operating-system versions.
Current private-contact options were not verified. Raw API redaction and OWL deployment are attributed developments in the 2024 thread; they do not demonstrate today's complete contact workflow or erase copies already distributed through repository activity. The phishing discussion does not prove how every recipient's address was collected. The historical suggestion to use Discord is not a tested registration example, and this review supplies no replacement JSON schema.
The supplied records for #6627 and #16295 contain no confirmed cause-and-resolution account. The general closure of #26018 does not identify the final fate of every listed domain and nested service. Provider comparisons in #14153 are historical discussion rather than current pricing or our performance measurements. Issue #1150 supplies no completed Railway migration, and the provider requests in #489 supply no confirmation that the requested behavior was implemented.
We have not measured adoption, uptime, support capacity or DNS behavior under load. The separate abuse discussion in #2003 includes disputed allegations and a retraction, so it supplies no verified attack finding for this review. Rendered layout, resolved evidence links, recommendation modules and related-page behavior also remain outside these checks. Before depending on an address for an essential application, decide how its users would move to another hostname.


