commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Heine Pedersen (JIRA)" <>
Subject [jira] [Commented] (VALIDATOR-305) Some TLDs are missing from DomainValidator
Date Fri, 06 Jun 2014 12:42:02 GMT


Heine Pedersen commented on VALIDATOR-305:

Hi, according to which says
"The expansion of generic Top-Level Domains (e.g. .COM, .ORG, .NET) in the Domain Name System
is underway. Over 1,300 new names or "strings" could become available in the next few years.".

This also - in my mind - suggests that the solution of updating an array in the code with
the new gTLDs is poor. Then users of the API needs to update the dependency constantly, and
always will run into issues with domains being reported as invalid, even though they are actually

I can think of a couple of (possible better) alternatives.
1. Let the list of valid gTLDs be in a property file - then it would be enough just updating
that, instead of updating the entire API (which causes regression testing)
2. Do a more generic validation (eg. must contain letters - I'll assume ICANN has a specification
of which new gTLDs can be accepted)
3. Allow this to be updated automatically by retrieving a list from somewhere, and parse that
- has some issues with the necessity of making a connection to the Internet - so probably
not a good solution.

I really would hope that this gets solved in the right way, unfortunately I do not have any
experience in contributing to Apache projects, so it seems quite a big hurdle to try and implement
this myself.

Cheers, Heine

> Some TLDs are missing from DomainValidator
> ------------------------------------------
>                 Key: VALIDATOR-305
>                 URL:
>             Project: Commons Validator
>          Issue Type: Bug
>          Components: Routines
>    Affects Versions: 1.4.0 Release
>            Reporter: Nick Burch
>         Attachments:
> As reported on list <>,
DomainValidator is missing some of the new TLDs
> The full list is available from <>

This message was sent by Atlassian JIRA

View raw message