The new registrar did not reply, so I interpreted that as a success.
A year later, the Melbourne IT began sending notices that our registration was about to expire. This was unsettling, but I assigned the issue a low priority because I "knew" the new registrar had transferred the domain. I was wrong.
Eventually, just to verify what I "knew," I checked. The old registrar still held the registration.
Through some back-and-forth with the new registrar, I found that they had failed to notify me that the code I sent was not the correct code.
Back at Melbourne IT's site, I could not find an EPP code. I finally left them a message asking for it. Later, I found that they called it by a different name.
This was the short version of the story. Most of it had repeated elements. I am not happy with the new registrar's service.
Here are some hints to save you headaches.
- You can learn about EPP codes under Transfer Secret on Wikipedia.
- The Extensible Provisioning Protocol (hence "EPP"), which defines Transfer Secrets, is maintained by ICANN (Internet Corporation for Assigned Names and Numbers).
- The correct term is AuthInfo Code or Auth-Info code.
- Your registrar service may call it
- Auth code
- Authorization code
- Domain auth code
- Domain name password
- Domain password
- EPP authentication code
- EPP authorization code
- EPP code
- EPP Key
- EPP Password
- Transfer key
- Transfer secret
Copyright 2013, Richard Wheeler -- Permission granted for non-profit or personal use with a link to this post.