Repository navigation
Invalid Domain for Non TLD. #333
Description
I am working for one of the Financial organisation, we have a custom domain endpoint which is ending say for ex: .xyz. I would like to know the process, how to approach TrustKit team to get my custom domain to be whitelisted so that we can have TrustKit integrated to our ongoing iOS app.
Appreciating the early reply as we have some critical deliverables. Thank you.
Reacted by Cody Richmond
Activity
cxr932 commentedon Nov 14, 2024
Likewise, my team uses internally-available endpoints with self-signed certs that we would like to allow connections to for testing critical features of the application. Is there a configuration that can be provided to allow domain suffixes that are not on the public suffix list?
alexanderdibenedetto commentedon Jun 1, 2026
Hi @sreekanthrad - you should be able to use any domain you wish so long as you correctly configure with the certificate pinning values in initialization. Can you please share more details with us if you have them?
alexanderdibenedetto commentedon Oct 15, 2026
.xyz is accepted, but internal names (.internal, .corp, .local, localhost) are rejected. The bundled list from 2018 also rejects 11 of
the 1,280 public TLDs on the current list, including .music, .kids, .hotel, .web and .ss.
Next step: Refresh the bundled list. Decide on internal names together with #341, possibly merging the two issues.
Allow any domain name or IP address in the pinning configuration (#333,
alexanderdibenedetto commentedon Oct 22, 2026
Fixed in #371
TrustKit 4.0 (#378)