-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How many newGTLDs are managed by thin registries? #126
Comments
Hello,
I would say it depends on the implementation. I did some PoC and at some times we miss data or it broke. If you enable recursion for all of them, will it be true recursion or only for one query more? while (fgets(buf, sizeof(buf), fi)) {
/* If multiple attributes are returned then use the first result.
This is not supposed to happen. */
if (state == 0 && strneq(buf, "Domain Name:", 12))
state = 1;
if (state == 1 && strneq(buf, "Registrar WHOIS Server:", 23)) {
for (p = buf; *p != ':'; p++); /* skip until colon */
for (p++; *p == ' '; p++); /* skip colon and spaces */
referral_server = strdup(p);
if ((p = strpbrk(referral_server, "\r\n ")))
*p = '\0';
state = 2;
}
/* the output must not be hidden or no data will be shown for
host records and not-existing domains */
if (hide_line(&hide, buf))
continue;
if ((p = strpbrk(buf, "\r\n")))
*p = '\0';
recode_fputs(buf, stdout);
fputc('\n', stdout);
} I have found some domain names where the thin whois also contains another whois referral server but with the implementation above you will only get one : e.g. taban.aero :
Then querrying whois.atakteknoloji.com server
Then querying whois.apiname.com
On the other hand, you might have a loop because one thin might refer to another whois server and this server will refer to the first one (I have seen it, but do not remember the domain name). Also, I found out "Registrar WHOIS server" string is not the only one to take into consideration for getting thin but also "whois:" and "referto:". And as you mention on another git issues, you might have "http" in it. Regards, |
I don't really understand what you mean by an authoritative list but by the ICANN whois primer (https://whois.icann.org/en/primer) all new gTLD must be a thick:
As I know : newGTLDs must provide RDAP service and IANA provides an accurate map for TLDs to RDAP services https://data.iana.org/rdap/dns.json. In this list we have 1191 TLDs, if we remove the gTLDs and ccTLDs you listed in tld_serv_list it makes 1147 TLDs. Removing the newGTLDs you already listed, it makes 4 newGTLDs :
So I would say you are already managing an authoritative list ? |
My point is that, as you noted, the "new" gTLDs are supposed to be thick, but I showed that .scot domain which requires recursion to get more information. |
Is there an authoritative list? Can I just enable recursion for all of them and hope nothing breaks?
e.g.:
The text was updated successfully, but these errors were encountered: