Tajik Names

Structure & order

Under the Soviet system the inherited order is the East-Slavic three-part pattern (see Russian Names, Name Ordering):

[GIVEN] [PATRONYMIC] [SURNAME]

e.g. Emomali Sharipovich Rahmonov, given name + father-derived patronymic + family name. Documents and everyday usage frequently shorten to [GIVEN] [SURNAME]. The native Persian pattern is simpler, a given name plus a derived family name, and the post-1991 revival pushes toward [GIVEN] [SURNAME(-Persian suffix)], sometimes with a patronymic still present.

Given names

Given names draw overwhelmingly on Persian roots: vocabulary words, nature imagery, and figures from Persian literature (notably the Shahnameh), alongside Islamic/Arabic religious names. Examples: Rustam (legendary warrior), Firuz "successful" / Firuza "turquoise," Jahongir "world-conqueror," Mahsa "moon-like," Gulshan "rose garden." Gender is conveyed by meaning and convention rather than by a rigid suffix system, though Persian feminine forms (final -a, e.g. Firuz / Firuza) recur. Since 2016 the state has constrained given-name choice: parents are expected to select from an official register of approved "Tajik/national" names (reported at around 3,000–4,000 names), and forenames deemed foreign to national culture may be refused at registration, a contested restriction (see Distinctive practices & pitfalls). RFE/RL (June 2026) reports the register being revised again: of the previous 4,056 names, 1,745 were removed (most of them Arabic) and 965 new "Arian" (Tajik/ancient-Persian) names added. Registrars now refuse to issue a birth certificate for an off-list name unless the parents petition the State Language and Terminology Committee for approval; in one case a couple wanting Tayeeba (after a grandmother) had to substitute the on-list Anisa. The 2016 law also banned adding Islamic/Arabic titles or suffixes (mullah, khalifa, shaikh, amir, sufi) to men's names; the government has not banned Islamic names outright but urges "purely" Tajik-Persian ones, the policy reportedly aimed at names of prominent Islamic figures (Sumayah, Khadija, Muhammad, Abubakr).

Family names & patronymics

Two competing layers coexist:

Native Persian formation. Family names are built from a father's given name (or a surname root) using Persian suffixes: -zod / -zoda "born of, descendant of," -i (the most common; turns a name or place into an adjectival surname), -iyon / -yon / -on (plural/collective), -pur "son of," -far, -niyo. These also serve a patronymic function (e.g. Alizoda ≈ "of Ali"). Note: some sources cite gendered variants such as a feminine -zodagi alongside masculine -zoda; this distinction is not consistently documented and should be treated as uncertain.

Soviet/Russian formation. From the 20th century, surnames were standardised on the Russian model with -ov / -ova (m/f) and patronymics in -ovich / -ovna (or -evich / -evna). Thus a single lineage may appear as Rahmonov (Russified) or Rahmon / Rahmoni (Persian). Under this regime the patronymic regenerates each generation from the father's given name, exactly as in Russian Names (see Patronymics and Lineage).

The 2016 law. A measure promoted under President Emomali Rahmon restricted ethnic Tajiks from registering newborns with Russian-style endings -ov / -ova / -ev / -eva and Russian-style patronymics, directing them instead toward native endings (-zod, -i, -iyon, -pur, -far); children of minority and mixed families retained the right to their traditional surnames (Wikipedia, citing the April 2016 ban). It built on Rahmon's own example: born Emomali Sharipovich Rahmonov, in March 2007 he dropped the Russian-style -ov ending to "Rahmon" and removed the patronymic "Sharipovich" altogether, explaining the change as respect for his cultural heritage. "Scores of government officials, including members of parliament and civil servants, also removed Russian-style patronymics and '-ov' endings" in his wake (Wikipedia). AsiaNews dates the Tajik vogue for rejecting Russian endings to that 2007 move, "immediately imitated by many state officials." Reporting on the scope is mixed and politically contested: some accounts describe a binding obligation for new registrations (with existing surnames and non-Tajik minorities exempt), while others report officials later framed it as a recommendation rather than a strict requirement. A frequently noted countercurrent: the process later partly reversed "so as not to complicate the issuing of documents and employment in Russia for labour migrants," and Tajik labour migrants prefer to keep -ov surnames because they ease life and paperwork in Russia (one Khujand migrant: "One million Tajiks work in Russia… Russian-style surnames simply make our lives easier"). AsiaNews reports the Prosecutor General of Dushanbe voiced concern about a "return to Russian surnames" among young people, banned in 2020 by parliamentary decision for the "defence of national self-consciousness", a distinction the article notes often "ends up depending on a couple of letters, between -on and -zoda." (The 2016/2020 chronology of successive measures is not fully consistent across reports, flagged as uncertain.)

How to address someone

Persian honorific and address conventions apply (see Salutations and Address, Persian Names): respectful forms include titles like Khan, Hoji/Hajji (one who has performed the Hajj), and religiously/socially marked terms. Soviet-era and Russian-contact usage also brought the formal given name + patronymic as a polite address mode (as in Russian Names). Professional and religious titles (e.g. teacher, mullah) are used before the name in spoken Tajik. Specific Tajik honorific vocabulary and current preferred address forms were not well-attested in the consulted sources; treat the inventory above as indicative rather than exhaustive.

Pitfalls for software

• Same person, two surnames. A lineage can surface as both -ov/-ova (Russified) and -zoda/-i (Persian) depending on era and document, a major identity-resolution hazard. Name-parsing software should treat Rahmonov ↔ Rahmon ↔ Rahmoni as variants of one root.
• -ov is a suffix, not part of the root. Stripping/normalising Russified endings (-ov, -ova, -ev, -eva, -ovich, -ovna) recovers the Persian stem, but doing so blindly can collide distinct names; keep both surface forms.
• Patronymic ambiguity. A middle element ending in -ovich/-ovna is a patronymic, not a second given name or surname; native -zoda/-i forms can occupy either the patronymic or surname slot.
• Script duality. The same Tajik name exists in Cyrillic (Tajikistan) and Perso-Arabic (Afghanistan/Iran); cross-border matching needs transliteration awareness. Persian/Arabic given-name overlap also links this system to Arabic Names.
• Politically loaded registration. Whether a Russian or Persian form is "correct" is contested state policy, not a neutral fact; the obligation-vs-recommendation status and the exact approved-name list have shifted and are reported inconsistently; claims here are flagged uncertain.
• Romanization variance. Rahmon / Rakhmon / Rahmonov / Rakhmonov and Emomali / Imomali / Imamali are all the same person across transliteration schemes.