{"id":458,"date":"2026-01-18T20:01:50","date_gmt":"2026-01-18T20:01:50","guid":{"rendered":"https:\/\/narhost.com\/blog\/?p=458"},"modified":"2026-09-11T14:57:21","modified_gmt":"2026-09-11T14:57:21","slug":"domain-transfer-sureci-nasil-isler","status":"publish","type":"post","link":"https:\/\/narhost.com\/blog\/domain-transfer-sureci-nasil-isler\/","title":{"rendered":"Domain Transfer S\u00fcreci Nas\u0131l \u0130\u015fler, Ad\u0131m Ad\u0131m Anlat\u0131m"},"content":{"rendered":"<div id=\"ai-ozet\" class=\"ai-box\">\n<p class=\"ai-box-title\">K\u0131saca \u00f6zet<\/p>\n<ul>\n<li>Domain transfer s\u00fcreci, bir alan ad\u0131n\u0131n kay\u0131t hakk\u0131n\u0131 bir kay\u0131t kurulu\u015fundan di\u011ferine ta\u015f\u0131ma i\u015flemidir; alan ad\u0131 sizde kal\u0131r, yaln\u0131zca onu y\u00f6neten firma de\u011fi\u015fir.<\/li>\n<li>gTLD uzant\u0131larda transfer i\u00e7in alan ad\u0131n\u0131n kay\u0131ttan ya da son transferden bu yana 60 g\u00fcn\u00fc doldurmu\u015f olmas\u0131 gerekir.<\/li>\n<li>Alan ad\u0131n\u0131n transfer kilidi kapal\u0131 olmal\u0131 ve WHOIS kayd\u0131ndaki y\u00f6netici e-posta adresine eri\u015febiliyor olmal\u0131s\u0131n\u0131z; onay ba\u011flant\u0131s\u0131 oraya gider.<\/li>\n<li>EPP (auth) kodu eski kay\u0131t kurulu\u015funun panelinden al\u0131n\u0131r, yeni kurulu\u015fa girilir ve talep bu kodla ba\u015flat\u0131l\u0131r.<\/li>\n<li>Onay verildi\u011finde i\u015flem \u00e7o\u011funlukla ayn\u0131 g\u00fcn biter; onay verilmezse gTLD taraf\u0131nda be\u015finci g\u00fcn\u00fcn sonunda kendili\u011finden tamamlan\u0131r.<\/li>\n<li>Transfer nameserver kay\u0131tlar\u0131n\u0131 de\u011fi\u015ftirmez; DNS ve MX kay\u0131tlar\u0131 ayn\u0131 kald\u0131\u011f\u0131 s\u00fcrece site de e-posta da kesilmez.<\/li>\n<\/ul>\n<\/div>\n<p>Alan ad\u0131n\u0131 ba\u015fka bir firmaya ta\u015f\u0131mak, \u00e7o\u011fu ki\u015finin sand\u0131\u011f\u0131 kadar riskli bir i\u015f de\u011fil. Riskli olan haz\u0131rl\u0131ks\u0131z ba\u015flamak: kilit a\u00e7\u0131lmam\u0131\u015ft\u0131r, WHOIS&#8217;teki e-posta adresi y\u0131llar \u00f6nce kapanm\u0131\u015ft\u0131r, eski firma DNS b\u00f6lgesini i\u015flem biter bitmez siler. A\u015fa\u011f\u0131da domain transfer s\u00fcreci ba\u015ftan sona anlat\u0131l\u0131yor \u2014 hangi \u015fartlar sa\u011flanmal\u0131, EPP kodu nereden al\u0131n\u0131r, onay e-postas\u0131 ne i\u015fe yarar, .tr uzant\u0131lar\u0131nda i\u015fleyi\u015f neden ayr\u0131\u015f\u0131r.<\/p>\n<h2>Domain transfer s\u00fcreci nedir ve ne zaman gerekir?<\/h2>\n<p>Transfer, alan ad\u0131n\u0131n kay\u0131t hakk\u0131n\u0131n bir akredite kay\u0131t kurulu\u015fundan di\u011ferine ge\u00e7irilmesidir. Alan ad\u0131n\u0131n sahibi de\u011fi\u015fmez, s\u00fcresi s\u0131f\u0131rlanmaz, kay\u0131t tarihi silinmez. De\u011fi\u015fen tek \u015fey, alan ad\u0131n\u0131 kay\u0131t veritaban\u0131nda kimin y\u00f6netti\u011fidir.<\/p>\n<p>Domain transfer s\u00fcreci genelde \u00fc\u00e7 sebeple ba\u015flat\u0131l\u0131r. Birincisi hizmetleri tek yerde toplamak: hosting bir firmada, alan ad\u0131 ba\u015fka firmadaysa yenileme takibi da\u011f\u0131l\u0131r. \u0130kincisi eski kurulu\u015ftan memnun kalmamak \u2014 panel eri\u015fimi, destek ya da yenileme uygulamalar\u0131. \u00dc\u00e7\u00fcnc\u00fcs\u00fc devir: alan ad\u0131 ba\u015fka bir \u015firkete sat\u0131ld\u0131\u011f\u0131nda ya da ajanstan m\u00fc\u015fteriye teslim edildi\u011finde ta\u015f\u0131n\u0131r.<\/p>\n<div class=\"highlight-box\">\n<p class=\"label\">Bilgi<\/p>\n<p>Transfer, alan ad\u0131na genelde bir y\u0131l ekler. Mevcut biti\u015f tarihinizin \u00fczerine bir y\u0131l daha yaz\u0131l\u0131r, g\u00fcn kaybetmezsiniz. Bu y\u00fczden yenileme zaman\u0131 yakla\u015fan bir alan ad\u0131n\u0131 ta\u015f\u0131mak mant\u0131kl\u0131d\u0131r; iki i\u015flemi tek seferde yapars\u0131n\u0131z.<\/p>\n<\/div>\n<h2>Transfer \u00f6ncesi sa\u011flanmas\u0131 gereken \u015fartlar<\/h2>\n<p>gTLD uzant\u0131larda (.com, .net, .org, .info gibi) kurallar\u0131 ICANN belirler. \u00dc\u00e7 \u015fart kar\u015f\u0131lanmadan talep zaten ba\u015flamaz.<\/p>\n<p><strong>60 g\u00fcnl\u00fck kural:<\/strong> Alan ad\u0131 yeni kaydedildiyse ya da son 60 g\u00fcn i\u00e7inde transfer edildiyse yeni bir transfer kabul edilmez. Ayn\u0131 kural, WHOIS&#8217;teki kay\u0131t sahibi bilgisi de\u011fi\u015ftirildi\u011finde de i\u015fleyebilir; sahip de\u011fi\u015fikli\u011finden sonra 60 g\u00fcnl\u00fck bir kilit devreye girer. H\u00fck\u00fcmlerin tamam\u0131 <a href=\"https:\/\/www.icann.org\/en\/contracted-parties\/accredited-registrars\/transfer-policy-01-06-2016-en\" title=\"ICANN Transfer Politikas\u0131 \u2014 resm\u00ee metin\" target=\"_blank\" rel=\"noopener\">ICANN Transfer Politikas\u0131<\/a> metninde yer al\u0131r.<\/p>\n<p><strong>Transfer kilidi kapal\u0131 olmal\u0131:<\/strong> Kay\u0131t kurulu\u015flar\u0131 alan ad\u0131n\u0131 varsay\u0131lan olarak <code>clientTransferProhibited<\/code> durumunda tutar. Bu kilit izinsiz transferleri engellemek i\u00e7indir ve panelden kapat\u0131l\u0131r. Kilidin a\u00e7\u0131k olup olmad\u0131\u011f\u0131n\u0131 <a href=\"https:\/\/narhost.com\/blog\/whois-bilgisi-nasil-sorgulanir\/\" title=\"WHOIS bilgisi nas\u0131l sorgulan\u0131r \u2014 kilit ve ileti\u015fim kayd\u0131 kontrol\u00fc\">WHOIS sorgusuyla<\/a> kendiniz g\u00f6rebilirsiniz.<\/p>\n<p><strong>WHOIS e-postas\u0131 eri\u015filebilir olmal\u0131:<\/strong> Onay ba\u011flant\u0131s\u0131 bu adrese gider. Adres kapanm\u0131\u015fsa, \u00fcstelik ta\u015f\u0131nacak alan ad\u0131n\u0131n kendi e-postas\u0131ysa ve posta hizmeti \u00e7al\u0131\u015fm\u0131yorsa onay hi\u00e7bir zaman elinize ge\u00e7mez. Bu adresi transferden \u00f6nce g\u00fcncellemek gerekir \u2014 ama g\u00fcncellemenin 60 g\u00fcnl\u00fck kilidi tetikleyebilece\u011fini hesaba kat\u0131n.<\/p>\n<div class=\"warn-box\">\n<p class=\"label\">Dikkat<\/p>\n<p>S\u00fcresi dolmu\u015f ya da kurtarma (redemption) d\u00f6neminde olan bir alan ad\u0131 transfer edilemez. \u00d6nce eski kurulu\u015fta yenilenir, ard\u0131ndan ta\u015f\u0131n\u0131r. Kurtarma d\u00f6neminde geri alma bedeli normal yenilemenin epey \u00fczerine \u00e7\u0131kabildi\u011fi i\u00e7in, biti\u015f tarihini beklemeden hareket etmek en ucuz yoldur.<\/p>\n<\/div>\n<h2>EPP kodu nas\u0131l al\u0131n\u0131r?<\/h2>\n<p>EPP kodu \u2014 auth kodu ya da transfer \u015fifresi olarak da ge\u00e7er \u2014 alan ad\u0131n\u0131n ta\u015f\u0131nmas\u0131n\u0131 yetkilendiren tek kullan\u0131ml\u0131k bir anahtard\u0131r. Eski kay\u0131t kurulu\u015funun m\u00fc\u015fteri panelinde alan ad\u0131 detay\u0131na girilir ve &#8220;transfer kodu al&#8221; benzeri bir ba\u011flant\u0131dan istenir. Kod ya ekranda g\u00f6sterilir ya da WHOIS&#8217;teki y\u00f6netici adresine g\u00f6nderilir.<\/p>\n<p>Kod b\u00fcy\u00fck-k\u00fc\u00e7\u00fck harf duyarl\u0131d\u0131r ve \u00f6zel karakter i\u00e7erir. Kopyalarken ba\u015f\u0131na veya sonuna bo\u015fluk almamaya dikkat edin; yeni kurulu\u015fa yap\u0131\u015ft\u0131rd\u0131\u011f\u0131n\u0131zda &#8220;ge\u00e7ersiz kod&#8221; uyar\u0131s\u0131 al\u0131yorsan\u0131z ilk bak\u0131lacak yer buras\u0131d\u0131r. Kodun nas\u0131l \u00fcretildi\u011fini ve neden tek kullan\u0131ml\u0131k oldu\u011funu <a href=\"https:\/\/narhost.com\/blog\/epp-kodu-nedir\/\" title=\"EPP kodu nedir, nas\u0131l al\u0131n\u0131r\">EPP kodu yaz\u0131m\u0131zda<\/a> ayr\u0131nt\u0131land\u0131rd\u0131k.<\/p>\n<p>Baz\u0131 kurulu\u015flar kodu vermeden \u00f6nce kimlik do\u011frulamas\u0131 ister ya da destek talebi a\u00e7man\u0131z\u0131 bekler. Do\u011frulama me\u015frudur, oyalama de\u011fildir; kodun makul bir s\u00fcre i\u00e7inde verilmesi beklenir. Talebinizi ba\u015ftan yaz\u0131l\u0131 olarak kayda ge\u00e7irin.<\/p>\n<h2>Transfer nas\u0131l ba\u015flat\u0131l\u0131r ve onay e-postas\u0131 ne yapar?<\/h2>\n<p>Yeni kay\u0131t kurulu\u015funda transfer sipari\u015fi olu\u015fturulur, alan ad\u0131 ile EPP kodu girilir. \u00d6deme al\u0131nd\u0131ktan sonra talep kay\u0131t veritaban\u0131na d\u00fc\u015fer ve alan ad\u0131 <code>pendingTransfer<\/code> durumuna ge\u00e7er.<\/p>\n<p>Bu noktada iki taraf devreye girer. Yeni kurulu\u015f kay\u0131t sahibinden yetkilendirme al\u0131r. Eski kurulu\u015f ise WHOIS&#8217;teki y\u00f6netici adresine bir onay e-postas\u0131 g\u00f6nderir. O e-postadaki ba\u011flant\u0131ya t\u0131klay\u0131p onay verirseniz i\u015flem hemen tamamlan\u0131r. Hi\u00e7bir \u015fey yapmazsan\u0131z gTLD taraf\u0131nda be\u015finci g\u00fcn\u00fcn sonunda talep kendili\u011finden ge\u00e7er. Eski kurulu\u015f ge\u00e7erli bir gerek\u00e7eyle reddederse i\u015flem iptal olur ve gerek\u00e7e size bildirilir.<\/p>\n<div class=\"senaryo-block\">\n<p class=\"label\">\u00d6rnek senaryo<\/p>\n<p>Bir mimarl\u0131k ofisi alan ad\u0131n\u0131 ve hostingini iki ayr\u0131 firmadan al\u0131yordu. Alan ad\u0131n\u0131 hosting sa\u011flay\u0131c\u0131s\u0131na ta\u015f\u0131maya karar verdiler. \u00d6nce WHOIS&#8217;ten kilidin durumunu g\u00f6rd\u00fcler, y\u00f6netici e-postas\u0131n\u0131 ofisin kurumsal adresiyle g\u00fcncellediler ve 60 g\u00fcn\u00fc beklediler. Sonra EPP kodunu al\u0131p talebi ba\u015flatt\u0131lar. Onay e-postas\u0131 ayn\u0131 g\u00fcn geldi, ba\u011flant\u0131ya t\u0131kland\u0131, i\u015flem birka\u00e7 saatte bitti. Nameserver kay\u0131tlar\u0131 ayn\u0131 kald\u0131\u011f\u0131 i\u00e7in site de posta da hi\u00e7 kesilmedi.<\/p>\n<\/div>\n<figure class=\"nh-sema\"><img loading=\"lazy\" src=\"https:\/\/narhost.com\/blog\/wp-content\/uploads\/2026\/09\/domain-transfer-sureci-nasil-isler-sema-narhost.webp\" alt=\"Domain transfer s\u00fcreci ak\u0131\u015f \u015femas\u0131 \u2014 \u015fart kontrol\u00fc, EPP kodu, talep ve onay ad\u0131mlar\u0131\" width=\"1200\" height=\"500\" loading=\"lazy\" decoding=\"async\"><figcaption>Domain transfer s\u00fcreci d\u00f6rt ad\u0131mda: \u015fartlar\u0131 do\u011frula, EPP kodunu al, talebi ba\u015flat, onay e-postas\u0131n\u0131 yan\u0131tla.<\/figcaption><\/figure>\n<h2>A\u015fama a\u015fama domain transfer s\u00fcreci ve tipik s\u00fcreler<\/h2>\n<table>\n<thead>\n<tr>\n<th>A\u015fama<\/th>\n<th>Kimde<\/th>\n<th>Tipik s\u00fcre<\/th>\n<th>Dikkat edilecek<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>\u015eartlar\u0131n kontrol\u00fc<\/td>\n<td>Sizde<\/td>\n<td>10-20 dakika<\/td>\n<td>60 g\u00fcn kural\u0131, kilit durumu, WHOIS e-postas\u0131<\/td>\n<\/tr>\n<tr>\n<td>EPP kodunun al\u0131nmas\u0131<\/td>\n<td>Eski kay\u0131t kurulu\u015fu<\/td>\n<td>An\u0131nda &#8211; 1 i\u015f g\u00fcn\u00fc<\/td>\n<td>Kod tek kullan\u0131ml\u0131k, bo\u015fluksuz kopyalanmal\u0131<\/td>\n<\/tr>\n<tr>\n<td>Talebin ba\u015flat\u0131lmas\u0131<\/td>\n<td>Yeni kay\u0131t kurulu\u015fu<\/td>\n<td>Dakikalar<\/td>\n<td>\u00d6deme tamamlanmadan talep d\u00fc\u015fmez<\/td>\n<\/tr>\n<tr>\n<td>Onay e-postas\u0131<\/td>\n<td>Sizde<\/td>\n<td>Hemen &#8211; 5 g\u00fcn<\/td>\n<td>Onaylamazsan\u0131z 5. g\u00fcn\u00fcn sonunda otomatik ge\u00e7er<\/td>\n<\/tr>\n<tr>\n<td>Kay\u0131tlar\u0131n oturmas\u0131<\/td>\n<td>Kay\u0131t veritaban\u0131<\/td>\n<td>Birka\u00e7 saat<\/td>\n<td>WHOIS&#8217;te yeni kurulu\u015fun ad\u0131 g\u00f6r\u00fcn\u00fcr<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Tabloyu tek c\u00fcmleye indirirsek: haz\u0131rl\u0131k sizde, bekleme s\u00fcresi ise onay davran\u0131\u015f\u0131n\u0131za ba\u011fl\u0131. Onay ba\u011flant\u0131s\u0131na ayn\u0131 g\u00fcn t\u0131klayan biri i\u015fi saatler i\u00e7inde bitirir, e-postay\u0131 fark etmeyen biri be\u015f g\u00fcn bekler.<\/p>\n<h2>.tr uzant\u0131lar\u0131nda s\u00fcre\u00e7 neden farkl\u0131 i\u015fler?<\/h2>\n<p>.tr ailesi ICANN&#8217;in gTLD kurallar\u0131na de\u011fil, T\u00fcrkiye&#8217;de <a href=\"https:\/\/www.trabis.gov.tr\/\" title=\"TRAB\u0130S \u2014 .tr A\u011f Bilgi Sistemi resm\u00ee sitesi\" target=\"_blank\" rel=\"noopener\">TRAB\u0130S<\/a> taraf\u0131ndan y\u00fcr\u00fct\u00fclen d\u00fczenlemelere tabidir. Bu y\u00fczden gTLD al\u0131\u015fkanl\u0131klar\u0131n\u0131 oldu\u011fu gibi ta\u015f\u0131mak yan\u0131lt\u0131r.<\/p>\n<p>En g\u00f6r\u00fcn\u00fcr fark, gTLD&#8217;deki EPP kodu mant\u0131\u011f\u0131n\u0131n ayn\u0131 \u015fekilde i\u015flememesidir. .tr taraf\u0131nda i\u015flem &#8220;kay\u0131t kurulu\u015fu de\u011fi\u015fikli\u011fi&#8221; olarak adland\u0131r\u0131l\u0131r ve alan ad\u0131 y\u00f6netim paneli \u00fczerinden, kay\u0131t sahibinin kimli\u011fi do\u011frulanarak y\u00fcr\u00fct\u00fcl\u00fcr. 60 g\u00fcnl\u00fck ICANN kilidi de burada ge\u00e7erli de\u011fildir; s\u00fcreler ve \u015fartlar TRAB\u0130S taraf\u0131nda ayr\u0131ca tan\u0131mlan\u0131r.<\/p>\n<p>Belgeli ve belgesiz .tr kay\u0131tlar\u0131n\u0131n \u015fartlar\u0131 da birbirinden ayr\u0131l\u0131r. Uzant\u0131 se\u00e7iminin bu taraf\u0131n\u0131 <a href=\"https:\/\/narhost.com\/blog\/ulke-domain-uzantilari-nedir\/\" title=\"\u00dclke domain uzant\u0131lar\u0131 nedir, .tr ailesi nas\u0131l i\u015fler\">\u00fclke domain uzant\u0131lar\u0131 yaz\u0131m\u0131zda<\/a> ele ald\u0131k. Belgesiz .com.tr kayd\u0131 ve y\u00f6netimi i\u00e7in <a href=\"https:\/\/narhost.com\/belgesiz-tr-domain\" title=\"Belgesiz .com.tr alan ad\u0131 kayd\u0131\">belgesiz .tr sayfas\u0131na<\/a> bakabilirsiniz.<\/p>\n<h2>Transfer s\u0131ras\u0131nda site ve e-postalar kesilir mi?<\/h2>\n<p>Hay\u0131r \u2014 transfer bir kay\u0131t kurulu\u015fu de\u011fi\u015fikli\u011fidir, hosting de\u011fi\u015fikli\u011fi de\u011fil. Nameserver kay\u0131tlar\u0131 alan ad\u0131yla birlikte ta\u015f\u0131n\u0131r, DNS b\u00f6lgeniz nerede duruyorsa orada durmaya devam eder. Site de e-posta da \u00e7al\u0131\u015fmay\u0131 s\u00fcrd\u00fcr\u00fcr.<\/p>\n<p>Kesinti i\u015flemin kendisinden de\u011fil, \u00e7evresindeki yanl\u0131\u015f varsay\u0131mlardan do\u011far. Eski firma DNS b\u00f6lgesini kendi sunucusunda bar\u0131nd\u0131r\u0131yorsa ve transferden sonra hizmeti kapat\u0131rsa nameserver&#8217;lar cevap veremez h\u00e2le gelir. Ayn\u0131 \u015fekilde posta hizmeti eski firmadaysa, MX kay\u0131tlar\u0131 art\u0131k bo\u015flu\u011fa i\u015faret ediyor demektir.<\/p>\n<div class=\"warn-box\">\n<p class=\"label\">Dikkat<\/p>\n<p>\u0130\u015flemden \u00f6nce mevcut DNS b\u00f6lgenizin tam bir kopyas\u0131n\u0131 \u00e7\u0131kar\u0131n: A, CNAME, MX, TXT (SPF, DKIM, DMARC) ve varsa SRV kay\u0131tlar\u0131. Bu kay\u0131tlar\u0131 yeni tarafta haz\u0131r edin, TTL de\u011ferlerini bir g\u00fcn \u00f6nceden d\u00fc\u015f\u00fcr\u00fcn. B\u00f6ylece bir aksilik \u00e7\u0131karsa geri d\u00f6n\u00fc\u015f dakikalar s\u00fcrer, saatler de\u011fil. Kurumsal posta taraf\u0131n\u0131 <a href=\"https:\/\/narhost.com\/blog\/sirket-e-posta-olusturma\/\" title=\"\u015eirket e-postas\u0131 olu\u015fturma ve MX kay\u0131tlar\u0131\">\u015firket e-postas\u0131 yaz\u0131m\u0131zda<\/a> anlatt\u0131k.<\/p>\n<\/div>\n<h2>Transfer neden ba\u015far\u0131s\u0131z olur?<\/h2>\n<p>Reddedilen taleplerin sebepleri birka\u00e7 ba\u015fl\u0131kta toplan\u0131r: alan ad\u0131 kilitli b\u0131rak\u0131lm\u0131\u015ft\u0131r, EPP kodu hatal\u0131 ya da s\u00fcresi ge\u00e7mi\u015ftir, 60 g\u00fcnl\u00fck kural dolmam\u0131\u015ft\u0131r, WHOIS&#8217;teki y\u00f6netici adresi eri\u015filemez durumdad\u0131r, alan ad\u0131n\u0131n s\u00fcresi dolmu\u015f ya da kurtarma d\u00f6nemine girmi\u015ftir, alan ad\u0131 hakk\u0131nda a\u00e7\u0131k bir uyu\u015fmazl\u0131k vard\u0131r ya da eski kurulu\u015fta \u00f6denmemi\u015f bir bakiye bulunmaktad\u0131r.<\/p>\n<p>Talep reddedilirse alan ad\u0131 eski kurulu\u015fta kal\u0131r, kaybolmaz. Sebep giderildikten sonra yeniden ba\u015flat\u0131l\u0131r. Reddedilen bir talebin \u00f6demesinin ne olaca\u011f\u0131 yeni kurulu\u015fun iade ko\u015fullar\u0131na ba\u011fl\u0131d\u0131r; sipari\u015fi vermeden \u00f6nce bu ko\u015fulu okuyun.<\/p>\n<h2>Transfer \u00f6ncesi kontrol listesi<\/h2>\n<ul class=\"kontrol-listesi\">\n<li>WHOIS sorgusu \u00e7ekin; kilit durumunu ve y\u00f6netici e-posta adresini do\u011frulay\u0131n.<\/li>\n<li>Kay\u0131t ya da son transfer tarihinin \u00fczerinden 60 g\u00fcn ge\u00e7ti\u011fini kontrol edin.<\/li>\n<li>Y\u00f6netici e-posta adresine ger\u00e7ekten eri\u015febildi\u011finizi test edin, gerekirse \u00f6nce g\u00fcncelleyin.<\/li>\n<li>Mevcut DNS b\u00f6lgesinin tamam\u0131n\u0131 d\u0131\u015fa aktar\u0131n: A, CNAME, MX, TXT ve SRV kay\u0131tlar\u0131.<\/li>\n<li>TTL de\u011ferlerini i\u015flemden bir g\u00fcn \u00f6nce d\u00fc\u015f\u00fcr\u00fcn.<\/li>\n<li>Alan ad\u0131n\u0131n biti\u015f tarihini not edin; kurtarma d\u00f6nemine yak\u0131nsa \u00f6nce yenileyin.<\/li>\n<li>EPP kodunu al\u0131n ve bo\u015fluksuz kopyalad\u0131\u011f\u0131n\u0131zdan emin olun.<\/li>\n<li>Talebi ba\u015flatt\u0131ktan sonra onay e-postas\u0131n\u0131 be\u015f g\u00fcn boyunca takip edin.<\/li>\n<\/ul>\n<div class=\"success-box\">\n<p class=\"label\">Sonu\u00e7<\/p>\n<p>Domain transfer s\u00fcreci teknik olarak k\u0131sad\u0131r; as\u0131l i\u015f haz\u0131rl\u0131kta biter. Kilit kapal\u0131, WHOIS adresi eri\u015filebilir ve DNS kay\u0131tlar\u0131 yeni tarafta haz\u0131rsa i\u015flem \u00e7o\u011funlukla ayn\u0131 g\u00fcn tamamlan\u0131r, hi\u00e7bir hizmet kesintiye u\u011framaz. .tr uzant\u0131lar\u0131nda ise gTLD kurallar\u0131n\u0131 de\u011fil TRAB\u0130S i\u015fleyi\u015fini esas al\u0131n.<\/p>\n<\/div>\n<div class=\"kb-faq\">\n<h2>S\u0131k\u00e7a sorulan sorular<\/h2>\n<h3>Domain transfer s\u00fcreci ne kadar s\u00fcrer?<\/h3>\n<p>Onay e-postas\u0131ndaki ba\u011flant\u0131ya t\u0131klarsan\u0131z i\u015flem genelde birka\u00e7 saat i\u00e7inde biter. Hi\u00e7bir \u015fey yapmazsan\u0131z gTLD uzant\u0131larda talep be\u015finci g\u00fcn\u00fcn sonunda kendili\u011finden tamamlan\u0131r. Kay\u0131t veritaban\u0131ndaki de\u011fi\u015fikli\u011fin WHOIS \u00e7\u0131kt\u0131s\u0131na yans\u0131mas\u0131 birka\u00e7 saat daha alabilir.<\/p>\n<h3>Transferden sonra alan ad\u0131m\u0131n s\u00fcresi s\u0131f\u0131rlan\u0131r m\u0131?<\/h3>\n<p>Hay\u0131r. Mevcut biti\u015f tarihinizin \u00fczerine genelde bir y\u0131l eklenir. Kay\u0131t tarihi ve alan ad\u0131n\u0131n ya\u015f\u0131 de\u011fi\u015fmez, dolay\u0131s\u0131yla arama motorlar\u0131 taraf\u0131nda bir kay\u0131p olu\u015fmaz.<\/p>\n<h3>EPP kodunu vermezlerse ne yapabilirim?<\/h3>\n<p>Kod, alan ad\u0131 sahibinin hakk\u0131d\u0131r ve makul s\u00fcrede verilmesi beklenir. Talebinizi destek kayd\u0131 \u00fczerinden yaz\u0131l\u0131 olarak iletin; yan\u0131ts\u0131z kal\u0131rsa kay\u0131t kurulu\u015funun akreditasyonunu veren kuruma \u015fik\u00e2yet yolu a\u00e7\u0131kt\u0131r. S\u00f6zl\u00fc taleplerin izi kalmad\u0131\u011f\u0131 i\u00e7in her ad\u0131m\u0131 yaz\u0131l\u0131 y\u00fcr\u00fct\u00fcn.<\/p>\n<h3>S\u00fcresi dolmu\u015f alan ad\u0131 ta\u015f\u0131nabilir mi?<\/h3>\n<p>Hay\u0131r. S\u00fcresi dolan alan ad\u0131 \u00f6nce eski kay\u0131t kurulu\u015funda yenilenir, sonra ta\u015f\u0131n\u0131r. Kurtarma d\u00f6nemine girmi\u015fse geri alma bedeli normal yenilemenin epey \u00fczerinde olabilir; bu y\u00fczden biti\u015f tarihini beklemeden hareket etmek gerekir.<\/p>\n<h3>\u0130\u015flem s\u0131ras\u0131nda e-postalar\u0131m kaybolur mu?<\/h3>\n<p>Kay\u0131t kurulu\u015fu de\u011fi\u015fikli\u011fi MX kay\u0131tlar\u0131na dokunmaz. Posta hizmeti eski firmadaysa ve o hizmet kapat\u0131l\u0131rsa e-posta ak\u0131\u015f\u0131 durur. Bu y\u00fczden posta kutular\u0131n\u0131n nerede duraca\u011f\u0131na \u00f6nceden karar verip MX kay\u0131tlar\u0131n\u0131 haz\u0131rlamak gerekir.<\/p>\n<\/div>\n<div class=\"cta-box\">\n<p class=\"label\">Narhost&#8217;ta<\/p>\n<p>Alan ad\u0131 sorgulama, kay\u0131t ve transfer i\u015flemlerini tek panelden y\u00fcr\u00fctebilir, hosting ile alan ad\u0131n\u0131z\u0131 ayn\u0131 yerde toplayabilirsiniz.<\/p>\n<p><a class=\"cta-btn\" href=\"https:\/\/narhost.com\/domain-kaydi\" title=\"Narhost alan ad\u0131 sorgulama, kay\u0131t ve transfer\">Alan ad\u0131 i\u015flemlerine git<\/a><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Domain transfer s\u00fcreci, alan ad\u0131n\u0131n kay\u0131t hakk\u0131n\u0131n bir kurulu\u015ftan di\u011ferine ge\u00e7mesidir. 60 g\u00fcn kural\u0131, transfer kilidi, EPP kodu, onay e-postas\u0131, .tr uzant\u0131lar\u0131ndaki farkl\u0131 i\u015fleyi\u015f ve DNS ile MX kay\u0131tlar\u0131n\u0131n \u00f6nceden haz\u0131rlanmas\u0131 ad\u0131m ad\u0131m anlat\u0131l\u0131yor.<\/p>\n","protected":false},"author":1,"featured_media":2286,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[18],"tags":[],"class_list":["post-458","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-domain"],"_links":{"self":[{"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/posts\/458","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/comments?post=458"}],"version-history":[{"count":3,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/posts\/458\/revisions"}],"predecessor-version":[{"id":2285,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/posts\/458\/revisions\/2285"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/media\/2286"}],"wp:attachment":[{"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/media?parent=458"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/categories?post=458"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/tags?post=458"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}