YDNS
ydns.io/Free dynamic subdomaindomains-dns/ydnsJSONcomparereport an errorprovider JSON
- Free allowance
- Unlimited hosts per user on a fair-use model, as dynamic DNS names such as example.ydns.io, plus full DNS hosting for the user's own domains
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- noneno named constraint binds
- Evidence
- documented6 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 | unlimited hosts per user on a fair-use model, as dynamic DNS names such as example.ydns.io, plus full DNS hosting for the user's own domains unit unlimited; metered on none |
|---|
| Price | none stated |
|---|
| Limits | - per-object-cap unlimited hosts per user on a fair-use model; the fair-use limit is not stated source
|
|---|
| Binding | none no count, expiry or review is published; the fair-use model is the one unstated bound; the zone is the vendor's |
|---|
| Identity | email no phone and no card field on the register page |
|---|
| Egress | no query cap published |
|---|
| Per-object cap | no number is published: unlimited hosts per user under a fair-use model, whose limit is not stated |
|---|
| Retention | unverified: no expiry, inactivity or confirmation rule for a free host is stated on the pages read; the introduction says the service is guaranteed to be free for its entire lifetime |
|---|
| Interface | rest a lightweight API that works with most DynDNS implementations; DNSSEC is not available for all zones |
|---|
| Tooling | any DynDNS-compatible client or router, or curl against the vendor's API |
|---|
| Composes with | a free name for a changing address; the vendor also hosts the DNS of the user's own domain for free, which is the way to a zone the user controls |
|---|
| Reliability | the fair-use limit behind 'unlimited' is not stated, and the introduction promises a free service for its entire lifetime; the suffix was not found in the captured Public Suffix List, which is an inference from absence, so a TLS limit may be shared across users of the suffix |
|---|
| Notes | Nothing published binds except an unstated fair-use bound. The zone is the vendor's for ydns.io names; hosting the user's own domain there is the free route to an own zone. The TLS limit is unverified: the suffix has no entry in the captured Public Suffix List, so the Let's Encrypt count for the suffix is shared by inference. |
|---|
| Evidence note | documented the features page, the introduction and the register page were read and quoted; no fair-use figure, expiry rule or suffix list was read; the Public Suffix List statement is an inference from the absence of an entry and cannot be quoted |
|---|
| Parsed numbers | |
|---|
Evidence 6