I’ve recently been tinkering with some local services and small projects, and needed a few subdomains for testing and tunneling. While I was at it, I tested a range of free domain options currently available.
Many long-standing free domain services now either enforce strict speed limits or don’t let you change the NS records, making it impossible to point them directly to Cloudflare. After filtering and testing, I found two projects that are still stable and usable. Neither requires a credit card or an overseas phone number for identity verification, making them suitable for small tests or as backups.
Here are the details from my testing, along with some pitfalls to avoid, for anyone interested:
1. is-a.dev (11.5k GitHub Stars)
Many people are familiar with this long-running project. It mainly uses GitHub PR reviews:
- Requirements: Just a GitHub account; completely free.
- Supported records: CNAME, A, AAAA, URL redirects, and TXT.
- Configuration:
After forking the official repository (is-a-dev/register), create ayourname.jsonfile in thedomains/directory:{ "owner": { "username": "你的GitHub用户名", "email": "你的邮箱" }, "record": { "CNAME": "你的二级地址.pages.dev" } } - Tips to avoid problems:
- The JSON format must be exact. Never add a comma after the last field;
- After you submit a PR, automated Actions run the CI checks. Tests are usually completed and the PR merged automatically within 2–5 minutes;
- Many common prefixes (such as
api,admin, andtest) have already been claimed, so it’s best to search for your desired name on their website before submitting.
2. DigitalPlat FreeDomain (204k GitHub Stars)
Its biggest advantage is that it supports changing the NameServer (NS) records directly, meaning you can point the entire domain to Cloudflare for DNS management:
- Suffixes: Several public suffixes are available, including
.dpdns.org,.us.kg, and.qzz.io. - Requirements: Sign in with GitHub and claim a domain directly.
- Cloudflare setup:
- Register a prefix in their control panel;
- In the Cloudflare dashboard, click „Add a site“, select the Free plan, and obtain the two assigned NS records (such as
ns1.cloudflare.com); - Return to their domain management page, enter the NS records, and save;
- After about 3–5 minutes, Cloudflare should indicate that the change has taken effect. You can then use the orange-cloud CDN proxy, configure WAF, and obtain a free SSL certificate as usual.
- Tips to avoid problems:
- Some less-common suffixes may trigger Cloudflare’s site-addition policy restrictions. Based on my tests,
.dpdns.organd.us.kgare recommended and have the highest success rates; - These public domains need to be manually renewed once a year through the dashboard (also free) to prevent the system from removing them after a long period of inactivity.
- Some less-common suffixes may trigger Cloudflare’s site-addition policy restrictions. Based on my tests,
Are any of you using other stable, useful free domain or DDNS solutions? Feel free to share your recommendations below.