{"id":3749,"date":"2025-12-30T18:51:05","date_gmt":"2025-12-30T15:51:05","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/alan-adi-guvenligi-rehberi-registry-lock-transfer-kilidi-ve-yetkisiz-degisiklikleri-onlemek\/"},"modified":"2025-12-30T18:51:05","modified_gmt":"2025-12-30T15:51:05","slug":"alan-adi-guvenligi-rehberi-registry-lock-transfer-kilidi-ve-yetkisiz-degisiklikleri-onlemek","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/alan-adi-guvenligi-rehberi-registry-lock-transfer-kilidi-ve-yetkisiz-degisiklikleri-onlemek\/","title":{"rendered":"Alan Ad\u0131 G\u00fcvenli\u011fi Rehberi: Registry Lock, Transfer Kilidi ve Yetkisiz De\u011fi\u015fiklikleri \u00d6nlemek"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><div id=\"toc_container\" class=\"toc_transparent no_bullets\"><p class=\"toc_title\">\u0130&ccedil;indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#Alan_adi_guvenligi_neden_kritik_bir_is_varligi_konusu\"><span class=\"toc_number toc_depth_1\">1<\/span> Alan ad\u0131 g\u00fcvenli\u011fi neden kritik bir i\u015f varl\u0131\u011f\u0131 konusu?<\/a><\/li><li><a href=\"#Tehdit_modeli_Alan_adiniza_gercekte_ne_olabilir\"><span class=\"toc_number toc_depth_1\">2<\/span> Tehdit modeli: Alan ad\u0131n\u0131za ger\u00e7ekte ne olabilir?<\/a><\/li><li><a href=\"#Registry_lock_nedir_registrar_locktan_farki_ne\"><span class=\"toc_number toc_depth_1\">3<\/span> Registry lock nedir, registrar lock\u2019tan fark\u0131 ne?<\/a><ul><li><a href=\"#Registry_registrar_ve_domain_sahibi_iliskisi\"><span class=\"toc_number toc_depth_2\">3.1<\/span> Registry, registrar ve domain sahibi ili\u015fkisi<\/a><\/li><li><a href=\"#Registry_lock_nedir\"><span class=\"toc_number toc_depth_2\">3.2<\/span> Registry lock nedir?<\/a><\/li><li><a href=\"#Registry_lockin_tipik_ozellikleri\"><span class=\"toc_number toc_depth_2\">3.3<\/span> Registry lock\u2019\u0131n tipik \u00f6zellikleri<\/a><\/li><li><a href=\"#Registrar_lock_transfer_kilidi_nedir\"><span class=\"toc_number toc_depth_2\">3.4<\/span> Registrar lock (transfer kilidi) nedir?<\/a><\/li><li><a href=\"#Registry_lock_ve_registrar_lock_farklarini_ozetleyelim\"><span class=\"toc_number toc_depth_2\">3.5<\/span> Registry lock ve registrar lock farklar\u0131n\u0131 \u00f6zetleyelim<\/a><\/li><\/ul><\/li><li><a href=\"#Hangi_durumlarda_registry_lock_kullanmalisiniz\"><span class=\"toc_number toc_depth_1\">4<\/span> Hangi durumlarda registry lock kullanmal\u0131s\u0131n\u0131z?<\/a><\/li><li><a href=\"#Transfer_kilidi_registrar_lock_ve_EPP_kodu_yonetimi\"><span class=\"toc_number toc_depth_1\">5<\/span> Transfer kilidi (registrar lock) ve EPP kodu y\u00f6netimi<\/a><ul><li><a href=\"#Transfer_kilidi_nasil_calisir\"><span class=\"toc_number toc_depth_2\">5.1<\/span> Transfer kilidi nas\u0131l \u00e7al\u0131\u015f\u0131r?<\/a><\/li><li><a href=\"#EPP_kodu_yetki_kodu_guvenligi\"><span class=\"toc_number toc_depth_2\">5.2<\/span> EPP kodu (yetki kodu) g\u00fcvenli\u011fi<\/a><\/li><\/ul><\/li><li><a href=\"#Yetkisiz_degisiklikleri_onlemek_icin_pratik_stratejiler\"><span class=\"toc_number toc_depth_1\">6<\/span> Yetkisiz de\u011fi\u015fiklikleri \u00f6nlemek i\u00e7in pratik stratejiler<\/a><ul><li><a href=\"#1_Domain_paneli_hesabinizi_saglamlastirin\"><span class=\"toc_number toc_depth_2\">6.1<\/span> 1. Domain paneli hesab\u0131n\u0131z\u0131 sa\u011flamla\u015ft\u0131r\u0131n<\/a><\/li><li><a href=\"#2_Rol_ve_yetki_tasarimi_yapin\"><span class=\"toc_number toc_depth_2\">6.2<\/span> 2. Rol ve yetki tasar\u0131m\u0131 yap\u0131n<\/a><\/li><li><a href=\"#3_Standart_degisiklik_sureci_tanimlayin\"><span class=\"toc_number toc_depth_2\">6.3<\/span> 3. Standart de\u011fi\u015fiklik s\u00fcreci tan\u0131mlay\u0131n<\/a><\/li><li><a href=\"#4_Bildirim_ve_loglari_aktif_kullanin\"><span class=\"toc_number toc_depth_2\">6.4<\/span> 4. Bildirim ve loglar\u0131 aktif kullan\u0131n<\/a><\/li><\/ul><\/li><li><a href=\"#DCHost_tarafinda_registry_lock_ve_transfer_guvenligi_yaklasimimiz\"><span class=\"toc_number toc_depth_1\">7<\/span> DCHost taraf\u0131nda registry lock ve transfer g\u00fcvenli\u011fi yakla\u015f\u0131m\u0131m\u0131z<\/a><ul><li><a href=\"#Transfer_kilidi_ve_EPP_kodu_yonetimi\"><span class=\"toc_number toc_depth_2\">7.1<\/span> Transfer kilidi ve EPP kodu y\u00f6netimi<\/a><\/li><li><a href=\"#Registry_lock_talepleri\"><span class=\"toc_number toc_depth_2\">7.2<\/span> Registry lock talepleri<\/a><\/li><\/ul><\/li><li><a href=\"#Alan_adi_guvenligini_diger_katmanlarla_birlestirmek\"><span class=\"toc_number toc_depth_1\">8<\/span> Alan ad\u0131 g\u00fcvenli\u011fini di\u011fer katmanlarla birle\u015ftirmek<\/a><\/li><li><a href=\"#Kurum_ici_politika_ve_kontrol_listesi\"><span class=\"toc_number toc_depth_1\">9<\/span> Kurum i\u00e7i politika ve kontrol listesi<\/a><ul><li><a href=\"#Alan_adi_guvenligi_kontrol_listesi\"><span class=\"toc_number toc_depth_2\">9.1<\/span> Alan ad\u0131 g\u00fcvenli\u011fi kontrol listesi<\/a><\/li><\/ul><\/li><li><a href=\"#Sonuc_Registry_lock_transfer_kilidi_ve_saglam_sureclerle_alan_adinizi_gercekten_koruyun\"><span class=\"toc_number toc_depth_1\">10<\/span> Sonu\u00e7: Registry lock, transfer kilidi ve sa\u011flam s\u00fcre\u00e7lerle alan ad\u0131n\u0131z\u0131 ger\u00e7ekten koruyun<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Alan_adi_guvenligi_neden_kritik_bir_is_varligi_konusu\">Alan ad\u0131 g\u00fcvenli\u011fi neden kritik bir i\u015f varl\u0131\u011f\u0131 konusu?<\/span><\/h2>\n<p>Alan ad\u0131n\u0131z, markan\u0131z\u0131n internetteki en kritik varl\u0131klar\u0131ndan biri. Web siteniz, e-posta adresleriniz, API u\u00e7lar\u0131n\u0131z, hatta baz\u0131 entegrasyonlar\u0131n\u0131z do\u011frudan bu alan ad\u0131na ba\u011fl\u0131. Yani bir sald\u0131rgan alan ad\u0131n\u0131z\u0131 ele ge\u00e7irdi\u011finde, asl\u0131nda web sitenizi hacklemeden de t\u00fcm trafi\u011fi kendi altyap\u0131s\u0131na y\u00f6nlendirebilir, e-posta kutular\u0131n\u0131z\u0131 taklit edebilir veya SEO itibar\u0131n\u0131z\u0131 k\u0131sa s\u00fcrede yok edebilir.<\/p>\n<p>G\u00fcvenlik denetimleri yapt\u0131\u011f\u0131m\u0131z pek \u00e7ok projede, sunucu taraf\u0131nda son derece s\u0131k\u0131 \u00f6nlemler al\u0131nd\u0131\u011f\u0131 h\u00e2lde alan ad\u0131 taraf\u0131n\u0131n neredeyse hi\u00e7 d\u00fc\u015f\u00fcn\u00fclmedi\u011fini g\u00f6r\u00fcyoruz. Oysa basit bir yetkisiz transfer, yanl\u0131\u015fl\u0131kla a\u00e7\u0131lm\u0131\u015f bir DNS kayd\u0131 d\u00fczenleme yetkisi veya ele ge\u00e7irilmi\u015f bir domain paneli; en iyi yap\u0131land\u0131r\u0131lm\u0131\u015f VPS, dedicated veya colocation altyap\u0131s\u0131n\u0131 bile tek hamlede devre d\u0131\u015f\u0131 b\u0131rakabilir.<\/p>\n<p>Bu rehberde, \u00f6zellikle \u00fc\u00e7 kilit mekanizmaya odaklanaca\u011f\u0131z: <strong>registry lock<\/strong>, <strong>transfer kilidi (registrar lock)<\/strong> ve <strong>yetkisiz de\u011fi\u015fiklikleri \u00f6nlemeye y\u00f6nelik pratik s\u00fcre\u00e7ler<\/strong>. Hedefimiz; teknik seviyeniz ne olursa olsun, alan ad\u0131 g\u00fcvenli\u011finizi sistematik bir \u015fekilde g\u00fc\u00e7lendirebilmeniz ve DCHost \u00fczerinde y\u00f6netti\u011finiz domainleri daha g\u00fcvenle kullanabilmeniz.<\/p>\n<h2><span id=\"Tehdit_modeli_Alan_adiniza_gercekte_ne_olabilir\">Tehdit modeli: Alan ad\u0131n\u0131za ger\u00e7ekte ne olabilir?<\/span><\/h2>\n<p>Sa\u011flam bir alan ad\u0131 g\u00fcvenli\u011fi stratejisi kurman\u0131n ilk ad\u0131m\u0131, neye kar\u015f\u0131 korundu\u011funuzu netle\u015ftirmektir. DCHost taraf\u0131nda sahada g\u00f6rd\u00fc\u011f\u00fcm\u00fcz tipik riskler \u015f\u00f6yle \u00f6zetlenebilir:<\/p>\n<ul>\n<li><strong>Yetkisiz transfer (domain hijacking):<\/strong> Sald\u0131rgan, alan ad\u0131n\u0131z\u0131 r\u0131zan\u0131z d\u0131\u015f\u0131nda ba\u015fka bir kay\u0131t operat\u00f6r\u00fcne (registrar) ta\u015f\u0131r, siz fark etti\u011finizde i\u015f i\u015ften ge\u00e7mi\u015f olur.<\/li>\n<li><strong>DNS kay\u0131tlar\u0131n\u0131n de\u011fi\u015ftirilmesi:<\/strong> Nameserver veya A\/MX\/TXT kay\u0131tlar\u0131 de\u011fi\u015ftirilerek trafi\u011finiz sald\u0131rgan\u0131n sunucular\u0131na y\u00f6nlendirilir. Bu, phishing, k\u00f6t\u00fc ama\u00e7l\u0131 yaz\u0131l\u0131m yayma veya e-posta ele ge\u00e7irme i\u00e7in kullan\u0131l\u0131r.<\/li>\n<li><strong>Alan ad\u0131n\u0131n silinmesi veya s\u00fcresinin bilerek uzat\u0131lmamas\u0131:<\/strong> Domain kas\u0131tl\u0131 olarak silinir ya da yenileme yap\u0131lmayarak d\u00fc\u015f\u00fcr\u00fcl\u00fcr; ard\u0131ndan \u00fc\u00e7\u00fcnc\u00fc taraflar taraf\u0131ndan yeniden kaydedilir.<\/li>\n<li><strong>Hesap ele ge\u00e7irme:<\/strong> Domain panelinize ait kullan\u0131c\u0131 hesab\u0131 ele ge\u00e7irilir; transfer kilidi kapat\u0131l\u0131r, EPP kodu al\u0131n\u0131r, DNS ayarlar\u0131 de\u011fi\u015ftirilir.<\/li>\n<li><strong>Sosyal m\u00fchendislik:<\/strong> Destek ekibi kand\u0131r\u0131larak, sizmi\u015fsiniz gibi davran\u0131l\u0131r ve alan ad\u0131 \u00fczerinde i\u015flem yap\u0131lmas\u0131 istenir.<\/li>\n<\/ul>\n<p>Bu tehditlerin \u00e7o\u011fu, <strong>do\u011fru kombinasyon<\/strong>daki teknik ve operasyonel kontrollerle ciddi oranda azalt\u0131labilir. DCHost blogunda yay\u0131nlad\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/alan-adi-yasam-dongusu-ve-dusen-domain-yakalama-rehberi\/\">alan ad\u0131 ya\u015fam d\u00f6ng\u00fcs\u00fc ve d\u00fc\u015fen domain yakalama rehberi<\/a> alan ad\u0131n\u0131z\u0131n s\u00fcresi doldu\u011funda neler olabilece\u011fini, <a href=\"https:\/\/www.dchost.com\/blog\/subdomain-takeover-ve-bosta-kalan-dns-kayitlari-cloudflare-ve-cpanel-icin-uygulamali-rehber\/\">subdomain takeover ve bo\u015fta kalan DNS kay\u0131tlar\u0131<\/a> ise DNS taraf\u0131ndaki yap\u0131land\u0131rma hatalar\u0131n\u0131n nas\u0131l istismar edilebilece\u011fini detayl\u0131 anlat\u0131yor. Bu yaz\u0131da ise odak noktam\u0131z: <strong>k\u00f6k seviyede alan ad\u0131n\u0131n kendisini kilitlemek<\/strong>.<\/p>\n<h2><span id=\"Registry_lock_nedir_registrar_locktan_farki_ne\">Registry lock nedir, registrar lock\u2019tan fark\u0131 ne?<\/span><\/h2>\n<p>Alan ad\u0131 g\u00fcvenli\u011fi konu\u015fulurken en \u00e7ok kar\u0131\u015ft\u0131r\u0131lan iki kavram <strong>registry lock<\/strong> ve <strong>registrar lock<\/strong> (transfer kilidi) oluyor. \u0130sim benzerli\u011fi y\u00fcz\u00fcnden ayn\u0131 \u015fey san\u0131lsalar da, asl\u0131nda tamamen farkl\u0131 katmanlarda \u00e7al\u0131\u015fan iki g\u00fcvenlik mekanizmas\u0131d\u0131r.<\/p>\n<h3><span id=\"Registry_registrar_ve_domain_sahibi_iliskisi\">Registry, registrar ve domain sahibi ili\u015fkisi<\/span><\/h3>\n<p>Basit\u00e7e \u00f6zetleyelim:<\/p>\n<ul>\n<li><strong>Registry:<\/strong> \u0130lgili TLD\u2019nin (\u00f6rne\u011fin .com, .net vb.) k\u00f6k veritaban\u0131n\u0131 y\u00f6neten kurum.<\/li>\n<li><strong>Registrar (kay\u0131t operat\u00f6r\u00fc):<\/strong> Bizim gibi, son kullan\u0131c\u0131ya alan ad\u0131n\u0131 satan ve y\u00f6neten firma.<\/li>\n<li><strong>Domain sahibi:<\/strong> Alan ad\u0131n\u0131n hukuki sahibi olan ger\u00e7ek veya t\u00fczel ki\u015fi.<\/li>\n<\/ul>\n<p>Registry lock, <strong>k\u00f6k veritaban\u0131 d\u00fczeyinde<\/strong>; registrar lock ise <strong>registrar aray\u00fcz\u00fc d\u00fczeyinde<\/strong> \u00e7al\u0131\u015fan bir kilit mekanizmas\u0131d\u0131r.<\/p>\n<h3><span id=\"Registry_lock_nedir\">Registry lock nedir?<\/span><\/h3>\n<p><strong>Registry lock<\/strong>, alan ad\u0131n\u0131z\u0131n registry taraf\u0131nda \u201c\u00f6zel kilit\u201d stat\u00fcs\u00fcne al\u0131nmas\u0131d\u0131r. Bu durumda a\u015fa\u011f\u0131daki kritik i\u015flemler, <strong>sadece registry ile \u00f6zel ve ek do\u011frulamal\u0131 bir s\u00fcre\u00e7<\/strong> sonunda yap\u0131labilir:<\/p>\n<ul>\n<li>Alan ad\u0131n\u0131n ba\u015fka bir registrara transfer edilmesi<\/li>\n<li>Nameserver\u2019lar\u0131n de\u011fi\u015ftirilmesi<\/li>\n<li>Alan ad\u0131n\u0131n silinmesi<\/li>\n<li>Alan ad\u0131 \u00fczerinde baz\u0131 kritik alanlar\u0131n g\u00fcncellenmesi<\/li>\n<\/ul>\n<p>Yani varsay\u0131msal en k\u00f6t\u00fc senaryoyu d\u00fc\u015f\u00fcnelim: Registrar hesab\u0131n\u0131z ele ge\u00e7irildi, hatta registrar altyap\u0131s\u0131 bile bir \u015fekilde kompromize oldu. Registry lock aktifse, sald\u0131rgan registry ile ek do\u011frulama s\u00fcrecini ge\u00e7meden bu kritik i\u015flemleri yapamaz.<\/p>\n<h3><span id=\"Registry_lockin_tipik_ozellikleri\">Registry lock\u2019\u0131n tipik \u00f6zellikleri<\/span><\/h3>\n<ul>\n<li><strong>Out-of-band do\u011frulama:<\/strong> Registry lock a\u00e7ma\/kapama veya de\u011fi\u015fiklik talepleri i\u00e7in \u00e7o\u011fu zaman telefonla geri arama, kay\u0131tl\u0131 g\u00fcvenlik sorular\u0131, PGP imzal\u0131 e-posta gibi ek do\u011frulamaya ihtiya\u00e7 duyulur.<\/li>\n<li><strong>Manuel s\u00fcre\u00e7:<\/strong> Ger\u00e7ek bir insan\u0131n onay\u0131 gerekir; bu da otomatik bot sald\u0131r\u0131lar\u0131n\u0131 ciddi \u015fekilde zorla\u015ft\u0131r\u0131r.<\/li>\n<li><strong>Kapsaml\u0131 koruma:<\/strong> Sadece transferi de\u011fil, \u00e7o\u011fu zaman update ve delete i\u015flemlerini de engeller.<\/li>\n<\/ul>\n<p>Registry lock t\u00fcm TLD\u2019ler i\u00e7in zorunlu bir \u00f6zellik de\u011fildir; baz\u0131 uzant\u0131lar destekler, baz\u0131lar\u0131 desteklemez. Kritik alan ad\u0131 portf\u00f6yleri olan m\u00fc\u015fterilerimizde, destekleyen TLD\u2019ler i\u00e7in registry lock kullan\u0131lmas\u0131n\u0131 net \u015fekilde \u00f6neriyoruz.<\/p>\n<h3><span id=\"Registrar_lock_transfer_kilidi_nedir\">Registrar lock (transfer kilidi) nedir?<\/span><\/h3>\n<p><strong>Registrar lock<\/strong> veya panelde s\u0131k\u00e7a g\u00f6rd\u00fc\u011f\u00fcn\u00fcz h\u00e2liyle <strong>transfer kilidi<\/strong>, alan ad\u0131n\u0131z\u0131n ba\u015fka bir registrara transfer edilmesini engelleyen, registrar taraf\u0131nda uygulanan bir EPP stat\u00fcs\u00fcd\u00fcr. \u00c7o\u011fu zaman teknik olarak \u015fu EPP koduyla temsil edilir: <code>clientTransferProhibited<\/code>.<\/p>\n<p>Bu kilit aktifken, alan ad\u0131n\u0131z\u0131n transfer talebi iletilse bile, registry bu talebi reddeder. Transfer yapman\u0131z gerekti\u011finde, \u00f6nce DCHost panelinizden transfer kilidini kapat\u0131rs\u0131n\u0131z; ard\u0131ndan EPP kodunu kullanarak yeni registrara transferi ba\u015flat\u0131rs\u0131n\u0131z.<\/p>\n<p>Burada kritik nokta \u015fu: Registrar lock, <strong>hesab\u0131n\u0131z ele ge\u00e7irilirse sald\u0131rgan taraf\u0131ndan da kapat\u0131labilir<\/strong>. Yani tek ba\u015f\u0131na \u201cson savunma hatt\u0131\u201d de\u011fildir; fakat registry lock desteklenmeyen uzant\u0131larda veya daha hafif g\u00fcvenlik ihtiya\u00e7lar\u0131nda <strong>olmazsa olmaz<\/strong> bir katmand\u0131r.<\/p>\n<h3><span id=\"Registry_lock_ve_registrar_lock_farklarini_ozetleyelim\">Registry lock ve registrar lock farklar\u0131n\u0131 \u00f6zetleyelim<\/span><\/h3>\n<table border=\"1\" cellpadding=\"6\" cellspacing=\"0\">\n<tr>\n<th>\u00d6zellik<\/th>\n<th>Registry Lock<\/th>\n<th>Registrar Lock (Transfer Kilidi)<\/th>\n<\/tr>\n<tr>\n<td>Uygulama katman\u0131<\/td>\n<td>Registry (k\u00f6k veritaban\u0131)<\/td>\n<td>Registrar (DCHost gibi kay\u0131t operat\u00f6r\u00fc)<\/td>\n<\/tr>\n<tr>\n<td>Kim a\u00e7ar\/kapat\u0131r?<\/td>\n<td>Registry ile \u00f6zel s\u00fcre\u00e7, genellikle registrar arac\u0131l\u0131\u011f\u0131yla<\/td>\n<td>Domain sahibi veya yetkili kullan\u0131c\u0131, panel \u00fczerinden<\/td>\n<\/tr>\n<tr>\n<td>Hangi i\u015flemleri engeller?<\/td>\n<td>Transfer, \u00e7o\u011fu zaman update ve delete<\/td>\n<td>Genelde yaln\u0131zca transfer<\/td>\n<\/tr>\n<tr>\n<td>Hesap ele ge\u00e7irilirse?<\/td>\n<td>Ek out-of-band do\u011frulama gerekti\u011finden daha dayan\u0131kl\u0131<\/td>\n<td>Sald\u0131rgan panelden kapatabilir; ek koruma \u015fart<\/td>\n<\/tr>\n<\/table>\n<h2><span id=\"Hangi_durumlarda_registry_lock_kullanmalisiniz\">Hangi durumlarda registry lock kullanmal\u0131s\u0131n\u0131z?<\/span><\/h2>\n<p>Registry lock her domain i\u00e7in \u201czorunlu\u201d de\u011fildir; ancak baz\u0131 senaryolarda ciddi anlamda hayat kurtar\u0131c\u0131 olabilir. DCHost taraf\u0131nda g\u00f6rd\u00fc\u011f\u00fcm\u00fcz ve registry lock tavsiye etti\u011fimiz tipik durumlar \u015f\u00f6yle:<\/p>\n<ul>\n<li><strong>Marka alan adlar\u0131:<\/strong> \u015eirketinizin ana .com veya .com.tr gibi kurumsal alan adlar\u0131, m\u00fc\u015fteri g\u00f6z\u00fcnde markan\u0131z\u0131 temsil eder.<\/li>\n<li><strong>Y\u00fcksek trafik alan projeler:<\/strong> E-ticaret, haber portal\u0131, b\u00fcy\u00fck SaaS \u00fcr\u00fcnleri gibi ciddi gelir \u00fcreten siteler.<\/li>\n<li><strong>Kritik entegrasyonlar\u0131 olan altyap\u0131lar:<\/strong> \u00d6rne\u011fin \u00e7ok say\u0131da API client\u2019\u0131n\u0131n ba\u011fland\u0131\u011f\u0131 merkezi bir alan ad\u0131.<\/li>\n<li><strong>Reg\u00fcle sekt\u00f6rler:<\/strong> Finans, sa\u011fl\u0131k, kamu ve benzeri y\u00fcksek reg\u00fclasyonlu alanlarda hizmet veren projeler.<\/li>\n<li><strong>Alan ad\u0131 sald\u0131r\u0131 ge\u00e7mi\u015fi olan kurumlar:<\/strong> Daha \u00f6nce domain hijacking veya DNS manip\u00fclasyonu ya\u015fam\u0131\u015f i\u015fletmeler.<\/li>\n<\/ul>\n<p>Alan ad\u0131 portf\u00f6y\u00fcn\u00fcz geni\u015fse, hangi domainlerde registry lock kullanman\u0131z gerekti\u011fini belirlemek i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/alan-adi-portfoy-yonetimi-onlarca-domaini-kontrol-altina-alma-rehberi\/\">alan ad\u0131 portf\u00f6y y\u00f6netimi rehberimizdeki<\/a> s\u0131n\u0131fland\u0131rma yakla\u015f\u0131m\u0131n\u0131 kullanabilirsiniz. \u00d6zetle, her domain e\u015fit kritik de\u011fildir; en kritik %10\u201320\u2019lik dilime registry lock gibi ileri seviye korumalar\u0131 uygulamak \u00e7o\u011fu zaman en mant\u0131kl\u0131 stratejidir.<\/p>\n<h2><span id=\"Transfer_kilidi_registrar_lock_ve_EPP_kodu_yonetimi\">Transfer kilidi (registrar lock) ve EPP kodu y\u00f6netimi<\/span><\/h2>\n<p>Registry lock olsa da olmasa da, <strong>transfer kilidi<\/strong> ve <strong>EPP kodu<\/strong> y\u00f6netimi alan ad\u0131 g\u00fcvenli\u011finin temel ta\u015f\u0131d\u0131r. DCHost panelinizde alan ad\u0131 detay\u0131na girdi\u011finizde genellikle \u201cTransfer Kilidi: A\u00e7\u0131k\/Kapal\u0131\u201d \u015feklinde bir anahtar g\u00f6r\u00fcrs\u00fcn\u00fcz; bu anahtar tam da bu EPP stat\u00fcs\u00fcn\u00fc kontrol eder.<\/p>\n<h3><span id=\"Transfer_kilidi_nasil_calisir\">Transfer kilidi nas\u0131l \u00e7al\u0131\u015f\u0131r?<\/span><\/h3>\n<p>Arka planda olanlar, sadele\u015ftirilmi\u015f h\u00e2liyle \u015fu \u015fekildedir:<\/p>\n<ol>\n<li>Transfer kilidi <strong>a\u00e7\u0131ksa<\/strong> (clientTransferProhibited): Ba\u015fka bir registrar sizin alan ad\u0131n\u0131z\u0131 transfer etmek istedi\u011finde, registry bu transfer talebini otomatik olarak reddeder.<\/li>\n<li>Transfer kilidini <strong>kapatt\u0131\u011f\u0131n\u0131zda<\/strong>: EPP stat\u00fcs\u00fc kald\u0131r\u0131l\u0131r, transfer yap\u0131labilir h\u00e2le gelir.<\/li>\n<li>Transfer tamamland\u0131ktan veya iptal edildikten sonra: G\u00fcvenlik i\u00e7in tekrar a\u00e7\u0131lmas\u0131 gerekir.<\/li>\n<\/ol>\n<p>Bu s\u00fcrecin kesintisiz ve g\u00fcvenli \u015fekilde nas\u0131l i\u015fleyece\u011fini detayl\u0131 anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/alan-adi-transferi-nasil-yapilir-epp-kodu-transfer-kilidi-ve-kesintisiz-gecise-sakin-bir-rehber\/\">alan ad\u0131 transfer rehberine<\/a> g\u00f6z atman\u0131zda fayda var. \u00d6zellikle e-posta kesintilerini \u00f6nlemek, DNS yay\u0131l\u0131m\u0131n\u0131 do\u011fru y\u00f6netmek ve SEO etkilerini minimize etmek i\u00e7in oradaki ad\u0131mlar kritik.<\/p>\n<h3><span id=\"EPP_kodu_yetki_kodu_guvenligi\">EPP kodu (yetki kodu) g\u00fcvenli\u011fi<\/span><\/h3>\n<p><strong>EPP kodu<\/strong>, alan ad\u0131n\u0131z\u0131 ba\u015fka bir registrara transfer etmek i\u00e7in kullan\u0131lan, bir nevi \u201ctek kullan\u0131ml\u0131k \u015fifre\u201d gibidir. G\u00fcvenli\u011fi \u00e7o\u011fu zaman hafife al\u0131nsa da \u015fu prensipler hayat kurtar\u0131r:<\/p>\n<ul>\n<li>EPP kodunu asla <strong>\u015fifresiz e-posta<\/strong> ile g\u00f6ndermeyin; en az\u0131ndan \u015fifreli ar\u015fiv, g\u00fcvenli mesajla\u015fma veya parola y\u00f6neticisi kullan\u0131n.<\/li>\n<li>Kodu kopyalay\u0131p \u015firket i\u00e7i wiki, herkesin eri\u015febildi\u011fi notlar gibi ortamlara yap\u0131\u015ft\u0131rmay\u0131n.<\/li>\n<li>Transfer tamamland\u0131ktan sonra m\u00fcmk\u00fcnse <strong>yeni bir EPP kodu<\/strong> \u00fcretin (baz\u0131 sistemler otomatik yapar).<\/li>\n<li>EPP kodu talebi geldi\u011finde, bu talebin <strong>ger\u00e7ek sahibinden<\/strong> geldi\u011fini mutlaka ikinci bir kanal (telefon, kurumsal chat vb.) ile do\u011frulay\u0131n.<\/li>\n<\/ul>\n<p>Transfer kilidinin a\u00e7\u0131k, EPP kodunun ise yaln\u0131zca gerekti\u011finde \u00fcretilip g\u00fcvenle sakland\u0131\u011f\u0131 bir d\u00fczen, pratikte \u00e7o\u011fu yetkisiz transfer vakas\u0131n\u0131 ba\u015ftan keser.<\/p>\n<h2><span id=\"Yetkisiz_degisiklikleri_onlemek_icin_pratik_stratejiler\">Yetkisiz de\u011fi\u015fiklikleri \u00f6nlemek i\u00e7in pratik stratejiler<\/span><\/h2>\n<p>Registry lock ve transfer kilidi kritik, ama tek ba\u015f\u0131na yeterli de\u011fil. Ger\u00e7ek hayatta alan adlar\u0131 en \u00e7ok <strong>hesap ele ge\u00e7irilmesi<\/strong>, <strong>yanl\u0131\u015f yetki payla\u015f\u0131m\u0131<\/strong> ve <strong>s\u00fcreci olmayan de\u011fi\u015fiklik talepleri<\/strong> y\u00fcz\u00fcnden zarar g\u00f6r\u00fcyor. A\u015fa\u011f\u0131daki pratikleri DCHost m\u00fc\u015fterilerimize d\u00fczenli olarak \u00f6neriyoruz.<\/p>\n<h3><span id=\"1_Domain_paneli_hesabinizi_saglamlastirin\">1. Domain paneli hesab\u0131n\u0131z\u0131 sa\u011flamla\u015ft\u0131r\u0131n<\/span><\/h3>\n<ul>\n<li><strong>\u00d6zel e-posta kullan\u0131n:<\/strong> Ki\u015fisel e-posta adresleriniz yerine, sadece domain y\u00f6netimi i\u00e7in kullan\u0131lan kurumsal bir adres (\u00f6r. domains@&#8230;) tercih edin.<\/li>\n<li><strong>G\u00fc\u00e7l\u00fc ve benzersiz parola:<\/strong> Parolay\u0131 ba\u015fka hi\u00e7bir sistemde kullanmay\u0131n, parola y\u00f6neticisiyle y\u00f6netin.<\/li>\n<li><strong>\u0130ki fakt\u00f6rl\u00fc kimlik do\u011frulama (2FA):<\/strong> DCHost hesab\u0131n\u0131zda 2FA a\u00e7\u0131ksa, bunu devreye al\u0131n; de\u011filse, hesab\u0131n\u0131zla ili\u015fkili e-posta hesaplar\u0131 i\u00e7in mutlaka aktif edin.<\/li>\n<li><strong>Oturum ve cihaz kontrol\u00fc:<\/strong> M\u00fcmk\u00fcnse hesab\u0131n\u0131z\u0131 yaln\u0131zca kurumsal cihazlardan ve g\u00fcvenilir a\u011flardan kullan\u0131n.<\/li>\n<\/ul>\n<p>Temel seviye \u00f6nlemler i\u00e7in daha geni\u015f bir \u00e7er\u00e7eve isterseniz, <a href=\"https:\/\/www.dchost.com\/blog\/alan-adi-guvenligi-rehberi-registrar-lock-dnssec-whois-gizliligi-ve-2fa\/\">alan ad\u0131 g\u00fcvenli\u011fi, DNSSEC, Whois gizlili\u011fi ve 2FA rehberimizi<\/a> mutlaka okuyun. Bu yaz\u0131da registry lock gibi ileri seviye konular\u0131 onun \u00fczerine in\u015fa ediyoruz.<\/p>\n<h3><span id=\"2_Rol_ve_yetki_tasarimi_yapin\">2. Rol ve yetki tasar\u0131m\u0131 yap\u0131n<\/span><\/h3>\n<p>\u00d6zellikle ajanslar ve b\u00fcy\u00fck ekiplerde s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz hata \u015fu: Tek bir kullan\u0131c\u0131 hesab\u0131, hem fatura \u00f6demeden hem DNS g\u00fcncellemesinden hem de <a href=\"https:\/\/www.dchost.com\/tr\/alan-adi\/transfer-et\">alan ad\u0131 transfer<\/a>inden sorumlu. Bu, hem g\u00fcvenlik hem operasyonel a\u00e7\u0131dan riskli.<\/p>\n<ul>\n<li>Domain paneline eri\u015fimi olan ki\u015fi say\u0131s\u0131n\u0131 minimumda tutun.<\/li>\n<li>DNS de\u011fi\u015fikliklerini yapacak teknik ekip ile fatura \u00f6demelerini yapan ekibi birbirinden ay\u0131r\u0131n.<\/li>\n<li>En kritik alan adlar\u0131 i\u00e7in \u201ciki ki\u015fi onay\u0131 olmadan de\u011fi\u015fiklik yok\u201d politikas\u0131n\u0131 benimseyin (en az\u0131ndan fiili olarak).<\/li>\n<\/ul>\n<h3><span id=\"3_Standart_degisiklik_sureci_tanimlayin\">3. Standart de\u011fi\u015fiklik s\u00fcreci tan\u0131mlay\u0131n<\/span><\/h3>\n<p>\u201c\u015eu DNS kayd\u0131n\u0131 de\u011fi\u015ftirelim mi?\u201d mesaj\u0131yla ba\u015flayan, ama kimin onaylad\u0131\u011f\u0131n\u0131n, ne zaman yap\u0131ld\u0131\u011f\u0131n\u0131n kayd\u0131n\u0131n tutulmad\u0131\u011f\u0131 s\u00fcre\u00e7ler, hem g\u00fcvenlik hem hata y\u00f6netimi a\u00e7\u0131s\u0131ndan s\u0131k\u0131nt\u0131l\u0131. Basit ama etkili bir \u00e7er\u00e7eve \u015f\u00f6yle olabilir:<\/p>\n<ol>\n<li>De\u011fi\u015fiklik talebi yaz\u0131l\u0131 bir kanaldan (ticket, proje y\u00f6netim arac\u0131 vb.) gelir.<\/li>\n<li>\u0130lgili ki\u015fi, iste\u011fi teknik ve i\u015f a\u00e7\u0131s\u0131ndan inceler; gerekiyorsa risk analizini yazar.<\/li>\n<li>Onaylayan ki\u015fi net \u015fekilde bellidir (ad\/soyad veya kullan\u0131c\u0131 ad\u0131).<\/li>\n<li>De\u011fi\u015fiklik yap\u0131ld\u0131ktan sonra <strong>ne de\u011fi\u015fti\u011fi<\/strong> kayda ge\u00e7irilir ve m\u00fcmk\u00fcnse ekran g\u00f6r\u00fcnt\u00fcs\u00fc veya diff tutulur.<\/li>\n<\/ol>\n<p>Bu s\u00fcre\u00e7; DNSSEC anahtar d\u00f6n\u00fc\u015f\u00fc (<a href=\"https:\/\/www.dchost.com\/blog\/dnssec-key-rollover-ksk-zsk-ve-ds-kayit-guncelleme-sifir-kesintiyle-anahtar-dondurme-nasil-yapilir\/\">DNSSEC key rollover rehberinde<\/a> anlatt\u0131\u011f\u0131m\u0131z gibi), nameserver de\u011fi\u015fiklikleri veya TTL d\u00fc\u015f\u00fcrme gibi daha sofistike i\u015flemlerde hayat kurtar\u0131r.<\/p>\n<h3><span id=\"4_Bildirim_ve_loglari_aktif_kullanin\">4. Bildirim ve loglar\u0131 aktif kullan\u0131n<\/span><\/h3>\n<ul>\n<li>Domain panelinizde varsa, <strong>hesap etkinlik bildirimlerini<\/strong> ve <strong>giri\u015f uyar\u0131lar\u0131n\u0131<\/strong> aktif edin.<\/li>\n<li>DNS de\u011fi\u015fiklikleri, nameserver g\u00fcncellemeleri, transfer kilidi a\u00e7ma\/kapama olaylar\u0131n\u0131n loglar\u0131n\u0131 belirli aral\u0131klarla g\u00f6zden ge\u00e7irin.<\/li>\n<li>Kritik alan adlar\u0131 i\u00e7in, d\u0131\u015far\u0131dan periyodik <strong>DNS b\u00fct\u00fcnl\u00fck kontrolleri<\/strong> (\u00f6rne\u011fin monitoring arac\u0131yla A\/MX\/NS kay\u0131tlar\u0131n\u0131 do\u011frulama) kurun.<\/li>\n<\/ul>\n<h2><span id=\"DCHost_tarafinda_registry_lock_ve_transfer_guvenligi_yaklasimimiz\">DCHost taraf\u0131nda registry lock ve transfer g\u00fcvenli\u011fi yakla\u015f\u0131m\u0131m\u0131z<\/span><\/h2>\n<p>DCHost olarak oda\u011f\u0131m\u0131z, sadece h\u0131zl\u0131 ve kararl\u0131 hosting sunmak de\u011fil; ayn\u0131 zamanda <strong>alan ad\u0131, DNS ve sunucu g\u00fcvenli\u011fini birlikte ele alan<\/strong> bir yakla\u015f\u0131m geli\u015ftirmek. Registry lock ve transfer kilidi de bu yakla\u015f\u0131m\u0131n par\u00e7as\u0131.<\/p>\n<h3><span id=\"Transfer_kilidi_ve_EPP_kodu_yonetimi\">Transfer kilidi ve EPP kodu y\u00f6netimi<\/span><\/h3>\n<p>Genel ak\u0131\u015f \u015fu \u015fekilde olmal\u0131d\u0131r:<\/p>\n<ol>\n<li>Kritik g\u00f6rd\u00fc\u011f\u00fcn\u00fcz t\u00fcm alan adlar\u0131nda transfer kilidini <strong>varsay\u0131lan olarak a\u00e7\u0131k<\/strong> tutun.<\/li>\n<li>Transfer yap\u0131laca\u011f\u0131 zaman, yaln\u0131zca ilgili, yetkili ki\u015fi kilidi kapats\u0131n ve EPP kodunu als\u0131n.<\/li>\n<li>Transfer tamamland\u0131\u011f\u0131nda veya iptal oldu\u011funda, kilidin tekrar a\u00e7\u0131ld\u0131\u011f\u0131ndan emin olun.<\/li>\n<\/ol>\n<p>Transfer planlamas\u0131 yaparken, DNS yay\u0131l\u0131m\u0131 ve e-posta kesinti risklerini minimize etmek i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/zero-downtime-tasima-icin-ttl-stratejileri-dns-yayilimini-gercekten-nasil-hizlandirirsin\/\">TTL stratejileri rehberimizdeki<\/a> \u00f6nerileri de uygulaman\u0131z\u0131 \u00f6neririz. B\u00f6ylece hem g\u00fcvenli hem kesintisiz bir ge\u00e7i\u015f elde edersiniz.<\/p>\n<h3><span id=\"Registry_lock_talepleri\">Registry lock talepleri<\/span><\/h3>\n<p>Registry lock, TLD\u2019ye g\u00f6re de\u011fi\u015fen ve \u00e7o\u011fu zaman manuel s\u00fcre\u00e7 i\u00e7eren bir hizmet oldu\u011fu i\u00e7in, tipik ak\u0131\u015f \u015fu \u015fekilde ilerler:<\/p>\n<ol>\n<li>Kritik alan adlar\u0131n\u0131z\u0131 belirler ve hangileri i\u00e7in registry lock istedi\u011finizi netle\u015ftirirsiniz.<\/li>\n<li>DCHost destek ekibiyle ileti\u015fime ge\u00e7erek TLD bazl\u0131 olanaklar\u0131, \u00fccretlendirme ve s\u00fcre\u00e7 detaylar\u0131n\u0131 \u00f6\u011frenirsiniz.<\/li>\n<li>Onay\u0131n\u0131z sonras\u0131, registry ile gerekli s\u00fcre\u00e7ler ba\u015flat\u0131l\u0131r ve alan ad\u0131n\u0131z registry lock kapsam\u0131na al\u0131n\u0131r.<\/li>\n<li>\u0130leride DNS veya transfer gibi kritik bir de\u011fi\u015fiklik gerekti\u011finde, \u00f6nceden tan\u0131mlanm\u0131\u015f do\u011frulama kanallar\u0131 \u00fczerinden bu kilidin ge\u00e7ici olarak a\u00e7\u0131lmas\u0131 sa\u011flan\u0131r; i\u015flem sonras\u0131 tekrar kapat\u0131l\u0131r.<\/li>\n<\/ol>\n<p>Buradaki en \u00f6nemli nokta, <strong>\u00f6nceden tan\u0131ml\u0131 ve yaz\u0131l\u0131 bir prosed\u00fcr\u00fcn\u00fcz\u00fcn olmas\u0131d\u0131r<\/strong>. Kim, hangi kanaldan, hangi kimlik do\u011frulama ad\u0131mlar\u0131yla talepte bulunabilir; bunlar\u0131 netle\u015ftirmek, sosyal m\u00fchendislik riskini ciddi \u015fekilde azalt\u0131r.<\/p>\n<h2><span id=\"Alan_adi_guvenligini_diger_katmanlarla_birlestirmek\">Alan ad\u0131 g\u00fcvenli\u011fini di\u011fer katmanlarla birle\u015ftirmek<\/span><\/h2>\n<p>Registry lock ve transfer kilidi, b\u00fcy\u00fck resmin sadece bir par\u00e7as\u0131. Ger\u00e7ek anlamda g\u00fcvenli bir alan ad\u0131 altyap\u0131s\u0131 i\u00e7in, \u015fu katmanlar\u0131 da mutlaka hesaba katmal\u0131s\u0131n\u0131z:<\/p>\n<ul>\n<li><strong>DNSSEC:<\/strong> DNS yan\u0131tlar\u0131n\u0131n kriptografik olarak imzalanmas\u0131n\u0131 sa\u011flayarak, DNS spoofing riskini azalt\u0131r. <a href=\"https:\/\/www.dchost.com\/blog\/dnssec-nedir-ne-ise-yarar-alan-adiniz-ve-hostinginiz-icin-adim-adim-dnssec-kurulum-rehberi\/\">DNSSEC nedir ve ad\u0131m ad\u0131m kurulum rehberi<\/a> bu konuda iyi bir ba\u015flang\u0131\u00e7 noktas\u0131.<\/li>\n<li><strong>CAA kay\u0131tlar\u0131:<\/strong> Hangi sertifika otoritelerinin alan ad\u0131n\u0131z i\u00e7in <a href=\"https:\/\/www.dchost.com\/tr\/ssl\">SSL sertifikas\u0131<\/a> \u00fcretebilece\u011fini s\u0131n\u0131rland\u0131r\u0131r; yanl\u0131\u015f veya sahte sertifika riskini azalt\u0131r.<\/li>\n<li><strong>Whois verisi ve ileti\u015fim e-postalar\u0131:<\/strong> Kay\u0131tl\u0131 e-posta adreslerinizin g\u00fcncel ve g\u00fcvenli olmas\u0131, hem yenileme hem de g\u00fcvenlik bildirimleri i\u00e7in hayati.<\/li>\n<li><strong>HTTP g\u00fcvenlik ba\u015fl\u0131klar\u0131 ve HSTS:<\/strong> DNS veya sertifika taraf\u0131ndaki bir ihlalin etkisini azaltmak i\u00e7in, <a href=\"https:\/\/www.dchost.com\/blog\/http-guvenlik-basliklari-rehberi-hsts-csp-ve-digerlerini-ne-zaman-nasil-uygulamalisin\/\">HTTP g\u00fcvenlik ba\u015fl\u0131klar\u0131 rehberindeki<\/a> ayarlarla web uygulaman\u0131z\u0131 g\u00fc\u00e7lendirin.<\/li>\n<\/ul>\n<p>B\u00f6ylece sadece alan ad\u0131n\u0131z\u0131n kay\u0131t taraf\u0131n\u0131 de\u011fil, o alan ad\u0131n\u0131n i\u015faret etti\u011fi t\u00fcm HTTP, e-posta ve API ekosistemini birlikte sertle\u015ftirmi\u015f olursunuz.<\/p>\n<h2><span id=\"Kurum_ici_politika_ve_kontrol_listesi\">Kurum i\u00e7i politika ve kontrol listesi<\/span><\/h2>\n<p>Son olarak, konuyu tamamen operasyonel bir seviyeye indirip, kullanabilece\u011finiz pratik bir kontrol listesi \u00e7\u0131karal\u0131m. Bu listeyi, \u015firket i\u00e7i bilgi g\u00fcvenli\u011fi veya DevOps dok\u00fcmantasyonunuza ekleyebilirsiniz.<\/p>\n<h3><span id=\"Alan_adi_guvenligi_kontrol_listesi\">Alan ad\u0131 g\u00fcvenli\u011fi kontrol listesi<\/span><\/h3>\n<ul>\n<li><strong>Kritiklik s\u0131n\u0131fland\u0131rmas\u0131:<\/strong> T\u00fcm alan adlar\u0131n\u0131z\u0131 listeleyin; \u201ckritik \/ \u00f6nemli \/ d\u00fc\u015f\u00fck \u00f6nemde\u201d \u015feklinde s\u0131n\u0131fland\u0131r\u0131n.<\/li>\n<li><strong>Registry lock:<\/strong> Kritik alan adlar\u0131 i\u00e7in TLD baz\u0131nda registry lock imk\u00e2n\u0131n\u0131 de\u011ferlendirin, uygunsa aktive edin.<\/li>\n<li><strong>Transfer kilidi:<\/strong> T\u00fcm alan adlar\u0131nda transfer kilidinin varsay\u0131lan olarak a\u00e7\u0131k oldu\u011fundan emin olun.<\/li>\n<li><strong>EPP kodu y\u00f6netimi:<\/strong> Kimlerin EPP kodu talep edebilece\u011fi, nas\u0131l saklanaca\u011f\u0131 ve ne zaman yenilenece\u011fi yaz\u0131l\u0131 olsun.<\/li>\n<li><strong>Hesap g\u00fcvenli\u011fi:<\/strong> Domain paneli hesab\u0131n\u0131zda g\u00fc\u00e7l\u00fc parola, 2FA ve g\u00fcvenilir kurtarma e-posta adresleri kullan\u0131n.<\/li>\n<li><strong>Yetki da\u011f\u0131l\u0131m\u0131:<\/strong> DNS ve domain y\u00f6netimi yetkilerini ki\u015fi baz\u0131nda de\u011fil, rol baz\u0131nda tan\u0131mlay\u0131n.<\/li>\n<li><strong>De\u011fi\u015fiklik s\u00fcreci:<\/strong> DNS, nameserver, transfer kilidi a\u00e7ma, EPP kodu talebi gibi i\u015flemler i\u00e7in standart onay ad\u0131mlar\u0131n\u0131z olsun.<\/li>\n<li><strong>Bildirimler:<\/strong> M\u00fcmk\u00fcn olan her durumda giri\u015f ve de\u011fi\u015fiklik bildirimlerini aktif edin; loglar\u0131 periyodik g\u00f6zden ge\u00e7irin.<\/li>\n<li><strong>DNSSEC ve CAA:<\/strong> Uygun alan adlar\u0131nda DNSSEC\u2019i etkinle\u015ftirin, CAA kay\u0131tlar\u0131n\u0131 yap\u0131land\u0131r\u0131n.<\/li>\n<li><strong>Yedek ileti\u015fim kanal\u0131:<\/strong> Domain ile ilgili acil durumlarda kullan\u0131lacak alternatif ileti\u015fim kanallar\u0131 (telefon, ikincil e-posta) belirli olsun.<\/li>\n<\/ul>\n<h2><span id=\"Sonuc_Registry_lock_transfer_kilidi_ve_saglam_sureclerle_alan_adinizi_gercekten_koruyun\">Sonu\u00e7: Registry lock, transfer kilidi ve sa\u011flam s\u00fcre\u00e7lerle alan ad\u0131n\u0131z\u0131 ger\u00e7ekten koruyun<\/span><\/h2>\n<p>Alan ad\u0131 g\u00fcvenli\u011fi, \u00e7o\u011fu zaman \u201c\u015fimdi de\u011fil, sonra bakar\u0131z\u201d denilen ama sorun \u00e7\u0131kt\u0131\u011f\u0131nda en pahal\u0131ya mal olan konulardan biri. Bu rehberde registry lock, transfer kilidi ve yetkisiz de\u011fi\u015fiklikleri engellemek i\u00e7in kurulmas\u0131 gereken s\u00fcre\u00e7leri detayl\u0131 \u015fekilde ele ald\u0131k. \u00d6zetle; kritik alan adlar\u0131n\u0131z i\u00e7in registry lock, t\u00fcm alan adlar\u0131n\u0131z i\u00e7in s\u0131k\u0131 transfer kilidi ve EPP kodu y\u00f6netimi, bunlar\u0131n \u00fczerinde de iyi tan\u0131mlanm\u0131\u015f kurum i\u00e7i s\u00fcre\u00e7ler, sizi alan ad\u0131 taraf\u0131ndaki tipik sald\u0131r\u0131 senaryolar\u0131n\u0131n b\u00fcy\u00fck \u00e7o\u011funlu\u011fundan korur.<\/p>\n<p>\u015eimdi yapabilece\u011finiz somut ad\u0131m basit: DCHost hesab\u0131n\u0131za girin, t\u00fcm alan adlar\u0131n\u0131z\u0131 kritik seviyesine g\u00f6re s\u0131n\u0131fland\u0131r\u0131n ve bu rehberdeki kontrol listesini tek tek uygulamaya ba\u015flay\u0131n. Registry lock, DNSSEC, CAA veya daha karma\u015f\u0131k g\u00fcvenlik yap\u0131land\u0131rmalar\u0131 i\u00e7in ek deste\u011fe ihtiyac\u0131n\u0131z olursa, DCHost ekibi olarak domain, hosting, VPS, <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a> ve colocation altyap\u0131lar\u0131n\u0131z\u0131 birlikte ele al\u0131p size uygun bir g\u00fcvenlik yol haritas\u0131 \u00e7\u0131karmaktan memnuniyet duyar\u0131z.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 Alan ad\u0131 g\u00fcvenli\u011fi neden kritik bir i\u015f varl\u0131\u011f\u0131 konusu?2 Tehdit modeli: Alan ad\u0131n\u0131za ger\u00e7ekte ne olabilir?3 Registry lock nedir, registrar lock\u2019tan fark\u0131 ne?3.1 Registry, registrar ve domain sahibi ili\u015fkisi3.2 Registry lock nedir?3.3 Registry lock\u2019\u0131n tipik \u00f6zellikleri3.4 Registrar lock (transfer kilidi) nedir?3.5 Registry lock ve registrar lock farklar\u0131n\u0131 \u00f6zetleyelim4 Hangi durumlarda registry lock kullanmal\u0131s\u0131n\u0131z?5 Transfer [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":3750,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-3749","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-teknoloji"],"_links":{"self":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3749","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/comments?post=3749"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3749\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/3750"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=3749"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=3749"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=3749"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}