I sold one of my domains I have registered at DynaDot. Transaction conducted via escrow.com
When it came time to transfer, the buyer's recipient registrar 123-reg told her that it could not accept/receive the transfer via authorization code, even though the domain was UNlocked at my end, because it was a "premium listed" domain.
Eventually buyer had to create a DynaDot account and I pushed it over to her with no problem, DynaDot to DynaDot.
Later she contacted me and said that there was still some issue at her end, even though WhoIs now showed her as owning the domain, because it was still listed for sale as a "premium listed" domain - she said that it still showed as listed for sale at at least:
123-reg.co.uk
Godaddy.com
Sedo.com
Afternic.com
This is true - the domain was still listed for sale at Sedo and Afternic (GoDaddy and 123-reg.co.uk must be affiliates of the other two, at least, we know for certain that GoDaddy owns Afternic), but I had not yet gotten around to removing the Sedo/Afternic listings since I had not yet received the funds since the escrow had not yet closed (still hasn't closed, but is in inspection period now).
I can understand I suppose buyer's wanting to have any for sale listings removed once she controls the domain, but WHY would the domain's being listed for sale affect the domain transfer via authorization code?
Something like this happened before now I recall, where I ended up having to push the domain over same way, DynaDot to DynaDot.
(By the way, this was not a domain that had a BIN price at Afternic - so it was not a "Fast Transfer" at DynaDot listed domain.)
Anyone else encountered anything like this? where the for sale listing status of a domain somehow affects its transfer via authorization code?
When it came time to transfer, the buyer's recipient registrar 123-reg told her that it could not accept/receive the transfer via authorization code, even though the domain was UNlocked at my end, because it was a "premium listed" domain.
Eventually buyer had to create a DynaDot account and I pushed it over to her with no problem, DynaDot to DynaDot.
Later she contacted me and said that there was still some issue at her end, even though WhoIs now showed her as owning the domain, because it was still listed for sale as a "premium listed" domain - she said that it still showed as listed for sale at at least:
123-reg.co.uk
Godaddy.com
Sedo.com
Afternic.com
This is true - the domain was still listed for sale at Sedo and Afternic (GoDaddy and 123-reg.co.uk must be affiliates of the other two, at least, we know for certain that GoDaddy owns Afternic), but I had not yet gotten around to removing the Sedo/Afternic listings since I had not yet received the funds since the escrow had not yet closed (still hasn't closed, but is in inspection period now).
I can understand I suppose buyer's wanting to have any for sale listings removed once she controls the domain, but WHY would the domain's being listed for sale affect the domain transfer via authorization code?
Something like this happened before now I recall, where I ended up having to push the domain over same way, DynaDot to DynaDot.
(By the way, this was not a domain that had a BIN price at Afternic - so it was not a "Fast Transfer" at DynaDot listed domain.)
Anyone else encountered anything like this? where the for sale listing status of a domain somehow affects its transfer via authorization code?
Last edited:

















