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.

 

[SuperPorky]

On a completed sale marked as Manual Transfer, when I try to start the transfer or even send a message to the Afternic agent from the transaction page, the panel throws a generic error:

“Something went wrong, please try again”

Nothing proceeds after that. No error details, no transfer initiation. I’ve tested this across multiple browsers and devices, so it doesn’t appear to be local.

I’ve already contacted Afternic support to open a ticket, but I’m curious if this is a known or ongoing platform issue.

If anyone has experienced this recently or found a workaround, I’d appreciate the insight.

Thanks.

@GoDaddy

 

[SuperPorky]

I was able to isolate the cause of the issue in the Afternic transaction panel.

The error occurs specifically when the authorization code contains certain special characters (for example: single quote ', hash #, or equals =). When such a code is pasted either into the message field or the auth code field, the panel fails to submit and returns the generic error:

“Something went wrong, please try again.”

If the same message is sent without the auth code, the submission works correctly. This strongly suggests a character escaping / input validation issue in the frontend or backend handling of manual transfer messages.

This is not browser-related (reproduced across multiple browsers and devices).

I’m sharing this in case it helps your technical team identify and correct the problem.

 

[Future Sensors]

Half a year later, the Afternic UPDATE_PROCESSED CSV upload bug at @GoDaddy remains unfixed.

 

[MasterOfMyDomains]

https://www.namepros.com/threads/problems-bugs-and-fixes-at-afternic-report-problems-here.1006373/

Maybe putt it in this thread to Mr.Sensors
https://www.namepros.com/threads/problems-bugs-and-fixes-at-afternic-report-problems-here.1006373/

Why the original thread was retired i guess just to kiss some you know maybe eh
Ya sure its only been issue for 6 months?
Maybe Nick R will come back if we start a new sav thread.
Pappy keeps filling u.all with so much meat 77-79% of you probably think your walk in coolers.
Buy the way everyone is so loyal to daddy me thinks you like it.
Do.daddy a/z spit test and mark your names as not for sale for week or two. See if pops still cares.
Godaddy.vaseline coming soon
No brick and mortar store would get away with this poo. Same with Sav
This thread should be a duplicate of the original and closed
But its not who you know its who you

https://www.namepros.com/threads/problems-bugs-and-fixes-at-afternic-report-problems-here.1006373/

Sorry bruh’s you try take this business seriously and daddy just leaves you high and dry.
Sorry james i know you only appear when someone praises the elephant trunk

Godaddy new slogan
Damned if you do
Damned if you dont

 

[Future Sensors]

Thanks for your support, appreciate it.

 

[SuperPorky]

Quick update with a technical finding that may help others.

The problem is not a single character, but a combination of special characters in the auth code triggering Afternic’s security filters (WAF).

In my case, the EPP code generated by my registrar contains a mix of characters like:
• single quote (')
• equals (=)
• hash (#)

Individually these characters can be submitted without issue.
But when combined in the same string, they match common SQLinjection signatures (string termination + operator + comment), so Afternics WAF blocks the entire request.

Result:
• The panel rejects both the auth code field and messages containing the code
• Shows only the generic “Something went wrong” error
• Happens across multiple browsers and devices

This is not a browser issue and not a registrar issue. Its Afternic’s security layer incorrectly blocking valid authorization codes.

Workaround so far is to provide the auth code by email or have Afternic process the transfer manually on the backend.

Posting this in case others run into the same issue with manual transfers.

@GoDaddy

 

[GoDaddy]

@GoDaddy Is there some legal/accounting reason you don't let buyers immediately pay off LTO (lease to own) balances in 1 single payment? Having someone make 12-36+ manual payments one-by-one is kind of crazy. That's alot of friction with a lot of potential for annoying payment issues.

We hear you on the friction. It is a current system limitation; we'll make sure the feedback is logged for the product team.

@Afternic @GoDaddy

Please stop sending emails on domains that have been sold and no longer listed by me.

I've already mentioned this a couple of times. Today you sent out an email on a domain I sold on Afternic back in August of 2024. It looks like you just have an automation-bot sending out emails on an annual basis??? Please have that automation-bot check to see if the domain name is still in my portfolio before sending out emails...

Show attachment 292401

That shouldn't be happening. Our automated follow-ups shouldn't be sent unless a domain is active within Afternic's inventory. We'd like to investigate - we’ll DM you to get the domain name

They said the Price Request landers were going to switch to forsale.godaddy.com back in late October

Still waiting...

Show attachment 292415

We have successfully completed testing and the new Request Price lander is live, but the URL switchover is a significantly larger undertaking. Once we have an update on this, of course - we'll let the community know.

I was able to isolate the cause of the issue in the Afternic transaction panel.

The error occurs specifically when the authorization code contains certain special characters (for example: single quote ', hash #, or equals =). When such a code is pasted either into the message field or the auth code field, the panel fails to submit and returns the generic error:

“Something went wrong, please try again.”

If the same message is sent without the auth code, the submission works correctly. This strongly suggests a character escaping / input validation issue in the frontend or backend handling of manual transfer messages.

This is not browser-related (reproduced across multiple browsers and devices).

I’m sharing this in case it helps your technical team identify and correct the problem.

We’re going to DM you for your username so we can attach this data to the active support investigation and escalate it directly to the technical team for a fix. Thank you for taking the time to break that down.

 

[Brian L.]

 

[Kyle Tully]

. I’m struggling to understand why this is occurring.

Read this thread.

 

[alcy]

Has anyone else noticed a steep decline in inquiries and sales since @Afternic / @GoDaddy took over @DAN.COM? I’m using the same @DAN.COM landers, but my sales are down by approximately 50% and inquiries are down by at least 75% since @Afternic / @GoDaddy took over. I’m struggling to understand why this is occurring.

u using dan?

do u talk to dead folk too?

for me all domain sales down by like 80% since a bit before gd closed auctions.

luckily... my last 2 sales were also my best ever in 5fig .....

so this lets me continue my hobby lol

as aalways I say... the best thing about domaining is that one sale can equal 100 smaller ones.. or 10.... so it's more about annual roi .. or total roi really.... then number annual sales...

gotta love this about domaining.. 1 sale to rule em all hahah
and can happen any time
to any non newbie person bahaha

just have decent names... even older regs... and make sure u put bug whale hook.... hard to sell name for 50k if your bin 5k lol

enjoy

 

[Blueleaf66]

4th day of landers resolving very slowly or... not resolving.

 

[Future Sensors]

4th day of landers resolving very slowly or... not resolving.

They're probably experimenting to find the HTTP error with the best conversion rate to frustration.

 

[nlitenme]

4th day of landers resolving very slowly or... not resolving.

Show attachment 292710

Same here - of all that I tested, only about 1 in 4 resolved.

 

[GoDaddy]

Same here - of all that I tested, only about 1 in 4 resolved.

We’re currently investigating this, and we’ll provide an update as soon as we have more info.

Update: Following up to confirm that the 403 errors on landers have been resolved.

 

[Jannes]

I'm seeing 403 and 504

example domain:

then it was 504, then it started working

 

[Future Sensors]

We’re currently investigating this, and we’ll provide an update as soon as we have more info.

Shouldn't your monitoring tools have alerted you well before it reached this point?

 

[Mister Funsky]

It's all back up now...I'm on East coast.

 

[Blueleaf66]

It happens intermittently. 2-3 times out of 10 it loads. Usually slowly. Very slowly.

 

[Garet]

Shouldn't your monitoring tools have alerted you well before it reached this point?

I suspect that we are their monitoring tools.

 

[love4ever]

Shouldn't your monitoring tools have alerted you well before it reached this point?

Are there monitoring tools !!?

.