Open-source project
dnshe/DNSHE-FreeDomains avatar
dnshe/DNSHE-FreeDomains

DNSHE Free Domains: free subdomains under .de5.net, .us.ci and .cc.cd

🌐 DNSHE Official - Stable & Free Subdomains for Developers. Support 180-day renewal window, Anycast DNS, and REST API. (us.ci, cc.cd, de5.net, ccwu.cc)

22,912 stars527 forksUnknownMIT

At a glance

What is it?
The DNSHE-FreeDomains repository is the public information hub for a free subdomain and DNS service aimed at developers, students and open-source projects. It documents four recommended suffixes, a dashboard workflow and a REST API, and includes example API clients (client.py, client.php, client.cjs) under examples/.
Who is it for?
Adopt DNSHE for throwaway and low-stakes hostnames: CI test environments on .us.ci, a demo or portfolio on .de5.net, a webhook or bot endpoint on .bot.cd. Do not adopt it for a production brand, a mail domain you depend on, or anything where losing the name would break users, because the README says free services may be restricted or terminated for operational reasons.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 13 days ago.
What is it written in?
GitHub does not report a main language for this repository.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • dnshe/DNSHE-FreeDomains22,912 ★ · +6,531
Star history
Repository2026-09-212026-11-15
dnshe/DNSHE-FreeDomains16.4k22.9k

6,531 Stars in the last 55 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What DNSHE Free Domains actually is, and who it is for

This repository is not a program you compile. The top level contains LICENSE, README.md with nine translated READMEs, and assets, docs, examples and scripts directories, and the README says the repository "introduces DNSHE Free Domains and provides registration guidance, suffix information, and links to API documentation". The thing you actually use is the hosted service at dnshe.com and the client area at my.dnshe.com. There is no application source tree here; the examples directory holds API client samples (client.py, client.php, client.cjs).

The audience is stated plainly: developers, students and open-source enthusiasts worldwide, served by a non-profit platform driven by a Singapore youth team. The concrete offer is a free subdomain under a suffix DNSHE operates, plus full record management. The README lists A, AAAA, CNAME, MX, TXT, NS, SRV and CAA as supported record types, which is the full set most small projects need, including the CAA records that certificate authorities check before issuing.

The problem it solves is the gap between a localhost port and a real hostname. You want a URL that resolves publicly for a demo, a webhook receiver, a CI preview environment or a student project, and you do not want to buy a domain or hand a card number to a registrar. DNSHE's answer is a shared root domain with per-user subdomains underneath it, and the README states no credit card is required for the basic free service. The trade-off is baked into that model: you do not own the root, so your name lives at the operator's discretion.

The four open registration suffixes and what each one is for

The README highlights four recommended suffixes, each with a suggested use. .de5.net is pitched at personal blogs, portfolios and open-source demos. .us.ci is recommended for continuous integration, SaaS, API endpoints and test environments. .cc.cd is aimed at personal brands, design studios and creative projects. .bot.cd is built for AI bots, chat assistants, webhooks and automation projects.

These recommendations are marketing framing, not technical constraints. Nothing in the README says a .us.ci name cannot host a blog or that a .bot.cd name cannot point at a portfolio. The suffix table is a hint about intended audience, and the real constraints live in the dashboard: the README says to check the console for more suffixes, live availability, registration quotas, and review requirements. That means the four suffixes above are a starting point, and the authoritative list and per-account quotas are only visible in the console.

The renewal rules are worth pausing on. The README's Validity & Renewal section says free domains have a default registration term of 1 year, can be renewed for free within 180 days before expiration, and can be given permanent validity for free through friend assistance under Feature Center, Permanent Domain Upgrade. Expiration reminders are sent by email, and Telegram reminders are available. Check your domain's status in the console.

Installing nothing: registering a domain and pointing it at a server

There is no install step, because there is no software to install. The README's quick start is a five-step browser flow. Create an account at dnshe.com or the client area at my.dnshe.com/register.php. Open the Domain Hub at my.dnshe.com/index.php?m=domain_hub. Search for an available prefix and pick a supported suffix. Register it and add the DNS records your project needs, or change NS to a third-party DNS provider. Connect the domain to your website or application and follow your hosting provider's instructions for verification and HTTPS. Keep your contact email up to date and renew for free when notified.

The only command-line work happens after registration, when you verify that the record you created in the dashboard is actually resolving. The README does not give a verification command, so the check is whatever resolver tool you already have. Query the public resolver for the record type you configured, and query the same name for NS. If the record you created is missing from the first answer, it has not propagated yet or was saved under the wrong name. If the NS answer is empty, you are querying before the zone is live.

For automation, the README links the DNSHE Free Domain API User Guide V2.0 at my.dnshe.com/knowledgebase/13/DNSHE-Free-Domain-API-User-Guide-V2.0.html, repository API documentation in docs/api.md, and credential management in the console, and the examples directory holds client.py, client.php and client.cjs. The README itself says to refer to the latest online documentation and console for endpoints, authentication and request limits. What the README does say about credentials is unambiguous: keep API keys, API secrets and account credentials private, and never commit them to a public repository. If you wire the API into a pipeline, that token belongs in your CI secret store, not in the repository.

Shared root domains mean shared risk, and the README says so

The acceptable use section is the most important part of this repository, because it defines the failure mode. Prohibited activity includes phishing, fraud, malware, spam, DDoS, unauthorized scanning, brute-force attacks, proxy abuse, ban evasion, infringement and other illegal activities, as well as quota bypass. The README also bars resale, rental and unauthorized sharing of account resources.

