name.tr Domain Guide 2026: Personal Domain

If you want a personal domain name in Turkey, name.tr is most likely the first extension you should evaluate. Where.com.tr signals commercial entities,.org.tr suggests associations and foundations, and.av.tr is reserved for attorneys, the firstname-lastname.name.tr format is purpose-built for individual online identity — it's semantically correct and one of the few second-level.tr extensions that can be registered without supporting documents. Following the post-2018 TRABİS transition, the 2020 document-free registration reform, and the 2022 launch of single-level .tr, name.tr can now be acquired through an automated 5-10 minute process. This guide covers name.tr's history, regulations, registration flow, technical requirements, and pricing tiers end-to-end with 2026 data.

We've structured this article not as a mere price list but as a technical reference written from inside Turkey's domain ecosystem. Below you'll find BTK regulations, the accredited registrar concept, EPP authcode, nameserver requirements, the redemption period, and dispute resolution mechanisms — illustrated with real commands and sample WHOIS output.

What Is name.tr? Definition, Position, and Semantic Context

name.tr is one of the second-level domain (SLD) groupings under .tr, the country-code top-level domain (ccTLD) for Turkey. The full form is username.name.tr;.tr sits at the top level while the classification prefix name sits at the second level. The label itself derives from the English word name and clearly signals personal use. Where.com.tr targets commerce,.org.tr civil society, and.gen.tr general use, name.tr is aimed at the individual.

In the broader hierarchy, name.tr sits like this: in the URL www.egemen-brandname.name.tr, tr is the top-level, name is the second-level prefix, egemen-brandname is the third-level (the actual allocated label), and www is the host part. DNS queries resolve this tree toward the root; the authoritative servers for the.tr zone live within Turkey's TRABİS infrastructure.

For a separate comparison of the other.tr extensions and their target audiences, see our.com and.net usage guide and domain search guide 2026. For the SEO and brand perception side of choosing name.tr, also read our local SEO guide.

A Short History: From METU's Nic.tr to TRABİS

The.tr extension was delegated by IANA in the early 1990s to Middle East Technical University (METU). The registry system, known as nic.tr and operated within METU, was for years the sole authority managing.tr domains. During that era, all second-level extensions including name.tr required strict supporting documents; the process was manual, paper-heavy, and typically took 2-7 business days.

Following Electronic Communications Law No. 5809, BTK (Information and Communication Technologies Authority, ICTA) was designated as the country's domain regulator. You can find a detailed BTK overview in our BTK organizational structure article. Starting in 2018, BTK launched the TRABİS (.tr Network Information System) project, moving the.tr ecosystem to an ICANN-style multi-registrar model.

The post-TRABİS ecosystem has three layers: TRABİS (the registry, supervised by BTK), TRABİS-accredited registrars (local Turkish providers), and end users (registrants). The 2020 reform opened com.tr/net.tr/org.tr/biz.tr/info.tr/tv.tr/web.tr/gen.tr/name.tr to document-free registration. In 2022, single-level brand.tr applications became available via nic.tr.

Who Can Register name.tr? 2026 Eligibility

The post-reform rules are clear: name.tr can be registered by both individuals and legal entities without submitting any supporting documentation. The only requirement is that the applicant provide accurate identity information — a Turkish national ID number (TCKN) for individuals or a tax number plus company name for legal entities. The pre-2018 rule of 'a notarized copy of the national ID for name.tr' no longer applies.

Turkish citizens (individuals): direct registration with TCKN, full name, and a contact email.
Foreigners residing in Turkey: registration possible with foreign ID number or passport details; in practice, registrar panels accept both.
Turkish companies: registration is possible with tax number and trade name, but since name.tr's natural target is individual use,.com.tr or.tr is more appropriate for brand usage.
Foreign individuals abroad: some registrars accept name.tr applications with a foreign passport; this varies by registrar, so confirm before applying.
Age requirement: for those under 18, registration can be made under a guardian's TCKN; this detail becomes relevant if a dispute escalates to a TRABİS UÇHS proceeding.

