PSA: iwantmyname is utterly broken

This is just a PSA for anyone unfortunate enough to have to use iwantmyname.

TL;DR: Generation of EPP auth codes for many TLDs is completely broken, and support appears to be out to lunch.

We've been long-time customers of iwantmyname (our first invoice goes back to 2014). We generally only used them for registration of TLDs that were unavailable on Google Cloud Domains (RIP) or Route 53.

We have rarely had cause to use their support as we typically nameserved away to external DNS solutions - but the few times we did it seemed fine. However, as many of the domains we originally registered on iwantmyname now have TLDs which are supported by our other infrastructure providers we have begun the slow process of migrating off of the platform.

On June 7th of this year, iwantmyname released a new, "upgraded" dashboard. However, since this update the generation of EPP auth codes for transfer out of the system - a requirement of ICANN as well as most international TLD governance bodies - is completely broken. When attempting to view an EPP Auth code via the dashboard, it shows an empty input or a value of "N/A". When attempting to email the EPP Auth code from the same dashboard, the emails send with a value of "n/a".

We have raised 6 separate support cases over the past two weeks, including attempting to raise them on chat during both US and NZ working hours, and have received zero response. Nada, nothing, zilch.

We haven't been able to thoroughly test all of our domains (we are in the process of that now), but to date these are the TLDs we've seen this issue affecting:

- .es - .at - .in - .blue - .quest - .us - .com.au (some EPP Auth codes are available) - .au (some EPP Auth codes are available) - .nz (some EPP Auth codes are available)

To each their own - but I would stay well away from iwantmyname. We can't get off the platform fast enough (literally).