The domains are missing from the public suffix list. This impacts how cookies are handled by the domain names, with concerns the browser will allow software to set the cookie on the shared domain name instead of the subdomain. This can be a security problem. Getting added to the PSL may not happen: https://github.com/publicsuffix/list/pull/79

It can be difficult to get a free HTTPS certificate for your subdomain. Let's Encrypt applies per-domain name rate limits and these domain names see lots of issuance requests. There's a process to lift those limits, but last I checked FreeDNS didn't use it. You can still, of course, pay for a certificate.

There's tons of abuse on free domains so you may find that your domain is blocked on various lists.

Here are some compelling alternatives I use now, which manage these issues better:

- https://messwithdns.net/ - Exceptionally well-made DNS console for learning DNS

- https://open-domains.com/ - Uses Cloudflare, great Discord group

- Even more: https://free.hrsn.dev/#/?id=domains

https://nic.eu.org/ is also very cool for getting a domain name if paying for one is a challenge.

How well is continuation guaranteed?

What if someone buys them? Or the maintainer stops for whatever reason?

So you could pay for hosted DNS and then use them as the name server and other DNS records for multiple domains that you have?

Not to downplay my own skills, but their OpenBSD infrastructure is a good idea. They'll be up when my DNS servers are down.

Members: 7,161,633 > Premium: 5,594 > Records: 13,834,581 > Zones: 1,276,010

That’s pretty cool.

Free services are never free. It is only free because someone else is paying.

I don’t use this but “hoping” that someone else will donate is not sustainable for them and unrealistic in the long term.

Maybe they should start charging.