Document-free does not mean unverified: TRABİS validates the accuracy of the information supplied during registration. Records made with a wrong TCKN or fabricated information can be revoked retroactively, and the name may end up on the blacklist (TAKAL). Additionally, names on the historical-cultural-geographic protection list known as TAKİL (e.g., province/district names, historical figures) cannot be registered without documents — acquiring them requires authorization from the relevant institution.

name.tr Character Rules, IDN, and Format

The technical constraints imposed by the TRABİS contract for name.tr are:

Length: 2-63 characters; in practice, registrar panels block anything under 3 characters. The upper bound matches the DNS standard (RFC 1035).
Allowed characters: a-z, 0-9, and hyphen (-). The hyphen cannot appear at the start or end; consecutive hyphens (--) are only allowed in the IDN punycode prefix (xn--).
Case sensitivity: DNS is case-insensitive; Egemen.name.tr and egemen.name.tr point to the same record.
IDN support: Turkish characters (ı, ş, ğ, ç, ü, ö) are supported via punycode encoding. türkçe.name.tr is actually registered as xn--trke-1qa6e.name.tr.
Forbidden combinations: a TAKAL check runs at registration time; combinations containing slurs, insults, or terrorist organization names are rejected.
All-numeric labels: labels consisting entirely of digits (e.g., 12345.name.tr) are technically permitted, but registrars rarely approve them.

An IDN example demonstrating Turkish character support:

# Punycode conversion (with the idn2 tool)
sudo apt install idn2

# Turkish-character label → ASCII (DNS-compatible) form
idn2 'şahin.name.tr'
# Output: xn--ahin-yqa.name.tr

idn2 'gümüş-kuyumculuk.name.tr'
# Output: xn---kuyumculuk-vmbf75c.name.tr

# Reverse decoding
idn2 -d 'xn--ahin-yqa.name.tr'
# Output: şahin.name.tr

When choosing IDN, keep three practical caveats in mind: some legacy email systems can't normalize punycode addresses, certificate authorities (CAs) may require additional validation before issuing a certificate for an IDN domain, and homograph attacks (e.g., Cyrillic 'а' substituted for Latin 'a') create a security risk. We cover this in detail in our phishing guide.

TRABİS Registration Process: Step by Step

A typical name.tr registration flow through a TRABİS-accredited registrar takes 5-10 minutes and consists of these stages:

1. Lookup: check the availability of your desired label via the registrar's lookup form or directly through WHOIS/RDAP.
2. Cart and term selection: pick a registration period of 1-5 years. Longer terms (3-5 years) earn discounts and reduce the risk of forgetting to renew.
3. Registrant information: TCKN, full name, date of birth, address, email, phone. Accuracy is critical — the dispute section below explains why.
4. NS (nameserver) information: at least 2 authoritative NS entries. You can use your registrar's defaults or pick your own DNS provider (Cloudflare, Bunny DNS, Hetzner DNS).
5. Contract acceptance: approve the TRABİS Registration Agreement and the registrar's terms of service.
6. Payment: credit card, bank transfer, or — at some registrars — mobile payment.
7. EPP submission: the registrar transmits the application to TRABİS over EPP (Extensible Provisioning Protocol).
8. WHOIS reflection: the domain typically becomes visible in WHOIS/RDAP within 5-30 minutes. DNS propagation depends on cache TTLs and may take 1-24 hours.

When choosing a registrar, evaluate accreditation status (TRABİS-accredited?), API quality, panel ergonomics, pricing transparency, and customer support response times. Common Turkish registrars include İsimTescil, Natro, Turhost, Atak Domain, IHS, Hosting.com.tr, Radore, and PremierDC. For comparison criteria, review our domain selection guide.

Pricing in 2026: Ranges and Expectations

For Q1 2026, the price ranges observed at Turkish registrars for name.tr are (approximate, varies by provider, 2026 data):

