nsupdate.info
www.nsupdate.info/Free dynamic subdomaindomains-dns/nsupdate-infoJSONcomparereport an errorprovider JSON
- Free allowance
- A free dynamic DNS service on the nsupdate.info suffix, several hosts per user, with no ads or spam
- Verdict
- fails: identitythe identity required is not reachable without it
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- noneno named constraint binds
- Evidence
- documented7 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-12-05checked 2026-11-04 (live); stale on 2026-12-05
| Free tier | a free dynamic DNS service on the nsupdate.info suffix, several hosts per user, with no ads or spam unit objects; metered on none |
|---|
| Price | none stated |
|---|
| Binding | none no count, expiry or review is published on the pages read, so no limit binds there; the zone is the operator's |
|---|
| Identity | email new account registration is closed on the public service; the sign-up page states that registration of new accounts is currently not possible, and the software's feature list names local or remote account login |
|---|
| Egress | no query cap published |
|---|
| Per-object cap | unverified: the pages read say multiple hosts per user and publish no number |
|---|
| Retention | unverified: no expiry, inactivity or confirmation rule is stated on the pages read |
|---|
| Interface | rest dynamic updates by the dyndns2 protocol that many routers and clients speak, with a separate secret for each host; a browser-based updater and a manual web update also exist |
|---|
| Tooling | any dyndns2 client or router, curl, or the web interface |
|---|
| Composes with | a free name for a changing address; the zone is the operator's, so it cannot be a Cloudflare zone; the project is open-source software that can also be run by the user on a machine of their own, which ranks after every hosted offer |
|---|
| Reliability | an operator-run public service whose count and expiry rules were not found; the suffix is on the Public Suffix List, so the TLS limit counts per name |
|---|
| Notes | This record is the hosted public service. The count and the withdrawal rule are unverified. The zone is the operator's. The TLS limit does not bind, because the suffix is listed. |
|---|
| Evidence note | documented the home page and the documentation introduction were read and quoted; no count, expiry or sign-up form was read; the TLS statement is an inference from the Let's Encrypt registered-domain rule and the Public Suffix List entry |
|---|
| Parsed numbers | |
|---|
Evidence 7