# Available TLDs — all five creepers.sbs domains explained
Source: https://docs.creepers.sbs/available-domains
creepers.sbs offers five free TLDs: creepers.sbs, creepers.cloud, creepers.pro, creepers.lol, and any other future domain. Each must be registered separately with its own PR.
creepers.sbs currently offers five top-level domains (TLDs) for free subdomain registration. You can use any combination of them, subject to the [usage limits](/policies/usage-limits). Each TLD requires its own registration — claiming a name on one does not automatically reserve it on the others.
## Available TLDs
The original Creepers TLD. "sbs" stands for "side by side." A general-purpose domain suitable for any type of website, project, or server.
A good fit for web applications, cloud-hosted services, and anything deployed to a cloud provider. Works for any project type.
Suitable for professional portfolios, developer tools, or projects where a polished presentation matters.
A lighthearted option for fun, experimental, or community-oriented projects.
Oriented toward servers, applications, and infrastructure. Especially fitting for Minecraft servers, game servers, bots, and other always-on services.
Registering `yourname.creepers.sbs` does **not** reserve `yourname.creepers.cloud` or any other TLD. If you want the same name across multiple TLDs, you must register each one separately — either in separate Pull Requests or all at once using the [complete template](https://github.com/creepersbs/register/blob/main/domains/complete.template.json).
## Choosing a TLD
Any TLD works for any type of project — there are no technical restrictions on which one you pick. That said, here are some practical guidelines:
* **Websites and portfolios** — any TLD works. Pick the one that fits your brand or sounds right.
* **Servers and applications** — `run-it.tech` was designed with this use case in mind, but `creepers.cloud` or `creepers.pro` are equally valid.
* **Minecraft servers** — `run-it.tech` or `creepers.sbs` are popular choices. You can use SRV records on any TLD to point players to your server port.
* **Fun or experimental projects** — `creepers.lol` suits projects where a serious-sounding domain would feel out of place.
If you are unsure, start with `creepers.sbs` — it is the most established TLD in the registry.
## Usage limits
Each account may register up to **2 subdomains per TLD**, with a maximum of **8 subdomains total** across all TLDs. See [usage limits](/policies/usage-limits) for the full breakdown, including legacy user allowances and how limits are applied when a name is shared across TLDs.
The current per-account limit is:
| TLD | Max subdomains |
| -------------- | -------------- |
| creepers.sbs | 2 |
| creepers.cloud | 2 |
| creepers.pro | 2 |
| creepers.lol | 2 |
| run-it.tech | 1 (temp) |
When the same subdomain name is registered across multiple TLDs, each registration counts separately toward its respective TLD limit. Limits may change over time — check the [changelogs](https://github.com/creepersbs/register/blob/main/changelogs) to stay up to date.
# Cloudflare proxy settings for your creepers.sbs subdomain
Source: https://docs.creepers.sbs/guides/cloudflare-proxy
The proxy field controls whether traffic routes through Cloudflare. Enable it for web apps; disable it for Minecraft servers, mail, and custom nameservers.
The `"proxy"` field in your registration file controls whether traffic to your subdomain passes through Cloudflare's network before reaching your server. This single boolean string — `"true"` or `"false"` — has a significant impact on which services work correctly behind your subdomain.
## What the proxy does
When `"proxy": "true"`, Cloudflare acts as an intermediary between visitors and your server:
* **Hides your origin IP** — your server's real IP address is not exposed to the public.
* **DDoS protection** — Cloudflare filters malicious traffic before it reaches your server.
* **CDN caching** — static assets can be cached at Cloudflare's edge nodes, reducing load on your server.
* **HTTPS enforcement** — Cloudflare can serve your site over HTTPS even if your server only speaks HTTP.
When `"proxy": "false"`, the DNS record points directly to your server. There is no intermediary — clients connect straight to your IP.
## When to enable the proxy
Set `"proxy": "true"` when you are hosting a **standard website or web application** served over HTTP or HTTPS on port 80 or 443. This is the most common setup for personal sites, blogs, and web apps.
```json theme={null}
{
"record": {
"A": ["198.51.100.10"]
},
"proxy": "true"
}
```
## When to disable the proxy
Set `"proxy": "false"` for any service that does not use standard HTTP/HTTPS, or that requires a direct connection to your server.
Game servers communicate on ports that Cloudflare proxy does not support. Use DNS-only mode so players connect directly to your server.
```json theme={null}
{
"record": {
"A": ["198.51.100.50"],
"SRV": [
{
"content": "_minecraft._tcp",
"priority": 10,
"weight": 60,
"ttl": "auto",
"port": 25565,
"target": "mc.myserver.net"
}
]
},
"proxy": "false"
}
```
Email delivery (SMTP) and retrieval (IMAP/POP3) do not work through the Cloudflare proxy. MX records require a direct connection.
```json theme={null}
{
"record": {
"MX": ["mx1.mymailprovider.com", "mx2.mymailprovider.com"]
},
"proxy": "false"
}
```
NS records always bypass the proxy regardless of the `"proxy"` setting. Setting `"proxy": "false"` makes this explicit and avoids confusion.
```json theme={null}
{
"record": {
"NS": [
"ns1.myprovider.com",
"ns2.myprovider.com"
]
},
"proxy": "false"
}
```
A `CNAME` pointing to a hostname on another Cloudflare account or a Cloudflare Worker does not work with `"proxy": "true"`. Disable the proxy for these targets.
```json theme={null}
{
"record": {
"CNAME": "my-worker.my-account.workers.dev"
},
"proxy": "false"
}
```
## Summary
| Service type | Proxy setting |
| ------------------------------------------ | --------------------------- |
| Static website or web app (HTTP/HTTPS) | `"true"` |
| Minecraft or other game server | `"false"` |
| Mail server (MX records) | `"false"` |
| Custom name servers (NS records) | `"false"` (always bypassed) |
| Non-HTTP ports (e.g., 25565, 587, 3306) | `"false"` |
| CNAME to another Cloudflare account/Worker | `"false"` |
Cloudflare proxy does not work with the majority of non-web services. If you are unsure whether your service is compatible, set `"proxy": "false"`. You can always open a new Pull Request to change the setting later.
NS records always bypass the Cloudflare proxy regardless of the `"proxy"` value you set. When you delegate your DNS zone to custom name servers, Cloudflare has no control over the traffic flowing through that zone.
# DNS record types supported in creepers.sbs registrations
Source: https://docs.creepers.sbs/guides/dns-record-types
Reference for every DNS record type in your creepers.sbs registration file: A, AAAA, CNAME, MX, NS, TXT, and SRV — with JSON examples and usage guidance.
[creepers.sbs](http://creepers.sbs) supports seven DNS record types in the `"record"` object of your registration file: `A`, `AAAA`, `CNAME`, `MX`, `NS`, `TXT`, and `SRV`. You only need to include the types relevant to your use case — leave out any you do not need. Each type has a specific value format described below.
## A — IPv4 address
An `A` record maps your subdomain to one or more IPv4 addresses. The value is an array of strings, so you can list multiple IPs for basic load balancing or redundancy.
```json theme={null}
"A": ["198.51.100.10", "198.51.100.11"]
```
## AAAA — IPv6 address
An `AAAA` record maps your subdomain to one or more IPv6 addresses. Like `A`, the value is an array.
```json theme={null}
"AAAA": ["2001:db8::1", "2001:db8::2"]
```
## CNAME — canonical name (alias)
A `CNAME` record points your subdomain to another domain name instead of an IP address. The value is a single string, not an array.
```json theme={null}
"CNAME": "myproject.netlify.app"
```
A `CNAME` cannot coexist with any other record type of the same name, except `TXT`. If you need both a `CNAME` and other record types (for example, a `CNAME` and an `MX`), use spare records for the additional entries. See the [spare records guide](/guides/spare-records).
A `CNAME` does not work when pointing to another Cloudflare account or a Cloudflare Worker. If your target is on another Cloudflare account, use a different regional subdomain (for example, `.eu.yourname.creepers.sbs`) with `"proxy": "false"` instead.
## MX — mail exchange
An `MX` record specifies the mail servers responsible for receiving email for your subdomain. The value is an array of hostnames.
```json theme={null}
"MX": ["mx1.yourmailprovider.com", "mx2.yourmailprovider.com"]
```
MX records require `"proxy": "false"`. Cloudflare proxy does not handle mail traffic.
## NS — name servers
An `NS` record delegates DNS control of your subdomain to a set of name servers you manage. This is useful if you want to manage the DNS zone for your subdomain yourself using another provider. The value is an array of up to five name server hostnames.
```json theme={null}
"NS": [
"ns1.myprovider.com",
"ns2.myprovider.com",
"ns3.myprovider.com",
"ns4.myprovider.com",
"ns5.myprovider.com"
]
```
NS records always bypass the Cloudflare proxy regardless of your `"proxy"` setting. When you use NS records, you take full responsibility for the DNS configuration of your subdomain — CreeperHUB has no technical control over it.
## TXT — text records
A `TXT` record stores arbitrary text data. It is commonly used for domain ownership verification (e.g., Google Search Console, email authentication). The value is an array of strings, allowing multiple entries.
```json theme={null}
"TXT": ["google-site-verification=Xk9mN2pQ7rL3vW8yZ1"]
```
`TXT` is the only record type that can coexist alongside a `CNAME` for the same subdomain name.
## SRV — service records
An `SRV` record advertises the location of a specific service running on your subdomain. It is commonly used for Minecraft servers, VoIP services, and other non-HTTP protocols. The value is an array of objects, each describing one service endpoint.
Each SRV entry has the following fields:
| Field | Description |
| ---------- | -------------------------------------------------------------- |
| `content` | The service and protocol identifier (e.g., `_minecraft._tcp`). |
| `priority` | Lower values are preferred when multiple SRV records exist. |
| `weight` | Used to distribute load among records with the same priority. |
| `ttl` | Time to live. Set to `"auto"` to let Cloudflare manage it. |
| `port` | The port your service listens on. |
| `target` | The hostname of the server running the service. |
```json theme={null}
"SRV": [
{
"content": "_minecraft._tcp",
"priority": 10,
"weight": 60,
"ttl": "auto",
"port": 25565,
"target": "mc.myserver.net"
},
{
"content": "_minecraft._tcp",
"priority": 20,
"weight": 10,
"ttl": "auto",
"port": 25566,
"target": "mc2.myserver.net"
}
]
```
For Minecraft servers, SRV records let you use a custom domain without requiring players to type the port number. Pair an `SRV` record with an `A` record pointing to your server's IP, and set `"proxy": "false"` — Cloudflare proxy does not work with game server traffic.
## Choosing the right record type
Use `A` or `AAAA` for servers you control directly, or `CNAME` for platforms like Netlify, Vercel, or GitHub Pages. Enable `"proxy": "true"` for HTTP/HTTPS traffic.
Use `SRV` to advertise your server with a clean domain, paired with an `A` record. Set `"proxy": "false"`.
Use `MX` records pointing to your mail provider's servers. Set `"proxy": "false"`.
Use `NS` records to delegate the zone to your own provider. The proxy is bypassed automatically.
# How to register a subdomain on creepers.sbs step by step
Source: https://docs.creepers.sbs/guides/registering-a-subdomain
Fork the repo, create a JSON file with your DNS records, and open a Pull Request. Covers every required field and the PR checklist for first-time registrations.
Registering a subdomain on creepers.sbs is entirely GitHub-based. You fork the repository, add a single JSON file to the `/domains` folder describing your project and DNS records, then open a Pull Request. A CreeperHUB team member reviews it manually, and once merged, your subdomain is live. There is no web panel or account to create — GitHub is the interface.
## The JSON file structure
Every subdomain registration is a `.json` file placed in `/domains`. The file name must exactly match the `"subdomain"` value inside it. For example, if you want `myapp.creepers.sbs`, the file must be named `myapp.json` and contain `"subdomain": "myapp"`.
Below is a walkthrough of every field in the template.
### Top-level fields
| Field | Required | Description |
| -------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `title` | Yes | The name of your website, project, or server. |
| `description` | Yes | A short summary of what the subdomain is for. |
| `domain` | Yes | The TLD you are registering under. Choose one: `creepers.sbs`, `creepers.cloud`, `creepers.pro`, `creepers.lol`, or `run-it.tech`. |
| `subdomain` | Yes | Your chosen subdomain name. Must match the file name exactly (without `.json`). |
| `country_code` | Yes | ISO 2-letter country code for the region your service targets, or `"none"` if not applicable. Currently stored as metadata only — subdomains are not divided by region yet. |
| `proxy` | Yes | `"true"` to enable Cloudflare proxy, or `"false"` for DNS-only mode. See [Cloudflare proxy guide](/guides/cloudflare-proxy). |
### The `owner` object
The `owner` block identifies who owns the subdomain. This information is used to contact you if action needs to be taken on your subdomain.
| Field | Required | Description |
| ------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `github_user` | Yes | The full URL to your GitHub profile (e.g., `https://github.com/yourusername`). Must be the account submitting the PR. |
| `email` | Yes | An email address where you can be reached for service-related notices. |
| `discord` | No | Your Discord username (e.g., `@yourusername`). Required if you ever need to transfer the subdomain. You must be a member of the official CreeperHUB Discord server. |
### The `record` object
The `record` block contains your DNS records. Include only the record types you need — you do not have to fill in all of them. For a full reference of each supported record type and its syntax, see [DNS record types](/guides/dns-record-types).
## Complete example
The following is a filled-in JSON file for a developer portfolio site on `creepers.sbs`.
```json alexdev.json theme={null}
{
"title": "Alex Dev Portfolio",
"description": "Personal developer portfolio showcasing open-source projects and a blog.",
"domain": "creepers.sbs",
"subdomain": "alexdev",
"country_code": "gb",
"owner": {
"github_user": "https://github.com/alexdev",
"email": "alex@alexdev.dev",
"discord": "@alexdev.codes"
},
"record": {
"A": ["198.51.100.42"],
"TXT": ["google-site-verification=Xk9mN2pQ7rL3vW8yZ1"]
},
"proxy": "true"
}
```
If you want to register the same subdomain name across multiple TLDs in a single Pull Request, use the `complete.template.json` format. Each additional TLD adds numbered fields: `"domain_2"`, `"record_2"`, `"proxy_2"`, and so on.
## Submitting the Pull Request
Go to [creepersbs/register](https://github.com/creepersbs/register) on GitHub. Star the repo to follow updates, then fork it to create your own copy.
In your fork, navigate to the `/domains` folder and create your file. Name it exactly after your desired subdomain — `yourname.json` for `yourname.creepers.sbs`. Paste in your filled-out JSON and remove all parenthetical comments from the template so the file is valid JSON.
Creepers enforces a **Zero-Manual-Fix Policy**. If your file has syntax errors, misplaced fields, or is in the wrong directory, your PR will be rejected and you will need to fix and resubmit it yourself. Use [JSONLint](https://jsonlint.com/) to validate before submitting.
In your fork, click **Contribute** then **Open Pull Request**. The PR description will be pre-filled with the official template. Fill in every required section:
* **Type of PR** — check "New Subdomain Request"
* **Your information** — GitHub username, email, and optionally your Discord username
* **Subdomain request details** — the full subdomain you want, the TLD, and any custom NS records
* **Description** — explain the purpose of the subdomain and any existing infrastructure
* **Confirmation checkboxes** — confirm you have read the Terms of Service and that all information is accurate
All three confirmation checkboxes must be checked before the PR can be reviewed.
A CreeperHUB team member will review your PR manually. Approval typically takes **24 hours to one week**. Once merged, your subdomain is live.
Do not point to placeholder or test IPs such as `1.1.1.1`, `0.0.0.0`, or `localhost`. Your service must already be live and reachable at the time of submission.
## Things to double-check before submitting
`yourname.json` must contain `"subdomain": "yourname"` — any mismatch will result in rejection.
Remove all parenthetical comments from the template. Validate with [JSONLint](https://jsonlint.com/) before opening the PR.
The file must be directly inside `/domains`, not in a subfolder. Incorrect placement will not be corrected by the team.
Your subdomain must point to a real, reachable service — not a placeholder IP or localhost.
# Remove or release your creepers.sbs subdomain voluntarily
Source: https://docs.creepers.sbs/guides/removing-a-subdomain
Release a subdomain via GitHub Issue, or learn how CreeperHUB removes domains for ToS violations, DMCA requests, and how the transparency ledger works.
There are two situations in which a subdomain is removed: you voluntarily give it up because you no longer need it, or CreeperHUB removes it due to a Terms of Service violation, a DMCA-style takedown, or verified abuse. Both outcomes are permanent — once a subdomain is removed, it may be blacklisted and become unavailable for future registration.
## Voluntary removal
If you no longer need your subdomain and want to release it, open a GitHub Issue in the `creepersbs/register` repository using the official issue template.
Go to [github.com/creepersbs/register/issues/new/choose](https://github.com/creepersbs/register/issues/new/choose) and select the **Subdomain Issue / Request** template.
Complete the issue form with the following:
* **Type of request** — select **Other** and note that this is a voluntary removal request
* **Your information** — your GitHub username and email address
* **Subdomain** — the full subdomain you want removed (e.g., `yourname.creepers.sbs`)
* **Detailed description** — confirm that you are the current owner and that you want the subdomain released
* **Confirmation checkboxes** — check both boxes before submitting
The CreeperHUB team will process the removal and close the issue once complete. The subdomain will be deleted from the `/domains` folder in the main repository.
## Forced removal
CreeperHUB may remove a subdomain without prior notice if it violates the Terms of Service, is involved in abuse or illegal activity, or is subject to a verified third-party takedown request. Grounds for forced removal include:
* Violation of the Terms of Service
* False or misleading registration information
* Abuse, phishing, malware, or scam activity
* A verified DMCA-style takedown from a legitimate rights holder
For high-risk security issues, DMCA requests, or takedown requests, contact [@giocoliere](https://github.com/giocoliere) directly on GitHub. For the full third-party takedown process, see [Takedowns and blacklisting](/policies/takedowns-and-blacklisting).
## The transparency ledger
All forced removals are recorded publicly in the `/removed` folder of the repository. Each entry in the ledger contains:
* **Blacklisted name** — the domain name that was removed
* **Previous owner** — the GitHub account that held the registration
* **Category** — one of `TOS`, `DMCA`, or `OTHER`
* **Requesting party** — who initiated the removal (CreeperHUB or a third party)
* **Reason** — a brief explanation of the violation
This ledger is maintained to ensure transparency around enforcement decisions.
## Blacklisting
Domains removed for violations are placed in the `/blacklisted` folder and cannot be registered again by any user. Voluntary removals may also be blacklisted at CreeperHUB's discretion.
If your subdomain is removed due to a Terms of Service violation, you permanently lose any **legacy limit** you held (granted to users who registered before 02-24-2026). Your account reverts to the standard limit of 2 subdomains per TLD and the legacy allocation cannot be restored.
# Spare records: create nested subdomains in creepers.sbs
Source: https://docs.creepers.sbs/guides/spare-records
Spare records add DNS entries under your subdomain — like mc.yourname.creepers.sbs or docs.yourname.creepers.sbs — all configured in the same registration file.
When you register `yourname.creepers.sbs`, you get exactly that subdomain. Spare records let you go further — they create additional DNS entries that live under your subdomain, such as `mc.yourname.creepers.sbs` or `docs.yourname.creepers.sbs`. You define them inside the `"record"` object of your registration file, alongside your main DNS records.
## How spare records work
A spare record is an array with three elements:
1. **Subdomain prefix** — the label to prepend to your registered subdomain (e.g., `"mc"` creates `mc.yourname.creepers.sbs`).
2. **Record type** — any supported DNS record type: `A`, `AAAA`, `CNAME`, `MX`, etc.
3. **Target** — the value the record points to (an IP address, hostname, etc.).
The key name starts with `"spare_record"` and is incremented for each additional entry: `"spare_record"`, `"spare_record_2"`, `"spare_record_3"`, and so on. You can add as many as you need.
```json theme={null}
"spare_record": ["mc", "A", "198.51.100.50"],
"spare_record_2": ["docs", "CNAME", "yourname.github.io"],
"spare_record_3": ["api", "A", "198.51.100.51"]
```
The example above, registered under the subdomain `yourname` on `creepers.sbs`, would create:
* `mc.yourname.creepers.sbs` → A record pointing to `198.51.100.50`
* `docs.yourname.creepers.sbs` → CNAME pointing to `yourname.github.io`
* `api.yourname.creepers.sbs` → A record pointing to `198.51.100.51`
## Full example with spare records
The following is a complete registration file for a developer using spare records to separate their Minecraft server, documentation site, and API from their main web presence.
```json devsetup.json theme={null}
{
"title": "Dev Setup",
"description": "Personal developer hub with a portfolio, Minecraft server, docs, and API.",
"domain": "creepers.sbs",
"subdomain": "devsetup",
"country_code": "none",
"owner": {
"github_user": "https://github.com/devsetup",
"email": "hello@devsetup.dev",
"discord": "@devsetup"
},
"record": {
"spare_record": ["mc", "A", "198.51.100.50"],
"spare_record_2": ["docs", "CNAME", "devsetup.github.io"],
"spare_record_3": ["api", "A", "198.51.100.51"],
"A": ["198.51.100.10"],
"TXT": ["google-site-verification=abc123xyz"]
},
"proxy": "true"
}
```
This file produces the following DNS entries:
| Subdomain | Type | Target |
| ---------------------------- | ----- | ------------------------------------ |
| `devsetup.creepers.sbs` | A | `198.51.100.10` |
| `mc.devsetup.creepers.sbs` | A | `198.51.100.50` |
| `docs.devsetup.creepers.sbs` | CNAME | `devsetup.github.io` |
| `api.devsetup.creepers.sbs` | A | `198.51.100.51` |
| `devsetup.creepers.sbs` | TXT | `google-site-verification=abc123xyz` |
## Spare records when registering multiple TLDs
If you register across multiple TLDs using the complete template, spare records are scoped to the TLD section they appear in. The `"record"` block handles `creepers.sbs`, the `"record_2"` block handles `creepers.cloud`, and so on. Each block has its own independent set of spare records.
```json theme={null}
"record": {
"spare_record": ["mc", "A", "198.51.100.50"],
"A": ["198.51.100.10"]
},
"proxy": "true",
"domain_2": "creepers.cloud",
"record_2": {
"spare_record": ["status", "CNAME", "status.devsetup.dev"],
"A": ["198.51.100.10"]
},
"proxy_2": "false"
```
In this example, `mc.devsetup.creepers.sbs` is created under `.sbs`, while `status.devsetup.creepers.cloud` is created under `.cloud` — they are completely independent.
Spare record prefixes follow the same naming restrictions as top-level subdomains. Reserved names such as `mc`, `play`, `admin`, and country codes are not allowed as root subdomains, but they are allowed as spare record prefixes under your own subdomain (e.g., `mc.yourname.creepers.sbs` is fine).
You can use spare records to solve the `CNAME` limitation — if you need a `CNAME` for your main subdomain but also want an `MX` record, put the `CNAME` as a spare record on a different prefix, keeping the main subdomain free for the `MX`.
# Transfer your creepers.sbs subdomain to another account
Source: https://docs.creepers.sbs/guides/transferring-a-subdomain
Move subdomain ownership to a new GitHub account. Requires Discord server membership and is processed manually by CreeperHUB after identity verification.
A transfer moves ownership of your subdomain from your current GitHub account to a different GitHub account. This is useful if you are handing off a project, changing GitHub usernames, or passing control to a collaborator. Transfers are handled manually by the CreeperHUB team — there is no self-service option. GitHub ownership is verified through your registration file, and Discord is used as an additional layer of identity confirmation.
## Requirements before you request a transfer
Before contacting support, make sure all of the following are true:
* Your **Discord username** is listed in the `"discord"` field of your registration JSON file. If it is not, you need to add it via a Pull Request before requesting the transfer. See [Update DNS records](/guides/updating-records).
* You are a member of the **official CreeperHUB Discord server**: [creepers.sbs/discord](https://creepers.sbs/discord).
* The transfer request comes **explicitly from the current owner**. Transfers requested by anyone other than the current registered owner will not be processed.
If you change your Discord username at any point, you must update the `"discord"` field in your registration file to match. An outdated Discord username will prevent identity verification and block any future transfer request.
## How to initiate a transfer
Open your registration JSON file in your fork and confirm the `"discord"` field in the `"owner"` block contains your current Discord username (e.g., `"@yourusername"`). If it is missing or outdated, update it and open a Pull Request to merge the change before proceeding.
If you are not already a member, join the official server at [creepers.sbs/discord](https://creepers.sbs/discord). Membership is required for identity verification during the transfer process.
Reach out to CreeperHUB via one of the two official channels below. Include the following information in your message:
* The subdomain you want to transfer (e.g., `yourname.creepers.sbs`)
* Your current GitHub username
* The GitHub username of the new owner
**Contact options:**
* **Email:** [hello@creeperhub.net](mailto:hello@creeperhub.net)
* **Discord:** [creepers.sbs/discord](https://creepers.sbs/discord)
The CreeperHUB team will verify your identity using your GitHub account and your Discord username, then process the transfer. You will be notified once it is complete.
Discord is used as **additional identity verification** only — it does not replace GitHub ownership checks. The team will confirm that the GitHub account submitting the request matches the registered owner in the JSON file.
# Update the DNS records for your creepers.sbs subdomain
Source: https://docs.creepers.sbs/guides/updating-records
Edit your registration JSON file and open a new Pull Request to update DNS records. Includes steps for syncing your fork and re-confirming the Terms of Service.
Updating your subdomain's DNS records works the same way as the original registration: you edit your JSON file and open a new Pull Request against the `creepersbs/register` repository. There is no web panel — every change must go through GitHub. Once your PR is merged, the updated records go live within the normal review window.
If you already have a fork of `creepersbs/register`, sync it with the latest `main` branch before making changes. Out-of-date forks can cause merge conflicts that delay your PR.
On GitHub, open your fork and click **Sync fork** → **Update branch** to pull in the latest changes.
Navigate to the `/domains` folder in your fork and open your existing registration file (e.g., `yourname.json`). Update the record values you want to change — for example, a new IP address in the `"A"` field, or an updated `"TXT"` entry.
Do not rename the file or change the `"subdomain"` value. Only update the fields that need to change.
Changing your `"proxy"` field between `"true"` and `"false"` also requires a PR update. Include the new value in the same edit.
Before opening the PR, paste your updated file into [JSONLint](https://jsonlint.com/) and confirm it returns **Valid JSON**. A single misplaced comma or missing bracket will cause your PR to be rejected.
Creepers enforces a **Zero-Manual-Fix Policy**. If your JSON is invalid, your PR will be rejected outright — it will not be corrected by the team. You must fix the error and resubmit.
In your fork, click **Contribute** → **Open Pull Request**. The PR description will be pre-filled with the official template. Fill it in as follows:
* **Type of PR** — check **Update / Change DNS Records**
* **Your information** — GitHub username and email
* **Subdomain request details** — the subdomain you are updating
* **Description** — briefly describe what you are changing and why
* **Confirmation checkboxes** — all three must be checked
If you are updating **NS records specifically**, select **Change NS records** instead of "Update / Change DNS Records".
As of the **04-17-2026** Terms of Service update, you must re-confirm the Terms of Service on every PR submission. All three confirmation checkboxes in the template must be checked before your PR can be reviewed.
A CreeperHUB team member will review your PR manually. Once merged, your updated DNS records go live. Review time is typically 24 hours to one week.
# What is creepers.sbs? Free subdomain provider by CreeperHUB
Source: https://docs.creepers.sbs/introduction
creepers.sbs is a free subdomain service operated by CreeperHUB for developers and Minecraft players, registered entirely via GitHub Pull Requests (PR).
creepers.sbs is a free subdomain provider operated by [CreeperHUB](https://creeperhub.net). Instead of a control panel or paid account, registration works through GitHub: you fork the repository, add a JSON file describing your DNS records, open a Pull Request, and a team member reviews and merges it. Once merged, your subdomain goes live — no fees, no credit card, no waiting list.
Follow the step-by-step guide to get your subdomain live.
Browse the supported domains and pick the right one for your project.
Detailed walkthrough of the JSON format and PR process.
Read the rules and responsibilities before submitting a request.
## Who is it for?
creepers.sbs is open to anyone who wants a free, real domain name on the internet.
* **Developers** — give your project, API, or side project a proper subdomain instead of sharing a bare IP address.
* **Minecraft players and server owners** — point a friendly domain at your server's IP so players connect without memorizing numbers.
* **Anyone** — personal sites, portfolios, hobby projects, or anything else that deserves a real URL.
There are no requirements beyond a GitHub account and a working service to point the subdomain at. Pointing to placeholder IPs like `1.1.1.1` or `localhost` is not allowed — your service must already exist and be reachable when you open the PR.
## DNS infrastructure
Your subdomains are backed by three DNS providers, giving you broad record type support and reliable uptime.
| Provider | Role |
| ------------------------------------ | ----------------------------------------- |
| [Cloudflare](https://cloudflare.com) | Primary DNS and optional proxy protection |
| [Gcore](https://gcore.com) | Additional DNS redundancy |
| [deSEC](https://desec.io) | Secondary DNS provider |
The optional Cloudflare proxy (`"proxy": "true"`) hides your origin IP and adds DDoS protection, but it does not work with services hosted behind another Cloudflare account or Cloudflare Workers. For those cases, set `"proxy": "false"`.
## Planned features
The service is actively developed. Features planned for the future include:
* **Web panel** — a self-service interface that will eventually replace the GitHub PR workflow
* **Automation** — faster PR approval without manual review
* **Public domain list** — a browsable list of all registered subdomains and their status
* **Webring** — a community discovery feature linking Creepers-registered sites
* **Whois service** — public whois lookups with optional privacy protection
Until the web panel launches, all registrations go through GitHub Pull Requests as described in the [quickstart](/quickstart).
# Restricted and reserved names on creepers.sbs subdomains
Source: https://docs.creepers.sbs/policies/restricted-names
Names unavailable for root registration: country codes, Minecraft/staff terms, official system names, and social media impersonation are prohibited on all TLDs.
Not every name is available for registration. CH maintains a list of restricted and reserved terms to prevent impersonation, confusion with official services, and misuse of the registry. If your requested name falls into any of the categories below, your PR may be rejected or removed — without prior notice.
CH reserves the right to update the restricted names list at any time without prior notice. A name that was available yesterday may be reserved tomorrow. Always check before submitting a request.
## Restricted categories
You cannot register a country or continent code as a **root** subdomain (e.g., `en.creepers.sbs`, `eu.creepers.sbs`, `us.creepers.cloud`).
These codes are reserved for potential future regional use.
**Nested use is allowed.** For example, `anything.en.creepers.sbs` is permitted as long as the root subdomain (`anything`) is not itself restricted.
Names that imply an official shop, store, or ecommerce presence associated with creepers.sbs or CH are prohibited. This includes terms that would make a casual visitor believe they are interacting with an official commercial service.
Because there are currently **no official creepers.sbs Minecraft servers**, names that imply official server status are prohibited as root subdomains. Restricted terms include:
`mc` · `play` · `smp` · `network` · `bedwars` · `staff` · `admin`
**Nested use is allowed.** For example, `mc.yourserver.creepers.sbs` is permitted — the restriction applies only to registering `mc.creepers.sbs` directly.
Names that could be mistaken for official CH system services are reserved. These include (but are not limited to):
`about` · `status` · `whois` · `translate`
Similar terms that imply infrastructure, tooling, or official registry operation fall under this category as well.
CH maintains a full list of explicitly reserved domain names. You must check this list before submitting a request.
[View the reserved names list on GitHub](https://github.com/creepersbs/register/tree/main/domains/reserved/list.json)
This list is updated without notice. If a name you registered later appears on the reserved list, it may be subject to removal.
Names that could be mistaken for official creepers.sbs or CreeperHUB social media accounts are prohibited. This includes variations of account names CH uses or could reasonably use on any platform.
## What happens if you violate these rules
Requests for restricted names are rejected outright. If a restricted name is discovered after registration (for example, because the reserved list was updated), CH may remove the subdomain without prior notice or appeal.
Repeated violations may result in account review and potential blacklisting. See [Takedowns & Blacklisting](/policies/takedowns-and-blacklisting) for details on what happens after a removal.
# Subdomain takedowns, DMCA requests, and blacklisting
Source: https://docs.creepers.sbs/policies/takedowns-and-blacklisting
How CreeperHUB handles subdomain removals, what makes a valid third-party takedown request, the transparency ledger format, and what blacklisting prevents.
CH may remove any registered subdomain at any time and for any reason within the scope of these policies. This page explains what triggers a takedown, how third-party requests are evaluated, and what happens to a domain after it is removed.
CH reserves the right to refuse, suspend, or revoke service at any time without prior notice.
## Conditions for removal by CH
A subdomain may be suspended or removed if any of the following apply:
* The Terms of Service are violated
* False or misleading information was provided during registration
* The GitHub account or repository used for the registration is deleted
* The subdomain is used for abuse, scams, phishing, malware distribution, or illegal activity
* A verified third party submits a valid takedown request
## Third-party takedown requests
CH accepts takedown requests from outside parties under specific conditions. Anonymous, unverifiable, or frivolous requests are ignored without response.
### Who can submit a request
To be considered, the requesting party must be one of the following:
The legitimate copyright holder of the affected content or product, or a legally authorized representative acting on their behalf.
A notable individual, company, or organization whose name, brand, or product is being abused or impersonated by the subdomain in question.
A recognized institution or authority reporting a verified legal violation connected to the subdomain.
### What you must provide
A valid takedown request must include **clear and verifiable proof** of the violation. Depending on the nature of the request, this may include:
* Evidence of copyright ownership or registered trademark rights
* Documentation or public records proving your affiliation or legal standing
* A clear explanation of how the subdomain violates your rights or these policies
* Any additional information reasonably required by CH to evaluate the request
Requests that cannot be verified, that appear frivolous or retaliatory, or that are submitted anonymously will be disregarded entirely. CH reserves the right to reject any request that does not meet these requirements.
### How to submit
For DMCA, high-risk, or sensitive takedown requests, contact the maintainer directly:
For DMCA, legal, or sensitive takedown requests only. General support questions will not be answered through this channel.
## Transparency ledger
CH maintains a public record of all removed domains in the [`/removed` folder](https://github.com/creepersbs/register/edit/main/domains/removed) of the repository. Each entry in the ledger includes:
| Field | Description |
| ---------------- | --------------------------------------------- |
| Blacklisted name | The subdomain that was removed |
| Previous owner | The GitHub account that held the registration |
| Category | `TOS`, `DMCA`, or `OTHER` |
| Requesting party | Who initiated the removal (CH or third party) |
| Reason | A brief description of the violation |
This ledger exists to provide accountability and transparency for the community.
## Blacklisting
Domains that are removed for violations are moved to the `/blacklisted` folder. A blacklisted domain **cannot be reregistered** by anyone — not even the original owner or a new party with a legitimate use case.
If you believe a domain was blacklisted in error, contact CH via [hello@creeperhub.net](mailto:hello@creeperhub.net) or the [official Discord server](https://creepers.sbs/discord). CH is not obligated to reinstate any blacklisted domain.
# Terms of Service for the creepers.sbs subdomain registry
Source: https://docs.creepers.sbs/policies/terms-of-service
Terms governing creepers.sbs subdomain registration. Covers acceptance, Zero-Manual-Fix Policy, user responsibilities, removal conditions, and service disclaimer.
By submitting any Pull Request, Issue, or other request in the [creepersbs/register](https://github.com/creepersbs/register) repository, you explicitly confirm that you have read, understood, and agree to these Terms of Service. Acceptance is required every time a PR is submitted or updated. If you do not agree, do not submit a request.
This page is a plain-English summary of the authoritative Terms of Service. For the binding, canonical version, refer to [TERMS.md on GitHub](https://github.com/creepersbs/register/blob/main/TERMS.md).
## Acceptance of terms
You accept these Terms every time you submit or update a Pull Request — not just on your first registration. The checkmark confirmation in the PR template is mandatory and carries legal weight. There are no exceptions.
## Relationship with the MIT License
The source code in this repository is licensed under the MIT License. That license applies **only to the code itself** — it does not grant you any right to use the `creepers.sbs`, `creepers.cloud`, `creepers.pro`, or `creepers.lol` services, domains, or infrastructure. Use of the service is governed exclusively by these Terms.
## Service description
[creepers.sbs](http://creepers.sbs) is a free subdomain registry operated by **CreeperHUB / Giocoliere** (referred to as "CH"). Subdomains are requested via GitHub Pull Requests, reviewed manually, and approved at the sole discretion of CH. Once approved, you receive control of the DNS records associated with your subdomain, including the option to use custom Name Server (NS) records.
## Request process
All requests must use the official templates:
* **Single TLD:** [`domains/template.json`](https://github.com/creepersbs/register/blob/main/domains/template.json)
* **All TLDs at once:** [`domains/complete.template.json`](https://github.com/creepersbs/register/blob/main/domains/complete.template.json)
Requests that do not follow the templates, or that contain false or incomplete information, may be rejected without explanation.
CH enforces a strict **Zero-Manual-Fix Policy**. You are solely responsible for ensuring your PR is correctly formatted before submission:
* **JSON must be valid.** Syntax errors will cause your PR to be rejected or deferred until you fix them yourself — staff will not correct them for you.
* **Files must be in the correct directory.** Staff will no longer move or rename files on your behalf.
* **No placeholder targets.** Requests must point to an already existing, functional service. Pointing to `localhost`, `test`, `1.1.1.1`, `0.0.0.0`, or similar placeholder addresses is strictly forbidden.
If you have questions before submitting, [open an issue](https://github.com/creepersbs/register/issues/new).
## Your responsibilities
You are solely responsible for:
* DNS configuration and ongoing management
* All content hosted on your subdomain
* Every website, service, application, or server reachable through the subdomain
* Compliance with all applicable laws and regulations
CH assumes **no responsibility** for abuse, illegal activity, DNS misconfiguration, downtime, data loss, reputational damage, or any other consequence arising from your use of the subdomain.
## DNS and Name Server usage
If you request or configure custom NS records, you take on full management of your DNS zone through your own provider. CH has no technical control over your DNS configuration once NS records are delegated. Any misuse, error, or violation remains entirely your responsibility. CH reserves the right to revoke a subdomain if your DNS usage violates these Terms.
## Removal and takedown conditions
CH may suspend or remove any subdomain if:
* These Terms are violated
* False or misleading information was provided during registration
* The GitHub account or repository used for registration is deleted
* The subdomain is involved in abuse, scams, phishing, malware, or illegal activity
* A verified third party submits a valid takedown request
See [Takedowns & Blacklisting](/policies/takedowns-and-blacklisting) for the full process and third-party verification requirements.
## Domain lifecycle
Subdomains are reserved **indefinitely** unless removed by CH or transferred by you. If you need to transfer a subdomain to another user or organization, contact CH via:
* **Email:** [hello@creeperhub.net](mailto:hello@creeperhub.net)
* **Discord:** [creepers.sbs/discord](https://creepers.sbs/discord)
To complete a transfer, you must be a member of the official Discord server and have your Discord username listed in your registration file.
## Blacklisting
Domains that are removed for serious violations are placed in the `/blacklisted` folder and cannot be reregistered by anyone.
## Disclaimer
This service is provided **"as is"**, without warranties of any kind. CH reserves the right to modify these Terms at any time, and to refuse, suspend, or revoke service without prior notice. Continued use of the service after a Terms update constitutes your acceptance of the updated Terms.
***
**Last updated:** 04-17-2026
# Subdomain registration limits per creepers.sbs account
Source: https://docs.creepers.sbs/policies/usage-limits
Standard limit is 2 subdomains per TLD (8 total). Legacy users pre-02-24-2026 may hold up to 10. Includes anti-alt-account policy and per-TLD breakdown.
To keep the registry fair and sustainable, CH enforces per-account limits on how many subdomains you can hold across all available TLDs. These limits apply regardless of how many GitHub accounts you use — creating alternate accounts to bypass them is a violation of the Terms of Service.
## Standard limits
Each account is entitled to **2 subdomains per TLD**, for a maximum of **8 subdomains** across all four TLDs.
| TLD | Max subdomains |
| -------------- | -------------- |
| creepers.sbs | 2 |
| creepers.cloud | 2 |
| creepers.pro | 2 |
| creepers.lol | 2 |
| **Total** | **8** |
Limits may change. Check the [changelogs](https://github.com/creepersbs/register/blob/main/changelogs) to stay up to date.
## Registrations are per-TLD, not cross-TLD
Claiming `myname.creepers.sbs` does **not** automatically reserve `myname.creepers.cloud`, `myname.creepers.pro`, or `myname.creepers.lol`. Each TLD is treated as a separate registration. If you want the same name on multiple TLDs, you must submit a separate PR for each one (subject to the per-TLD limit).
## Legacy users (pre 02-24-2026)
If you successfully had a PR merged **before 02-24-2026 (CET)**, you qualify for a grandfathering exception on the two original TLDs.
| TLD | Legacy max | Standard max |
| ---------------- | ---------- | ------------ |
| creepers.sbs | 3 | 2 |
| creepers.cloud | 3 | 2 |
| creepers.pro | 2 | 2 |
| creepers.lol | 2 | 2 |
| **Legacy total** | **10** | **8** |
If any of your legacy subdomains are removed due to a ToS violation or a valid third-party takedown request, you **cannot recover the legacy slot**. Once removed, that TLD reverts to the standard 2-subdomain limit for your account — permanently.
## Anti-alt-account policy
Creating multiple GitHub accounts to claim more subdomains than your limit allows is strictly prohibited.
CH actively reviews accounts that submit PRs. Accounts that appear to have been created solely for the purpose of claiming subdomains on this registry — with no other activity — will have their requests cancelled.
Fraudulent or duplicate requests create significant delays in the review queue for every user. Accounts found to be evading limits may be blacklisted, affecting all subdomains associated with that identity.
If you believe your account was incorrectly flagged, contact CH via [hello@creeperhub.net](mailto:hello@creeperhub.net) or the [official Discord server](https://creepers.sbs/discord).
# Quickstart: register your first creepers.sbs subdomain
Source: https://docs.creepers.sbs/quickstart
Step-by-step guide to registering a free subdomain on creepers.sbs: fork the repo, add a JSON file with your DNS records, and open a Pull Request.
This guide walks you through registering a subdomain from start to finish. The entire process happens on GitHub: you add a JSON file describing your DNS records and open a Pull Request for review. No account signup, no payment details.
Go to [creepersbs/register](https://github.com/creepersbs/register) on GitHub. Click **Star** to follow updates, then click **Fork** to create your own copy of the repository.
You will make all your changes in your fork and then open a Pull Request back to the main repository.
In your fork, navigate to the `/domains` folder and create a new file. The file name must exactly match the subdomain you want — for example, if you want `myproject.creepers.sbs`, create `myproject.json`.
Use the template below as your starting point. Delete every comment (the text in parentheses) before submitting — the file must be valid JSON.
```json myproject.json theme={null}
{
"title": "My Project",
"description": "A short description of your website or server.",
"domain": "creepers.sbs",
"subdomain": "myproject",
"country_code": "none",
"owner": {
"github_user": "https://github.com/yourusername",
"email": "you@example.com",
"discord": "optional"
},
"record": {
"A": ["203.0.113.10"],
"TXT": ["example-verification=abc123"]
},
"proxy": "false"
}
```
**Key fields explained:**
* `"domain"` — choose one of the available TLDs: `creepers.sbs`, `creepers.cloud`, `creepers.pro`, `creepers.lol`, and any other future domain.
* `"subdomain"` — must match the file name exactly (without `.json`).
* `"country_code"` — set to `"none"` unless you need a regional sub-prefix (e.g., `en.yourname.creepers.sbs`). Currently used as additional metadata.
* `"record"` — include only the record types you need. Supported types: `A`, `AAAA`, `CNAME`, `MX`, `NS`, `TXT`, `SRV`.
* `"proxy"` — set to `"true"` to enable Cloudflare proxy protection, or `"false"` to use DNS-only mode.
A `CNAME` record cannot coexist with any other record type of the same name (except `TXT`). If you need both a `CNAME` and other record types, use spare records — see the [spare records guide](/guides/spare-records).
Cloudflare proxy (`"proxy": "true"`) does not work with services hosted on another Cloudflare account or Cloudflare Workers. Use `"proxy": "false"` for those.
Before opening a Pull Request, paste your file contents into [JSONLint](https://jsonlint.com/) and confirm it shows **Valid JSON**. A single misplaced comma or missing quote will cause your PR to be rejected.
[creepers.sbs](http://creepers.sbs) enforces a **Zero-Manual-Fix Policy**. If your JSON has syntax errors, your PR will be rejected and you will need to fix it yourself and resubmit. The team will not correct formatting on your behalf.
In your fork on GitHub, click **Contribute** then **Open Pull Request**. Fill in the PR description using the provided template, check all boxes in the checklist, and confirm you agree to the [Terms of Service](/policies/terms-of-service).
Make sure:
* Your JSON file is in the `/domains` folder (not in a subfolder).
* The file name matches your `"subdomain"` value exactly.
* You are not pointing to placeholder IPs (`1.1.1.1`, `0.0.0.0`, `localhost`) — your service must be live and reachable.
A CreeperHUB team member will review your PR manually. Approval typically happens within **24 hours to one week**. Once merged, your subdomain is live.
If your PR is rejected, the reviewer will explain why. Common reasons include invalid JSON, placeholder IPs, or a name that appears on the [restricted names list](/policies/restricted-names).
## Registering multiple TLDs at once
If you want the same subdomain name across several TLDs simultaneously (e.g., `myproject.creepers.sbs` and `myproject.creepers.cloud`), use the `complete.template.json` format instead of the single-TLD template.
The complete template lets you configure different DNS records for each TLD in a single file and a single Pull Request. See [complete.template.json](https://github.com/creepersbs/register/blob/main/domains/complete.template.json) for the full format. Each additional TLD uses a numbered suffix: `"domain_2"`, `"record_2"`, `"proxy_2"`, and so on.
Check the [usage limits](/policies/usage-limits) before registering multiple TLDs — you may register up to 2 subdomains per TLD, with a maximum of 8 subdomains in total.
# Contact CreeperHUB: support channels and when to use them
Source: https://docs.creepers.sbs/support/contact
The right support channel for registration issues, subdomain transfers, DMCA notices, and security reports — GitHub Issues, Discord, email, and direct contact.
CreeperHUB offers several ways to get help depending on the nature of your request. Choose the channel that best matches your situation — using the right one will get you a faster response. Note that the Discord contact form option requires you to join the official server before a response can be sent.
Open a public issue for registration questions, PR feedback, or general bugs in the repository.
Submit a private request via the CreeperHUB contact form. Choose Email or Discord as your preferred reply method.
Join the official creepers.sbs Discord server for real-time community support and transfer requests.
Contact the maintainer directly for high-risk security issues, DMCA notices, and sensitive takedown requests.
## Which channel should I use?
**General questions** — Open a [GitHub Issue](https://github.com/creepersbs/register/issues/new/choose). This is the best place for questions about registration format, PR rejections, and policy clarifications. Issues are public, so answers benefit the whole community.
**Transfer requests** — Contact CreeperHUB via the [Discord server](https://creepers.sbs/discord) or the [contact form](https://creeperhub.net/contact). Transfers require identity verification through Discord, so the current owner must be a member of the official server and have their Discord username listed in the registration file. Email alone is not sufficient.
**DMCA and legal requests** — Use the [maintainer's GitHub profile](https://github.com/giocoliere) to initiate contact directly. Third-party takedown requests must include proof of identity and standing; anonymous or unverifiable requests will not receive a response.
The contact form at creeperhub.net requires you to select either Email or Discord as your contact method. If you choose Discord, you must join the [official server](https://creepers.sbs/discord) first, or a reply cannot be sent.
# creepers.sbs subdomain registry: frequently asked questions
Source: https://docs.creepers.sbs/support/faq
Answers on approval timelines, usage limits, PR rejections, Minecraft server setup, custom nameservers, subdomain transfers, and the Zero-Manual-Fix Policy.
creepers.sbs is a free subdomain registry operated by CreeperHUB. Registration is done by submitting a Pull Request to the GitHub repository, and subdomains are approved manually. The questions below cover the most common topics users ask about before and after registration.
After your Pull Request is approved, subdomains typically go live within **24 hours to one week**. Approval is manual, so timing depends on reviewer availability. Make sure your PR follows the template exactly to avoid delays.
Yes. creepers.sbs charges nothing. There are no hidden fees, no credit cards, and no paid tiers. The service is operated by CreeperHUB as a free public resource for developers, Minecraft players, and anyone who wants a personalized online presence.
Yes. You can register the same subdomain name across multiple TLDs (`.sbs`, `.cloud`, `.pro`, `.lol`). Each TLD counts as a separate registration. See the usage limits below for how many you can hold at once.
Fix the issue described in the rejection and resubmit. Common causes of rejection include:
* **JSON syntax errors** — validate your file at [JSONLint](https://jsonlint.com/) before submitting
* **Reserved or restricted names** — check the [reserved names list](https://github.com/creepersbs/register/tree/main/domains/reserved/list.json)
* **Placeholder IPs** — pointing to `localhost`, `0.0.0.0`, `1.1.1.1`, or similar is not allowed; the service must already exist
CreeperHUB enforces a Zero-Manual-Fix Policy, meaning reviewers will not edit your file for you. The fix is always the requester's responsibility.
Standard users may hold up to **8 subdomains total** — a maximum of **2 per TLD** across `.sbs`, `.cloud`, `.pro`, and `.lol`. `run-it.tech` is also available; its limit is not separately specified in the ToS so treat it consistently with the others.
**Legacy users** (those who successfully submitted a PR before 02-24-2026 CET) may retain up to **3 names** for the original TLDs (`.sbs` and `.cloud`), for a possible total of 10. Legacy allocations are lost permanently if the domains are removed for Terms violations.
Using multiple accounts to exceed these limits is prohibited under the Anti-Alt Account Policy.
Yes. You can request NS records in your registration file to delegate your subdomain to your own DNS provider. When custom NS records are in use, CreeperHUB has no technical control over your DNS configuration, and all responsibility for that zone rests with you.
Yes. To point a subdomain at a Minecraft server, use a combination of **SRV** and **A** records in your registration file. Set `proxy` to `false` when using SRV records, as proxied mode is incompatible with raw TCP connections used by Minecraft.
The Zero-Manual-Fix Policy means that Pull Requests containing errors are **rejected outright** rather than corrected by a reviewer. Reviewers will not move files, fix JSON, or adjust your DNS records on your behalf.
You are solely responsible for submitting a correctly formatted PR. Use the official templates and validate your JSON before opening a PR.
Yes, subdomain transfers are supported. To initiate a transfer, the current owner must contact CreeperHUB through Discord (the official server is required for identity verification). See the [transfer guide](/guides/transferring-a-subdomain) for the full requirements and steps.
# Responsible disclosure and security policy for creepers.sbs
Source: https://docs.creepers.sbs/support/security
How to report security vulnerabilities in creepers.sbs infrastructure, what is in and out of scope, and which contact method to use for sensitive disclosures.
CreeperHUB takes security issues seriously and welcomes responsible disclosure from the community. If you discover a vulnerability affecting the creepers.sbs registry infrastructure or automation, please contact us privately before making any public disclosure. This page describes what is in scope, how to reach us, and what to expect.
## Scope
This security policy covers infrastructure and systems directly managed by CreeperHUB.
**In scope:**
* Repository infrastructure (the `creepersbs/register` GitHub repository and its configuration)
* Automation and scripts used in the registration and review pipeline
* DNS records and zones under direct CreeperHUB control
**Out of scope:**
* User-managed DNS zones (subdomain owners who control their own records)
* External nameservers delegated to third-party providers via NS records
* Content, services, or servers operated by individual subdomain owners
If you believe a subdomain owner is hosting abusive or illegal content, that is a takedown request rather than a security report. See the [contact page](/support/contact) for DMCA and legal channels.
## How to report
Use one of the following methods to report a security issue:
* **Email:** [support@creeperhub.net](mailto:support@creeperhub.net)
* **Contact form:** [creeperhub.net/report](https://creeperhub.net/report) — select Email or Discord as your reply method; Discord requires joining the official server
* **High-risk or sensitive issues only:** Contact the maintainer directly via [@giocoliere on GitHub](https://github.com/giocoliere)
Do not publicly disclose a security vulnerability — in a GitHub issue, social media post, or anywhere else — before contacting us privately. Public disclosure before a fix is in place puts users at risk and may prevent us from coordinating a response.
After you reach out, we will acknowledge your report and work with you on next steps. We do not have a formal bug bounty program, but we appreciate responsible disclosure and will credit contributors where appropriate.