New registration (1 year): 90-200 TL band (around $3-7 USD). During promotions, prices have dropped to 60-80 TL.
Renewal (1 year): 450-700 TL (around $15-23 USD) — renewals are notably more expensive than initial registration, reflecting the.tr ecosystem's 'low entry, high recurring' model.
Transfer (registrar change): 400-600 TL (around $13-20 USD). The transfer typically adds 1 year to the existing expiration.
Redemption: 1,500-3,000 TL (around $50-100 USD) — for names that have expired and entered the grace/redemption period.
Multi-year registration discount: for 3-5 year registrations, the per-year average can drop to 60-150 TL.
WHOIS privacy: TRABİS masks part of the WHOIS data for name.tr by default; there is no separate 'privacy' fee.

Prices vary based on the registration fee set annually by BTK plus the registrar's margin. For a cost analysis comparing with gTLDs like.com, see our .com domain prices 2026 article.

WHOIS / RDAP Lookups for name.tr

The authoritative WHOIS server for name.tr is whois.nic.tr. The RDAP (Registration Data Access Protocol) endpoint is announced via IANA bootstrap and resolves to the URL TRABİS publishes. Sample command-line queries:

# Classic WHOIS
whois -h whois.nic.tr ornek-isim.name.tr

# Brief WHOIS summary (modern alternative to jwhois)
whois ornek-isim.name.tr | grep -E '(Domain|Status|Registrant|Registrar|Created|Expires|Name Server)'

# RDAP query in JSON format
curl -s 'https://rdap.nic.tr/domain/ornek-isim.name.tr' | jq.

# Pull only nameserver records via RDAP
curl -s 'https://rdap.nic.tr/domain/ornek-isim.name.tr' \
 | jq -r '.nameservers[].ldhName'

The key fields when reading WHOIS output are: Domain Name (the registered label), Status (lifecycle state — clientHold, ok, redemptionPeriod, pendingDelete), Registrant (registrant identity, masked for individuals), Registrar (the accredited operator), Creation Date (initial registration), Expiration Date (end of term), and Name Server (list of authoritative NSes).

For details on the differences between WHOIS and RDAP, privacy policy, and standards, I recommend reading our WHOIS, RDAP, and DNS lookup tools article.

Sample WHOIS Output (Fictitious)

** Domain Name: ornek-isim.name.tr
** Status: ok

** Registrant:
 name: Ali Veli (masked)
 email: ******@*****.com

** Registrar:
 Sample TRABIS Accredited Registrar
 Address: Istanbul, TR
 URL: https://sample-registrar.com.tr

** Domain Servers:
 ns1.sample-dns.com
 ns2.sample-dns.com

** Additional Info:
 Created on: 2024-03-12
 Expires on: 2026-03-12
 Last Updated on: 2025-04-01

DNS and Nameserver Setup

name.tr requires at least 2 authoritative nameservers; most registrars and TRABİS validation accept up to 4 NS entries. The authoritative NS's SOA and NS records must be consistent — otherwise the TRABİS DNS check fails and the registration won't go live. The primary references for DNS standards are RFC 1034/1035 and RFC 7480.

Three approaches are common in practice:

Registrar's default NS: the easiest path; you manage A/AAAA/MX/TXT records through the DNS interface in the registrar panel.
Cloudflare DNS: point your NS to the two addresses Cloudflare assigns (e.g., chad.ns.cloudflare.com, uma.ns.cloudflare.com). Anycast routing delivers low latency and free DDoS protection.
Self-hosted DNS (BIND, PowerDNS, Knot DNS): for advanced users. Be sure to read our DNS configuration guide first.

Wiring name.tr DNS to Cloudflare:

# 1) In the Cloudflare panel: 'Add a Site' → ornek-isim.name.tr
# 2) Cloudflare hands you 2 NS (e.g., chad.ns.cloudflare.com / uma.ns.cloudflare.com)
# 3) Update the NS in your TRABIS-accredited registrar's panel
# 4) Verify NS propagation:

