Switched to Google's new Invisible reCaptcha, as well as additional improvements related to botnet detection.
If you see messages like "you are doing this too often, try again later" it means you triggered botnet protections and need to wait a
few minutes before you can continue using the service. Also, added better detection
of SEO activities.
Lots of under-the-hood performance improvements. Server load was reduced by almost 50%, which
means more users can be accommodated on the same hardware. IP address updating and website response times were also greatly reduced.
Added optional &myip parameter to allow pointing domains to any arbitrary IP address.
(Thanks to Jon Gerdes for proposing and testing this feature).
Added configuration examples for many devices, routers and software to the Help section.
(Special thanks to eibgrad and Alozaros for testing it on dd-wrt,
and to Gertjan and Jon Gerdes for testing it on pfSense).
Added support for dyndns and dyndns2 protocols. This means that all devices that support these protocols
can now be configured to use freemyip.com, as long as they allow to configure custom server name.
(Thanks to hestermofet for testing it on EdgeRouter).
SSL configuration on this site was only getting "C" grade on
This was fixed by disallowing RC4 encryption, and generating stronger and unique primes for Diffie-Hellman key exchange to provide better forward-secrecy.
(Thanks to Ligushka for reporting this issue).
Any subdomain in your domain will now return your IP. For example, if your domain is domain.freemyip.com,
you can access your IP by going to this.is.my.domain.freemyip.com or i.really.like.my.domain.freemyip.com, etc.
You can use this to set up virtual servers in your network.
The script used for updating IP address was named update.py. This was causing problems on some browsers that were configured to treat .py
extension as Python source file, and tried to save the file. Removing the .py extension fixed this issue. (Thanks
to wpeckham for reporting this issue).
The "Let's Encrypt" certificate that this site uses is not yet being recognized correctly on all browsers and operating systems.
This was causing some browsers to raise certificate errors. The problem was fixed by including the full chain of certificates in the web server.
(Thanks to hestermofet
for reporting this issue)