.мкд.xn--d1alf

Internationalised top-level domain

WHOIS

Register: —first year
Renew: —a year
Transfer: —to move it
Registrars: —quoting it
Lookup: WHOISanswers for it
DNSSEC: Unsignedno DS in the root
Level: Secondmybrand.мкд

Check a name

One command, straight against the registry — no account, no page to load.

Name

Fills the command and the registrar links below in with your own name. The page is static — nothing is looked up here, and nothing you type leaves the browser.

ds mybrand --tld xn--d1alf

Add --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 .мкд, 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 .мкд, 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. .мкд has no RDAP service, so the answer comes from WHOIS text on port 43.

WHOIS: whois.marnet.mkQueried on port 43, from the bundled whois.json. The name is called free when the reply contains no entries found — text matching, which is why RDAP is preferred where it exists.

ds mybrand --tld xn--d1alf --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .мкд today. See Accuracy notes.

The registry

From IANA's delegation record for .мкд. .мкд is a country-code TLD.

Run by: Macedonian Academic Research Network SkopjeBased in North Macedonia. Delegated 2014-04-21, record last updated 2024-02-21.
Registry site: marnet.mkWhere the registry documents .мкд — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services: whois.marnet.mkWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers: b.dns.sidns-mk.univie.ac.atmk-e.ns.nic.cztld1.marnet.mkThe 4 authoritative servers for the .мкд zone — what the root delegates to. Nothing ds queries 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.

country-code IANA Root Zone Database types it "country-code"
idn the label is punycode — an internationalised TLD; unicode is how it reads

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 .мкд was delegated to; this is what the root actually answers with when a resolver asks it where .мкд lives.

Delegated to: b.dns.si153.5.81.1402001:1470:8000:53::44
mk-e.ns.nic.cz185.43.134.122001:148f:fffd::12
tld1.marnet.mk194.149.137.168
dns-mk.univie.ac.at78.104.145.42001:628:453:bb::4
The 4 name servers the root hands out for .мкд, with the glue addresses that come with them — 3 of them answer over IPv6. None of this is what ds queries: these servers know which names exist, not who registered them.
DNSSEC: UnsignedThe root publishes no DS record for .мкд, so the chain of signatures stops at the root and a resolver has no way to prove an answer under .мкд is genuine — it takes it on trust, as all of the DNS did before DNSSEC. 88 of the 1,438 TLDs in the root are in the same position. Names here still work; they are just not verifiable.

Ask the root yourself — no registry involved, and the same records this section was built from: dig +norec @a.root-servers.net xn--d1alf. NS and dig +norec @a.root-servers.net xn--d1alf. DS.