dig +trace ornek-isim.name.tr NS

# Check which NS Cloudflare itself reports
dig @1.1.1.1 ornek-isim.name.tr NS +short

# After adding the A record:
dig ornek-isim.name.tr A +short
dig ornek-isim.name.tr AAAA +short

# DNSSEC status (TRABIS supports DNSSEC)
dig ornek-isim.name.tr DS +short

Typical Record Set (Personal Website)

; Apex domain
@ IN A 203.0.113.45
@ IN AAAA 2001:db8::45
www IN CNAME @

; Mail (email forwarding)
@ IN MX 10 mx.sample-mail.com.
@ IN TXT "v=spf1 include:_spf.sample-mail.com -all"
_dmarc IN TXT "v=DMARC1; p=quarantine; rua=mailto:dmarc@ornek-isim.name.tr"

; Domain verification (Search Console, etc.)
@ IN TXT "google-site-verification=..."

; Auto-discover (optional for CalDAV/CardDAV/mail clients)
autoconfig IN CNAME sample-mail.com.

; CAA (certificate authority restriction)
@ IN CAA 0 issue "letsencrypt.org"

With a CAA record, only the CAs you specify (e.g., Let's Encrypt) can issue certificates — adding a layer of defense against mis-issuance. For free SSL setup, follow our Let's Encrypt guide.

DNSSEC for name.tr

TRABİS supports DNSSEC for the.tr zone. By signing DNS responses, DNSSEC builds a cryptographic chain of trust against cache poisoning and man-in-the-middle attacks. To enable DNSSEC on your name.tr, your DNS provider (Cloudflare, PowerDNS, BIND) generates a DS record, which you publish at the parent zone via your TRABİS-accredited registrar's panel or API.

# After enabling DNSSEC in Cloudflare, retrieve the DS record:
# DNS > Settings > DNSSEC > 'Enable DNSSEC' > 'View DS record'

# Fields to enter in the registrar panel:
# Key Tag: 12345
# Algorithm: 13 (ECDSAP256SHA256)
# Digest Type: 2 (SHA-256)
# Digest: AB12CD34...

# Verification after propagation:
delv +rtrace ornek-isim.name.tr A
# You should see 'fully validated'

# Alternative: Verisign DNSSEC analyzer
# https://dnssec-analyzer.verisignlabs.com/ornek-isim.name.tr

If you want to keep DNSSEC enabled long-term, automate key rollovers; a DS-DNSKEY synchronization error during a manual rollover can render the entire domain unreachable. For the complementary relationship between DNSSEC and TLS, review our HTTPS and TLS 1.3 guide.

Lifecycle: Registration → Renewal → Redemption → Deletion

name.tr follows the standard lifecycle of any gTLD/ccTLD. After expiration, the domain doesn't immediately become available to others — there are grace and redemption periods.

Active: registration active, NS responding, web/email working.
Auto-renew Grace Period: typically 0-30 days after expiration; renewal is possible at the regular price during this window, and most registrars retry automatic billing.
Redemption Grace Period (RGP): 30-45 days; if no renewal occurs the domain is suspended and NS are deactivated. Recovering it requires paying a redemption fee (1,500-3,000 TL band, around $50-100 USD).
Pending Delete: a 5-7 day technical deletion window; no actions can be taken during this period.
Released: the domain reopens for registration; first-come, first-served applies.

To minimize redemption costs and forgetting risk, apply three steps: (1) enable auto-renew in the registrar panel and verify your card's expiration date; (2) add at least 3 separate emails plus 1 phone number as WHOIS contact information; (3) set calendar reminders 30/15/7 days ahead of expiry. There's a discipline parallel between domain backup logic and the 3-2-1 backup rule.

Transfer Process: Registrar Change with EPP Authcode

Transfers between TRABİS-accredited registrars use Turkey's adaptation of the ICANN model. The three core steps are:

1. Get the EPP / authcode from the current registrar: from the registrar panel's 'Transfer' or 'Authorization Code' menu, generate an 8-32 character code.
2. Submit a transfer request to the new registrar: enter the name.tr and authcode, then complete the payment.
3. Reply to the confirmation email: a confirmation email arrives at the admin address registered in WHOIS; the transfer doesn't proceed until you click.

Transfer time ranges from 1-7 business days; in most cases it completes within 24-48 hours. Common blockers: an active domain lock (turn it off), the 60-day lock from a recent registration or prior transfer, fewer than 7 days remaining until expiration, and a missing or wrong authcode. Specific to.tr, some legacy document-based registrations (acquired before 2020) may still require supplementary documents.

# Pre-transfer status check (lock must be off)
whois ornek-isim.name.tr | grep -i status

# If you see 'Status: clientTransferProhibited', ask your current
# registrar to disable the transfer lock

# Authcode validation (in the registrar panel)
# - 8-32 characters
# - Mix of uppercase, lowercase, digits, special characters
# - Authcode is single-use; it changes automatically after transfer

Dispute Resolution Mechanisms (UÇHS)

Within TRABİS, arbitration centers known as Dispute Resolution Service Providers (UÇHS) operate as Turkey's adaptation of ICANN's UDRP. Common UÇHS dispute themes for name.tr: trademark infringement, personality rights, bad-faith registration (cybersquatting), and account loss by the previous owner.

Filing: the rights holder submits a written application to the UÇHS arbitration panel (power of attorney + evidence).
Response window: the registrant is typically given 10 business days to reply.
Decision: the panel issues a decision within 30-60 days; the name is then transferred, cancelled, or kept by the existing holder.
Administrative court route: an appeal to administrative courts is possible against a UÇHS decision, but this can take months or years.
Cost: single-arbitrator panels run 5,000-15,000 TL (around $165-500 USD); three-arbitrator proceedings run 15,000-30,000 TL (around $500-1,000 USD).

Specifically for name.tr, the holder of a personal name (e.g., a person named Egemen brandname seeking egemen-brandname.name.tr) has a strong arbitration case against someone who has registered that label in their stead. A common defensive practice against bad-faith registration is to pre-register your name in multiple variations (kebab-case, no separator, given+surname).

name.tr Compared: gen.tr, web.tr,.tr, and.com

A quick comparison of candidates for personal use:

name.tr: natural target is personal use. The strongest semantic layer; ideal for CV / personal blog / portfolio.
gen.tr: stands for 'general'; preferred for personal and hobby use, perceived as similar to name.tr but lacks the explicit name connotation.
web.tr: aimed at web-focused individuals/projects; popular with developers.
.tr (single-level): allocated since 2022. A 'low-conflict-pricing' entry for unconested names — but the good labels are typically already taken. Attractive for brands; can feel overly formal for personal use.
.com: the most global, the most universal; SEO-neutral (no geo-targeting); for a personal brand, firstnamelastname.com may still be the #1 choice.

A cross-registration strategy: a common combination for the professional user is firstnamelastname.com + firstnamelastname.name.tr;.com handles global outreach while name.tr provides Turkey-focused SEO and a local trust signal. For brand identity, I recommend reading our domain valuation guide.

Email on name.tr: Setting Up a Professional Personal Account

One of name.tr's strongest use cases is personal email. The format egemen@egemen-brandname.name.tr looks far more professional than gmail.com and builds personal brand. Three setup paths:

Email included by your registrar: most hosting packages include 5-100 mailboxes; convenient but limited in features.
Google Workspace / Microsoft 365: $6-15 USD/month; enterprise-grade quality, though potentially expensive for individual use.
Self-hosted (Mailcow, Mailu, Mail-in-a-Box): $5-15 USD/month for VPS; requires technical knowledge but offers maximum control.

For deliverability, the SPF + DKIM + DMARC trio must be configured fully and correctly; otherwise, Gmail and Outlook will route messages to spam.

; SPF — only allow your provider's mail servers
@ IN TXT "v=spf1 include:_spf.mailprovider.com -all"

; DKIM — public key (generated in the provider panel)
mail._domainkey IN TXT "v=DKIM1; k=rsa; p=MIGfMA0GCS...IDAQAB"

; DMARC — start with 'none', then quarantine, finally reject
_dmarc IN TXT "v=DMARC1; p=none; rua=mailto:dmarc@ornek-isim.name.tr; pct=100"

; Then:
; _dmarc IN TXT "v=DMARC1; p=quarantine; rua=mailto:dmarc@ornek-isim.name.tr; pct=50"
; _dmarc IN TXT "v=DMARC1; p=reject; rua=mailto:dmarc@ornek-isim.name.tr; pct=100"

To test the DKIM/SPF/DMARC pipeline for name.tr, mail-tester.com and dmarcian's DMARC inspector are free and effective. For SMTP/IMAP configuration details, read our Postfix mail server guide.

SSL Certificates and HTTPS for name.tr

On name.tr, modern HTTPS is now mandatory. All browsers flag plain HTTP traffic with a 'Not Secure' warning, and on the SEO front, Google Search Console penalizes non-HTTPS sites. Three paths:

Let's Encrypt (free, auto-renews every 90 days): the most common choice for individual name.tr. Certbot installs it in 5 minutes.
ZeroSSL / Buypass (free alternatives): alternatives to Let's Encrypt; ACME protocol is supported.
Paid OV/EV certificates: not necessary for personal use; preferred for commercial domains with high security requirements like banks or e-commerce.

# Let's Encrypt certificate for name.tr with Nginx + Certbot
sudo apt update
sudo apt install certbot python3-certbot-nginx -y

# Certificate + Nginx config update in one command
sudo certbot --nginx \
 -d ornek-isim.name.tr \
 -d www.ornek-isim.name.tr \
 --email egemen@ornek-isim.name.tr \
 --agree-tos --no-eff-email --redirect

# Verify auto-renewal
sudo certbot renew --dry-run

# CAA record permitting only Let's Encrypt (in DNS)
# @ IN CAA 0 issue "letsencrypt.org"

# Test certificate strength
curl -sI https://ornek-isim.name.tr | head -5
openssl s_client -connect ornek-isim.name.tr:443 -servername ornek-isim.name.tr < /dev/null 2>&1 | openssl x509 -noout -dates

For security hardening details like HSTS, OCSP stapling, and TLS cipher selection, follow our how to obtain an SSL certificate guide, and on the Nginx side our Nginx configuration guide.

Hosting Side: Server Selection for name.tr

Once name.tr is registered, you'll need a hosting environment. Personal use profiles:

Static blog / portfolio: free static hosts like Cloudflare Pages, GitHub Pages, or Netlify suffice. Connect via CNAME.
Personal WordPress site: shared hosting (10-50 TL/month, around $0.30-1.70 USD) is sufficient; our hosting types guide simplifies the decision.
Self-hosted application (Hugo, Ghost, Mastodon): requires a VPS; start with our VPS guide and Linux server basics.
File sharing / personal cloud: a Nextcloud + name.tr combo creates a professional 'own cloud'.

Choosing a server in Turkey is advantageous for SEO and round-trip times; if you're building a Turkey-focused personal brand in particular, opt for a Turkish data center (Istanbul/Ankara). To run servers in multiple regions with geo-DNS routing, read our CDN guide.

Automated Workflow: DevOps for name.tr

Advanced users can fully automate DNS management, certificate renewal, and deployment by leveraging the APIs exposed by TRABİS registrar panels. A sample Terraform deployment (using the Cloudflare DNS provider):

# main.tf — name.tr DNS via Cloudflare
terraform {
 required_providers {
 cloudflare = {
 source = "cloudflare/cloudflare"
 version = "~> 4.0"
 }
 }
}

provider "cloudflare" {
 api_token = var.cf_token
}

resource "cloudflare_zone" "name_tr" {
 zone = "ornek-isim.name.tr"
 plan = "free"
}

resource "cloudflare_record" "root" {
 zone_id = cloudflare_zone.name_tr.id
 name = "@"
 value = "203.0.113.45"
 type = "A"
 ttl = 1
 proxied = true
}

resource "cloudflare_record" "www" {
 zone_id = cloudflare_zone.name_tr.id
 name = "www"
 value = "ornek-isim.name.tr"
 type = "CNAME"
 ttl = 1
 proxied = true
}

resource "cloudflare_record" "mx" {
 zone_id = cloudflare_zone.name_tr.id
 name = "@"
 type = "MX"
 value = "mx.sample-mail.com"
 priority = 10
 ttl = 3600
}

We cover the basics of managing infrastructure as code with Terraform in our Terraform IaC guide, and CI/CD integration with GitHub Actions in the GitHub Actions guide. For automated certificate renewal, our recommended Ansible playbook lives in the Ansible automation article.

Security: Protecting Your name.tr Account from Hijack

A domain is the foundation of an individual's digital identity. To defend against domain hijack attacks, you should build at least a 5-layer defense:

1. 2FA on the registrar account: use TOTP (Google Authenticator, Authy) or a hardware key (YubiKey) instead of SMS — SIM-swap attacks defeat SMS-based 2FA.
2. Domain Lock (registrar lock): enable it from the registrar panel; clientTransferProhibited appears in WHOIS.
3. Separate WHOIS contact email: don't use your primary public-facing email as your WHOIS contact; assign a dedicated email for this account.
4. DNSSEC enabled: publish the DS record as described above; a shield against cache poisoning.
5. CAA record: only allow the CAs you actually use; reduces mis-issuance risk.
6. Regular WHOIS audit: monthly, check whether your WHOIS information has changed (with an automated script).

One of the best-known examples in domain hijack history is the 2008 Twitter DNS hijack incident; attackers compromised the registrar account and the site was offline for minutes. The post-mortem reports published afterward remain relevant today. We cover domain takeover attacks in detail in our OWASP Top 10 2026 article.

Frequently Asked Questions about name.tr

Can I register a name.tr and use it from outside Turkey?

Yes. DNS is a global protocol; you can point your name.tr to a server in Germany, a Cloudflare account in the US, or a VPS in India. TRABİS only validates the registrant's identity — traffic flow and server location are unrestricted. For Turkish citizens living abroad, applying with a TCKN is the standard route, and there's no requirement to reside in Turkey. Paying through the registrar panel with a foreign payment card or PayPal is supported by virtually all accredited registrars; some even accept SWIFT wire transfers. The one practical caveat: write the WHOIS contact phone with the correct country code (e.g., +49...) and ensure you can receive the registrar's SMS verification.

What's the SEO impact of name.tr outside Turkey?

ccTLDs have strong geo-targeting in Google's eyes; a.tr domain defaults to focusing on Turkey, and global search visibility is generally low outside Turkey. If your audience spans multiple countries, choose firstnamelastname.com; for a strictly Turkey-focused personal identity, name.tr is the right pick. More details in our SEO and search engine guide.

Can I sell my name.tr?

Technically yes; transfers between TRABİS-accredited registrars are possible. However, the secondary market for name.tr is very thin; you'll never see prices like.com.tr or.com fetch. Good labels typically settle in the 500-5,000 TL band (around $17-170 USD).

What if two people request the same name.tr label?

Pure time priority applies: first come, first served. If escalated to UÇHS, the arbitration panel weighs trademark, personality rights, intent (bad-faith registration), and similar factors. The same rule holds even for two people sharing the same name; the first to register wins.

Are there subdomain restrictions on name.tr?

No. You can create unlimited subdomains like blog.egemen-brandname.name.tr, cv.egemen-brandname.name.tr, api.egemen-brandname.name.tr. Subdomains are managed by your DNS provider and require no additional notice to TRABİS. You can issue a separate SSL certificate per subdomain; alternatively, a *.egemen-brandname.name.tr wildcard certificate covers all subdomains in one shot. Wildcard certificates from Let's Encrypt can only be issued via the DNS-01 challenge; HTTP-01 doesn't issue wildcards. The detailed implementation lives in our Let's Encrypt guide.

How do I verify name.tr in Search Console?

After adding name.tr to Google Search Console, three verification methods exist: TXT record (most common), HTML file upload, and Google Analytics. For the TXT method, publish the google-site-verification=... value Search Console provides as a TXT record at the apex (@) level on your DNS provider; once propagation completes (5-30 minutes), click 'Verify' in the panel. With the domain property option, all subdomains and both HTTP and HTTPS variants are tracked under a single property; the URL prefix option only covers a specific variant. For personal use, prefer domain property.

Is trademark registration required for name.tr?

No, registering a name.tr doesn't require a TÜRKPATENT trademark, and the name.tr space is naturally protected through firstname/lastname matches. However, if you operate a personally branded business (e.g., publisher, author, consultant who uses your name as a service mark), trademark registration is a significant advantage in UÇHS proceedings. A trademark protects for 10 years, is renewable, and serves as a strong legal foundation against cybersquatters for both.com.tr and name.tr.

Common Mistakes and How to Avoid Them

No glue records when using your own NS: if you use ns1.your-domain.name.tr, glue records are mandatory. Without them, DNS resolution falls into an infinite loop.
Stale email in WHOIS: you'll miss renewal/transfer messages; audit monthly.
Single NS: TRABİS expects a minimum of 2 NSes; with one NS the registration won't go live.
TTL set too high: with TTLs of 86400+, fixing a mistake takes 24 hours; use 300-600 TTL during development and raise it for prod.
No WhoisGuard: TRABİS masks WHOIS for individuals by default, but for legal entities your information is fully visible.
Expired card: if auto-renew fails, you face redemption pricing; renew the card 60 days in advance.
DNSSEC off (vulnerable to cache poisoning): free, easy protection — always enable it.
Missing SPF: emails sent from name.tr land in Gmail spam; don't skip the SPF + DKIM + DMARC setup.

name.tr Practical Checklist (First 24 Hours After Registration)

1. Confirm the name reflects in WHOIS / RDAP: whois ornek-isim.name.tr
2. Check NS propagation with dig +trace.
3. Add A and AAAA records — don't forget IPv6.
4. Connect the www CNAME to apex.
5. Issue a Let's Encrypt certificate, enforce HTTPS (Strict-Transport-Security).
6. Publish a CAA record.
7. Set up MX + SPF + DKIM + DMARC.
8. Enable DNSSEC and publish the DS record at the parent.
9. Activate 2FA in the registrar panel.
10. Turn on registrar lock (clientTransferProhibited).
11. Add the expiration date to a calendar reminder (30/15/7 days ahead).
12. Test that the WHOIS contact email is reachable.

Resources and References

.com.tr Extension Registration Guide 2026 — comprehensive process for commercial.tr
.av.tr Domain Registration — document-based.tr for attorneys
What Is a Domain Name, WHOIS Lookup
Domain Search Guide 2026
What Is DNS, How to Change Settings
Free SSL with Let's Encrypt
BTK Lookup Guide

Professional support for your initial name.tr technical setup

To register name.tr, choose a TRABİS-accredited registrar, configure DNS / DNSSEC / SSL / mail and set up hosting from scratch with the brandname team, get in touch

Readers of this article also read these

hosting 27 min

Software Development

SEO & Optimization

API & Integration

Web Hosting

VPS Server

Dedicated Server

Domain & SSL

Why KEYDAL?

Projelerimiz

About Us

Contact