The enforcement clause is broad: DNSHE may remove DNS records, suspend domains, restrict accounts, refuse renewals, preserve evidence, or report abuse to upstream providers or authorities. Read that as an operational reality, not a threat. Every user sits under the same root domain, so one phishing page on .cc.cd can affect the reputation of every other name on that suffix, including yours. That is the structural cost of a free shared suffix, and it is why the abuse process exists.

There is a second limitation that matters for anything serious. The README states that users are responsible for content published through their domains, that DNSHE is shared infrastructure, and that "Free services may be restricted or terminated for security, compliance, operational, or abuse-prevention reasons." A paid registrar gives you a contractual hold on a name. This gives you a service that can be withdrawn. If your users bookmark the URL, or your email depends on an MX record under the domain, that asymmetry is the whole decision. For a CI preview hostname it is irrelevant. For a mail domain it is disqualifying.

DNSHE against DigitalPlat FreeDomain and a self-hosted setup

The obvious comparison is DigitalPlat FreeDomain. Both give away subdomains under suffixes the operator controls, both manage DNS through a dashboard, and both are aimed at people who do not want to pay for a name. The practical difference to check is the suffix list and the renewal policy on each side, because those are the two things that determine whether your hostname survives the year. DNSHE's README promotes .de5.net, .us.ci, .cc.cd and .bot.cd, and says free domains can be renewed for free within 180 days before expiration. DigitalPlat's own published suffix list and renewal terms are the numbers you would compare against, and this repository does not contain them.

The other direction is running your own DNS. If you own a domain, you can point it at Cloudflare's free tier and get a dashboard, an API and a stable zone under your own control. That costs the price of the domain, roughly the cost of a coffee per year, and it removes the shared-root problem entirely: nobody else's abuse can get your name suspended. The reason to choose DNSHE instead is that you want a hostname without owning anything, or you want several hostnames across different suffixes for separate projects and do not want to manage a registrar account for each. The reason to choose self-hosted or Cloudflare-backed DNS is that you need the name to be yours.

A third option worth naming is simply using a free hosting provider's default subdomain, such as the one your PaaS hands you. That requires no DNS setup at all. It becomes the wrong tool the moment you need a record type the platform does not expose, a CNAME to an external service, or a second hostname pointing at the same app. That is the point where a service like DNSHE starts to make sense.

Maintenance, licence and what this repository actually costs you

The repository is licensed MIT, which covers the contents of this repository: the README and its translations, the docs directory, and the examples and scripts. It does not license the DNSHE service, the domain suffixes, the dashboard or the API. Those are governed by the Terms of Service at dnshe.com/tos.html and the Privacy Policy at dnshe.com/privacy.html, which the README links but does not summarise. If you are evaluating this for a company, the MIT licence on a documentation repository tells you almost nothing about the terms you accept when you register a name.

Maintenance status is worth stating precisely. The last push to this repository was on 2026-11-02, and the repository is not archived. There are no releases. Those signals describe the documentation repository, not the service.

The upgrade cost is close to zero in the software sense and non-trivial in the operational sense. There is nothing to update, no dependency graph, no breaking API migration documented in this repository. What you pay instead is attention: renewal dates, contact information that has to stay current, and the possibility that a suffix you chose is no longer promoted. The README's own advice is to keep contact details up to date and manage renewal through the dashboard. If you ignore the expiration reminders, the README warns the domain may be deleted once it stays unrenewed beyond the redemption period.

Editorial conclusion

Adopt DNSHE for throwaway and low-stakes hostnames: CI test environments on .us.ci, a demo or portfolio on .de5.net, a webhook or bot endpoint on .bot.cd. Do not adopt it for a production brand, a mail domain you depend on, or anything where losing the name would break users, because the README says free services may be restricted or terminated for operational reasons. Before you commit, register one prefix at the Domain Hub, confirm the renewal window in the dashboard, and decide whether the API token you generate there is worth wiring into your pipeline.

Frequently asked questions

What is DNSHE Free Domains and who is it for?

It is a free domain registration and DNS resolution service run as a non-profit platform driven by a Singapore youth team, aimed at developers, students and open-source enthusiasts. This repository introduces the service with registration guidance, suffix information and links to API documentation, rather than being the service itself.

Which suffixes can I register a DNSHE domain under?

The README promotes .de5.net for blogs and demos, .us.ci for CI/CD and API endpoints, .cc.cd for personal brands and creative projects, and .bot.cd for bots, webhooks and automation. It notes that more suffixes may be available after signing in to the DNSHE Console.

Does DNSHE Free Domains have an API for automation?

Yes. The README says the API can manage domains and DNS records programmatically from scripts, CI/CD, testing environments and deployment pipelines. It links the DNSHE Free Domain API User Guide V2.0 and repository API documentation in docs/api.md, and the examples directory has client.py, client.php and client.cjs.

Do I need a credit card to register a DNSHE free domain?

The README states that no credit card is required for the basic free domain service. Registration happens through the DNSHE website or the client area, and DNS records are configured in the dashboard.

What happens if a DNSHE domain is used for abuse?

The README lists prohibited activities including phishing, malware, spam, DDoS and intellectual-property infringement, and states that DNSHE may remove DNS records, suspend domains, restrict accounts, refuse renewals, preserve evidence, or report abuse to upstream providers or authorities.

Official sources

  1. dnshe/DNSHE-FreeDomains on GitHub
  2. Issues
  3. License: MIT
  4. README
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/dnshe-dnshe-freedomains.svg)](https://hysenlabs.com/projects/dnshe-dnshe-freedomains)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/dnshe-dnshe-freedomains.svg)](https://hysenlabs.com/projects/dnshe-dnshe-freedomains)

Was this useful?