The domain maktabat-alweibdeh.com and the same name under Jordan’s own code look like one name with two endings, but two entirely different organisations stand behind them. The first is run by Verisign, can be registered by anyone from any country without documents, supports a chain from the root, and moves between registrars under ICANN’s policy. The second is run by a national body that sets its rules alone, and booking it usually takes a link to the country and documents to prove it. So the extension isn’t decoration at the end of a name; it decides who sets the rules for your domain for its whole life. This article explains how extensions work from the root down to your name, where they differ, and how to choose between them.
01From the root to your name
DNS is an upside-down tree. At the top is the root zone, published by IANA under ICANN’s oversight, which today holds more than 1,400 extensions. The root zone stores no domains at all; for each extension it only stores the servers responsible for it. Each extension’s servers in turn store, for every domain beneath them, the name servers that answer for it. That is how a query for maktabat-alweibdeh.com travels from the root to the .com servers, and from there to the domain’s own name servers.
# The tools on Ubuntu or Debiansudo apt install -y dnsutils# The servers responsible for .org, as delegated by the rootdig NS org.# The .com SOA record: primary server, admin mailbox and serialdig +short SOA com.# Trace the query from the root to the extension to the domain’s serversdig +trace maktabat-alweibdeh.com
Behind every extension are four roles people often confuse, the most important being the , which owns the extension’s database, and the you deal with:
| Role | What it does | Example |
|---|---|---|
| ICANN and IANA | Run the root; ICANN sets policy for generic extensions and accredits their registrars | The domain transfer policy and its 60-day rule |
| Registry | Runs the extension’s database and servers, and sets its rules and wholesale price | Verisign for .com, and each country’s national body for its code |
| Registrar | Sells you the name and passes your commands to the registry: register, renew, transfer, update | The company you register with, such as Illevante for generic extensions |
| Registrant | Holds the right to the name for the registration term | Your company, or you personally |
02Types of extensions
IANA sorts extensions into categories, each with its own rule-maker:
| Type | Examples | Who sets the rules | Who registers |
|---|---|---|---|
| Classic generic | .com, .net, .org, .info | The registry, under contract with ICANN | Anyone, from any country |
| New generic | .shop, .tech, .app, .clinic | The registry, under contract with ICANN; some with special terms | Usually anyone |
| Sponsored | .edu, .gov, .mil | A sponsor for a specific community | Only those who prove they belong |
| Country code | .ae, .sa, .eg, .de | A body in the country itself, outside ICANN contracts | Per each country’s rules |
| Country code in a national script | .امارات, .السعودية, .مصر | The country’s own registry | Per its rules |
The classic extensions are the oldest, and after 2013 hundreds of new generic extensions were added, named after fields, cities and brands. ICANN opened a new application round in 2026, so expect more extensions in the root over the coming years. are two-letter codes for each country or territory, each with its own independent policy.
Some new extensions carry technical rules their buyers don’t expect. The .app and .dev extensions, for example, are on the HSTS preload list built into browsers as a whole, so a browser will only open a site on them over HTTPS. If you register one of these, set up an SSL certificate before you publish the site.
03Country codes in the region
Every country has a two-letter code from the ISO 3166 list, and the region’s are .ae for the UAE, .sa for Saudi Arabia, .kw for Kuwait, .qa for Qatar, .bh for Bahrain, .om for Oman, .eg for Egypt, .jo for Jordan, .iq for Iraq and .lb for Lebanon. Each is run by a registry in its own country, most often the telecoms regulator or a national information centre, outside ICANN’s contracts, and each registry sets its own terms. This is what they usually have in common:
- One code per country: The code stands for the country alone and is run by one registry there, so the rules of .ae don’t apply to .sa, and what holds at one registry may not hold at its neighbour.
- Codes in Arabic script: Several countries in the region have an Arabic-script extension beside their Latin code, such as .امارات, .السعودية and .مصر, so the whole address can be written in Arabic.
- Categories under the code: Many registries organise names into categories under the code, such as .com.sa for companies, .edu.eg for education and .gov.ae for government bodies, each with its own terms.
- A link to the country: Most registries in the region ask for proof of a link to the country: a trade licence, a company registered there, residence, or a registered trademark, and the documents differ from one code to the next.
- Registrars the registry accredits: Booking goes through registrars the national registry accredits, under its own rules rather than the transfer policy ICANN sets for generic extensions.
- Categories reserved for certain bodies: The government and education categories, and others under some codes, are reserved for bodies that prove their status with a licence or an official letter.
Illevante registers generic extensions, and for a country’s own code, its national registry publishes its terms and its list of accredited registrars on its website. On the technical side, check two things before you build on any country code. First, whether its delegation in the root is signed with DNSSEC: if the extension has no DS record in the root, no chain of trust reaches your domain however you sign its zone. Second, where its registration data is looked up: many country registries run a WHOIS server of their own rather than RDAP, and IANA’s database tells you which.
# An answer with numbers: a DNSSEC chain of trust starting at the rootdig +short DS com.# The same question for the region’s codes: no answer means no chain of trustfor t in ae sa kw qa bh om eg jo iq lb; do echo "$t: $(dig +short DS $t. | head -1)"; done# Who runs a country code, and its WHOIS server, from IANA’s databasewhois -h whois.iana.org ae
04Rules that differ by registry
When you choose an extension, you accept all of its registry’s rules. These are the main differences between a generic extension and a country one:
| Rule | A generic extension such as .com | A country extension such as .ae or .sa |
|---|---|---|
| Who may register | Any person or organisation, from any country | Usually those with a link to the country, with documents per category |
| Maximum term | 10 years | Set by each national registry |
| Transfer between registrars | ICANN policy: an EPP code, and a year added to the term | The national registry’s rules |
| DNSSEC | Supported; .com has been signed since 2011 | It varies: look for the extension’s DS record in the root |
| Registration data | RDAP, the official source in place of WHOIS since early 2025 | The national registry’s WHOIS server |
| Geographic effect in Google | Neutral | A signal of an audience in that country |
Even among generic extensions the rules vary. The .co registry, for instance, hasn’t accepted registrations longer than 5 years since its management moved to CentralNic in late 2025. Some country extensions outside the region require a link to the country too: .eu for EU citizens and residents, .us for those with a genuine connection to the United States. And generic extensions in regulated fields, such as finance and health, require you to declare at registration that you hold the licences the field demands, and may be reviewed if someone complains.
Support for Arabic names varies too: an extension accepts them if its registry has published an Arabic script table with IANA, and many haven’t.
05Price: the first year isn’t the whole story
The registry sets each extension’s wholesale price, the registrar adds its own cost, and generic extensions carry ICANN’s yearly fee, which is included in the prices Illevante shows. Three patterns make next year’s invoice differ from today’s:
- A first-year promotion: Many new extensions sell at a promotional price in their first year, then renew at the regular price, which can be several times higher.
- Premium names: Some registries classify short names or common words as premium names with a higher price, and their renewals may stay higher too.
- Wholesale price changes: Some registries’ contracts allow them to raise prices periodically, so the renewal price itself changes over the years.
So work out the cost over five years: the first-year price, then four renewals at the regular price. And if the extension suits you, registering for several years at once fixes the price for the years you’ve paid.
06Extensions and search engines
This is where myths pile up, while the facts are few and clear:
- A country extension is a geographic signal: Google treats a country extension, such as .ae or .eg, as a strong signal that the site targets that country’s audience. That helps in search results inside it, but it doesn’t put you in first place on its own.
- Generic extensions are neutral: Google gives no ranking advantage to a generic extension, old or new, and a keyword in the extension, such as .shop or .tech, doesn’t help you.
- Some country codes count as generic: Google treats some commercially popular country extensions, such as .io, .co, .me and .tv, as generic, so it doesn’t tie them to their country.
- No country-targeting setting: Google removed the target-country setting from Search Console in 2022. So if your site is on .com and targets an audience in Jordan, the signals are the content and its language, hreflang tags, a local address, and links from local sites.
The server’s physical location is a weak ranking signal, but it sets the latency your visitors get, and that is what they actually feel.
07Before you decide
These are problems we run into with extensions chosen without checking their rules:
- ProblemYou enabled DNSSEC on your domain and resolvers don’t validate it
- FixCheck the chain from the top: if the extension has no DS record in the root, resolvers treat your zone as unsigned; if it has one, the missing link is usually your domain’s own DS record, which you add at the registrar. Until the chain is whole, rely on HTTPS and CAA records to protect your site.
- ProblemThe renewal price doubled after the first year
- FixThe promotion ended. Compare the renewal price before registering, or register for several years if the extension suits you.
- ProblemYour .com site shows up for searchers abroad more than in Jordan
- FixA generic extension is neutral. Add local signals: content in your audience’s language, hreflang tags, an address in Amman, and links from local sites.
- ProblemA booking under a country code was rejected
- FixUsually missing documents or no link to the country: company categories such as .com.sa need a commercial register, education ones an educational licence, and government ones an official letter. The national registry sets out what each category needs.
The practical way to choose: define your audience first, then read the extension registry’s rules before its price, then work out the five-year cost. And before registering, look the name up with the WHOIS lookup tool on Illevante’s website to see its status and expiry date if it’s taken, with a signed PDF report. We cover the criteria for choosing the name itself in a separate article on the blog.
