Wp-calypso: com.pe and com.br domains appears as taken even if they aren´t [in the Domains add screen]

[rantoncuadrado]

Steps to reproduce

1. Starting at URL: https://wordpress.com/domains/add
2. Choose one of your sites
3. In the domain search field, write any arbitrary domain name finishing by com.pe or com.br (Don't use special characters like ñ)

What I expected

1.If the domain is not taken, the interface should allow to get it.

What happened instead

1. This message is displayed:
   "jkfdsjkfsjkjfsdkjfa.com.pe is taken.
   If you purchased jkfdsjkfsjkjfsdkjfa.com.pe elsewhere, you can map it for €13.00."

Browser / OS version

This bug is not browser dependent - chrome IOS

Screenshot / Video

Context / Source

This error is not shown when using special characters like 'Ñ' in the domain name.

We'd also love to know how you found the bug: #user-report (chat 381894-hc con gruago.com.pe)

[designsimply]

Tested and found that the same problem happens with any TLD not listed at https://en.support.wordpress.com/domains/#available-domains

^{Seen at https://wordpress.com/domains/add/design5279.wordpress.com using Firefox 53.0.2 on Mac OS X 10.12.4 logged in as design5279 unproxied.}

What happened:

• A message saying "thisisatestofaddingadomainwithadifferenttld.art is taken."

What I expected:

• A message saying "thisisatestofaddingadomainwithadifferenttld.art is unavailable." or ".art domains are not available for sale at WordPress.com."

[klimeryk]

I think we have to change our approach here - right now we have a short list of "unsupported TLDs" on the backend, which we know we can't check the availability of (see https://github.com/Automattic/wp-calypso/issues/11051). Obviously, that list is not complete and with gTLDs being added all the time (.art being a recent addition), it will be hard to keep it up to date (and to account for stuff like second level TLDs, ccTLDs...).
Instead, we should whitelist the TLDs we do know we can check availability for and show this message for other (we already do for those unsupported TLDs):

@aidvu, does that sound good to you? I think you had proposed the same thing in a Slack conversation we've had about this :)

[aidvu]

Sounds good. We can do something similar to https://github.com/Automattic/wp-calypso/blob/cabaf131c7bdfd58bcf0e9798f3439e06e484b34/client/lib/domains/registration/availability-messages.js#L37.

We should probably stop doing availability checks for the ones we don't have in our offering.

[klimeryk]

This should be fixed now - patched on the backend D5787-code.

The way it's working now is that we're only checking the availability of the TLDs we offer (.com, .net., .blog, etc.). For others, we show this type of message:

PS: As always, really grateful for reports like these - thanks, @rantoncuadrado! 🙇

[rantoncuadrado]

:) I'm glad to contribute!