{"id":2704,"date":"2026-10-03T15:00:00","date_gmt":"2026-10-03T12:00:00","guid":{"rendered":"https:\/\/narhost.com\/blog\/?p=2704"},"modified":"2026-09-26T23:13:54","modified_gmt":"2026-09-26T20:13:54","slug":"domain-hijacking-nedir","status":"publish","type":"post","link":"https:\/\/narhost.com\/blog\/domain-hijacking-nedir\/","title":{"rendered":"Domain Hijacking Nedir, Alan Ad\u0131n\u0131z Nas\u0131l \u00c7al\u0131n\u0131r"},"content":{"rendered":"<div id=\"ai-ozet\" class=\"ai-box\">\n<p class=\"ai-box-title\">K\u0131saca \u00f6zet<\/p>\n<ul>\n<li>Domain hijacking, bir alan ad\u0131n\u0131n kontrol\u00fcn\u00fcn sahibinin izni olmadan ele ge\u00e7irilmesidir; sald\u0131rgan alan ad\u0131n\u0131 ba\u015fka bir hesaba ya da kay\u0131t kurulu\u015funa ta\u015f\u0131r veya DNS kay\u0131tlar\u0131n\u0131 de\u011fi\u015ftirir.<\/li>\n<li>En yayg\u0131n d\u00f6rt yol: kay\u0131t kurulu\u015fu hesab\u0131n\u0131n \u015fifresinin ele ge\u00e7irilmesi, WHOIS&#8217;te yazan e-posta hesab\u0131n\u0131n \u00e7al\u0131nmas\u0131, sosyal m\u00fchendislik ve s\u00fcresi dolan alan ad\u0131n\u0131n ba\u015fkas\u0131na ge\u00e7mesi.<\/li>\n<li>Transfer kilidi, iki ad\u0131ml\u0131 do\u011frulama, EPP kodunun gizli tutulmas\u0131 ve kay\u0131t e-postas\u0131n\u0131n g\u00fcncel olmas\u0131 riskin b\u00fcy\u00fck k\u0131sm\u0131n\u0131 kapat\u0131r.<\/li>\n<li>ICANN Transfer Politikas\u0131&#8217;na g\u00f6re sahibi de\u011fi\u015fen genel uzant\u0131l\u0131 bir alan ad\u0131na 60 g\u00fcnl\u00fck transfer k\u0131s\u0131t\u0131 uygulanabilir; bu s\u00fcre sald\u0131rgan\u0131n ad\u0131 h\u0131zla ba\u015fka bir kay\u0131t kurulu\u015funa ka\u00e7\u0131rmas\u0131n\u0131 zorla\u015ft\u0131r\u0131r.<\/li>\n<li>Ka\u00e7\u0131r\u0131lan bir alan ad\u0131n\u0131n geri al\u0131nmas\u0131nda ilk muhatap kendi kay\u0131t kurulu\u015funuzdur; kay\u0131t kurulu\u015flar\u0131 aras\u0131ndaki uyu\u015fmazl\u0131k ICANN&#8217;in Transfer Uyu\u015fmazl\u0131k \u00c7\u00f6z\u00fcm Politikas\u0131 (TDRP) ile 12 ay i\u00e7inde ba\u015fvurularak \u00e7\u00f6z\u00fcl\u00fcr.<\/li>\n<li>Alan ad\u0131 kayb\u0131 yaln\u0131z sitenin de\u011fil e-postan\u0131n da kayb\u0131d\u0131r; gelen postalar sald\u0131rgan\u0131n sunucusuna akabilir.<\/li>\n<\/ul>\n<\/div>\n<p>Bir sabah sitenize giremiyorsunuz, kurumsal e-postalar gelmiyor, alan ad\u0131n\u0131z bilmedi\u011finiz bir sayfaya y\u00f6nleniyor. Kay\u0131t kurulu\u015funun paneline girdi\u011finizde alan ad\u0131 listede yok ya da ileti\u015fim e-postas\u0131 de\u011fi\u015fmi\u015f. Bu tablonun ad\u0131 domain hijacking, yani alan ad\u0131 ka\u00e7\u0131rmad\u0131r. \u00c7o\u011fu vakada karma\u015f\u0131k bir teknik sald\u0131r\u0131 de\u011fil, ele ge\u00e7irilmi\u015f bir \u015fifre ya da g\u00fcncellenmemi\u015f bir e-posta adresi vard\u0131r. A\u015fa\u011f\u0131da alan adlar\u0131n\u0131n hangi yollarla \u00e7al\u0131nd\u0131\u011f\u0131n\u0131, hangi ayarlar\u0131n bu yollar\u0131 kapatt\u0131\u011f\u0131n\u0131 ve ka\u00e7\u0131r\u0131lan bir ad\u0131n nas\u0131l geri istendi\u011fini bulacaks\u0131n\u0131z.<\/p>\n<h2>Domain hijacking nedir, alan ad\u0131 ka\u00e7\u0131rma nas\u0131l olur<\/h2>\n<p>Domain hijacking, alan ad\u0131 \u00fczerindeki y\u00f6netim yetkisinin sahibinin r\u0131zas\u0131 olmadan ba\u015fka birine ge\u00e7mesidir. Sald\u0131rgan iki \u015feyden birini hedefler. Birincisi alan ad\u0131n\u0131n kayd\u0131d\u0131r: ad\u0131 kendi hesab\u0131na ya da ba\u015fka bir kay\u0131t kurulu\u015funa transfer eder, ileti\u015fim bilgilerini de\u011fi\u015ftirir ve ger\u00e7ek sahibi d\u0131\u015far\u0131da b\u0131rak\u0131r. \u0130kincisi DNS&#8217;tir: kay\u0131t sizde kalsa bile ad sunucular\u0131n\u0131 ya da A ve MX kay\u0131tlar\u0131n\u0131 de\u011fi\u015ftirerek ziyaret\u00e7ileri ve e-postalar\u0131 kendi sunucusuna y\u00f6nlendirir.<\/p>\n<p>Bu sald\u0131r\u0131, alan ad\u0131n\u0131z\u0131 taklit eden benzer adlarla yap\u0131lan sahtecilikten farkl\u0131d\u0131r. Harf de\u011fi\u015ftirilmi\u015f bir adla sizin ad\u0131n\u0131za e-posta g\u00f6ndermek domain spoofing konusudur; domain hijacking ise do\u011frudan sizin ger\u00e7ek alan ad\u0131n\u0131z\u0131n kontrol\u00fcn\u00fc al\u0131r. Bu y\u00fczden etkisi daha b\u00fcy\u00fckt\u00fcr: g\u00fcvenilen adres, g\u00fcvenilen e-posta ve arama motorundaki s\u0131ralama ayn\u0131 anda sald\u0131rgan\u0131n eline ge\u00e7er.<\/p>\n<div class=\"highlight-box\">\n<p class=\"label\">Bilgi<\/p>\n<p>Alan ad\u0131n\u0131n ele ge\u00e7irildi\u011fini g\u00f6steren ilk i\u015faretler genellikle beklenmedik e-postalard\u0131r: &#8220;transfer talebiniz al\u0131nd\u0131&#8221;, &#8220;ileti\u015fim bilgileriniz g\u00fcncellendi&#8221; ya da &#8220;yeni cihazdan giri\u015f&#8221; bildirimi. Bu mesajlar\u0131 siz ba\u015flatmad\u0131ysan\u0131z hemen kay\u0131t kurulu\u015funuzla ileti\u015fime ge\u00e7in.<\/p>\n<\/div>\n<h2>Alan adlar\u0131 hangi yollarla \u00e7al\u0131n\u0131r<\/h2>\n<p>Sald\u0131r\u0131lar\u0131n \u00e7o\u011fu d\u00f6rt kap\u0131dan girer. A\u015fa\u011f\u0131daki tablo her kap\u0131n\u0131n nas\u0131l a\u00e7\u0131ld\u0131\u011f\u0131n\u0131 ve hangi \u00f6nlemin kapatt\u0131\u011f\u0131n\u0131 birlikte g\u00f6sterir.<\/p>\n<table>\n<thead>\n<tr>\n<th>Sald\u0131r\u0131 yolu<\/th>\n<th>Nas\u0131l i\u015fler<\/th>\n<th>Kapatan \u00f6nlem<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Kay\u0131t kurulu\u015fu hesab\u0131n\u0131n ele ge\u00e7irilmesi<\/td>\n<td>Tahmin edilen, s\u0131zd\u0131r\u0131lm\u0131\u015f ya da ba\u015fka sitede de kullan\u0131lan \u015fifreyle panele girilir<\/td>\n<td>Benzersiz g\u00fc\u00e7l\u00fc \u015fifre ve iki ad\u0131ml\u0131 do\u011frulama<\/td>\n<\/tr>\n<tr>\n<td>WHOIS e-posta hesab\u0131n\u0131n \u00e7al\u0131nmas\u0131<\/td>\n<td>Kay\u0131ttaki e-postaya &#8220;\u015fifremi unuttum&#8221; ba\u011flant\u0131s\u0131 istenir, panel s\u0131f\u0131rlan\u0131r<\/td>\n<td>E-posta hesab\u0131nda da iki ad\u0131ml\u0131 do\u011frulama, g\u00fcncel kurtarma bilgileri<\/td>\n<\/tr>\n<tr>\n<td>Sosyal m\u00fchendislik<\/td>\n<td>Destek ekibi sahte kimlik ya da acil durum hik\u00e2yesiyle ikna edilir, EPP kodu istenir<\/td>\n<td>Kay\u0131t kurulu\u015funda kimlik do\u011frulama s\u00fcreci, EPP kodunu kimseyle payla\u015fmamak<\/td>\n<\/tr>\n<tr>\n<td>S\u00fcresi dolan alan ad\u0131<\/td>\n<td>Yenilenmeyen ad serbest kal\u0131nca ba\u015fkas\u0131 kaydeder<\/td>\n<td>Otomatik yenileme ve g\u00fcncel \u00f6deme bilgisi<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>D\u00f6rd\u00fcnc\u00fc yol teknik olarak ka\u00e7\u0131rma say\u0131lmaz, ama sonu\u00e7 ayn\u0131d\u0131r: ad art\u0131k sizin de\u011fildir. \u0130lk \u00fc\u00e7 yolun ortak noktas\u0131 ise alan ad\u0131n\u0131n g\u00fcvenli\u011finin asl\u0131nda bir e-posta hesab\u0131n\u0131n ve bir panel \u015fifresinin g\u00fcvenli\u011fine ba\u011fl\u0131 olmas\u0131d\u0131r. Kay\u0131t kurulu\u015fu ne kadar g\u00fcvenli olursa olsun, WHOIS kayd\u0131ndaki e-posta adresi zay\u0131f bir \u00fccretsiz hesapsa zincirin en zay\u0131f halkas\u0131 odur.<\/p>\n<div class=\"senaryo-block\">\n<p class=\"label\">\u00d6rnek senaryo<\/p>\n<p>Ankara&#8217;da bir muhasebe b\u00fcrosu, alan ad\u0131n\u0131 on y\u0131l \u00f6nce kurucu orta\u011f\u0131n ki\u015fisel e-postas\u0131yla kaydettirmi\u015f. Ortak ayr\u0131lm\u0131\u015f, e-posta hesab\u0131 y\u0131llard\u0131r a\u00e7\u0131lmam\u0131\u015f ve \u015fifresi ba\u015fka bir sitede s\u0131zan listelerde yer al\u0131yor. Sald\u0131rgan bu e-postaya giriyor, kay\u0131t kurulu\u015fu panelinin \u015fifresini s\u0131f\u0131rl\u0131yor ve MX kay\u0131tlar\u0131n\u0131 de\u011fi\u015ftiriyor. B\u00fcro iki g\u00fcn boyunca m\u00fc\u015fteri e-postalar\u0131n\u0131n bir k\u0131sm\u0131n\u0131 alam\u0131yor. Kay\u0131t e-postas\u0131 b\u00fcronun kendi alan ad\u0131nda olmayan, iki ad\u0131ml\u0131 do\u011frulamal\u0131 bir y\u00f6netici hesab\u0131na ta\u015f\u0131nsayd\u0131 zincir ba\u015ftan kopard\u0131.<\/p>\n<\/div>\n<h2>Transfer kilidi ve EPP kodu neden bu kadar \u00f6nemli<\/h2>\n<p>Genel uzant\u0131l\u0131 bir alan ad\u0131n\u0131 ba\u015fka bir kay\u0131t kurulu\u015funa ta\u015f\u0131mak i\u00e7in iki \u015fey gerekir: ad\u0131n transfer kilidinin kapal\u0131 olmas\u0131 ve yetki kodunun (EPP kodu) do\u011fru girilmesi. Transfer kilidi a\u00e7\u0131k oldu\u011fu s\u00fcrece ad, kod ele ge\u00e7irilse bile ba\u015fka bir kay\u0131t kurulu\u015funa gidemez. Bu y\u00fczden kilidi yaln\u0131zca ger\u00e7ekten transfer yapaca\u011f\u0131n\u0131z g\u00fcn kapat\u0131n, i\u015f bitince yeniden a\u00e7\u0131n. Transfer s\u00fcrecinin ad\u0131mlar\u0131 <a href=\"https:\/\/narhost.com\/destek\/alan-adi-transferi-nasil-yapilir\/\" title=\"Alan Ad\u0131 Transferi Nas\u0131l Yap\u0131l\u0131r (EPP Kodu ve Transfer Kilidi) \u2014 Narhost Destek Merkezi\">alan ad\u0131 transferi rehberinde<\/a> anlat\u0131l\u0131yor.<\/p>\n<p>EPP kodu, alan ad\u0131n\u0131n anahtar\u0131 gibidir. Kodun ne i\u015fe yarad\u0131\u011f\u0131 ve ne kadar ge\u00e7erli oldu\u011fu <a href=\"https:\/\/narhost.com\/blog\/epp-kodu-nedir\/\" title=\"EPP Kodu Nedir \u2014 Narhost Blog\">EPP kodu nedir<\/a> yaz\u0131s\u0131nda ayr\u0131nt\u0131l\u0131. G\u00fcvenlik a\u00e7\u0131s\u0131ndan kural nettir: kodu yaln\u0131zca transferi siz ba\u015flatt\u0131\u011f\u0131n\u0131zda, yaln\u0131zca yeni kay\u0131t kurulu\u015funun resm\u00ee transfer ekran\u0131na girin. E-postayla, telefonla ya da mesajla kod isteyen biri, kim oldu\u011funu s\u00f6ylerse s\u00f6ylesin, \u015f\u00fcpheyle kar\u015f\u0131lanmal\u0131d\u0131r.<\/p>\n<p><a href=\"https:\/\/www.icann.org\/en\/contracted-parties\/accredited-registrars\/transfer-policy-01-06-2016-en\" title=\"ICANN Transfer Policy \u2014 kay\u0131t kurulu\u015flar\u0131 aras\u0131 transfer kurallar\u0131\" target=\"_blank\" rel=\"noopener\">ICANN Transfer Politikas\u0131<\/a> bu korumaya bir katman daha ekler. Metne g\u00f6re kay\u0131t kurulu\u015fu, sahibi de\u011fi\u015fen bir alan ad\u0131na 60 g\u00fcnl\u00fck transfer kilidi uygulayabilir (sahip bundan \u00f6nceden vazge\u00e7mediyse) ve yeni kaydedilmi\u015f ya da yak\u0131n zamanda transfer edilmi\u015f adlarda 60 g\u00fcn i\u00e7inde gelen transfer talebini reddedebilir. Bu s\u00fcreler sald\u0131rgan\u0131n ad\u0131 h\u0131zla elden ele ge\u00e7irip izini kaybettirmesini zorla\u015ft\u0131r\u0131r.<\/p>\n<figure class=\"nh-sema\"><img loading=\"lazy\" src=\"https:\/\/narhost.com\/blog\/wp-content\/uploads\/2026\/09\/domain-hijacking-nedir-sema-narhost.webp\" alt=\"domain hijacking sald\u0131r\u0131s\u0131na kar\u015f\u0131 \u015fifre, iki ad\u0131ml\u0131 do\u011frulama, transfer kilidi ve EPP kodu katmanlar\u0131n\u0131 g\u00f6steren \u015fema\" width=\"1200\" height=\"500\" loading=\"lazy\" decoding=\"async\"><figcaption>Alan ad\u0131 g\u00fcvenli\u011fi panel \u015fifresiyle ba\u015flar, iki ad\u0131ml\u0131 do\u011frulama ve transfer kilidiyle g\u00fc\u00e7lenir, EPP kodunun gizlili\u011fiyle tamamlan\u0131r.<\/figcaption><\/figure>\n<h2>Domain hijacking riskini azaltan ayarlar<\/h2>\n<p>Koruman\u0131n b\u00fcy\u00fck k\u0131sm\u0131 birka\u00e7 dakikal\u0131k ayardan olu\u015fur. \u0130lk s\u0131rada kay\u0131t kurulu\u015fu ve hosting panelindeki iki ad\u0131ml\u0131 do\u011frulama gelir; \u015fifre s\u0131zsa bile ikinci ad\u0131m olmadan panele girilemez. \u0130kinci s\u0131rada WHOIS kayd\u0131ndaki e-posta adresi vard\u0131r: \u015firkete ait, birden \u00e7ok y\u00f6neticinin eri\u015febildi\u011fi, iki ad\u0131ml\u0131 do\u011frulamas\u0131 a\u00e7\u0131k bir adres olmal\u0131d\u0131r.<\/p>\n<p>WHOIS gizlili\u011fi sald\u0131rgan\u0131n kay\u0131t e-postan\u0131z\u0131 ve telefonunuzu g\u00f6rmesini zorla\u015ft\u0131r\u0131r, sosyal m\u00fchendislik denemelerinde elini zay\u0131flat\u0131r; hangi uzant\u0131larda nas\u0131l i\u015fledi\u011fi <a href=\"https:\/\/narhost.com\/blog\/alan-adi-gizliligi-whois-privacy\/\" title=\"Alan Ad\u0131 Gizlili\u011fi WHOIS Privacy \u2014 Narhost Blog\">alan ad\u0131 gizlili\u011fi<\/a> yaz\u0131s\u0131nda. Kritik alan adlar\u0131 i\u00e7in baz\u0131 kay\u0131t merkezleri, de\u011fi\u015fikliklerin elle onayland\u0131\u011f\u0131 ek bir kilit (registry lock) da sunar; y\u00fcksek trafikli ya da marka de\u011feri b\u00fcy\u00fck adlar i\u00e7in bu se\u00e7ene\u011fi kay\u0131t kurulu\u015funuza sorun.<\/p>\n<div class=\"warn-box\">\n<p class=\"label\">Dikkat<\/p>\n<p>Alan ad\u0131 ile e-postan\u0131z\u0131 ayn\u0131 alan ad\u0131 \u00fczerinde tutuyorsan\u0131z, kay\u0131t kurulu\u015fu hesab\u0131n\u0131n kurtarma e-postas\u0131 olarak o alan ad\u0131ndaki bir adresi kullanmay\u0131n. Alan ad\u0131 ele ge\u00e7irildi\u011finde sald\u0131rgan MX kayd\u0131n\u0131 de\u011fi\u015ftirir, kurtarma e-postas\u0131 da onun sunucusuna gider ve hesab\u0131n\u0131z\u0131 geri alma yolunuz kapan\u0131r.<\/p>\n<\/div>\n<h2>Alan ad\u0131n\u0131z \u00e7al\u0131nd\u0131ysa ne yapmal\u0131s\u0131n\u0131z<\/h2>\n<p>\u0130lk ad\u0131m zaman kaybetmeden kay\u0131t kurulu\u015funuzla ileti\u015fime ge\u00e7mektir. Alan ad\u0131n\u0131n sahibi oldu\u011funuzu g\u00f6steren belgeleri (fatura, \u00f6deme kayd\u0131, eski WHOIS \u00e7\u0131kt\u0131s\u0131, yaz\u0131\u015fmalar) haz\u0131rlay\u0131n. Ad h\u00e2l\u00e2 ayn\u0131 kay\u0131t kurulu\u015fundaysa hesap eri\u015fimi ve ileti\u015fim bilgileri kimlik do\u011frulamas\u0131 sonras\u0131 geri verilebilir. Ele ge\u00e7irilen e-posta hesab\u0131n\u0131n ve panelin \u015fifrelerini de hemen de\u011fi\u015ftirip b\u00fct\u00fcn oturumlar\u0131 kapat\u0131n.<\/p>\n<p>Ad ba\u015fka bir kay\u0131t kurulu\u015funa transfer edildiyse s\u00fcre\u00e7 iki kay\u0131t kurulu\u015fu aras\u0131nda y\u00fcr\u00fcr. ICANN&#8217;in <a href=\"https:\/\/www.icann.org\/en\/contracted-parties\/accredited-registrars\/registrar-transfer-dispute-resolution-policy-01-06-2016-en\" title=\"ICANN Transfer Dispute Resolution Policy (TDRP)\" target=\"_blank\" rel=\"noopener\">Transfer Uyu\u015fmazl\u0131k \u00c7\u00f6z\u00fcm Politikas\u0131 (TDRP)<\/a> \u015fik\u00e2yeti kay\u0131t kurulu\u015flar\u0131n\u0131n a\u00e7mas\u0131n\u0131 \u00f6ng\u00f6r\u00fcr ve iddia edilen ihlalden sonra en ge\u00e7 12 ay i\u00e7inde ba\u015fvurulmas\u0131n\u0131 \u015fart ko\u015far. Sizin rol\u00fcn\u00fcz, kendi kay\u0131t kurulu\u015funuza olay\u0131 ayr\u0131nt\u0131l\u0131 bildirmek ve kan\u0131tlar\u0131 sunmakt\u0131r; beklemek kurtarma ihtimalini d\u00fc\u015f\u00fcr\u00fcr. .tr uzant\u0131lar\u0131nda s\u00fcre\u00e7 TRAB\u0130S kurallar\u0131 ve kay\u0131t kurulu\u015fu \u00fczerinden i\u015fler; uzant\u0131lar aras\u0131ndaki y\u00f6netim farklar\u0131n\u0131n \u00f6zeti <a href=\"https:\/\/narhost.com\/blog\/en-populer-domain-uzantilari-nedir\/\" title=\"En Pop\u00fcler Domain Uzant\u0131lar\u0131 Nedir \u2014 Narhost Blog\">en pop\u00fcler domain uzant\u0131lar\u0131<\/a> rehberinde.<\/p>\n<div class=\"success-box\">\n<p class=\"label\">Sonu\u00e7<\/p>\n<p>Domain hijacking \u00e7o\u011fu zaman zay\u0131f bir halkadan ba\u015flar: tekrar kullan\u0131lan bir \u015fifre, unutulmu\u015f bir e-posta hesab\u0131 ya da ikna edilmi\u015f bir destek temsilcisi. Transfer kilidini a\u00e7\u0131k tutmak, EPP kodunu payla\u015fmamak, iki ad\u0131ml\u0131 do\u011frulamay\u0131 a\u00e7mak ve kay\u0131t e-postas\u0131n\u0131 g\u00fcncel tutmak bu halkalar\u0131n hepsini g\u00fc\u00e7lendirir. Olay ya\u015fand\u0131\u011f\u0131nda da ilk saatlerde kay\u0131t kurulu\u015funa ula\u015fmak geri alma \u015fans\u0131n\u0131 belirler.<\/p>\n<\/div>\n<h2>Alan ad\u0131 g\u00fcvenli\u011fi kontrol listesi<\/h2>\n<ul class=\"kontrol-listesi\">\n<li>Kay\u0131t kurulu\u015fu panelinde benzersiz, g\u00fc\u00e7l\u00fc bir \u015fifre ve iki ad\u0131ml\u0131 do\u011frulama kullan\u0131n.<\/li>\n<li>WHOIS ve hesap e-postas\u0131n\u0131n \u015firkete ait, eri\u015filebilir ve iki ad\u0131ml\u0131 do\u011frulamal\u0131 oldu\u011funu kontrol edin.<\/li>\n<li>Transfer kilidinin a\u00e7\u0131k oldu\u011funu do\u011frulay\u0131n; yaln\u0131z transfer g\u00fcn\u00fcnde kapat\u0131n.<\/li>\n<li>EPP kodunu hi\u00e7bir kanaldan kimseyle payla\u015fmay\u0131n.<\/li>\n<li>Otomatik yenilemeyi a\u00e7\u0131n ve \u00f6deme bilgisini g\u00fcncel tutun.<\/li>\n<li>Ad sunucusu ve MX kay\u0131tlar\u0131n\u0131z\u0131n g\u00fcncel de\u011ferlerini bir yere not edin; de\u011fi\u015fiklik olursa hemen fark edersiniz.<\/li>\n<li>Panel bildirim e-postalar\u0131n\u0131 spam klas\u00f6r\u00fcne d\u00fc\u015fmeyecek \u015fekilde ayarlay\u0131n.<\/li>\n<\/ul>\n<div class=\"kb-faq\">\n<h2>S\u0131k\u00e7a sorulan sorular<\/h2>\n<h3>Domain hijacking ile alan ad\u0131n\u0131n s\u00fcresinin dolmas\u0131 ayn\u0131 \u015fey mi?<\/h3>\n<p>Teknik olarak de\u011fil. Domain hijacking, alan ad\u0131n\u0131n kontrol\u00fcn\u00fcn izinsiz ele ge\u00e7irilmesidir; s\u00fcresi dolan ad ise yenilenmedi\u011fi i\u00e7in serbest kal\u0131r ve ba\u015fkas\u0131 yasal olarak kaydedebilir. Sonu\u00e7 ayn\u0131d\u0131r, ad elinizden \u00e7\u0131kar. Fark\u0131 \u015fudur: s\u00fcresi dolan ad\u0131 otomatik yenilemeyle tamamen \u00f6nleyebilirsiniz, ka\u00e7\u0131rmaya kar\u015f\u0131 ise hesap g\u00fcvenli\u011fi gerekir.<\/p>\n<h3>Transfer kilidi a\u00e7\u0131kken alan ad\u0131m yine de \u00e7al\u0131nabilir mi?<\/h3>\n<p>Transfer kilidi ad\u0131n ba\u015fka bir kay\u0131t kurulu\u015funa gitmesini engeller, ama panelinize giren biri kilidi kapatabilir ya da hi\u00e7 transfer yapmadan DNS kay\u0131tlar\u0131n\u0131 de\u011fi\u015ftirebilir. Bu y\u00fczden kilit tek ba\u015f\u0131na yetmez; panel \u015fifresi ve iki ad\u0131ml\u0131 do\u011frulama ayn\u0131 derecede \u00f6nemlidir.<\/p>\n<h3>EPP kodumu ele ge\u00e7iren biri hemen transfer yapabilir mi?<\/h3>\n<p>Kilit a\u00e7\u0131ksa ve kay\u0131t kurulu\u015funun onay ad\u0131mlar\u0131 a\u015f\u0131labilirse deneyebilir. Genel uzant\u0131larda kay\u0131t kurulu\u015fu transfer talebini kay\u0131t sahibine bildirmek zorundad\u0131r; bu bildirim size ula\u015f\u0131rsa itiraz edebilirsiniz. Kod s\u0131zd\u0131\u011f\u0131ndan \u015f\u00fcpheleniyorsan\u0131z kay\u0131t kurulu\u015funuzdan yeni kod \u00fcretmesini isteyin ve kilidi a\u00e7\u0131k tutun.<\/p>\n<h3>Ka\u00e7\u0131r\u0131lan alan ad\u0131m\u0131 ne kadar s\u00fcrede geri alabilirim?<\/h3>\n<p>S\u00fcre, ad\u0131n h\u00e2l\u00e2 sizin kay\u0131t kurulu\u015funuzda olup olmad\u0131\u011f\u0131na ve kan\u0131tlar\u0131n\u0131z\u0131n g\u00fcc\u00fcne ba\u011fl\u0131d\u0131r. Ayn\u0131 kay\u0131t kurulu\u015funda kalan adlarda kimlik do\u011frulamas\u0131ndan sonra h\u0131zl\u0131 sonu\u00e7 al\u0131nabilir. Ba\u015fka kay\u0131t kurulu\u015funa ta\u015f\u0131nm\u0131\u015f adlarda s\u00fcre\u00e7 kay\u0131t kurulu\u015flar\u0131 aras\u0131nda y\u00fcr\u00fcr ve haftalar s\u00fcrebilir. TDRP ba\u015fvurusu i\u00e7in \u00fcst s\u0131n\u0131r ihlalden itibaren 12 ayd\u0131r.<\/p>\n<h3>WHOIS gizlili\u011fi alan ad\u0131m\u0131 \u00e7al\u0131nmaya kar\u015f\u0131 korur mu?<\/h3>\n<p>K\u0131smen. Gizlilik, e-posta adresinizi ve telefonunuzu herkese a\u00e7\u0131k kay\u0131ttan gizler; sald\u0131rgan\u0131n hangi hesab\u0131 hedefleyece\u011fini bulmas\u0131n\u0131 zorla\u015ft\u0131r\u0131r. Ama zay\u0131f bir panel \u015fifresini ya da ele ge\u00e7irilmi\u015f bir e-posta hesab\u0131n\u0131 telafi etmez. Gizlili\u011fi tamamlay\u0131c\u0131 bir katman olarak g\u00f6r\u00fcn, iki ad\u0131ml\u0131 do\u011frulaman\u0131n yerine koymay\u0131n.<\/p>\n<\/div>\n<div class=\"cta-box\">\n<p class=\"label\">Narhost&#8217;ta<\/p>\n<p>Alan ad\u0131n\u0131z\u0131 .com&#8217;dan .com.tr&#8217;ye geni\u015f uzant\u0131 se\u00e7ene\u011fiyle kaydedebilir, mevcut ad\u0131n\u0131z\u0131 transfer ederek y\u00f6netimini tek hesapta toplayabilirsiniz; \u015f\u00fcpheli bir transfer ya da DNS de\u011fi\u015fikli\u011finde 7\/24 destek ekibimize ula\u015fabilirsiniz.<\/p>\n<p><a class=\"cta-btn\" href=\"https:\/\/narhost.com\/domain-kaydi\" title=\"Narhost Domain Kayd\u0131\">Alan ad\u0131 sorgula<\/a><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Domain hijacking, bir alan ad\u0131n\u0131n kontrol\u00fcn\u00fcn sahibinin izni olmadan ele ge\u00e7irilmesidir. Alan adlar\u0131n\u0131n hangi yollarla \u00e7al\u0131nd\u0131\u011f\u0131, transfer kilidi ve EPP kodunun rol\u00fc, riski azaltan ayarlar ve ka\u00e7\u0131r\u0131lan ad\u0131n geri istenme s\u00fcreci bu yaz\u0131da.<\/p>\n","protected":false},"author":1,"featured_media":2705,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[18],"tags":[],"class_list":["post-2704","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\/2704","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=2704"}],"version-history":[{"count":1,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/posts\/2704\/revisions"}],"predecessor-version":[{"id":2706,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/posts\/2704\/revisions\/2706"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/media\/2705"}],"wp:attachment":[{"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/media?parent=2704"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/categories?post=2704"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/tags?post=2704"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}