cancel
Showing results for 
Search instead for 
Did you mean: 

Where is the secret TopLevelDomain list that webhooks allow?

We have a TLD that is "somesite.plumbing", and it works great everywhere else.

 

But when setting it up in the "Webhooks" area, it says it's an invalid URL. When I swap it to .com, .net, or some other common TLD, it stops complaining.

 

Authorize.net: We are a new era of TLDs. Almost anything goes. There's a huge list of them here: https://en.wikipedia.org/wiki/List_of_Internet_top-level_domains.

 

Instead of "validating" the url against some secret list of TLDs, how about doing a DNS QUERY to see if it's valid? That way it reduces the burden of maintaining the TLD list for you, and frees up your customers to use TLDs they already own, even if they are not the most common.

 

Please consider it! We are definately considering other providers for long-term solutions. :-)

natesutherland2
Contributor
2 REPLIES 2

Apparently you don't have a secret list.

 

Instead, you limit the TLD to 6 characters.

 

It thinks THIS is VALID:

https://wacky.monste/

 

But THIS is INVALID:

https://wacky.monster/

 

(I didn't actually visit those URLS, do so only at your own risk)

 

Go ahead, try it with any series of letters as the tld. Up to 6, it thinks things are golden. But put that 7th character in there and POOF, you are out of luck. Obviously no real TLDs are longer than 6 characters. :-)

 

Authorize.net, my wish still stands. Please do a DNS QUERY to see if the URL resolves, instead of relying on the internal validation.

natesutherland2
Contributor

 
CliffordJ12
Member