JS.ORG
js.org/Free registrable subdomaindomains-dns/js-orgJSONcomparereport an errorprovider JSON
- Free allowance
- Free <name>.js.org subdomains for JavaScript-ecosystem sites, added by a pull request to the js-org/js.org repository; the new URL goes live within 24 hours
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- write-gateda pull request is reviewed against the rule that a site must be directly related to the JavaScript ecosystem and carry substantive content; a naming conflict or a change request can hold it
- Evidence
- documented8 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 | free <name>.js.org subdomains for JavaScript-ecosystem sites, added by a pull request to the js-org/js.org repository; the new URL goes live within 24 hours unit objects; metered on none |
|---|
| Price | none stated |
|---|
| Limits | - write-gated (binding) a pull request is reviewed against the rule that a site must be directly related to the JavaScript ecosystem and carry substantive content; a naming conflict or a change request can hold it source
- retention-clamped the user acquires no ownership of the subdomain, and the operator may terminate a certain subdomain or all of them with at least 7 days of notice by an issue in the user's repository source
|
|---|
| Binding | write-gated the review gate is the first constraint and the operator can end any name on 7 days of notice; records are CNAME only and the zone is not the registrant's |
|---|
| Identity | email a GitHub account; the steps ask the user to log in to GitHub and open a pull request, and name no phone, card or ID |
|---|
| Egress | no query cap published |
|---|
| Per-object cap | no subdomain count per user is published on the pages read; the name must follow the GitHub Pages username or repository name |
|---|
| Retention | no expiry or renewal term is published; the user ends it by removing the entry in a pull request, and the operator may end a subdomain, or all of them, with at least 7 days of notice |
|---|
| Interface | git a pull request adds the name to the subdomains list file cnames_active.js of the repository; every entry is a CNAME to a host, so no other record type is offered |
|---|
| Tooling | git and a GitHub account; a CNAME file in a GitHub Pages repository or a custom-domain setting at another host |
|---|
| Composes with | a CNAME to GitHub Pages or another host that accepts a custom domain by CNAME; the zone is the operator's and sits on Cloudflare's free plan, so it cannot be a zone of the registrant's |
|---|
| Reliability | the service states no right to constant availability and may end a subdomain on 7 days of notice; the suffix is on the Public Suffix List, so the TLS limit counts per name |
|---|
| Notes | The owner can withdraw the name on 7 days of notice and a review gates the start. The zone is not the registrant's and offers CNAME only, so no apex records, no mail and no own zone. The TLS limit does not bind, because the suffix is listed and each name counts alone. |
|---|
| Evidence note | documented the repository README, the terms page and the subdomain-determination wiki page 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 | |
|---|
Evidence 8