Skip to content
Back to search

runs-on.dev

Grab your own cool 'runs-on.dev' subdomain to use for free forever.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/zordhalo/runs-on.dev with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/zordhalo/runs-on.dev'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/zordhalo--runs-on-dev/badge.svg)](/listings/zordhalo--runs-on-dev)

HTML

<a href="/listings/zordhalo--runs-on-dev"><img src="/api/listings/zordhalo--runs-on-dev/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 303 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <p align="center">
  2. <a href="https://runs-on.dev">
  3. <picture>
  4. <source media="(prefers-color-scheme: light)" srcset="https://runs-on.dev/opengraph-image">
  5. <img src="https://runs-on.dev/banner-dark" alt="runs-on.dev" width="820">
  6. </picture>
  7. </a>
  8. </p>
  9. <h1 align="center">runs-on.dev</h1>
  10. <p align="center">
  11. <a href="https://whobuildsagents.com/advancelabs.dev"><img src="https://whobuildsagents.com/badge/advancelabs.dev.svg" alt="MCP servers live" /></a>
  12. </p>
  13. <p align="center">
  14. Free subdomains for developers. Claim <code>yourname.runs-on.dev</code> in seconds,
  15. then point it wherever you like.
  16. </p>
  17. <p align="center">
  18. <a href="https://runs-on.dev"><b>Claim a name</b></a>
  19. &nbsp;·&nbsp;
  20. <a href="https://runs-on.dev/docs/quickstart">Quickstart</a>
  21. &nbsp;·&nbsp;
  22. <a href="https://runs-on.dev/docs/guides">Guides</a>
  23. &nbsp;·&nbsp;
  24. <a href="https://runs-on.dev/docs/records">Records</a>
  25. &nbsp;·&nbsp;
  26. <a href="https://runs-on.dev/policy">Policy</a>
  27. </p>
  28. <p align="center">
  29. <a href="https://github.com/zordhalo/runs-on.dev/stargazers"><img alt="stars" src="https://img.shields.io/github/stars/zordhalo/runs-on.dev?label=stars&color=1b4dff"></a>
  30. <a href="https://github.com/zordhalo/runs-on.dev/tree/main/domains"><img alt="names claimed" src="https://img.shields.io/github/directory-file-count/zordhalo/runs-on.dev/domains?type=file&extension=json&label=names%20claimed&color=1b4dff"></a>
  31. <a href="https://github.com/zordhalo/runs-on.dev/actions/workflows/test.yml"><img alt="tests" src="https://github.com/zordhalo/runs-on.dev/actions/workflows/test.yml/badge.svg"></a>
  32. <a href="./LICENSE"><img alt="license: AGPL-3.0" src="https://img.shields.io/badge/license-AGPL--3.0-informational"></a>
  33. </p>
  34. ---
  35. Claiming a name writes one file to this repository. That file is the record. It is the only
  36. thing that makes the name resolve, and you can read it without asking anyone.
  37. ```json
  38. {
  39. "name": "yourname",
  40. "owner": { "github": "yourname" },
  41. "claimedAt": "2026-01-01T00:00:00.000Z",
  42. "records": {}
  43. }
  44. ```
  45. There is no hidden database. The registry is this directory, the history is the git log, and
  46. the rules are in `lib/`.
  47. ## Why this exists
  48. A real top-level domain means an ICANN application. The 2026 round's
  49. evaluation fee alone is $227,000, before you've built or run a registry to
  50. back it. That's not a plausible way to get a custom-looking address for a
  51. side project.
  52. `runs-on.dev` gets the same feeling: a distinctive ending instead of
  53. `vercel.app` or `github.io`, for the price of one domain, about $10 a
  54. year, by giving away subdomains under it. This is a subdomain registry,
  55. not a TLD. Every name you claim lives under `runs-on.dev`, which Advance
  56. Labs registered and is responsible for. Saying that plainly, instead of
  57. dressing it up as something bigger, is the whole basis for trusting it.
  58. There's prior art doing exactly this: [is-a.dev](https://www.is-a.dev),
  59. [js.org](https://js.org), [eu.org](https://eu.org).
  60. ## Claim a name
  61. Go to [runs-on.dev](https://runs-on.dev), sign in with GitHub, and type
  62. the name you want. If it's available, claiming it writes a record to
  63. `domains/<name>.json` in this repo, as shown above, and the name is live
  64. within seconds. One name per GitHub account. See
  65. [docs/claiming.md](./docs/claiming.md) for eligibility rules, the
  66. per-account limit, and why they exist.
  67. ## Point it at your own hosting
  68. By default a claimed name serves a small profile card built from your
  69. GitHub account. To point it at your own site, forward email, or a plain
  70. redirect instead, there are two ways to change its record.
  71. **From the site.** Sign in and open
  72. [runs-on.dev/manage](https://runs-on.dev/manage). Pick a record type, fill
  73. it in, and save. That writes a commit to `domains/<name>.json` in this
  74. repository, exactly as a merged pull request would, and DNS follows within
  75. seconds. The form offers the record types in the combinations DNS actually
  76. permits, so it cannot build a record the schema would reject.
  77. **By pull request.** Still supported, and the right choice when you want the
  78. change reviewed before it lands:
  79. 1. Fork this repo.
  80. 2. Edit `domains/<name>.json`, adding a record under `records` (and
  81. optionally `subdomains`, for a one-level-deep entry like `_atproto`).
  82. 3. Open a pull request. CI validates the change against
  83. [`schema/record.schema.json`](./schema/record.schema.json); once it's
  84. green and merged, a workflow pushes the record to DNS automatically.
  85. Both paths enforce the same rules, from the same code in
  86. [`lib/edit.js`](./lib/edit.js): only the owner may change a record, and
  87. `owner`, `claimedAt`, and `name` are immutable once set.
  88. | Type | Shape | Coexistence |
  89. | --- | --- | --- |
  90. | `CNAME` | a hostname string | Alone: cannot sit next to `A`, `TXT`, or `MX`. |
  91. | `A` | 1+ IPv4 addresses | With `TXT`, `MX`. |
  92. | `TXT` | 1+ strings, up to 255 chars each | With `A`, `MX`. |
  93. | `MX` | 1 to 5 `{ priority, value }` entries | With `A`, `TXT`. |
  94. | `URL` | one absolute `http(s)://` string | Alone: cannot sit next to anything, not allowed under `subdomains`. |
  95. Nine hosting providers, a URL redirect, email forwarding, a Bluesky
  96. handle, and Discord verification, each with the exact record to copy, are
  97. in [docs/guides.md](./docs/guides.md). The same walkthroughs render on the
  98. site at `/docs/guides/<provider>` with more detail per provider; the
  99. markdown file is the compact version for reading here.
  100. Once a name serves your own site, [docs/seo.md](./docs/seo.md) covers what
  101. changes when that site lives on a subdomain: `robots.txt` and sitemaps are
  102. per host rather than per domain, redirect names cannot rank, and a name
  103. needs its own Search Console property.
  104. <details>
  105. <summary>Two worked examples</summary>
  106. Vercel, the shortest path from claim to a live custom domain:
  107. ```json
  108. "records": { "CNAME": "<hash>.vercel-dns-017.com" }
  109. ```
  110. Add `you.runs-on.dev` as a custom domain on the Vercel project first; the
  111. Domains tab then shows the CNAME target to use. It is usually specific to
  112. your project, so copy what it shows rather than the placeholder above.
  113. A Bluesky handle, which needs no hosting at all, just a subdomain entry:
  114. ```json
  115. "subdomains": {
  116. "_atproto": { "TXT": ["did=did:plc:abc123"] }
  117. }
  118. ```
  119. Full record reference, the `subdomains` grammar, and why `CNAME` can't
  120. coexist with anything else: [docs/records.md](./docs/records.md).
  121. </details>
  122. ## Built on runs-on.dev
  123. **[Overlap](https://overlap.runs-on.dev)** — finds meeting times for people
  124. spread across time zones. Share one link, everyone sets their hours once, and
  125. the page shows when you can all meet, with sleep treated as a hard constraint
  126. rather than as free time. Open source, AGPL-3.0:
  127. [zordhalo/overlap](https://github.com/zordhalo/overlap). Write-up:
  128. [the first thing built on runs-on.dev](/blog/2026-09-20-overlap-scheduling-across-time-zones).
  129. It runs on a claimed name like any other, which is the point: `domains/overlap.json`
  130. is an ordinary record, and the name resolved with a valid certificate before any
  131. DNS was configured for it.
  132. If you build something on a name from here, open a PR adding it to this list.
  133. ## How it works
  134. A single wildcard `*.runs-on.dev` DNS record points every possible
  135. subdomain at one Vercel project, so an unclaimed or record-less name still
  136. resolves with a valid HTTPS certificate and gets served the profile-card
  137. page. Claiming a name is therefore a git commit, not a DNS write. Pointing
  138. a name at your own hosting merges a record into `domains/<name>.json`, and
  139. a GitHub Actions workflow pushes that exact record to Vercel's DNS API on
  140. merge, which then takes priority over the wildcard for that one name. More
  141. detail, including the two write paths and the token split, in
  142. [docs/architecture.md](./docs/architecture.md).
  143. ## The rules
  144. Everything CI checks on a `domains/**` pull request, so you can verify a
  145. PR yourself before opening it:
  146. - One file per pull request.
  147. - The path must match `domains/<name>.json`, matching
  148. `^domains/([a-z0-9-]+)\.json$`.
  149. - Renaming a record is refused outright. Claim a new name instead.
  150. - `owner` and `claimedAt` are immutable once set; only the recorded owner
  151. may edit or remove a record.
  152. - New names may be claimed either on the site or by pull request. Both
  153. paths apply the same gates: the record must name its own author as
  154. owner, the name must not be reserved, the account must be at least 30
  155. days old with one public repository, and it must not already hold a
  156. name.
  157. - An owner may delete their own record by pull request; a maintainer can
  158. do the same under [POLICY.md](./POLICY.md).
  159. See [`lib/pr.js`](./lib/pr.js) for the implementation CI actually runs,
  160. and [docs/contributing.md](./docs/contributing.md) for the full breakdown
  161. of what it checks.
  162. <details>
  163. <summary>Self-hosting</summary>
  164. This is an open registry, not a hosted product with a private backend.
  165. Running your own copy under a domain you own means:
  166. - Fork this repo and rename it; `REGISTRY_REPO` in `.env.example` points
  167. at wherever the fork lives.
  168. - Register your own domain, point a wildcard record at your deployment,
  169. and add it to Vercel (or adapt `scripts/sync-dns.mjs` and `lib/dns.js`
  170. for a different DNS provider).
  171. - Change `ROOT` in `proxy.js` and the hostname literals in `app/page.jsx`
  172. and `app/sites/[name]/page.jsx` from `runs-on.dev` to your domain.
  173. - Create your own GitHub OAuth app and set `GITHUB_CLIENT_ID` /
  174. `GITHUB_CLIENT_SECRET`.
  175. - Review `data/reserved-*.json` and adjust `lib/eligibility.js` for your
  176. own abuse tolerance.
  177. </details>
  178. <details>
  179. <summary>Local development</summary>
  180. ```bash
  181. npm install
  182. npm run dev
  183. ```
  184. The claim flow needs a signed-in GitHub session, and the session and
  185. OAuth cookies are set `Secure` (see `app/api/auth/github/route.js` and
  186. `.../callback/route.js`). A `Secure` cookie is dropped by the browser over
  187. plain HTTP, so the GitHub sign-in flow cannot be exercised on
  188. `http://localhost`. This is correct for production: `runs-on.dev` is on
  189. the HSTS preload list, so it's always HTTPS there, and a cookie that only
  190. ever travels over HTTPS shouldn't get a `Secure`-free code path just for
  191. local convenience.
  192. To exercise sign-in locally, serve the app over HTTPS with a
  193. locally-trusted certificate,
  194. [mkcert](https://github.com/FiloSottile/mkcert) being the simplest way:
  195. ```bash
  196. mkcert -install
  197. mkcert localhost
  198. ```
  199. Then run `next dev` behind a TLS-terminating proxy pointed at it, and set
  200. `APP_ORIGIN` to the `https://` URL you're serving from so the OAuth
  201. redirect URI matches. Everything that doesn't touch sign-in, name
  202. validation, schema checks, the blocklist, the record UI, works over plain
  203. `http://localhost` without any of this. See
  204. [.env.example](./.env.example) for every variable the app reads.
  205. </details>
  206. ## Star the registry
  207. Every name claimed here is one commit in this repo, authored under the
  208. claimant's own GitHub account. If you have a name, you're already in the log —
  209. a star keeps the registry easy for the next person to find.
  210. ## Contributing
  211. Bug fixes, blocklist additions, and doc improvements are welcome. See
  212. [docs/contributing.md](./docs/contributing.md) for how to add to the
  213. blocklists, run the tests, and what CI checks.
  214. ```bash
  215. npm install
  216. npm test
  217. ```
  218. ## License
  219. The code in this repository is [AGPL-3.0 licensed](./LICENSE). It is a network
  220. service, so section 13 applies: run a modified copy and let other people use it
  221. over a network, and you owe those users your source. Using the registry, or
  222. claiming a name, carries no such obligation — this binds people who fork and
  223. host the software, not people who point a subdomain at their site.
  224. Up to commit `3492bf7` the code was MIT, and that grant still stands for the
  225. code as it was then; see [NOTICE](./NOTICE).
  226. The bundled profanity blocklist (`data/reserved-words.json`) is seeded from
  227. [LDNOOBW/List-of-Dirty-Naughty-Obscene-and-Otherwise-Bad-Words](https://github.com/LDNOOBW/List-of-Dirty-Naughty-Obscene-and-Otherwise-Bad-Words)
  228. (English list) and keeps its own
  229. [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) license; see
  230. [data/README.md](./data/README.md).
  231. ## Credits
  232. The idea of giving away free subdomains under one registered domain isn't
  233. new; credit to [is-a.dev](https://www.is-a.dev) for the prior art, and to
  234. [js.org](https://js.org) and [eu.org](https://eu.org) for more of it.
  235. ---
  236. Built and operated by [Advance Labs](https://advancelabs.dev), which registered
  237. `runs-on.dev` and is the party responsible for what runs under it. See
  238. [POLICY.md](./POLICY.md) · [All Advance Labs products](https://advancelabs.dev/lab).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.