Afternic - Official Thread

[GoDaddy]

Hello NamePros!
By popular demand, we have launched a dedicated feedback thread for Afternic, the GoDaddy-owned domain name marketplace.

We have created this thread as a way for you to tell us what works, what doesn't work, and what features you'd like to see at Afternic (please be constructive with your feedback). We're looking forward to hearing from the domain investment community to help us shape the future of Afternic.

We will also be sharing Afternic product updates in this thread.

Please note that this thread is not meant for support. Please email our support team at [email protected] for assistance.

 

[Bob Hawkes]

Do not get irritated. ... Don't worry be happy!

Good advice in general.
My solution for now is to stop trying to list anything new at Afternic.
Have a happy day.
-Bob

 

[Optixgroup]

I am getting this message pretty often (e.g. 3 times out of last 7 new listings today) lately. It is somewhat irritating to a workflow as you need to note which domain names had it and remember to go back in 24 to 48 hr and try listing them again. This never used to happen (well maybe extremely rarely), so I hope whatever change created it can be improved. The advantage of self-verification is largely lost when a significant number of names are successfully verified, but not accepted until a significant delay. Thank you.
-Bob

Update: Seems getting close to all new attempted listings this morning going that route. Hand regs, auction wins, etc. Are others seeing this? @James Iles Show attachment 307664

Same here, good to know it's not just me,

 

[Embrand]

I am getting this message pretty often (e.g. 3 times out of last 7 new listings today) lately. It is somewhat irritating to a workflow as you need to note which domain names had it and remember to go back in 24 to 48 hr and try listing them again. This never used to happen (well maybe extremely rarely), so I hope whatever change created it can be improved. The advantage of self-verification is largely lost when a significant number of names are successfully verified, but not accepted until a significant delay. Thank you.
-Bob

Update: Seems getting close to all new attempted listings this morning going that route. Hand regs, auction wins, etc. Are others seeing this? @James Iles Show attachment 307664

It is extremely annoying. It also takes a long time for Afternic to verify the nameserver or TXT. It takes Atom seconds...

 

[Future Sensors]

Good advice in general.
My solution for now is to stop trying to list anything new at Afternic.
Have a happy day.
-Bob

Over the course of a life, one often gains insights that are difficult to acquire any other way.

 

[NameGroove]

Over the course of a life, one often gains insights that are difficult to acquire any other way.

the highest level of insight/wisdom comes when you can learn from others mistakes and don't have to make them yourself. It's quite hard to level up to this. But it can be done

 

[Garet]

I am getting this message pretty often (e.g. 3 times out of last 7 new listings today) lately. It is somewhat irritating to a workflow as you need to note which domain names had it and remember to go back in 24 to 48 hr and try listing them again. This never used to happen (well maybe extremely rarely), so I hope whatever change created it can be improved. The advantage of self-verification is largely lost when a significant number of names are successfully verified, but not accepted until a significant delay. Thank you.
-Bob

Update: Seems getting close to all new attempted listings this morning going that route. Hand regs, auction wins, etc. Are others seeing this? @James Iles Show attachment 307664

I added 15 names today, Bob. All went to Pending Sync and seem to want to sit there. That's a a new twist (of the knife). Thank you, GoDaddy.

 

[DaveX]

Do not get irritated. ... Don't worry be happy!

GoHappy

 

[Bob Hawkes]

In case people did not see the update I just added, the synchronization problem with verified domain names at Afternic seems resolved. I have been able to add a number without issue just now. Thanks to @James Iles and Afternic staff for quickly resolving the issue.
-Bob

 

[Optinom]

I’ve been experiencing a few issues at Afternic over the past couple of weeks and could use some assistance/clarification:

1. Pending Sync Issue: As highlighted by Bob above, this issue was finally resolved today.
2. Delayed Transfers (2 Domains): I have two sold domains for which transfer has not been initiated for over a week, despite providing authorization codes and following up multiple times. One of these is a Lease-To-Own (LTO) sale.
3. Domain "On Hold": Another domain has been "On Hold" for 4 days now. A buyer (potentially the same buyer) reached out to me directly via WHOIS for this exact domain today. So I'm wondering what's going on.

 

[Jannes]

fyi

Afternic @afternic July 24, 2026

We've switched the Request Price Lander from afternic․com to godaddy․com!

✅ GoDaddy branding
✅ GoDaddy URLs

Visitors to your lander now experience the trusted GoDaddy brand from start to finish.

Afternic @afternic

New to the Request Price Lander!

We now show the Buy it Now price on domains priced up to $10,000 as a final inquiry step.

Capture lead data for follow-up campaigns and show a Buy it Now price for instant buys below $10,000.

View original Load full embed

 

[DomainRecap]

 

[Chris Co]

fyi

Afternic @afternic July 24, 2026

We've switched the Request Price Lander from afternic․com to godaddy․com!

✅ GoDaddy branding
✅ GoDaddy URLs

Visitors to your lander now experience the trusted GoDaddy brand from start to finish.

Afternic @afternic

