- Free allowance
- Free registration under the suffixes .DPDNS.ORG, .US.KG, .QZZ.IO, .XX.KG and .QD.JE, with the user's own authoritative nameservers entered in the dashboard; the default limit is 1 domain per user account
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- any-phone?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- per-object-capthe default limit is 1 domain per user account
- Evidence
- documented12 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-12-04checked 2026-11-03 (live); stale on 2026-12-04
| Free tier | free registration under the suffixes .DPDNS.ORG, .US.KG, .QZZ.IO, .XX.KG and .QD.JE, with the user's own authoritative nameservers entered in the dashboard; the default limit is 1 domain per user account unit objects; metered on object-count |
|---|
| Price | none stated |
|---|
| Limits | - per-object-cap (binding) the default limit is 1 domain per user account source
- write-gated supported suffixes, registration pauses, slot requirements, prices and limits change, and a registration may consume a slot or create a charge; a third-party report says .US.KG and .XX.KG paused new registrations and .QZZ.IO went paid-only, while the repository still lists them source
|
|---|
| Binding | per-object-cap 1 domain per account is the stated cap, and the operator reserves registration pauses and slot or charge requirements per suffix; the zone is the registrant's through delegation, and the suffix listing keeps the TLS limit per name |
|---|
| Identity | any-phone (placeholder) the account tutorial's preparation list names an email address, a name, a valid phone number in the format the form requests and a complete contact address; the dashboard registration form itself was not read: unverified whether the phone is checked by a code |
|---|
| Egress | no query cap published; the service holds no zone, so queries go to the user's chosen DNS provider |
|---|
| Per-object cap | 1 domain per user account by default; sub-subdomains under the assigned name are made at the user's DNS provider |
|---|
| Retention | the dashboard is the source of truth for status and expiration date; renewal windows, fees and slot rules are not stated on the pages read and are said to change |
|---|
| Interface | unknown a web dashboard at dash.domain.digitalplat.org that needs an account (unverified: behind a sign-up); the tutorial has an API chapter whose content was not read. The service stores only the delegation: A, CNAME, MX and TXT records are managed at the external DNS service the nameservers name |
|---|
| Tooling | the DigitalPlat dashboard, then an external authoritative DNS service of the user's choice |
|---|
| Composes with | the delegation can point at an external DNS service such as Cloudflare, which makes the name a zone of the registrant's; the suffix is on the Public Suffix List |
|---|
| Reliability | the operator can pause a suffix, change slots or charges, or suspend a domain, and a third party reports two suffixes paused and one gone paid-only |
|---|
| Notes | The zone is the registrant's: the service stores only NS delegation, so a Cloudflare zone or any DNS host can serve it. The operator can still withdraw it, because a suffix can be paused, put behind a slot or charge, or a domain suspended. The TLS limit does not bind, because the suffixes are listed and each name counts alone. The dashboard is behind a login wall, so the live slot and renewal rules are unverified. |
|---|
| Evidence note | documented the repository README, FAQ and tutorial pages were read and quoted; the dashboard answered a login wall, so the live registration form, the current slot rule and the renewal terms are unverified; the suffix status report is third-party |
|---|
| Parsed numbers | |
|---|