Hi Vercel team,

I'd like to raise visibility on an outdated Public Suffix List entry that's blocking domain verification for an Indonesian domain extension.

The issue When a domain registered under ai.id (for example, example.ai.id) is added to a project, Vercel treats ai.id as the apex domain and the registered domain as a subdomain. The dashboard then says the domain is linked to another Vercel account and asks for a TXT record at _vercel.ai.id, which no individual domain owner can create.

Why this is a parsing issue ai.id is an official second-level extension operated by PANDI, the .id registry, in the same way as co.id, my.id and web.id. It is already accepted in the Public Suffix List, in the ICANN section for .id: https://github.com/publicsuffix/list/blob/main/public_suffix_list.dat

Support confirmed that Vercel parses domains using its internal copy of the PSL, and that ai.id domains will be verifiable once that copy is synced. They also confirmed they can't trigger an update or bypass verification in the meantime.

Impact This affects every domain registered under ai.id. Since all of them are parsed as subdomains of the same "apex", the first account to claim ai.id effectively blocks every other ai.id owner on the platform.

Request Could the team sync the internal Public Suffix List with the current upstream version, or share roughly when the next sync is planned?

Thanks!