.merckmsd
Generic top-level domain
- Register
- —first year
- Renew
- —a year
- Transfer
- —to move it
- Registrars
- —quoting it
- Lookup
- RDAP + WHOISanswers for it
- DNSSEC
- Signed1 DS record in the root
- Level
- Secondmybrand.merckmsd
Check a name
One command, straight against the registry — no account, no page to load.
ds mybrand --tld merckmsdAdd --where for the registrars and the registry's rules, --registry for the server that answered, or --all-info for everything at once.
What it costs
No registrar in the price table bundled with ds quotes .merckmsd, so the CLI prints no figure beside it — one of 927 such TLDs. That is a gap in the table as often as it is a TLD nobody sells. See Prices for supplying your own table with --pricing-file.
Who can register
No eligibility rule is on file for .merckmsd, which is not the same as a promise that it is open: the list is hand-maintained and covers the restricted TLDs a registrar is likely to offer you. Check the registry's own page before counting on a name. 81 TLDs do carry a rule — see Who can register.
How ds answers for it
RDAP first, WHOIS second — the same order for every TLD. .merckmsd has both, so RDAP answers and WHOIS is the fallback if it does not.
- RDAP
https://rdap.nic.merckmsdFrom IANA's bootstrap, refreshed when this page was built. The lookup ishttps://rdap.nic.merckmsd/domain/mybrand.merckmsd— a 404 means the name is free.- WHOIS
whois.nic.merckmsdQueried on port 43, from the bundled whois.json. The name is called free when the reply containsno data found— text matching, which is why RDAP is preferred where it exists.
ds mybrand --tld merckmsd --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .merckmsd today. See Accuracy notes.
The registry
From IANA's delegation record for .merckmsd. .merckmsd is a generic TLD.
- Run by
- MSD Registry Holdings, Inc.Based in United States of America. Delegated 2017-06-15, record last updated 2025-01-24.
- Published services
rdap.nic.merckmsd · whois.nic.merckmsdWhat the registry itself tells IANA it runs. They agree with whatdsasks.- Name servers
a.nic.merckmsdb.nic.merckmsdc.nic.merckmsdx.nic.merckmsdy.nic.merckmsdz.nic.merckmsdThe 6 authoritative servers for the .merckmsd zone — what the root delegates to. Nothingdsqueries directly; they are what makes a registered name resolve.
What it is
Derived from the root zone and ICANN's registry list — each one is a fact with a source.
genericIANA Root Zone Database types it "generic"new-gtldICANN delegated it on or after 2013-10-23, when the 2013 round opened — seedelegated
In the root zone
The delegation itself, read out of the root zone — serial 2026090900, on 2026-09-09. The registry section above is IANA's record of what .merckmsd was delegated to; this is what the root actually answers with when a resolver asks it where .merckmsd lives.
- Delegated to
a.nic.merckmsd37.209.192.92001:dcd:1::9b.nic.merckmsd37.209.194.92001:dcd:2::9c.nic.merckmsd37.209.196.92001:dcd:3::9x.nic.merckmsd156.154.172.822610:a1:1074::1:82y.nic.merckmsd156.154.173.822610:a1:1075::1:82z.nic.merckmsd156.154.174.822610:a1:1076::1:82
dsqueries: these servers know which names exist, not who registered them.- DNSSEC
- Signed — 1 DS record in the root
- key 5134RSA/SHA-256 · SHA-256
F4C8E4AC4A227663517FB28FEAA416635CC013CCAB079ECEDA756A89541BAABA
- key 5134RSA/SHA-256 · SHA-256
Ask the root yourself — no registry involved, and the same records this section was built from: dig +norec @a.root-servers.net merckmsd. NS and dig +norec @a.root-servers.net merckmsd. DS.