Former DyNS services

The old dynamic DNS and URL forwarding services are retired. Under its new ownership, dyns.cx now provides a public domain checker. It does not continue the former service or support former accounts.

A familiar address, a different purpose

For many years, DyNS helped people reach home computers and servers through a memorable hostname, even when their internet connection’s IP address changed. Its archived website also offered static URL forwarding, forwarding to a changing IP address and port, and versions of these services for customers’ own domains.

Some forwarding options hid the destination address or passed a visitor’s requested path to another website. Those functions are not offered here today. Old accounts, hostnames and forwarding destinations cannot be restored through the current website.

How we handle old traffic

We have put protections in place to keep retired services separate from the current checker:

Old device updates are not applied. Automated requests to the known legacy update endpoints are blocked by Cloudflare before reaching our application. They cannot update a hostname or register a device.
Old forwarding destinations are not reused. Visits to inactive web addresses and subdomains lead to the HTTPS homepage, rather than to a former customer’s server or website.
There is no legacy login. The current site does not authenticate former accounts or ask for their passwords.
No router connection is needed. The checker reads public domain information. You do not need to connect a router or install an update client.

These measures prevent the current application from acting on old update instructions. They do not change settings on your device: an old router or update program may keep sending requests until you disable it.

If your router still uses DyNS

Open your router or update program’s settings and look for Dynamic DNS or DDNS.
If its configuration points to dyns.cx or a subdomain such as www.dyns.cx, disable that entry and remove the saved login details.
If you still need remote access through a fixed hostname, configure a currently supported provider using that provider’s instructions.

Do not enter an old DyNS password into this website or send it to us. If you used that same password for another active account, replace it there with a unique password. This is a precaution, not a statement that your account has been compromised.

What about addresses and request data?

We do not use legacy updates to maintain a database of customer devices, changing IP addresses or forwarding destinations. However, blocking a request does not mean that no connection data are processed or logged. Cloudflare handles requests to deliver and protect the site and may retain technical and security records. Our application also uses diagnostic logs and usage-limit records for the current checker. See our privacy policy for details.

Removing an obsolete DDNS configuration is the best way to stop your device sending further updates. Ownership of this domain alone cannot guarantee the security of your router or network.

About this notice

This notice concerns dyns.cx and its subdomains. It does not describe the current ownership or operation of other domains once listed by DyNS.

The historical description is based on the archived DyNS services page. Cisco’s historical DDNS documentation also includes a dyns.cx update configuration, illustrating why an old device may still contact this address.

Questions about the current site? Contact us, without including passwords or other access credentials.