DigitalPlat FreeDomain: five suffixes, custom nameservers, no renewal terms

The registration code is not in this repository

This is a documentation repository and says so in the first quoted note. The public information and learning resources live here, while the application source is maintained separately in DigitalPlatDev/Domain-OSS. Everything at the top level agrees: LEARN.md, README.md, CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md, LICENSE, an assets/ directory, a documents/ directory and a .github/ directory, with Markdown as the primary language and no source tree, no package manifest and no test suite. So you cannot read the code that hands out a name, you cannot self-host the registrar, and any question about how a registration is validated has to be answered by that other repository. The licensing gap matters too. The LICENSE here is AGPL-3.0 and it covers these documents, while this repository does not state which license the application in Domain-OSS is under. Read both before you build anything on top of the service.

Five suffixes, all outside the familiar endings

The available extensions are listed as a closed set of five: .DPDNS.ORG, .US.KG, .QZZ.IO, .XX.KG and .QD.JE, followed by a note that more are coming soon. None of them is .com, .org, .net or a country code second level domain you would type out of habit, which is the first practical decision the service forces on you. For a class project or a homelab hostname that is irrelevant. For anything a stranger has to type from a poster, a link in a chat window, or a certificate that has to match what people read aloud, the suffix becomes part of your credibility problem, and a typo in .QZZ.IO is a dead visit. The list is also the whole catalogue as of this repository's state, and nothing in the documentation ranks the five, says which has the fewest collisions, or says which ones are stable under DNS root changes.

Custom nameservers are the mechanism, and the reason to bother

The flow is short and it is the actual product. Register a domain on the dashboard at https://dash.domain.digitalplat.org/, connect your preferred DNS provider through custom nameservers, and then follow the learning guide to take a project from registration to deployment. In other words the registrar delegates the name to whatever DNS you already run, rather than hosting records for you. That is why the project pairs a free domain with a book-style path in LEARN.md covering setup, general DNS, website, email, operations and advanced topics: the point is to practise delegation, not to get hosting. The email chapter is worth flagging, because nothing in this repository documents a mail service, a mail server or any mail-related guarantee. It is DNS material. Treat it as a lesson about records, and read nothing into it about being able to send mail from the domain you just registered.

The Telegram compromise is the sharpest warning in the repository

The security notice is the most useful paragraph here, and it is blunt. A previous Telegram account and group were compromised and are no longer under the project's control, so the request is not to trust any messages, links or announcements from Telegram, especially anything related to bonuses, earnings or external sites, and Telegram is no longer an official communication channel. Read that as a rule with a shape: an offer of bonuses or earnings arriving on Telegram is, by the project's own statement, a forgery, and there is no version of it that is legitimate. The second consequence is quieter. If you send a support request to that account expecting an answer, nobody is reading it, and the two channels that do answer are the Discord server at discord.gg/ma4RZzMmVW and GitHub Discussions on the repository page. Anything you need on the record has to go through one of those.

Two scale numbers, neither of them dated

The marketing section says that over 500,000 domains have already been registered and calls the service a trusted choice. The story section links a post whose headline says a domain bought at 15 now powers 400,000 users. Both numbers are the project's own, neither carries a date, and they measure different things, a count of registered names against a count of users, so they cannot be reconciled from the text. The origin story itself is the more useful part: a small DNS experiment at 15 handing subdomains to a few friends, which grew into something people rely on, with the founder's own conclusion that running it turned out to be much harder than building it. That admission from the person who wrote the code is worth more to a reader than either figure, because it tells you what to expect from a service run by one person.

Abuse reports run through one mailbox with a days-long window

Abuse handling is described in a single paragraph with a single address. Email [email protected], every report is carefully reviewed, and response times may vary from a few hours to several days depending on the complexity of the case. That range is the interesting part, because it is the only service level the project publishes, and its worst case is several days. If someone registers a phishing or malware host under one of the five suffixes, the site can keep serving for that whole window, and there is no emergency path, no status page and no documented API for a registrar or a browser vendor to push a takedown through. The project states that it takes domain name abuse seriously, which is a posture rather than a mechanism. If your threat model includes a fast blocklist, plan to block at your own DNS provider instead of waiting for a reply from this mailbox.

No renewal price, no transfer path, no deletion policy

The most consequential terms are the ones nobody wrote. Nothing in this repository states what a renewal costs, whether the registration is permanent, how a domain is transferred to another registrar, what happens to a name you stop using, who decides that a name is reclaimed, or how long the dashboard at https://dash.domain.digitalplat.org/ and the site at https://domain.digitalplat.org/ are expected to be available. The parent zones behind .US.KG, .QZZ.IO, .XX.KG and .QD.JE are not explained either, so the repository gives you no way to judge who actually controls the suffix you are typing. What this means for an engineer is that lock-in risk cannot be evaluated from the documentation, only guessed at. A domain you can move is an experiment. A domain you cannot move is a dependency, and this repository gives you nothing to price that dependency.

The last push was 2026-08-12, and the docs ship with no version

The maintenance story here is narrow but clean. The repository is not archived, the last push was on 2026-08-12, and the primary language is Markdown, so what gets reviewed in a pull request is prose: documentation improvements are explicitly welcome, and CONTRIBUTING.md is named as the file to read before opening one. CODE_OF_CONDUCT.md and SECURITY.md are both present. There are no GitHub releases and no version file, which means the tutorial has no numbered editions, and the only way to see what changed in the DNS walkthrough is to read the commit history of LEARN.md and documents/tutorial/index.md yourself. That has a direct consequence for anyone following the guide: since the application is maintained in a different repository, a step here can quietly stop matching the dashboard, and nothing in this tree ties the two together or reports the drift.

Editorial conclusion

Take DigitalPlat FreeDomain for a lab hostname, a class project or a throwaway subdomain, where delegating to your own nameservers is the whole point and losing the name costs nothing. Keep a paid domain for anything you cannot afford to move, because this repository documents no renewal price, no transfer path, no deletion policy and no uptime commitment, and the registration code is not even in this tree. Before you register, open documents/domains/faq.md, then ask on the Discord server whether your chosen suffix is still being issued, since there is no changelog and no release to check.

Frequently asked questions

Official sources

1. Official documentation
2. Official README
3. Project repository