{"id":4620,"date":"2026-02-06T17:58:51","date_gmt":"2026-02-06T14:58:51","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/alan-adi-ve-hosting-sahipligi-rehberi-whoisten-fatura-unvanina-mulkiyeti-dogru-kurmak\/"},"modified":"2026-02-06T17:58:51","modified_gmt":"2026-02-06T14:58:51","slug":"alan-adi-ve-hosting-sahipligi-rehberi-whoisten-fatura-unvanina-mulkiyeti-dogru-kurmak","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/alan-adi-ve-hosting-sahipligi-rehberi-whoisten-fatura-unvanina-mulkiyeti-dogru-kurmak\/","title":{"rendered":"Alan Ad\u0131 ve Hosting Sahipli\u011fi Rehberi: WHOIS\u2019ten Fatura \u00dcnvan\u0131na M\u00fclkiyeti Do\u011fru Kurmak"},"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_ve_hosting_sahipligini_yanlis_kurmanin_gercek_bedeli\"><span class=\"toc_number toc_depth_1\">1<\/span> Alan ad\u0131 ve hosting sahipli\u011fini yanl\u0131\u015f kurman\u0131n ger\u00e7ek bedeli<\/a><\/li><li><a href=\"#Alan_adi_sahipligi_WHOIS_kaydini_gercekten_dogru_okumak\"><span class=\"toc_number toc_depth_1\">2<\/span> Alan ad\u0131 sahipli\u011fi: WHOIS kayd\u0131n\u0131 ger\u00e7ekten do\u011fru okumak<\/a><ul><li><a href=\"#WHOIS_alanlari_registrant_admin_tech_ve_billing_rollerinin_anlami\"><span class=\"toc_number toc_depth_2\">2.1<\/span> WHOIS alanlar\u0131: registrant, admin, tech ve billing rollerinin anlam\u0131<\/a><\/li><li><a href=\"#GDPRKVKK_sonrasinda_WHOIS_ne_kadar_ise_yariyor\"><span class=\"toc_number toc_depth_2\">2.2<\/span> GDPR\/KVKK sonras\u0131nda WHOIS ne kadar i\u015fe yar\u0131yor?<\/a><\/li><li><a href=\"#Sirketler_icin_ideal_WHOIS_mimarisi\"><span class=\"toc_number toc_depth_2\">2.3<\/span> \u015eirketler i\u00e7in ideal WHOIS mimarisi<\/a><\/li><li><a href=\"#Ajansmusteri_iliskilerinde_domain_kimin_ustunde_olmali\"><span class=\"toc_number toc_depth_2\">2.4<\/span> Ajans\u2013m\u00fc\u015fteri ili\u015fkilerinde domain kimin \u00fcst\u00fcnde olmal\u0131?<\/a><\/li><\/ul><\/li><li><a href=\"#Fatura_unvani_sozlesme_ve_gercek_mulkiyet_iliskisi\"><span class=\"toc_number toc_depth_1\">3<\/span> Fatura \u00fcnvan\u0131, s\u00f6zle\u015fme ve ger\u00e7ek m\u00fclkiyet ili\u015fkisi<\/a><ul><li><a href=\"#Alan_adi_ve_hosting_faturasinda_hangi_unvan_gecmeli\"><span class=\"toc_number toc_depth_2\">3.1<\/span> Alan ad\u0131 ve hosting faturas\u0131nda hangi \u00fcnvan ge\u00e7meli?<\/a><\/li><li><a href=\"#Ajans_danisman_veya_calisan_uzerinden_alinan_domainlerin_riskleri\"><span class=\"toc_number toc_depth_2\">3.2<\/span> Ajans, dan\u0131\u015fman veya \u00e7al\u0131\u015fan \u00fczerinden al\u0131nan domain\u2019lerin riskleri<\/a><\/li><li><a href=\"#Marka_tescili_alan_adi_ve_fatura_ucgenini_hizalamak\"><span class=\"toc_number toc_depth_2\">3.3<\/span> Marka tescili, alan ad\u0131 ve fatura \u00fc\u00e7genini hizalamak<\/a><\/li><\/ul><\/li><li><a href=\"#Hosting_sahipligi_panel_sunucu_ve_erisim_mimarisini_netlestirmek\"><span class=\"toc_number toc_depth_1\">4<\/span> Hosting sahipli\u011fi: panel, sunucu ve eri\u015fim mimarisini netle\u015ftirmek<\/a><ul><li><a href=\"#Domain_paneli_hosting_paneli_DNS_ve_sunucu_kim_neye_sahip\"><span class=\"toc_number toc_depth_2\">4.1<\/span> Domain paneli, hosting paneli, DNS ve sunucu: kim neye sahip?<\/a><\/li><li><a href=\"#Erisim_paylasirken_mulkiyeti_riske_atmamak\"><span class=\"toc_number toc_depth_2\">4.2<\/span> Eri\u015fim payla\u015f\u0131rken m\u00fclkiyeti riske atmamak<\/a><\/li><li><a href=\"#VPS_dedicated_ve_colocation_tarafinda_sahiplik\"><span class=\"toc_number toc_depth_2\">4.3<\/span> VPS, dedicated ve colocation taraf\u0131nda sahiplik<\/a><\/li><\/ul><\/li><li><a href=\"#Yillardir_gordugumuz_mulkiyet_hatasi_senaryolari_ve_alinacak_onlemler\"><span class=\"toc_number toc_depth_1\">5<\/span> Y\u0131llard\u0131r g\u00f6rd\u00fc\u011f\u00fcm\u00fcz m\u00fclkiyet hatas\u0131 senaryolar\u0131 ve al\u0131nacak \u00f6nlemler<\/a><ul><li><a href=\"#Senaryo_1_Ajans_ile_yollar_ayriliyor_domain_ajansin_ustunde\"><span class=\"toc_number toc_depth_2\">5.1<\/span> Senaryo 1: Ajans ile yollar ayr\u0131l\u0131yor, domain ajans\u0131n \u00fcst\u00fcnde<\/a><\/li><li><a href=\"#Senaryo_2_Yenileme_maili_eski_calisan_adresine_gidiyor_domain_dusuyor\"><span class=\"toc_number toc_depth_2\">5.2<\/span> Senaryo 2: Yenileme maili eski \u00e7al\u0131\u015fan adresine gidiyor, domain d\u00fc\u015f\u00fcyor<\/a><\/li><li><a href=\"#Senaryo_3_Domain_dusuyor_baskasi_kapiyor\"><span class=\"toc_number toc_depth_2\">5.3<\/span> Senaryo 3: Domain d\u00fc\u015f\u00fcyor, ba\u015fkas\u0131 kap\u0131yor<\/a><\/li><li><a href=\"#Senaryo_4_Domain_bir_kayit_firmasinda_DNS_baska_yerde_kimse_nereden_baslayacagini_bilmiyor\"><span class=\"toc_number toc_depth_2\">5.4<\/span> Senaryo 4: Domain bir kay\u0131t firmas\u0131nda, DNS ba\u015fka yerde, kimse nereden ba\u015flayaca\u011f\u0131n\u0131 bilmiyor<\/a><\/li><li><a href=\"#Alan_adi_ve_hosting_sahipligi_icin_pratik_kontrol_listesi\"><span class=\"toc_number toc_depth_2\">5.5<\/span> Alan ad\u0131 ve hosting sahipli\u011fi i\u00e7in pratik kontrol listesi<\/a><\/li><\/ul><\/li><li><a href=\"#DCHost_ile_saglikli_domain_ve_hosting_sahipligi_yapisi_kurmak\"><span class=\"toc_number toc_depth_1\">6<\/span> DCHost ile sa\u011fl\u0131kl\u0131 domain ve hosting sahipli\u011fi yap\u0131s\u0131 kurmak<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Alan_adi_ve_hosting_sahipligini_yanlis_kurmanin_gercek_bedeli\">Alan ad\u0131 ve hosting sahipli\u011fini yanl\u0131\u015f kurman\u0131n ger\u00e7ek bedeli<\/span><\/h2>\n<p>DCHost taraf\u0131nda y\u0131llard\u0131r g\u00f6rd\u00fc\u011f\u00fcm\u00fcz en can s\u0131k\u0131c\u0131 vakalar, performans sorunlar\u0131 de\u011fil; yanl\u0131\u015f kurgulanm\u0131\u015f <strong>alan ad\u0131 ve hosting sahipli\u011fi<\/strong> y\u00fcz\u00fcnden siteyi, e\u2011postay\u0131 hatta markan\u0131n ana domain\u2019ini kaybetme noktas\u0131na gelen i\u015fletmeler. Teknik olarak her \u015fey yolunda olsa bile, WHOIS\u2019te yanl\u0131\u015f ki\u015fi, faturada yanl\u0131\u015f \u00fcnvan, yanl\u0131\u015f panelde yanl\u0131\u015f yetkilendirme derken kontrol yava\u015f yava\u015f elinizden kayabiliyor.<\/p>\n<p>Bir proje planlama toplant\u0131s\u0131nda sunucu mimarisini, yedeklemeyi, \u00f6l\u00e7eklenmeyi konu\u015furken \u00e7o\u011fu zaman en kritik soruyu en sona b\u0131rak\u0131yoruz: \u201cBu alan ad\u0131 ve hosting hukuken <strong>kimin<\/strong>?\u201d \u00c7o\u011fu i\u015fletmede net bir cevap yok. Domain ajans\u0131n \u00fczerinde, hosting ba\u015fka bir firman\u0131n hesab\u0131nda, y\u00f6netim eri\u015fimleri eski bir \u00e7al\u0131\u015fanda, fatura ise tamamen alakas\u0131z bir \u015fah\u0131s firmas\u0131 ad\u0131na kesilmi\u015f olabiliyor.<\/p>\n<p>Bu rehberde; alan ad\u0131 ve hosting sahipli\u011fini <strong>ba\u015f\u0131ndan itibaren do\u011fru kurman\u0131z<\/strong> i\u00e7in ad\u0131m ad\u0131m ilerleyece\u011fiz. WHOIS kayd\u0131n\u0131n ne anlama geldi\u011fini, fatura \u00fcnvan\u0131n\u0131n hukuki etkisini, ajans\u2013m\u00fc\u015fteri ili\u015fkilerinde ideal modeli, \u00e7al\u0131\u015fan de\u011fi\u015fimlerinde eri\u015fim devrini ve \u015firket birle\u015fme\/ayr\u0131lmalar\u0131nda nelere dikkat etmeniz gerekti\u011fini konu\u015faca\u011f\u0131z. Amac\u0131m\u0131z, projeleriniz b\u00fcy\u00fcd\u00fck\u00e7e sizi geriden vurmayan, \u015feffaf ve denetlenebilir bir m\u00fclkiyet yap\u0131s\u0131 kurman\u0131za yard\u0131mc\u0131 olmak.<\/p>\n<h2><span id=\"Alan_adi_sahipligi_WHOIS_kaydini_gercekten_dogru_okumak\">Alan ad\u0131 sahipli\u011fi: WHOIS kayd\u0131n\u0131 ger\u00e7ekten do\u011fru okumak<\/span><\/h2>\n<p>Bir\u00e7ok ki\u015fi i\u00e7in WHOIS kayd\u0131, \u201cdomain\u2019i nereden alm\u0131\u015f\u0131z ona bakar\u0131m\u201d seviyesinde kal\u0131yor. Oysa WHOIS, alan ad\u0131n\u0131n hukuki ve teknik sahipli\u011fini tarif eden <strong>\u00e7ok katmanl\u0131<\/strong> bir yap\u0131.<\/p>\n<h3><span id=\"WHOIS_alanlari_registrant_admin_tech_ve_billing_rollerinin_anlami\">WHOIS alanlar\u0131: registrant, admin, tech ve billing rollerinin anlam\u0131<\/span><\/h3>\n<p>Alan ad\u0131n\u0131z i\u00e7in WHOIS kayd\u0131nda tipik olarak \u015fu roller bulunur:<\/p>\n<ul>\n<li><strong>Registrant (Domain Holder \/ Sahip):<\/strong> Alan ad\u0131n\u0131n hukuki sahibi. \u0130htilaf, UDRP s\u00fcreci, mahkeme, marka davas\u0131 gibi durumlarda bak\u0131lan ilk kay\u0131t budur.<\/li>\n<li><strong>Admin Contact (Y\u00f6netici ki\u015fi):<\/strong> Genelde idari kararlar\u0131 veren, transfer onay\u0131 gibi kritik i\u015flemleri yapabilen ki\u015fi\/e\u2011posta.<\/li>\n<li><strong>Tech Contact (Teknik ki\u015fi):<\/strong> DNS de\u011fi\u015fiklikleri, nameserver ayarlar\u0131 gibi teknik s\u00fcre\u00e7lerde ileti\u015fim ki\u015fisi olarak kullan\u0131l\u0131r.<\/li>\n<li><strong>Billing Contact (Faturalama):<\/strong> \u00d6deme, yenileme hat\u0131rlatmalar\u0131 ve bor\u00e7 bildirimlerinin gitti\u011fi ki\u015fi\/e\u2011posta.<\/li>\n<\/ul>\n<p>Bir\u00e7ok i\u015fletmede bu roller ya tek bir ki\u015fide toplan\u0131yor ya da tamamen kar\u0131\u015f\u0131k durumda: Registrant eski orta\u011f\u0131n \u015fah\u0131s \u015firketi, admin ajans\u0131n info adresi, tech ise vaktiyle projeyi yapan freelancer\u2019\u0131n ki\u015fisel maili. Buradan \u00e7\u0131kacak kar\u0131\u015f\u0131kl\u0131\u011f\u0131n boyutunu tahmin etmek zor de\u011fil.<\/p>\n<h3><span id=\"GDPRKVKK_sonrasinda_WHOIS_ne_kadar_ise_yariyor\">GDPR\/KVKK sonras\u0131nda WHOIS ne kadar i\u015fe yar\u0131yor?<\/span><\/h3>\n<p>Avrupa\u2019daki GDPR ve T\u00fcrkiye\u2019deki KVKK sebebiyle bir\u00e7ok uzant\u0131da WHOIS \u00e7\u0131kt\u0131lar\u0131nda ki\u015fisel bilgiler maskeleniyor. Bu y\u00fczden baz\u0131 y\u00f6neticiler \u201cZaten WHOIS gizli, \u00e7ok da \u00f6nemli de\u011fil\u201d yan\u0131lg\u0131s\u0131na d\u00fc\u015f\u00fcyor.<\/p>\n<p>Ger\u00e7ekte olan \u015fu:<\/p>\n<ul>\n<li>Kay\u0131t operat\u00f6r\u00fcn\u00fcn (registrar) veritaban\u0131nda <strong>tam bilgileriniz<\/strong> yine tutuluyor.<\/li>\n<li>Uyu\u015fmazl\u0131k, mahkeme, resmi yaz\u0131\u015fma gibi durumlarda bu bilgiler referans al\u0131n\u0131yor.<\/li>\n<li>WHOIS\u2019te maske olsa bile, panelinizdeki <strong>registrant bilgileri<\/strong> ileride hakk\u0131n\u0131z\u0131 ispat etmeniz i\u00e7in hayati.<\/li>\n<\/ul>\n<p>Bu konuyu daha derinlemesine ele ald\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/alan-adi-whois-gizliligi-ve-gdpr-kvkk-ne-zaman-gerekli-neyi-gercekten-korur\/\">WHOIS gizlili\u011fi, GDPR ve KVKK dengesini anlatt\u0131\u011f\u0131m\u0131z ayr\u0131nt\u0131l\u0131 rehber<\/a> de mutlaka okunmal\u0131.<\/p>\n<h3><span id=\"Sirketler_icin_ideal_WHOIS_mimarisi\">\u015eirketler i\u00e7in ideal WHOIS mimarisi<\/span><\/h3>\n<p>Kurumsal bir yap\u0131da hedefimiz; alan ad\u0131n\u0131n ger\u00e7ek sahibi olan t\u00fczel ki\u015fili\u011fi netle\u015ftirmek ve ki\u015filer de\u011fi\u015fse bile s\u00fcreklili\u011fi garanti alt\u0131na almak olmal\u0131. Pratik bir model:<\/p>\n<ul>\n<li><strong>Registrant:<\/strong> \u015eirketin ticari unvan\u0131 (\u00f6rne\u011fin \u201c\u00d6rnek Teknoloji A.\u015e.\u201d), vergi numaras\u0131 ve resmi adres.<\/li>\n<li><strong>Admin Contact:<\/strong> Kurumsal bir rol e\u2011postas\u0131 (\u00f6r: domain@firma.com) ve yan\u0131nda alan ad\u0131 y\u00f6netiminden sorumlu pozisyon (IT y\u00f6neticisi, dijital pazarlama m\u00fcd\u00fcr\u00fc\u2026).<\/li>\n<li><strong>Tech Contact:<\/strong> IT ekibi veya DCHost \u00fczerindeki teknik ileti\u015fim adresiniz.<\/li>\n<li><strong>Billing Contact:<\/strong> muhasebe@firma.com gibi yenileme maillerinin kaybolmayaca\u011f\u0131 kurumsal bir adres.<\/li>\n<\/ul>\n<p>Burada kritik nokta; ki\u015fisel Gmail\/Hotmail adresleri yerine <strong>\u015firket kontrol\u00fcnde, rol bazl\u0131 e\u2011postalar<\/strong> kullanmak. B\u00f6ylece \u00e7al\u0131\u015fan ayr\u0131ld\u0131\u011f\u0131nda mail kutusu kapansa bile domain@firma.com eri\u015fimi kurumsal olarak y\u00f6netilmeye devam eder.<\/p>\n<h3><span id=\"Ajansmusteri_iliskilerinde_domain_kimin_ustunde_olmali\">Ajans\u2013m\u00fc\u015fteri ili\u015fkilerinde domain kimin \u00fcst\u00fcnde olmal\u0131?<\/span><\/h3>\n<p>Ajanslar a\u00e7\u0131s\u0131ndan en s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz hata, \u201cm\u00fc\u015fteriyi u\u011fra\u015ft\u0131rmayal\u0131m\u201d diye t\u00fcm alan adlar\u0131n\u0131 <strong>ajans\u0131n kendi ad\u0131na<\/strong> kaydetmek. Bu k\u0131sa vadede i\u015fleri h\u0131zland\u0131rsa da orta\u2013uzun vadede bombaya d\u00f6n\u00fc\u015f\u00fcyor:<\/p>\n<ul>\n<li>M\u00fc\u015fteri ajans de\u011fi\u015ftirmek istedi\u011finde alan ad\u0131n\u0131 devralmak zorla\u015f\u0131yor.<\/li>\n<li>Ajans\u0131n kapanmas\u0131\/iflas\u0131 durumunda <strong>domain\u2019e eri\u015fim kayb\u0131<\/strong> ya\u015fanabiliyor.<\/li>\n<li>Faturalama, marka tescili ve hukuki sahiplik birbirine kar\u0131\u015f\u0131yor.<\/li>\n<\/ul>\n<p>\u0130deal model \u015fu:<\/p>\n<ul>\n<li><strong>Alan ad\u0131 sahibi (registrant):<\/strong> Her zaman son m\u00fc\u015fteri (marka\/\u015firket) olmal\u0131.<\/li>\n<li>Ajans; admin veya tech contact olarak eklenebilir, ayr\u0131ca domain paneline yetkili kullan\u0131c\u0131 olarak tan\u0131mlanabilir.<\/li>\n<li>Ajans kendi i\u00e7inde <strong>Reseller<\/strong> veya <strong>VPS<\/strong> altyap\u0131s\u0131 kullan\u0131yorsa bile, hesap i\u00e7inde a\u00e7\u0131lan her domain i\u00e7in registrant m\u00fc\u015fterinin unvan\u0131 olarak girilmeli.<\/li>\n<\/ul>\n<p>Bu modeli ayr\u0131nt\u0131l\u0131 anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/ajanslar-icin-dns-ve-alan-adi-erisimi-yonetimi\/\">ajanslar i\u00e7in DNS ve alan ad\u0131 eri\u015fimi y\u00f6netimi kontrol listesi<\/a> ajans taraf\u0131nda \u00e7al\u0131\u015fan herkes i\u00e7in iyi bir referans.<\/p>\n<h2><span id=\"Fatura_unvani_sozlesme_ve_gercek_mulkiyet_iliskisi\">Fatura \u00fcnvan\u0131, s\u00f6zle\u015fme ve ger\u00e7ek m\u00fclkiyet ili\u015fkisi<\/span><\/h2>\n<p>WHOIS taraf\u0131 bir ayak, <strong>fatura ve s\u00f6zle\u015fme<\/strong> taraf\u0131 ise di\u011fer ayak. Bir\u00e7ok ihtilafta \u201cFatura kimin \u00fczerine kesilmi\u015f?\u201d sorusu, en az WHOIS kadar belirleyici oluyor.<\/p>\n<h3><span id=\"Alan_adi_ve_hosting_faturasinda_hangi_unvan_gecmeli\">Alan ad\u0131 ve hosting faturas\u0131nda hangi \u00fcnvan ge\u00e7meli?<\/span><\/h3>\n<p>Temel prensip: <strong>Masraf\u0131 \u00e7eken kimse, m\u00fclkiyet de onundur<\/strong> varsay\u0131m\u0131n\u0131 bo\u015fa \u00e7\u0131karacak bir durum istemiyoruz. Bunun i\u00e7in:<\/p>\n<ul>\n<li>Alan ad\u0131 ve hosting; m\u00fcmk\u00fcnse <strong>son m\u00fc\u015fterinin ticari unvan\u0131<\/strong> \u00fczerine faturaland\u0131r\u0131lmal\u0131.<\/li>\n<li>Ajans hizmet bedelini ayr\u0131ca kendi faturas\u0131yla kesmeli (tasar\u0131m, y\u00f6netim, dan\u0131\u015fmanl\u0131k vb.).<\/li>\n<li>\u015eah\u0131s \u015firketi ile kurumsal \u015firket ayr\u0131m\u0131nda, ileride \u015firket \u00fcnvan\u0131 de\u011fi\u015fse bile ili\u015fkilendirilebilecek a\u00e7\u0131klamalar fatura notlar\u0131nda yer almal\u0131.<\/li>\n<\/ul>\n<p>E\u011fer domain\u2019in WHOIS registrant k\u0131sm\u0131 \u201cAjans A.\u015e.\u201d, fatura ise \u201cM\u00fc\u015fteri B Ltd. \u015eti.\u201d ad\u0131na kesilmi\u015fse; olas\u0131 bir anla\u015fmazl\u0131kta her iki taraf da hak iddia edebilir. Bu gri alanlar\u0131 <strong>en ba\u015ftan temizlemek<\/strong> \u00e7ok daha sa\u011fl\u0131kl\u0131.<\/p>\n<h3><span id=\"Ajans_danisman_veya_calisan_uzerinden_alinan_domainlerin_riskleri\">Ajans, dan\u0131\u015fman veya \u00e7al\u0131\u015fan \u00fczerinden al\u0131nan domain\u2019lerin riskleri<\/span><\/h3>\n<p>Ger\u00e7ek vakalardan s\u0131k\u00e7a g\u00f6rd\u00fc\u011f\u00fcm\u00fcz riskli durumlar:<\/p>\n<ul>\n<li>Domain, projeyi yapan freelance yaz\u0131l\u0131mc\u0131n\u0131n ki\u015fisel hesab\u0131nda kal\u0131yor.<\/li>\n<li>Startup\u2019\u0131n alan ad\u0131 ba\u015flang\u0131\u00e7ta kuruculardan birinin kendi ad\u0131na, sonra \u015firket kuruldu\u011funda devri hi\u00e7 yap\u0131lm\u0131yor.<\/li>\n<li>IT \u00e7al\u0131\u015fan\u0131 \u015firket kart\u0131n\u0131 kullanarak kendi hesab\u0131na domain\/hosting al\u0131yor, i\u015ften ayr\u0131ld\u0131\u011f\u0131nda <strong>eri\u015fim tamamen onun \u00fczerinde kal\u0131yor<\/strong>.<\/li>\n<\/ul>\n<p>Bu durumlarda; marka b\u00fcy\u00fcd\u00fck\u00e7e alan ad\u0131n\u0131n hukuki ve ticari de\u011feri art\u0131yor ve <strong>ki\u015filerle \u015firket aras\u0131nda gerilim<\/strong> olu\u015fuyor. \u00c7\u00f6z\u00fcm:<\/p>\n<ol>\n<li>Mevcut domain\u2019ler i\u00e7in durum tespiti yap\u0131n (WHOIS, fatura, panel eri\u015fimleri).<\/li>\n<li>\u015eirket ad\u0131na al\u0131nmam\u0131\u015f domain\u2019ler i\u00e7in <strong>devir s\u00f6zle\u015fmesi ve fatural\u0131 sat\u0131\u015f<\/strong> ile resmiyet kazand\u0131r\u0131n.<\/li>\n<li>Yeni al\u0131nacak t\u00fcm domain ve hostinglerde <strong>kurumsal sat\u0131n alma prosed\u00fcr\u00fc<\/strong> uygulay\u0131n (onay, \u00f6deme, kay\u0131t, dok\u00fcmantasyon).<\/li>\n<\/ol>\n<h3><span id=\"Marka_tescili_alan_adi_ve_fatura_ucgenini_hizalamak\">Marka tescili, alan ad\u0131 ve fatura \u00fc\u00e7genini hizalamak<\/span><\/h3>\n<p>Marka tesciliniz (T\u00fcrk Patent vb.), alan ad\u0131n\u0131z ve fatura \u00fcnvan\u0131n\u0131z <strong>uyumlu<\/strong> olursa, olas\u0131 bir uyu\u015fmazl\u0131kta eliniz \u00e7ok g\u00fc\u00e7lenir. \u00d6zellikle jenerik ve de\u011ferli domain\u2019ler i\u00e7in bu kritik.<\/p>\n<ul>\n<li>Marka tescili hangi \u015firket\/ki\u015fi ad\u0131na ise alan ad\u0131n\u0131n <strong>registrant<\/strong> alan\u0131n\u0131 da ayn\u0131 \u015fekilde g\u00fcncelleyin.<\/li>\n<li>Faturan\u0131n da yine ayn\u0131 t\u00fczel ki\u015filik ad\u0131na kesildi\u011finden emin olun.<\/li>\n<li>Bu \u00fc\u00e7l\u00fc (marka \u2013 domain \u2013 fatura) uyumluysa, \u00fc\u00e7\u00fcnc\u00fc bir taraf\u0131n hak iddia etmesi \u00e7ok zorla\u015f\u0131r.<\/li>\n<\/ul>\n<p>Marka ve domain ihtilaflar\u0131n\u0131n hukuki boyutuna ilgi duyuyorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/marka-tescili-udrp-ve-alan-adi-ihtilaflari-domainlerinizi-hukuken-korumak\/\">marka tescili ve alan ad\u0131 ihtilaflar\u0131n\u0131 hukuken ele ald\u0131\u011f\u0131m\u0131z yaz\u0131<\/a> da iyi bir tamamlay\u0131c\u0131 olacakt\u0131r.<\/p>\n<h2><span id=\"Hosting_sahipligi_panel_sunucu_ve_erisim_mimarisini_netlestirmek\">Hosting sahipli\u011fi: panel, sunucu ve eri\u015fim mimarisini netle\u015ftirmek<\/span><\/h2>\n<p>Alan ad\u0131n\u0131n kime ait oldu\u011fu kadar, <strong>hosting ve sunucu altyap\u0131s\u0131n\u0131n kontrol\u00fc<\/strong> de \u00f6nemli. \u00c7o\u011fu i\u015fletmede \u015fu kar\u0131\u015f\u0131kl\u0131\u011f\u0131 g\u00f6r\u00fcyoruz: Domain bir yerde, DNS ba\u015fka yerde, hosting \u00fc\u00e7\u00fcnc\u00fc firmada, e\u2011posta ise tamamen d\u00f6rd\u00fcnc\u00fc bir altyap\u0131da.<\/p>\n<h3><span id=\"Domain_paneli_hosting_paneli_DNS_ve_sunucu_kim_neye_sahip\">Domain paneli, hosting paneli, DNS ve sunucu: kim neye sahip?<\/span><\/h3>\n<p>\u00d6nce kavramlar\u0131 netle\u015ftirelim:<\/p>\n<ul>\n<li><strong>Alan ad\u0131 (domain):<\/strong> \u201cfirma.com\u201d gibi adresin kendisi.<\/li>\n<li><strong>DNS:<\/strong> Alan ad\u0131n\u0131 IP adreslerine \u00e7eviren kay\u0131tlar (A, AAAA, MX, CNAME vb.).<\/li>\n<li><strong>Hosting:<\/strong> Web sitenizin ve\/veya e\u2011postan\u0131z\u0131n bar\u0131nd\u0131\u011f\u0131 alan (<a href=\"https:\/\/www.dchost.com\/tr\/web-hosting\">payla\u015f\u0131ml\u0131 hosting<\/a>, <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a>, dedicated, colocation vb.).<\/li>\n<li><strong>Kontrol panelleri:<\/strong> Domain paneli, cPanel\/DirectAdmin\/Plesk gibi hosting panelleri ve sunucu y\u00f6netim arabirimleri.<\/li>\n<\/ul>\n<p>Bu ayr\u0131m\u0131 detayl\u0131 anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/domain-ve-hosting-arasindaki-fark-nedir\/\">domain ve hosting aras\u0131ndaki fark\u0131 ad\u0131m ad\u0131m anlatt\u0131\u011f\u0131m\u0131z yaz\u0131<\/a>, \u00f6zellikle teknik olmayan y\u00f6neticiler i\u00e7in iyi bir referans.<\/p>\n<p>Sahiplik a\u00e7\u0131s\u0131ndan bak\u0131nca:<\/p>\n<ul>\n<li><strong>Domain paneli:<\/strong> Alan ad\u0131n\u0131n ger\u00e7ekten kime ait oldu\u011funu ve kimlerin transfer\/dns de\u011fi\u015fikli\u011fi yapabilece\u011fini belirler.<\/li>\n<li><strong>Hosting paneli:<\/strong> Web sitesi dosyalar\u0131, veritabanlar\u0131, e\u2011posta hesaplar\u0131 ve SSL gibi kritik ayarlar\u0131n yap\u0131ld\u0131\u011f\u0131 yer.<\/li>\n<li><strong>VPS\/Dedicated\/Colocation:<\/strong> \u0130\u015fletim sistemi, g\u00fcvenlik duvar\u0131, g\u00fcncellemeler ve t\u00fcm servisler \u00fczerinde tam yetki.<\/li>\n<\/ul>\n<p>Prensip olarak, <strong>\u015firket varl\u0131\u011f\u0131n\u0131n bir par\u00e7as\u0131 olan her kritik eri\u015fim<\/strong> (domain paneli, ana hosting hesab\u0131, ana sunucu) \u015firket ad\u0131na a\u00e7\u0131lm\u0131\u015f olmal\u0131 ve bireysel hesaplara mecbur kalmad\u0131k\u00e7a ba\u011f\u0131ml\u0131 olunmamal\u0131.<\/p>\n<h3><span id=\"Erisim_paylasirken_mulkiyeti_riske_atmamak\">Eri\u015fim payla\u015f\u0131rken m\u00fclkiyeti riske atmamak<\/span><\/h3>\n<p>Pratikte ajanslar, freelancer\u2019lar, yaz\u0131l\u0131mc\u0131lar ve sistem y\u00f6neticileriyle \u00e7al\u0131\u015fmak zorundas\u0131n\u0131z. Bu ki\u015filerle eri\u015fim payla\u015f\u0131rken \u015fu modele dikkat edin:<\/p>\n<ul>\n<li>Domain ve hosting hesab\u0131, <strong>\u015firketiniz ad\u0131na<\/strong> DCHost\u2019ta a\u00e7\u0131lm\u0131\u015f olsun.<\/li>\n<li>M\u00fcmk\u00fcnse ana hesap \u015fifresini vermek yerine, <strong>alt kullan\u0131c\u0131<\/strong> veya <strong>yetki bazl\u0131 eri\u015fim<\/strong> sa\u011flay\u0131n (\u00f6rne\u011fin sadece DNS veya sadece FTP gibi).<\/li>\n<li>T\u00fcm kritik panellerde <strong>iki fakt\u00f6rl\u00fc kimlik do\u011frulama (2FA)<\/strong> aktif olsun.<\/li>\n<li>\u00c7al\u0131\u015fma bitti\u011finde; yetkili kullan\u0131c\u0131y\u0131 kald\u0131r\u0131n, 2FA cihazlar\u0131n\u0131 s\u0131f\u0131rlay\u0131n ve de\u011fi\u015fiklikleri kay\u0131t alt\u0131na al\u0131n.<\/li>\n<\/ul>\n<p>Alan ad\u0131 ve panel g\u00fcvenli\u011fi taraf\u0131nda ek \u00f6nlemler i\u00e7in, <a href=\"https:\/\/www.dchost.com\/blog\/alan-adi-guvenligi-rehberi-registrar-lock-dnssec-whois-gizliligi-ve-2fa\/\">alan ad\u0131 g\u00fcvenli\u011fi i\u00e7in registrar lock ve DNSSEC kullan\u0131m\u0131n\u0131 anlatt\u0131\u011f\u0131m\u0131z rehber<\/a>e mutlaka g\u00f6z at\u0131n.<\/p>\n<h3><span id=\"VPS_dedicated_ve_colocation_tarafinda_sahiplik\">VPS, dedicated ve colocation taraf\u0131nda sahiplik<\/span><\/h3>\n<p>Daha ileri seviyede; VPS, <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a> veya colocation gibi hizmetler kullan\u0131yorsan\u0131z, burada da benzer prensipler ge\u00e7erli:<\/p>\n<ul>\n<li>S\u00f6zle\u015fme ve fatura <strong>\u015firketiniz ad\u0131na<\/strong> olmal\u0131.<\/li>\n<li>Sunucuya root\/administrator eri\u015fimi \u015firket taraf\u0131ndan y\u00f6netilmeli; \u00fc\u00e7\u00fcnc\u00fc ki\u015filere <strong>ki\u015fisel hesaplarla de\u011fil yetkili eri\u015fimlerle<\/strong> (sudo, RDP user vb.) giri\u015f imkan\u0131 verilmeli.<\/li>\n<li>Sunucu \u00fczerinde \u00e7al\u0131\u015fan t\u00fcm kritik servislerin (web, veritaban\u0131, e\u2011posta) dok\u00fcmantasyonu tutulmal\u0131; \u201cBu servisi kim kurdu, \u015fifresi nerede?\u201d sorusu asla cevaps\u0131z kalmamal\u0131.<\/li>\n<\/ul>\n<p>DCHost taraf\u0131nda ister payla\u015f\u0131ml\u0131 hosting, ister VPS\/dedicated, ister colocation kullan\u0131yor olun; sahiplik mimarisi do\u011fru kurguland\u0131\u011f\u0131nda, teknik \u00f6l\u00e7eklendirme ad\u0131mlar\u0131n\u0131 da \u00e7ok daha g\u00fcvenle planlayabiliyorsunuz.<\/p>\n<h2><span id=\"Yillardir_gordugumuz_mulkiyet_hatasi_senaryolari_ve_alinacak_onlemler\">Y\u0131llard\u0131r g\u00f6rd\u00fc\u011f\u00fcm\u00fcz m\u00fclkiyet hatas\u0131 senaryolar\u0131 ve al\u0131nacak \u00f6nlemler<\/span><\/h2>\n<p>Somutla\u015fmas\u0131 i\u00e7in s\u0131k kar\u015f\u0131la\u015ft\u0131\u011f\u0131m\u0131z birka\u00e7 senaryoyu payla\u015fmak faydal\u0131 olacak. Kendinizi hangi senaryoya daha yak\u0131n hissediyorsan\u0131z, \u00f6nlemleri oradan ba\u015flayarak uygulayabilirsiniz.<\/p>\n<h3><span id=\"Senaryo_1_Ajans_ile_yollar_ayriliyor_domain_ajansin_ustunde\">Senaryo 1: Ajans ile yollar ayr\u0131l\u0131yor, domain ajans\u0131n \u00fcst\u00fcnde<\/span><\/h3>\n<p>M\u00fc\u015fteri, ajansla \u00e7al\u0131\u015fmay\u0131 b\u0131rakmak istiyor; ancak alan ad\u0131 ajans ad\u0131na kay\u0131tl\u0131. Ajans iyi niyetli olsa bile, domain devri i\u00e7in karma\u015f\u0131k bir b\u00fcrokrasi ba\u015fl\u0131yor.<\/p>\n<p>\u00d6nlem:<\/p>\n<ul>\n<li>T\u00fcm mevcut domain\u2019leri g\u00f6zden ge\u00e7irip <strong>registrant devrini<\/strong> m\u00fc\u015fteriye yap\u0131n.<\/li>\n<li>Yeni projelerde alan ad\u0131n\u0131 do\u011frudan m\u00fc\u015fteri ad\u0131na DCHost \u00fczerinden kay\u0131t edin.<\/li>\n<li>Ajans eri\u015fimlerini admin\/tech contact veya panel yetkilendirmesi \u00fczerinden verin.<\/li>\n<\/ul>\n<h3><span id=\"Senaryo_2_Yenileme_maili_eski_calisan_adresine_gidiyor_domain_dusuyor\">Senaryo 2: Yenileme maili eski \u00e7al\u0131\u015fan adresine gidiyor, domain d\u00fc\u015f\u00fcyor<\/span><\/h3>\n<p>\u015eirketin alan ad\u0131n\u0131 ilk alan \u00e7al\u0131\u015fan i\u015ften ayr\u0131lm\u0131\u015f, WHOIS\u2019te ve registrar hesab\u0131nda hala onun ki\u015fisel e\u2011postas\u0131 var. Yenileme hat\u0131rlatmalar\u0131 oraya gidiyor, kimse fark etmiyor ve domain s\u00fcresi doluyor.<\/p>\n<p>Bu riski anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/alan-adi-yenileme-grace-ve-redemption-sureleri-degerli-domainleri-kaybetmemek-icin-strateji-rehberi\/\">alan ad\u0131 yenileme, grace ve redemption s\u00fcreleri rehberi<\/a> de \u00e7ok kritik. \u00c7\u00fcnk\u00fc bir\u00e7ok uzant\u0131da, s\u00fcre dolduktan sonra geri alma maliyetleri ciddi \u015fekilde art\u0131yor.<\/p>\n<p>\u00d6nlem:<\/p>\n<ul>\n<li>T\u00fcm alan adlar\u0131n\u0131z i\u00e7in <strong>yetkili e\u2011posta adreslerini<\/strong> kurumsal role (domain@firma.com) \u00e7evirin.<\/li>\n<li>Y\u0131ll\u0131k yerine <strong>uzun d\u00f6nemli (\u00f6r. 3\u20135 y\u0131l)<\/strong> yenileme yapmay\u0131 d\u00fc\u015f\u00fcn\u00fcn.<\/li>\n<li>Yenileme takvimini \u015firket i\u00e7inde ayr\u0131ca takip eden bir liste\/ara\u00e7 kullan\u0131n.<\/li>\n<\/ul>\n<h3><span id=\"Senaryo_3_Domain_dusuyor_baskasi_kapiyor\">Senaryo 3: Domain d\u00fc\u015f\u00fcyor, ba\u015fkas\u0131 kap\u0131yor<\/span><\/h3>\n<p>Yenileme unutuluyor, grace ve redemption s\u00fcreleri de ge\u00e7iyor, domain tamamen d\u00fc\u015f\u00fcyor ve ba\u015fka biri taraf\u0131ndan tescil ediliyor. \u00d6zellikle jenerik, k\u0131sa ve y\u00fcksek trafikli domain\u2019lerde bu durum <strong>geri d\u00f6n\u00fclemez bir kay\u0131p<\/strong> anlam\u0131na geliyor.<\/p>\n<p>Alan ad\u0131 ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fc ve d\u00fc\u015fen domain s\u00fcre\u00e7lerini detayl\u0131 anlatt\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>ni de mutlaka okuyun.<\/p>\n<p>\u00d6nlem:<\/p>\n<ul>\n<li>T\u00fcm kritik domain\u2019lerde <strong>otomatik yenileme<\/strong> ve g\u00fcncel kredi kart\u0131\/\u00f6deme metodu tan\u0131mlay\u0131n.<\/li>\n<li>DCHost panelinizden domainlerinizi tek ekranda g\u00f6r\u00fcp tarihlerini d\u00fczenli kontrol edin.<\/li>\n<li>Kritik marka alan adlar\u0131n\u0131z i\u00e7in <strong>defansif ek kay\u0131tlar<\/strong> (.com, .com.tr, .net vb.) d\u00fc\u015f\u00fcn\u00fcn.<\/li>\n<\/ul>\n<h3><span id=\"Senaryo_4_Domain_bir_kayit_firmasinda_DNS_baska_yerde_kimse_nereden_baslayacagini_bilmiyor\">Senaryo 4: Domain bir kay\u0131t firmas\u0131nda, DNS ba\u015fka yerde, kimse nereden ba\u015flayaca\u011f\u0131n\u0131 bilmiyor<\/span><\/h3>\n<p>\u015eirket i\u00e7inde \u201cDNS\u2019e kim bak\u0131yor?\u201d sorusuna net bir cevap yok. Domain bir yerden al\u0131nm\u0131\u015f, DNS Cloud X\u2019te, hosting ba\u015fka bir sunucuda. Her sorun \u00e7\u0131kt\u0131\u011f\u0131nda herkes birbirine pas at\u0131yor.<\/p>\n<p>\u00d6nlem:<\/p>\n<ul>\n<li>T\u00fcm alan adlar\u0131 i\u00e7in <strong>tek bir envanter dosyas\u0131<\/strong> haz\u0131rlay\u0131n: Nereden al\u0131nm\u0131\u015f, DNS nerede, hosting nerede, kim yetkili?<\/li>\n<li>Yeni al\u0131nacak alan adlar\u0131 i\u00e7in m\u00fcmk\u00fcn oldu\u011funca <strong>ayn\u0131 sa\u011flay\u0131c\u0131 ve ayn\u0131 DNS\/hosting mimarisini<\/strong> tercih edin.<\/li>\n<li>Ba\u015fka bir kay\u0131t firmas\u0131ndaki domain\u2019i DCHost\u2019a ta\u015f\u0131mak isterseniz, <a href=\"https:\/\/www.dchost.com\/blog\/alan-adini-farkli-kayit-firmasina-transfer-etmek-epp-dns-ve-e-postayi-kesintisiz-tasimak\/\">EPP kodu, DNS ve e\u2011postay\u0131 kesintisiz ta\u015f\u0131ma rehberimiz<\/a> size ad\u0131m ad\u0131m yol g\u00f6sterir.<\/li>\n<\/ul>\n<h3><span id=\"Alan_adi_ve_hosting_sahipligi_icin_pratik_kontrol_listesi\">Alan ad\u0131 ve hosting sahipli\u011fi i\u00e7in pratik kontrol listesi<\/span><\/h3>\n<p>Kendi yap\u0131n\u0131z\u0131 h\u0131zl\u0131ca taramak i\u00e7in a\u015fa\u011f\u0131daki listeyi kullanabilirsiniz:<\/p>\n<ul>\n<li>T\u00fcm domain\u2019ler i\u00e7in WHOIS\u2019te <strong>registrant<\/strong> k\u0131sm\u0131 ger\u00e7ekten \u015firket\/son m\u00fc\u015fteri mi?<\/li>\n<li>Admin, tech ve billing e\u2011postalar\u0131 <strong>kurumsal rol adresleri<\/strong> mi, yoksa ki\u015fisel mailler mi?<\/li>\n<li>Alan ad\u0131 ve hosting faturalar\u0131 \u015firket\/son m\u00fc\u015fteri ad\u0131na m\u0131 kesiliyor?<\/li>\n<li>Domain paneline kimler eri\u015febiliyor? Eri\u015fimler kay\u0131t alt\u0131nda m\u0131, 2FA a\u00e7\u0131k m\u0131?<\/li>\n<li>cPanel\/DirectAdmin\/Plesk veya sunucu panellerine eri\u015fen t\u00fcm ki\u015filerin <strong>g\u00fcncel listesi<\/strong> var m\u0131?<\/li>\n<li>Y\u0131ll\u0131k yenileme takviminiz, sorumlu ki\u015fi ve yedek sorumlu tan\u0131ml\u0131 m\u0131?<\/li>\n<li>Ajans, freelancer veya d\u0131\u015f ekiplerle \u00e7al\u0131\u015f\u0131yorsan\u0131z, eri\u015fim yetkileri i\u015f bitince <strong>g\u00f6zden ge\u00e7iriliyor mu?<\/strong><\/li>\n<\/ul>\n<h2><span id=\"DCHost_ile_saglikli_domain_ve_hosting_sahipligi_yapisi_kurmak\">DCHost ile sa\u011fl\u0131kl\u0131 domain ve hosting sahipli\u011fi yap\u0131s\u0131 kurmak<\/span><\/h2>\n<p>Sa\u011fl\u0131kl\u0131 bir sahiplik yap\u0131s\u0131 kurmak teknikten \u00e7ok organizasyonel bir konu gibi g\u00f6r\u00fcnse de, do\u011fru hosting ve domain altyap\u0131s\u0131 bu i\u015fi inan\u0131lmaz kolayla\u015ft\u0131r\u0131yor. DCHost olarak hem <strong>alan ad\u0131 kayd\u0131<\/strong> hem de <strong>payla\u015f\u0131ml\u0131 hosting, VPS, dedicated ve colocation<\/strong> hizmetlerini ayn\u0131 \u00e7at\u0131 alt\u0131nda sunarken, \u015fu prensiplerle \u00e7al\u0131\u015f\u0131yoruz:<\/p>\n<ul>\n<li>Hesab\u0131n\u0131z \u015firket\/marka ad\u0131na a\u00e7\u0131l\u0131r, domain\u2019leriniz do\u011frudan bu t\u00fczel ki\u015filik alt\u0131nda tutulur.<\/li>\n<li>Ajans veya dan\u0131\u015fmanlarla \u00e7al\u0131\u015f\u0131yorsan\u0131z, eri\u015fim yetkilerini <strong>g\u00fcvenli ve izlenebilir<\/strong> \u015fekilde kurgulaman\u0131z i\u00e7in size yol g\u00f6steririz.<\/li>\n<li>Kritik domain\u2019lerinizde <strong>registrar lock, 2FA, g\u00fcvenli DNS ve d\u00fczenli yenileme<\/strong> gibi \u00f6nlemleri kurman\u0131za yard\u0131mc\u0131 oluruz.<\/li>\n<li>VPS\/dedicated veya colocation kulland\u0131\u011f\u0131n\u0131zda, sahiplik ve eri\u015fim hiyerar\u015fisini nas\u0131l tasarlaman\u0131z gerekti\u011fini birlikte dok\u00fcmante ederiz.<\/li>\n<\/ul>\n<p>Alan ad\u0131, DNS, hosting ve sunucu mimariniz ne kadar b\u00fcy\u00fcrse b\u00fcy\u00fcs\u00fcn, sahiplik yap\u0131n\u0131z net ve \u015feffaf ise <strong>hi\u00e7bir ki\u015fi veya ajansa ba\u011f\u0131ml\u0131 kalmadan<\/strong> yolunuza devam edebilirsiniz. Bu rehberi bir ba\u015flang\u0131\u00e7 noktas\u0131 olarak g\u00f6r\u00fcp, \u015firket i\u00e7inde k\u0131sa bir envanter \u00e7al\u0131\u015fmas\u0131 yapman\u0131z\u0131 \u00f6neririm. Eksik ve riskli g\u00f6rd\u00fc\u011f\u00fcn\u00fcz alanlar\u0131 not al\u0131n; DCHost ekibi olarak, isterseniz bunlar\u0131 birlikte g\u00f6zden ge\u00e7irip hem teknik hem hukuki a\u00e7\u0131dan daha sa\u011flam bir yap\u0131ya kavu\u015fman\u0131z i\u00e7in yan\u0131n\u0131zda oluruz.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 Alan ad\u0131 ve hosting sahipli\u011fini yanl\u0131\u015f kurman\u0131n ger\u00e7ek bedeli2 Alan ad\u0131 sahipli\u011fi: WHOIS kayd\u0131n\u0131 ger\u00e7ekten do\u011fru okumak2.1 WHOIS alanlar\u0131: registrant, admin, tech ve billing rollerinin anlam\u01312.2 GDPR\/KVKK sonras\u0131nda WHOIS ne kadar i\u015fe yar\u0131yor?2.3 \u015eirketler i\u00e7in ideal WHOIS mimarisi2.4 Ajans\u2013m\u00fc\u015fteri ili\u015fkilerinde domain kimin \u00fcst\u00fcnde olmal\u0131?3 Fatura \u00fcnvan\u0131, s\u00f6zle\u015fme ve ger\u00e7ek m\u00fclkiyet ili\u015fkisi3.1 Alan ad\u0131 ve [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4621,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-4620","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\/4620","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=4620"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/4620\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/4621"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=4620"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=4620"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=4620"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}