.my
Availability-check reliability and the registry servers we query for .my domains.
Our answer rate
Not enough data Generic- Answer rate
- 100.0% of attempted checks returned a definitive answer
- Check volume
- Minimal (coarse band, not a count)
- Mostly answered by
- DNS
- Still available
- 100.0% of answered .my candidates were unregistered
- Last definitive answer
- 2026-09-21
Servers we query for .my
Public registry infrastructure — a whois, a
dig NS my, and one read of
IANA’s bootstrap file
return the same three values. Listed here for convenience.
- WHOIS host
-
whois.mynic.my - Authoritative nameservers
-
d.mynic.centralnic-dns.com212.18.249.114e.nic.my152.69.217.125ns01.trs-dns.com64.96.1.1ns01.trs-dns.net64.96.2.1a.mynic.centralnic-dns.com194.169.218.114b.mynic.centralnic-dns.com185.24.64.114c.mynic.centralnic-dns.com212.18.248.114 - RDAP endpoint
- no RDAP server — .my is checked by DNS / WHOIS
What this measures: the share of our own availability checks that came back with a definitive answer. Nobody else publishes this, because nobody else is running bulk registry lookups at this scale and recording what came back.
What it does not measure: a registry’s uptime or quality. A low rate here can just as easily mean our requests are being rate-limited as it can mean anything about the registry itself.
These are current-state figures, not a history. We keep one record per domain, holding its most recent check — so a TLD that failed hundreds of times and then recovered reads as healthy here. A low rate means checks are failing now; a high one does not mean they always have.
Figures count domains checked, not queries — a domain checked six times counts once. Candidates we generated but never checked are excluded entirely; they are not failures. Snapshot rebuilt 2026-09-27 02:19:47.