Which TLDs this system can answer for, at what tier, admitted on what date — and the endpoints it refused.
1,200 TLDs resolve at tier 1 through IANA's bootstrap without needing a row here. These are the ones where the bootstrap is absent or wrong.
| tld | tier | endpoint | admitted |
|---|---|---|---|
| .co | 2 · WHOIS | whois.registry.co | 2026-08-20 |
| .com | 1 · RDAP | https://rdap.verisign.com/com/v1/ | 2026-08-20 |
| .io | 1 · RDAP | https://rdap.identitydigital.services/rdap/ | 2026-08-20 |
| .me | 1 · RDAP | https://rdap.identitydigital.services/rdap/ | 2026-08-20 |
| .sh | 1 · RDAP | https://rdap.identitydigital.services/rdap/ | 2026-08-20 |
Recorded so nobody repeats the hunt. An endpoint that is only sometimes right is unusable: its 404 cannot be told apart from a real non-registration.
| tld | endpoint | verdict |
|---|---|---|
| .co | https://rdap.godaddy.com/v1/ | REJECTED — 404s 1/3 confirmed-registered names (start.co); a partially-correct endpoint is unusable, because its 404 cannot be distinguished from a real non-registration |
Every DNS-confirmed positive must return registered, an unregistered control must return not-registered, and the positives must span nameserver operators, label lengths and registration ages. Plural is not diverse: correlated positives can pass together while an endpoint knows only one slice of the zone.
curl -s https://api.scopeweb.io/coverage