New to the Request Price Lander!

We now show the Buy it Now price on domains priced up to $10,000 as a final inquiry step.

Capture lead data for follow-up campaigns and show a Buy it Now price for instant buys below $10,000.

View original Load full embed

Ah this probably explains why the majority of my BIN landers suddenly didn't have their prices showing & started showing request price instead. Nothing ever seems to go smoothly with Afternic Godaddy lately.

 

[MasterOfMyDomains]

https://forsale.godaddy.com/forsale...e&traffic_type=TDFS_DASLNC&traffic_id=daslnc&

Ns3 and ns4

Joe Joe’s name. I watch it to see what ns daddy’s man uses

Looks like eye candy for the serps, may be you are even being penil ized using ns3 ns4

R All afternic ns forwarders?

I tried to unlink twice but on mobile thats like driving a hummer with no power steering thru a crowded parking.lot

 

[Future Sensors]

Ns3 and ns4

Official notice.

Nowadays, all six Afternic Nameservers resolve to identical A records / IPs.

Lander type is now defined in the Dashboard, no longer via nameserver selection.

 

[Future Sensors]

Folks / @GoDaddy



It appears that none of Afternic's unique *.ns101.verify.hn verification nameservers are currently responding to DNS queries, which will result in roughly 1/3 of all DNS queries to fail for sellers that have configured such a verification NS as third NS option.

The main Afternic nameservers (ns1/ns2/ns3/ns4/ns5/ns6) are working without problems.

Kindly investigate and resolve the issue.

My advice to other sellers would be to remove the third Afternic verification nameserver without delay. Only ns1.afternic.com and ns2.afternic.com (or ns3/ns4/ns5/ns6) should remain. No additional verification nameservers are technically required once domain‑ownership verification has succeeded.

 

[Garet]

Folks / @GoDaddy



It appears that none of Afternic's unique *.ns101.verify.hn verification nameservers are currently responding to DNS queries, which will result in roughly 1/3 of all DNS queries to fail for sellers that have configured such a verification NS as third NS option.

The main Afternic nameservers (ns1/ns2/ns3/ns4/ns5/ns6) are working without problems.

Kindly investigate and resolve the issue.

My advice to other sellers would be to remove the third Afternic verification nameserver without delay. Only ns1.afternic.com and ns2.afternic.com should remain. No additional verification nameservers are technically required once domain‑ownership verification has succeeded.

Done. Thank you very much for the alert.

 

[Future Sensors]

Folks / @GoDaddy



It appears that none of Afternic's unique *.ns101.verify.hn verification nameservers are currently responding to DNS queries, which will result in roughly 1/3 of all DNS queries to fail for sellers that have configured such a verification NS as third NS option.

The main Afternic nameservers (ns1/ns2/ns3/ns4/ns5/ns6) are working without problems.

Kindly investigate and resolve the issue.

My advice to other sellers would be to remove the third Afternic verification nameserver without delay. Only ns1.afternic.com and ns2.afternic.com (or ns3/ns4/ns5/ns6) should remain. No additional verification nameservers are technically required once domain‑ownership verification has succeeded.

@Bob Hawkes I don't have visibility into your specific (NS) setup, so there's a chance this ties back to the verification problems you encountered recently. The symptoms may be related, though an independent issue remains equally plausible.

 

[fka]

It appears that none of Afternic's unique *.ns101.verify.hn verification nameservers are currently responding to DNS queries, which will result in roughly 1/3 of all DNS queries to fail for sellers that have configured such a verification NS as third NS option.

Are you sure? I can't reproduce this, I checked locally and using ~100 servers via ping.sx. The verify.hn nameservers have A records pointing to 13.248.169.48 and 76.223.54.146 but neither of these servers responds to requests on port 53. The only ports I can find open are http (80) and https (443).

dig @76.223.54.146 example.com a

; <<>> DiG 9.10.6 <<>> @76.223.54.146 example.com a
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

dig @13.248.169.48 example.com a

; <<>> DiG 9.10.6 <<>> @13.248.169.48 example.com a
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

I also checked for AAAA records but didn't find any so I don't think it would be different over IPv6.

curl -v http://13.248.169.48
*   Trying 13.248.169.48:80...
* Connected to 13.248.169.48 (13.248.169.48) port 80
> GET / HTTP/1.1
> Host: 13.248.169.48
> User-Agent: curl/8.7.1
> Accept: */*
>
* Request completely sent off
< HTTP/1.1 400 Bad Request
< content-length: 0
<
* Connection #0 to host 13.248.169.48 left intact

 

[Future Sensors]

Are you sure? I can't reproduce this, I checked locally and using ~100 servers via ping.sx. The verify.hn nameservers have A records pointing to 13.248.169.48 and 76.223.54.146 but neither of these servers responds to requests on port 53. The only ports I can find open are http (80) and https (443).

Yes. Ping is working, but port 53 not.

 

[Future Sensors]

You're getting the same non-responsive results.

I can't reproduce this

connection timed out; no servers could be reached