- Free allowance
- A free <name>.is-a.dev subdomain, registered by a pull request that adds one JSON file to the domains directory of the service's GitHub repository
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- write-gatedevery registration and every later change is a pull request that a maintainer reviews; the service states it can deny any request for any reason, and review time is volunteer time with no published figure; NS records are approved only...
- Evidence
- documented11 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-12-04checked 2026-11-03 (live); stale on 2026-12-04
| Free tier | a free <name>.is-a.dev subdomain, registered by a pull request that adds one JSON file to the domains directory of the service's GitHub repository unit objects; metered on none |
|---|
| Price | none stated |
|---|
| Limits | - write-gated (binding) every registration and every later change is a pull request that a maintainer reviews; the service states it can deny any request for any reason, and review time is volunteer time with no published figure source
- write-gated (binding) NS records are approved only in specific cases and are refused to an account without an is-a.dev subdomain held for at least 30 days; review takes usually 24 to 72 hours and up to 2 weeks source
- write-gated (binding) a root subdomain must belong to a software-development-related project; the eligibility is part of the review source
|
|---|
| Binding | write-gated the operator reviews each request and states it can terminate a subdomain at any time for any reason, so the owner can withdraw the name; the zone is the operator's and the registrant holds records only, apart from approved NS cases |
|---|
| Identity | email a GitHub account of an individual; the only owner field the JSON file requires is the GitHub username, and a GitHub organisation account cannot register; no phone and no card are asked (https://docs.is-a.dev/domain-structure/) |
|---|
| Egress | no query cap published |
|---|
| Per-object cap | no subdomain count per account is published on the pages read; only one single-letter subdomain per user is allowed |
|---|
| Retention | no expiry or renewal term is published; a subdomain lasts until the maintainers remove it or its JSON file is deleted by a pull request |
|---|
| Interface | git every create, change or delete is a pull request against the register repository with a JSON file per name; the supported record types are A, AAAA, CAA, CNAME, DS, MX, SRV, TLSA, TXT and a service-specific URL redirector, and NS only in approved cases |
|---|
| Tooling | git and a GitHub account; a pull request for each change, merged by a maintainer |
|---|
| Composes with | a CNAME to a free static host gives a named site; the zone is not yours (NS delegation is refused to an account that has held a subdomain for under 30 days and is otherwise decided case by case), so it cannot become a Cloudflare zone of its own by default |
|---|
| Reliability | the operator can remove a subdomain at any time for any reason, the service is run by volunteers and the TLS limit is per name because the suffix is on the Public Suffix List |
|---|
| Notes | Withdrawal binds first: a maintainer's pull-request review stands between the request and the name, and the operator can end the name at any time. The zone is not the registrant's, so there is no own zone, no Cloudflare zone and no wildcard certificate for the subdomain by default. The TLS limit does not bind, because the suffix is listed and each name counts alone against the Let's Encrypt limit. |
|---|
| Evidence note | documented the domain-structure, FAQ, quickstart and terms pages were read and quoted; the TLS statement is an inference from the Let's Encrypt registered-domain rule and the suffix's listing in the captured Public Suffix List |
|---|
| Parsed numbers | - has-free-tier 1
- write-gated 72 hours
|
|---|