ds

.mtn

Generic top-level domain

RDAPbrand TLD

Nobody outside the registry can register here. .mtn is a brand TLD run by MTN Dubai Limited, which under ICANN's Specification 13 means its operator is the only permitted registrant. ds reports names here as PRIVATE rather than AVAILABLE, and leaves the zone out of --tld all unless you pass --private include. See Brand and reserved TLDs.

Registration
Closedno public names
Operator
MTN Dubai Limited
Lookup
RDAPanswers for it
DNSSEC
Signed1 DS record in the root
Level
Secondmybrand.mtn

Check a name

Names under .mtn cannot be registered, but ds will still tell you what the registry says.

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 mtn

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 .mtn, 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, though here it is neither: the zone is closed. See Prices for supplying your own table with --pricing-file.

Who can register

Nobody outside MTN Dubai Limited — see the note at the top of this page.

How ds answers for it

RDAP first, WHOIS second — the same order for every TLD. .mtn has an RDAP service and no WHOIS entry, so every answer is authoritative RDAP.

RDAP
https://rdap.nominet.uk/mtnFrom IANA's bootstrap, refreshed when this page was built. The lookup is https://rdap.nominet.uk/mtn/domain/mybrand.mtn — a 404 means the name is free.

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

The registry

From IANA's delegation record for .mtn. .mtn is a generic TLD.

Run by
MTN Dubai LimitedBased in United Arab Emirates. Delegated 2015-03-12, record last updated 2025-01-28.
Registry site
www.mtn.comWhere the registry documents .mtn — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services
rdap.nominet.ukWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers
dns1.nic.mtndns2.nic.mtndns3.nic.mtndns4.nic.mtndnsa.nic.mtndnsb.nic.mtndnsc.nic.mtndnsd.nic.mtnThe 8 authoritative servers for the .mtn 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.

  • generic IANA Root Zone Database types it "generic"
  • brand ICANN records Specification 13 — a brand TLD, closed to the public
  • new-gtld ICANN delegated it on or after 2013-10-23, when the 2013 round opened — see delegated

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

Delegated to
  • dns1.nic.mtn213.248.219.422a01:618:403::42
  • dns2.nic.mtn103.49.83.422401:fd80:403::42
  • dns3.nic.mtn213.248.223.422a01:618:407::42
  • dns4.nic.mtn43.230.51.422401:fd80:407::42
  • dnsa.nic.mtn156.154.100.32001:502:ad09::3
  • dnsb.nic.mtn156.154.101.32001:502:2eda::3
  • dnsc.nic.mtn156.154.102.32610:a1:1009::3
  • dnsd.nic.mtn156.154.103.32610:a1:1010::3
The 8 name servers the root hands out for .mtn, with the glue addresses that come with them — every one of them answers over IPv6. None of this is what ds queries: these servers know which names exist, not who registered them.
DNSSEC
Signed — 1 DS record in the root
  • key 18374RSA/SHA-256 · SHA-25658114B80A64F8617AF3EC29668C55519D8CCB44A203562D746E7F2CC8850A1EB
Each one is a fingerprint of .mtn's own signing key, published by the root and signed with the root's key — which is how a resolver that trusts only one key can prove an answer under .mtn came from its registry and was not tampered with in transit. It says nothing about who owns a name or whether one is free.

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

Also answered by rdap.nominet.uk

and 68 more zones on the same server.