{"id":1017,"date":"2026-10-03T11:55:36","date_gmt":"2026-10-03T11:55:36","guid":{"rendered":"https:\/\/www.vps.tc\/blog\/?p=1017"},"modified":"2026-10-03T09:30:51","modified_gmt":"2026-10-03T09:30:51","slug":"domain-ve-url-farki","status":"publish","type":"post","link":"https:\/\/www.vps.tc\/blog\/tr\/domain-ve-url-farki\/","title":{"rendered":"Domain ve URL Fark\u0131 Nedir? \u00d6rneklerle A\u00e7\u0131klama"},"content":{"rendered":"<div class=\"aiw-summary\" id=\"aiw-ozet\">\n<p class=\"aiw-summary-title\">H\u0131zl\u0131 \u00d6zet &#8211; Domain ve URL Fark\u0131<\/p>\n<p>Domain, DNS \u00fczerinde kullan\u0131lan alan ad\u0131d\u0131r. URL ise bu alan ad\u0131yla birlikte protokol\u00fc, portu, yolu ve parametreleri belirten tam adrestir.<\/p>\n<ul>\n<li><strong>Domain nedir?<\/strong> \u2014 \u0130nsanlar\u0131n IP adresleri yerine kulland\u0131\u011f\u0131 alan ad\u0131 b\u00f6l\u00fcm\u00fcd\u00fcr; \u00f6rnek olarak ornek.com verilebilir.<\/li>\n<li><strong>URL nedir?<\/strong> \u2014 https:\/\/ornek.com\/blog?id=2 gibi, kayna\u011f\u0131n eri\u015fim y\u00f6ntemini ve konumunu birlikte g\u00f6steren tam adrestir.<\/li>\n<li><strong>DNS g\u00f6revi<\/strong> \u2014 Domain veya hostname de\u011ferini A, AAAA ve di\u011fer kay\u0131tlarla IP adresi ya da hizmet bilgisine ba\u011flar.<\/li>\n<li><strong>Path fark\u0131<\/strong> \u2014 URL i\u00e7indeki \/blog veya \/urun\/42 gibi b\u00f6l\u00fcmler domainin de\u011fil, web uygulamas\u0131n\u0131n kaynak yolunun par\u00e7as\u0131d\u0131r.<\/li>\n<li><strong>www ayr\u0131m\u0131<\/strong> \u2014 www.ornek.com ve ornek.com ayr\u0131 hostname&#039;lerdir; ayn\u0131 IP&#039;yi kullanmalar\u0131 zorunlu de\u011fildir.<\/li>\n<li><strong>Port ve \u015fema<\/strong> \u2014 https \u015femay\u0131, 443 ise varsay\u0131lan HTTPS portunu ifade eder; ikisi de domainin par\u00e7as\u0131 de\u011fildir.<\/li>\n<\/ul>\n<\/div>\n<p class=\"aiw-lead\">Domain, bir web sitesinin alan ad\u0131d\u0131r; URL ise o siteye veya belirli bir kayna\u011fa nas\u0131l ve nereden eri\u015filece\u011fini g\u00f6steren tam adrestir. \u00d6rne\u011fin ornek.com bir domain, https:\/\/ornek.com\/blog?id=2 bir URL&#039;dir. URL i\u00e7inde domain bulunabilir, fakat protokol, port, path ve sorgu parametreleri domain kapsam\u0131na girmez.<\/p>\n<div class=\"aiw-toc\" style=\"border:1px solid #dbe3ea;border-radius:8px;padding:16px 20px;margin:0 0 28px\">\n<p class=\"aiw-toc-head\"><strong>\u0130\u00e7indekiler<\/strong><span class=\"aiw-toc-meta\"> \u00b7 11 dk okuma<\/span><\/p>\n<ol style=\"margin:10px 0 0;padding-left:22px\">\n<li><a href=\"#domain-ve-url-arasindaki-temel-ayrim\">Domain ve URL aras\u0131ndaki temel ayr\u0131m<\/a><\/li>\n<li><a href=\"#url-hangi-parcalardan-olusur\">URL hangi par\u00e7alardan olu\u015fur?<\/a><\/li>\n<li><a href=\"#domain-nedir-nasil-calisir\">Domain nedir, nas\u0131l \u00e7al\u0131\u015f\u0131r?<\/a><\/li>\n<li><a href=\"#bir-domain-ile-url-arasindaki-fark-nasil-anlasilir\">Bir domain ile URL aras\u0131ndaki fark nas\u0131l anla\u015f\u0131l\u0131r?<\/a><\/li>\n<li><a href=\"#domain-hostname-ve-url-ayni-sey-midir\">Domain, hostname ve URL ayn\u0131 \u015fey midir?<\/a><\/li>\n<li><a href=\"#https-dns-ve-yonlendirme-domain-url-iliskisini-nasil-degistirir\">HTTPS, DNS ve y\u00f6nlendirme domain-URL ili\u015fkisini nas\u0131l de\u011fi\u015ftirir?<\/a><\/li>\n<li><a href=\"#komut-satirindan-domain-ve-url-nasil-test-edilir\">Komut sat\u0131r\u0131ndan domain ve URL nas\u0131l test edilir?<\/a><\/li>\n<li><a href=\"#gunluk-kullanimda-yapilan-domain-ve-url-hatalari\">G\u00fcnl\u00fck kullan\u0131mda yap\u0131lan domain ve URL hatalar\u0131<\/a><\/li>\n<li><a href=\"#domain-ve-url-farki-icin-kisa-karar-tablosu\">Domain ve URL fark\u0131 i\u00e7in k\u0131sa karar tablosu<\/a><\/li>\n<li><a href=\"#domain-ve-url-kontrol-listesi\">Domain ve URL Kontrol Listesi<\/a><\/li>\n<li><a href=\"#sik-sorulan-sorular\">S\u0131k Sorulan Sorular<\/a><\/li>\n<li><a href=\"#kaynaklar\">Kaynaklar<\/a><\/li>\n<\/ol>\n<\/div>\n<h2 id=\"domain-ve-url-arasindaki-temel-ayrim\">Domain ve URL aras\u0131ndaki temel ayr\u0131m<\/h2>\n<p>Bir web sitesine ula\u015f\u0131rken kullan\u0131lan adres, tek bir par\u00e7adan olu\u015fmaz. <strong>Domain<\/strong>, bir kayna\u011f\u0131n insanlar taraf\u0131ndan okunabilen alan ad\u0131d\u0131r; <strong>URL<\/strong> ise protokol\u00fc, alan ad\u0131n\u0131, portu, yolu, sorgu parametrelerini ve gerekirse b\u00f6l\u00fcm bilgisini bir araya getirerek belirli bir kayna\u011f\u0131n adresini tan\u0131mlar.<\/p>\n<p>\u00d6rne\u011fin <code>ornek.com<\/code> bir domaindir. <code>https:\/\/ornek.com\/blog?v=2#dns<\/code> ise bir URL&#8217;dir. Bu URL i\u00e7indeki <code>ornek.com<\/code> b\u00f6l\u00fcm\u00fc domaindir; URL, bundan daha fazla bilgi ta\u015f\u0131r.<\/p>\n<p>Domain ve URL fark\u0131; DNS ayar\u0131, TLS sertifikas\u0131, y\u00f6nlendirme ve web sunucusu yap\u0131land\u0131r\u0131l\u0131rken belirginle\u015fir. Bir domain DNS \u00fczerinden IP adresine \u00e7\u00f6z\u00fcmlenir; URL ise taray\u0131c\u0131ya hangi protokolle, hangi host \u00fczerindeki hangi kayna\u011f\u0131n istenece\u011fini s\u00f6yler.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; Bir adresi de\u011ferlendirirken \u00f6nce host b\u00f6l\u00fcm\u00fcn\u00fc, ard\u0131ndan protokol\u00fc, portu, yolu ve parametreleri ayr\u0131 ayr\u0131 inceleyin.<\/p>\n<h2 id=\"url-hangi-parcalardan-olusur\">URL hangi par\u00e7alardan olu\u015fur?<\/h2>\n<p>URL s\u00f6zdizimi, IETF&#8217;nin RFC 3986 standard\u0131nda tan\u0131mlanan genel URI yap\u0131s\u0131na dayan\u0131r. Web taray\u0131c\u0131lar\u0131nda s\u0131k g\u00f6r\u00fclen URL bi\u00e7imi a\u015fa\u011f\u0131daki gibidir:<\/p>\n<pre><code>https:\/\/kullanici:sifre@www.ornek.com:8443\/magaza\/urun?id=42&amp;renk=mavi#yorumlar<\/code><\/pre>\n<p>Bu \u00f6rnekte her b\u00f6l\u00fcm\u00fcn ayr\u0131 bir g\u00f6revi vard\u0131r:<\/p>\n<table>\n<thead>\n<tr>\n<th>B\u00f6l\u00fcm<\/th>\n<th>\u00d6rnek<\/th>\n<th>G\u00f6revi<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>\u015eema<\/td>\n<td><code>https<\/code><\/td>\n<td>\u0130leti\u015fimde kullan\u0131lacak protokol\u00fc belirtir.<\/td>\n<\/tr>\n<tr>\n<td>Kullan\u0131c\u0131 bilgisi<\/td>\n<td><code>kullanici:sifre@<\/code><\/td>\n<td>URL i\u00e7inde ta\u015f\u0131nabilen, g\u00fcvenlik a\u00e7\u0131s\u0131ndan sak\u0131ncal\u0131 kimlik bilgisi b\u00f6l\u00fcm\u00fcd\u00fcr.<\/td>\n<\/tr>\n<tr>\n<td>Host<\/td>\n<td><code>www.ornek.com<\/code><\/td>\n<td>Sunucunun domain, hostname veya IP tabanl\u0131 adresidir.<\/td>\n<\/tr>\n<tr>\n<td>Port<\/td>\n<td><code>8443<\/code><\/td>\n<td>Ba\u011flant\u0131n\u0131n yap\u0131laca\u011f\u0131 a\u011f portunu belirtir.<\/td>\n<\/tr>\n<tr>\n<td>Path<\/td>\n<td><code>\/magaza\/urun<\/code><\/td>\n<td>Sunucuda istenen kaynak ya da uygulama rotas\u0131d\u0131r.<\/td>\n<\/tr>\n<tr>\n<td>Query<\/td>\n<td><code>?id=42&amp;renk=mavi<\/code><\/td>\n<td>Uygulamaya g\u00f6nderilen anahtar-de\u011fer parametreleridir.<\/td>\n<\/tr>\n<tr>\n<td>Fragment<\/td>\n<td><code>#yorumlar<\/code><\/td>\n<td>\u0130stemcide, \u00e7o\u011funlukla taray\u0131c\u0131da se\u00e7ilen b\u00f6l\u00fcm bilgisidir.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><code>https:\/\/ornek.com\/<\/code> ge\u00e7erli bir URL&#8217;dir ve domaini <code>ornek.com<\/code> de\u011feridir. URL&#8217;de port yaz\u0131lmad\u0131\u011f\u0131nda istemci \u015femaya g\u00f6re varsay\u0131lan portu kullan\u0131r: HTTP i\u00e7in genellikle TCP 80, HTTPS i\u00e7in TCP 443.<\/p>\n<p>Kullan\u0131c\u0131 ad\u0131 ve \u015fifreyi URL i\u00e7ine yazmak baz\u0131 istemcilerde teknik olarak m\u00fcmk\u00fcn olsa da tercih edilmemelidir. URL&#8217;ler taray\u0131c\u0131 ge\u00e7mi\u015finde, proxy kay\u0131tlar\u0131nda ve web sunucusu loglar\u0131nda g\u00f6r\u00fcnebilir. Baz\u0131 ortamlarda URL, referer bilgisinin par\u00e7as\u0131 olarak da ta\u015f\u0131nabilir.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; URL i\u00e7inde kimlik bilgisi ta\u015f\u0131may\u0131n; y\u00f6netim eri\u015fimi i\u00e7in HTTPS ve ayr\u0131 kimlik do\u011frulama mekanizmalar\u0131 kullan\u0131n.<\/p>\n<div class=\"aiw-callout aiw-callout-tip\">\n<p class=\"aiw-callout-label\">\u0130pucu<\/p>\n<p>Adres \u00e7ubu\u011fundaki URL&#039;yi incelerken \u015femadan sonraki host b\u00f6l\u00fcm\u00fcn\u00fc ay\u0131r\u0131n. E\u011fik \u00e7izgiden, soru i\u015faretinden veya diyez i\u015faretinden sonraki b\u00f6l\u00fcm path, query ya da fragment olabilir; DNS kayd\u0131 aran\u0131rken bu k\u0131s\u0131mlar\u0131 kullanmay\u0131n.<\/p>\n<\/div>\n<h2 id=\"domain-nedir-nasil-calisir\">Domain nedir, nas\u0131l \u00e7al\u0131\u015f\u0131r?<\/h2>\n<p>Domain, DNS hiyerar\u015fisindeki bir alan\u0131 insanlar i\u00e7in okunabilir bir adla ifade eder. DNS bu adlar\u0131 IPv4 veya IPv6 adreslerine ve MX, TXT, CNAME gibi di\u011fer kay\u0131tlara \u00e7\u00f6z\u00fcmlemek i\u00e7in kullan\u0131l\u0131r.<\/p>\n<p><code>www.ornek.com<\/code> ifadesini par\u00e7alara ay\u0131r\u0131rsak:<\/p>\n<ul>\n<li><strong>www:<\/strong> Hostname veya subdomain olarak kullan\u0131lan etikettir.<\/li>\n<li><strong>ornek:<\/strong> Alan ad\u0131n\u0131n ikinci seviye b\u00f6l\u00fcm\u00fcd\u00fcr.<\/li>\n<li><strong>com:<\/strong> \u00dcst seviye alan ad\u0131d\u0131r; TLD olarak adland\u0131r\u0131l\u0131r.<\/li>\n<\/ul>\n<p>Alan ad\u0131n\u0131n sa\u011f\u0131ndaki nokta, DNS k\u00f6k\u00fcn\u00fc temsil eder. Tam bi\u00e7im teknik olarak <code>www.ornek.com.<\/code> \u015feklinde yaz\u0131labilir; sondaki nokta g\u00fcnl\u00fck kullan\u0131mda \u00e7o\u011funlukla g\u00f6sterilmez.<\/p>\n<p>Domain kayd\u0131 ile web bar\u0131nd\u0131rma ayn\u0131 hizmet de\u011fildir. Domain, ad\u0131n kay\u0131t ve y\u00f6netim hakk\u0131n\u0131 sa\u011flar. Hosting veya VPS ise bu ad \u00fczerinden sunulacak uygulaman\u0131n ve verinin bar\u0131nd\u0131r\u0131ld\u0131\u011f\u0131 altyap\u0131d\u0131r.<\/p>\n<p>Bir domain kayd\u0131 i\u00e7in kay\u0131t kurulu\u015fu, yetkili nameserver&#8217;lar ve ilgili DNS kay\u0131tlar\u0131n\u0131n do\u011fru \u00e7al\u0131\u015fmas\u0131 gerekir. Web sitesinin \u00e7al\u0131\u015fmas\u0131 i\u00e7in \u00e7o\u011fu senaryoda A veya AAAA kayd\u0131, e-posta i\u00e7in MX kayd\u0131, alan ad\u0131 do\u011frulamalar\u0131 i\u00e7in TXT kayd\u0131 gerekir.<\/p>\n<p><code>dig +short ornek.com A<\/code> komutu A kayd\u0131n\u0131, <code>dig +short ornek.com AAAA<\/code> komutu IPv6 kayd\u0131n\u0131 g\u00f6sterir. Bo\u015f \u00e7\u0131kt\u0131, kayd\u0131n bulunmad\u0131\u011f\u0131n\u0131 veya sorgulanan DNS sunucusunun cevap vermedi\u011fini g\u00f6sterebilir; tek ba\u015f\u0131na web sunucusunun kapal\u0131 oldu\u011funu kan\u0131tlamaz.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; Web eri\u015fim sorununda \u00f6nce <code>dig +short<\/code> ile A, AAAA ve CNAME kay\u0131tlar\u0131n\u0131 kontrol edin; DNS ile HTTP katmanlar\u0131n\u0131 birbirine kar\u0131\u015ft\u0131rmay\u0131n.<\/p>\n<h2 id=\"bir-domain-ile-url-arasindaki-fark-nasil-anlasilir\">Bir domain ile URL aras\u0131ndaki fark nas\u0131l anla\u015f\u0131l\u0131r?<\/h2>\n<p>En pratik y\u00f6ntem, web adresini \u015femadan ba\u015flayarak soldan sa\u011fa ve hosttan sonraki b\u00f6l\u00fcmleri ay\u0131rarak okumakt\u0131r. URL i\u00e7indeki host b\u00f6l\u00fcm\u00fc domaini veya domain alt\u0131nda tan\u0131ml\u0131 bir hostname&#8217;i g\u00f6sterir. Path, sorgu ve fragment b\u00f6l\u00fcmleri domainin par\u00e7as\u0131 de\u011fildir.<\/p>\n<table>\n<thead>\n<tr>\n<th>Adres<\/th>\n<th>Domain veya host<\/th>\n<th>URL&#8217;nin ek bilgileri<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>ornek.com<\/code><\/td>\n<td><code>ornek.com<\/code><\/td>\n<td>Protokol, path ve parametre yoktur.<\/td>\n<\/tr>\n<tr>\n<td><code>https:\/\/ornek.com<\/code><\/td>\n<td><code>ornek.com<\/code><\/td>\n<td><code>https<\/code> \u015femas\u0131 eklenmi\u015ftir.<\/td>\n<\/tr>\n<tr>\n<td><code>https:\/\/blog.ornek.com\/yazi<\/code><\/td>\n<td><code>blog.ornek.com<\/code><\/td>\n<td><code>\/yazi<\/code> path bilgisidir.<\/td>\n<\/tr>\n<tr>\n<td><code>https:\/\/ornek.com:8443\/app<\/code><\/td>\n<td><code>ornek.com<\/code><\/td>\n<td>8443 portu ve <code>\/app<\/code> path&#8217;i vard\u0131r.<\/td>\n<\/tr>\n<tr>\n<td><code>https:\/\/ornek.com\/urun?id=8<\/code><\/td>\n<td><code>ornek.com<\/code><\/td>\n<td>Path ve <code>id=8<\/code> sorgusu vard\u0131r.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Burada k\u00fc\u00e7\u00fck ama kritik bir ayr\u0131nt\u0131 bulunur: <code>blog.ornek.com<\/code> ile <code>ornek.com<\/code> ayn\u0131 DNS alan\u0131 alt\u0131nda olabilir, fakat DNS&#8217;te ayr\u0131 hostname&#8217;ler olarak yap\u0131land\u0131r\u0131labilir. Her ikisi de ayn\u0131 IP&#8217;ye gidebilir; bu zorunlu de\u011fildir.<\/p>\n<p>Benzer bi\u00e7imde <code>ornek.com<\/code>, <code>www.ornek.com<\/code> ve <code>m.ornek.com<\/code> \u00fc\u00e7 farkl\u0131 host ad\u0131d\u0131r. Web sunucusu, TLS sertifikas\u0131 ve y\u00f6nlendirme kurallar\u0131 bu adlar\u0131 ayr\u0131 ayr\u0131 de\u011ferlendirebilir.<\/p>\n<p>Bir URL&#8217;nin ba\u015f\u0131nda g\u00f6r\u00fclen <code>https:\/\/<\/code> domain de\u011fildir. Bu b\u00f6l\u00fcm \u015femad\u0131r. Domain, host i\u00e7indeki alan ad\u0131 b\u00f6l\u00fcm\u00fcd\u00fcr; URL ise kayna\u011f\u0131n konumunu ve eri\u015fim y\u00f6ntemini birlikte bildirir.<\/p>\n<div class=\"aiw-callout aiw-callout-warn\">\n<p class=\"aiw-callout-label\">Dikkat<\/p>\n<p>www.ornek.com ile ornek.com ayn\u0131 adres kabul edilmemelidir. DNS kay\u0131tlar\u0131, TLS sertifikas\u0131 ve web sunucusunun sanal host kurallar\u0131 iki hostname i\u00e7in ayr\u0131 yap\u0131land\u0131r\u0131labilir.<\/p>\n<\/div>\n<h2 id=\"domain-hostname-ve-url-ayni-sey-midir\">Domain, hostname ve URL ayn\u0131 \u015fey midir?<\/h2>\n<p>Bu \u00fc\u00e7 kavram birbiriyle ili\u015fkili olsa da e\u015f anlaml\u0131 de\u011fildir.<\/p>\n<ul>\n<li><strong>Domain:<\/strong> DNS hiyerar\u015fisindeki alan ad\u0131 veya kay\u0131tl\u0131 ad b\u00f6lgesidir. \u00d6rnek: <code>ornek.com<\/code>.<\/li>\n<li><strong>Hostname:<\/strong> A\u011f \u00fczerinde belirli bir makineyi ya da hizmeti tan\u0131mlayan add\u0131r. \u00d6rnek: <code>vps01.ornek.com<\/code>.<\/li>\n<li><strong>FQDN:<\/strong> Hostname&#8217;in DNS hiyerar\u015fisiyle birlikte tam yaz\u0131lm\u0131\u015f bi\u00e7imidir. Sondaki k\u00f6k noktas\u0131 g\u00f6sterilirse <code>vps01.ornek.com.<\/code> olur.<\/li>\n<li><strong>URL:<\/strong> \u015eema, host, port ve kaynak yolunu birle\u015ftiren adrestir. \u00d6rnek: <code>https:\/\/vps01.ornek.com:8443\/panel<\/code>.<\/li>\n<\/ul>\n<p><code>vps01.ornek.com<\/code> bir hostname olabilir. Ayn\u0131 ifade, bir URL&#8217;nin host b\u00f6l\u00fcm\u00fc olarak da kullan\u0131labilir; fakat ba\u015f\u0131na <code>https:\/\/<\/code> ve gerekiyorsa path eklenmeden tek ba\u015f\u0131na tam URL say\u0131lmaz.<\/p>\n<p>DNS kayd\u0131 ile web URL&#8217;si farkl\u0131 katmanlara aittir. A kayd\u0131 bir hostname&#8217;i IPv4 adresine ba\u011flar. HTTP iste\u011fi ise URL&#8217;deki host ve path bilgilerini web sunucusuna iletir. Nginx gibi bir sunucu, ayn\u0131 IP \u00fczerinde gelen iste\u011fi <code>Host<\/code> ba\u015fl\u0131\u011f\u0131na g\u00f6re do\u011fru sanal sunucuya y\u00f6nlendirebilir.<\/p>\n<p>Bu ayr\u0131m, tek VPS \u00fczerinde birden fazla site bar\u0131nd\u0131r\u0131rken \u00f6zellikle \u00f6nemlidir. Her domain ayn\u0131 IP&#8217;ye i\u015faret edebilir; Nginx, iste\u011fin hangi domain i\u00e7in geldi\u011fini okuyarak farkl\u0131 document root veya uygulama upstream&#8217;i se\u00e7er.<\/p>\n<h2 id=\"https-dns-ve-yonlendirme-domain-url-iliskisini-nasil-degistirir\">HTTPS, DNS ve y\u00f6nlendirme domain-URL ili\u015fkisini nas\u0131l de\u011fi\u015ftirir?<\/h2>\n<p>HTTPS, domainin kendisi de\u011fildir. TLS ba\u011flant\u0131s\u0131, istemcinin se\u00e7ti\u011fi hostname i\u00e7in sertifika do\u011frulamas\u0131 yapar. Sertifikan\u0131n <code>ornek.com<\/code> ad\u0131na sahip olmas\u0131, <code>www.ornek.com<\/code> ad\u0131n\u0131 otomatik olarak kapsad\u0131\u011f\u0131 anlam\u0131na gelmez; sertifikada ilgili ad\u0131n veya uygun bir wildcard kayd\u0131n\u0131n bulunmas\u0131 gerekir.<\/p>\n<p>Taray\u0131c\u0131 <code>https:\/\/ornek.com\/urun<\/code> URL&#8217;sini a\u00e7arken kabaca \u015fu a\u015famalardan ge\u00e7er:<\/p>\n<ol>\n<li><strong>DNS \u00e7\u00f6z\u00fcmleme:<\/strong> <code>ornek.com<\/code> i\u00e7in A veya AAAA kayd\u0131 sorgulan\u0131r.<\/li>\n<li><strong>Ba\u011flant\u0131:<\/strong> HTTPS i\u00e7in genellikle TCP 443 portuna ba\u011flant\u0131 kurulur; HTTP\/3 kullan\u0131l\u0131yorsa UDP 443 \u00fczerinden QUIC devreye girebilir.<\/li>\n<li><strong>TLS do\u011frulamas\u0131:<\/strong> Sunucunun sertifikas\u0131, hostname ve ge\u00e7erlilik s\u00fcresi kontrol edilir.<\/li>\n<li><strong>HTTP iste\u011fi:<\/strong> Sunucuya host ve <code>\/urun<\/code> path&#8217;i g\u00f6nderilir.<\/li>\n<li><strong>Uygulama yan\u0131t\u0131:<\/strong> Sunucu i\u00e7erik, hata veya 301\/302 gibi y\u00f6nlendirme d\u00f6nd\u00fcr\u00fcr.<\/li>\n<\/ol>\n<p>Bir y\u00f6nlendirme URL&#8217;nin domainini de\u011fi\u015ftirebilir. <code>http:\/\/ornek.com<\/code> adresinin <code>https:\/\/www.ornek.com\/<\/code> adresine 301 ile y\u00f6nlendirilmesi, DNS kayd\u0131n\u0131n de\u011fi\u015fti\u011fi anlam\u0131na gelmez. DNS h\u00e2l\u00e2 eski IP&#8217;yi g\u00f6sterebilir; y\u00f6nlendirmeyi yapan web sunucusu veya CDN&#8217;dir.<\/p>\n<p>Alan ad\u0131 ge\u00e7i\u015flerinde DNS \u00f6nbellekleri ve TTL nedeniyle farkl\u0131 resolver&#8217;lar bir s\u00fcre farkl\u0131 cevaplar verebilir. DNS de\u011fi\u015fiklikleri s\u0131ras\u0131nda yaln\u0131zca taray\u0131c\u0131y\u0131 kontrol etmek yerine yetkili nameserver ile public resolver cevaplar\u0131n\u0131 ayr\u0131 test etmek gerekir. <a href=\"https:\/\/www.vps.tc\/blog\/tr\/dns-yayilmasi-ne-kadar-surer\/\">DNS Yay\u0131lmas\u0131 Nedir? Ne Kadar S\u00fcrer?<\/a> ba\u015fl\u0131kl\u0131 i\u00e7erik, bu \u00f6nbellekleme davran\u0131\u015f\u0131n\u0131 ayr\u0131ca ele al\u0131r.<\/p>\n<p>Bir sitenin HTTP&#8217;den HTTPS&#8217;ye ge\u00e7irilmesinde 301 y\u00f6nlendirmesi, canonical URL, sertifika kapsam\u0131 ve uygulaman\u0131n olu\u015fturdu\u011fu mutlak URL&#8217;ler birlikte kontrol edilmelidir. <a href=\"https:\/\/www.vps.tc\/blog\/tr\/301-yonlendirme-nedir-seo-kullanim-rehberi\/\">301 Y\u00f6nlendirme Nedir? SEO \u0130\u00e7in Kullan\u0131m Rehberi<\/a> i\u00e7inde kal\u0131c\u0131 y\u00f6nlendirmelerin kullan\u0131m alanlar\u0131 a\u00e7\u0131klan\u0131r.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; Y\u00f6nlendirme sorununda DNS cevab\u0131n\u0131, TLS sertifikas\u0131n\u0131 ve HTTP durum kodunu ayr\u0131 ayr\u0131 test edin.<\/p>\n<div class=\"aiw-callout aiw-callout-example\">\n<p class=\"aiw-callout-label\">\u00d6rnek<\/p>\n<p>Bir site ornek.com adresinden 203.0.113.10 IP&#039;sine, www.ornek.com adresinden ise CDN IP&#039;sine cevap verebilir. Taray\u0131c\u0131daki URL ayn\u0131 uygulamaya i\u015faret ediyor gibi g\u00f6r\u00fcnse de DNS ve y\u00f6nlendirme ak\u0131\u015f\u0131 farkl\u0131 olabilir.<\/p>\n<\/div>\n<h2 id=\"komut-satirindan-domain-ve-url-nasil-test-edilir\">Komut sat\u0131r\u0131ndan domain ve URL nas\u0131l test edilir?<\/h2>\n<p>Taray\u0131c\u0131, DNS \u00f6nbelle\u011fi ve eklentiler nedeniyle sorunu gizleyebilir. Temel testler terminalden daha a\u00e7\u0131k sonu\u00e7 verir.<\/p>\n<pre><code>dig +short example.com A\ndig +short www.example.com CNAME\ncurl -I https:\/\/www.example.com\/<\/code><\/pre>\n<p>\u0130lk iki komut DNS kay\u0131tlar\u0131n\u0131 g\u00f6sterir. <code>curl -I<\/code> yaln\u0131zca HTTP ba\u015fl\u0131klar\u0131n\u0131 ister; \u00e7\u0131kt\u0131da <code>HTTP\/2 200<\/code>, <code>301<\/code>, <code>302<\/code> veya <code>404<\/code> gibi durum kodlar\u0131 g\u00f6r\u00fclebilir. 301 veya 302, iste\u011fin ula\u015ft\u0131\u011f\u0131n\u0131 fakat ba\u015fka bir URL&#8217;ye y\u00f6nlendirildi\u011fini g\u00f6sterir.<\/p>\n<p>Y\u00f6nlendirme zincirini g\u00f6rmek i\u00e7in <code>-L<\/code> se\u00e7ene\u011fi kullan\u0131labilir:<\/p>\n<pre><code>curl -IL https:\/\/example.com\/<\/code><\/pre>\n<p>Bu komut her y\u00f6nlendirme ad\u0131m\u0131n\u0131n ba\u015fl\u0131klar\u0131n\u0131 g\u00f6sterir. Gereksiz iki veya \u00fc\u00e7 y\u00f6nlendirme, gecikmeyi art\u0131rabilir ve baz\u0131 uygulamalarda \u00e7erez veya canonical URL sorunlar\u0131na yol a\u00e7abilir.<\/p>\n<p>DNS&#8217;in hangi sunucudan cevap verdi\u011fini g\u00f6rmek i\u00e7in:<\/p>\n<pre><code>dig example.com A\ndig @1.1.1.1 example.com A\ndig @8.8.8.8 example.com A<\/code><\/pre>\n<p>\u0130lk sorgu sistemde tan\u0131ml\u0131 resolver&#8217;\u0131, di\u011ferleri belirli public resolver&#8217;lar\u0131 kullan\u0131r. Cevaplar farkl\u0131ysa TTL, \u00f6nbellek veya yetkili nameserver yap\u0131land\u0131rmas\u0131 incelenmelidir. <code>dig +short<\/code> okunabilirli\u011fi art\u0131r\u0131r; ayr\u0131nt\u0131l\u0131 te\u015fhis gerekti\u011finde k\u0131sa bi\u00e7im yerine tam \u00e7\u0131kt\u0131y\u0131 saklay\u0131n.<\/p>\n<p>Bir URL&#8217;de hangi hostun g\u00f6nderildi\u011fini test etmek i\u00e7in belirli IP&#8217;ye ba\u011flan\u0131rken host ad\u0131n\u0131 korumak m\u00fcmk\u00fcnd\u00fcr:<\/p>\n<pre><code>curl --resolve example.com:443:203.0.113.10 -I https:\/\/example.com\/<\/code><\/pre>\n<p><code>--resolve<\/code>, belirtilen host ve port i\u00e7in ge\u00e7ici bir IP e\u015flemesi kullan\u0131r; TLS ile HTTP iste\u011finde <code>example.com<\/code> ad\u0131n\u0131 korur. Staging IP&#8217;sindeki yeni yap\u0131land\u0131rmay\u0131 public DNS&#8217;i de\u011fi\u015ftirmeden s\u0131namak i\u00e7in kullan\u0131\u015fl\u0131d\u0131r.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; Sorunu \u00f6nce <code>dig<\/code> ile DNS katman\u0131nda, ard\u0131ndan <code>curl -I<\/code> ile HTTP ve y\u00f6nlendirme katman\u0131nda do\u011frulay\u0131n.<\/p>\n<div class=\"aiw-callout aiw-callout-field\">\n<p class=\"aiw-callout-label\">Sahadan not<\/p>\n<p>Bir staging hostname&#039;ini public DNS&#039;i de\u011fi\u015ftirmeden test etmek i\u00e7in curl &#8211;resolve staging.example.com:443:203.0.113.10 -I https:\/\/staging.example.com\/ komutunu \u00e7al\u0131\u015ft\u0131rd\u0131m. Sertifika do\u011fru hostname i\u00e7in d\u00f6nerken HTTP yan\u0131t\u0131 h\u00e2l\u00e2 eski sanal hostu g\u00f6steriyordu; b\u00f6ylece DNS&#039;i de\u011fil, Nginx server_name yap\u0131land\u0131rmas\u0131n\u0131 d\u00fczeltmem gerekti\u011fini g\u00f6rd\u00fcm.<\/p>\n<\/div>\n<h2 id=\"gunluk-kullanimda-yapilan-domain-ve-url-hatalari\">G\u00fcnl\u00fck kullan\u0131mda yap\u0131lan domain ve URL hatalar\u0131<\/h2>\n<p>En s\u0131k kar\u0131\u015ft\u0131r\u0131lan \u00f6rneklerden biri, path b\u00f6l\u00fcm\u00fcn\u00fc domain sanmakt\u0131r. <code>ornek.com\/blog<\/code> ifadesinde domain <code>ornek.com<\/code>, path ise <code>\/blog<\/code> b\u00f6l\u00fcm\u00fcd\u00fcr. DNS sunucusuna <code>\/blog<\/code> yolu g\u00f6nderilmez; DNS yaln\u0131zca host ad\u0131n\u0131 \u00e7\u00f6z\u00fcmler.<\/p>\n<p>\u0130kinci hata, <code>www<\/code> ile k\u00f6k domaini ayn\u0131 kabul etmektir. <code>www.ornek.com<\/code> i\u00e7in CNAME kayd\u0131 varken <code>ornek.com<\/code> i\u00e7in ayr\u0131ca A veya uygun DNS kayd\u0131 bulunmas\u0131 gerekebilir. K\u00f6k domain i\u00e7in CNAME kullan\u0131m\u0131, DNS sa\u011flay\u0131c\u0131s\u0131n\u0131n ALIAS veya ANAME benzeri \u00f6zel deste\u011fine ba\u011fl\u0131d\u0131r.<\/p>\n<p>\u00dc\u00e7\u00fcnc\u00fc hata, URL&#8217;deki sorgu parametrelerini g\u00fcvenilir bir eri\u015fim kontrol\u00fc sanmakt\u0131r. <code>\/download?file=rapor.pdf<\/code> bi\u00e7imindeki parametre, tek ba\u015f\u0131na yetkilendirme sa\u011flamaz. Uygulama sunucusu oturum ve izin kontrol\u00fc yapmal\u0131d\u0131r.<\/p>\n<p>D\u00f6rd\u00fcnc\u00fc hata, URL kodlamas\u0131n\u0131 atlamakt\u0131r. Bo\u015fluk, T\u00fcrk\u00e7e karakterler ve <code>&amp;<\/code> gibi \u00f6zel karakterler URL i\u00e7inde uygun \u015fekilde kodlanmal\u0131d\u0131r. Uygulama geli\u015ftirirken taray\u0131c\u0131n\u0131n adres \u00e7ubu\u011funda g\u00f6r\u00fcnen bi\u00e7im ile sunucunun ayr\u0131\u015ft\u0131rd\u0131\u011f\u0131 bi\u00e7im aras\u0131nda fark olu\u015fabilir.<\/p>\n<p>Be\u015finci hata, <code>http<\/code> ile <code>https<\/code> adreslerini ayn\u0131 kaynak sanmakt\u0131r. Taray\u0131c\u0131 a\u00e7\u0131s\u0131ndan bunlar farkl\u0131 origin&#8217;lerdir; origin, \u015fema, host ve port \u00fc\u00e7l\u00fcs\u00fcyle belirlenir. <code>https:\/\/ornek.com<\/code> ile <code>http:\/\/ornek.com<\/code> aras\u0131nda yaln\u0131zca bir harf fark\u0131 yoktur; g\u00fcvenlik modeli ve ba\u011flant\u0131 \u015fifrelemesi farkl\u0131d\u0131r.<\/p>\n<p>CDN kullan\u0131ld\u0131\u011f\u0131nda URL yine ayn\u0131 kalabilir, fakat DNS cevab\u0131 CDN edge IP&#8217;sini g\u00f6sterebilir. <a href=\"https:\/\/www.vps.tc\/blog\/tr\/cdn-nedir-web-sitesini-nasil-hizlandirir\/\">CDN Nedir? Web Sitesini Nas\u0131l H\u0131zland\u0131r\u0131r?<\/a> i\u00e7eri\u011finde anlat\u0131ld\u0131\u011f\u0131 gibi, kullan\u0131c\u0131 ile origin sunucu aras\u0131na bir da\u011f\u0131t\u0131m katman\u0131 eklenmesi domain tan\u0131m\u0131n\u0131 de\u011fi\u015ftirmez; istek ak\u0131\u015f\u0131n\u0131 de\u011fi\u015ftirir.<\/p>\n<h2 id=\"domain-ve-url-farki-icin-kisa-karar-tablosu\">Domain ve URL fark\u0131 i\u00e7in k\u0131sa karar tablosu<\/h2>\n<p>Bir kavram\u0131n hangi durumda kullan\u0131laca\u011f\u0131n\u0131 a\u015fa\u011f\u0131daki tabloyla h\u0131zl\u0131ca ay\u0131rabilirsiniz:<\/p>\n<table>\n<thead>\n<tr>\n<th>Soru<\/th>\n<th>Bak\u0131lacak kavram<\/th>\n<th>\u00d6rnek<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Alan ad\u0131 kay\u0131tl\u0131 m\u0131?<\/td>\n<td>Domain<\/td>\n<td><code>ornek.com<\/code><\/td>\n<\/tr>\n<tr>\n<td>Hangi IP&#8217;ye \u00e7\u00f6z\u00fcl\u00fcyor?<\/td>\n<td>DNS kayd\u0131<\/td>\n<td><code>A<\/code> veya <code>AAAA<\/code><\/td>\n<\/tr>\n<tr>\n<td>Hangi protokol kullan\u0131lacak?<\/td>\n<td>URL \u015femas\u0131<\/td>\n<td><code>https:\/\/<\/code><\/td>\n<\/tr>\n<tr>\n<td>Hangi sayfa veya API \u00e7a\u011fr\u0131lacak?<\/td>\n<td>URL path&#8217;i<\/td>\n<td><code>\/api\/users<\/code><\/td>\n<\/tr>\n<tr>\n<td>Hangi filtre g\u00f6nderilecek?<\/td>\n<td>Query string<\/td>\n<td><code>?page=2<\/code><\/td>\n<\/tr>\n<tr>\n<td>Sayfan\u0131n hangi b\u00f6l\u00fcm\u00fc a\u00e7\u0131lacak?<\/td>\n<td>Fragment<\/td>\n<td><code>#yorumlar<\/code><\/td>\n<\/tr>\n<tr>\n<td>Hangi uygulamaya y\u00f6nlenecek?<\/td>\n<td>Host ve web sunucusu kural\u0131<\/td>\n<td><code>api.ornek.com<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>K\u0131sa form\u00fclle ifade edilirse: domain, URL&#8217;nin host taraf\u0131ndaki alan ad\u0131d\u0131r; URL ise bu hosta hangi y\u00f6ntemle ve hangi kayna\u011fa eri\u015filece\u011fini tarif eden tam adrestir. Her domain bir URL de\u011fildir. Her URL&#8217;nin host b\u00f6l\u00fcm\u00fcnde domain bulunmas\u0131 da zorunlu de\u011fildir; IP adresi veya localhost da kullan\u0131labilir.<\/p>\n<p>\u00d6rne\u011fin <code>http:\/\/127.0.0.1:8080\/test<\/code> ge\u00e7erli bir URL&#8217;dir, fakat i\u00e7inde kay\u0131tl\u0131 domain yoktur. Host b\u00f6l\u00fcm\u00fc IPv4 adresidir. Ayn\u0131 \u015fekilde <code>file:\/\/\/home\/user\/not.txt<\/code> bir URL bi\u00e7imidir; web domaini i\u00e7ermez.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; Dok\u00fcmantasyonda &#8220;domain&#8221; dedi\u011finizde alan ad\u0131n\u0131, &#8220;URL&#8221; dedi\u011finizde ise \u015fema ve kaynak yolu dahil tam adresi yaz\u0131n.<\/p>\n<h2 id=\"domain-ve-url-kontrol-listesi\">Domain ve URL Kontrol Listesi<\/h2>\n<ul class=\"aiw-checklist\">\n<li>Domain ile URL&#039;yi ayr\u0131 kavramlar olarak adland\u0131r\u0131n.<\/li>\n<li>A ve AAAA DNS kay\u0131tlar\u0131n\u0131 dig ile kontrol edin.<\/li>\n<li>www ve k\u00f6k domain i\u00e7in ayr\u0131 DNS cevaplar\u0131n\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/li>\n<li>URL&#039;nin \u015fema, port, host, path ve query b\u00f6l\u00fcmlerini ay\u0131r\u0131n.<\/li>\n<li>HTTPS sertifikas\u0131n\u0131n kullan\u0131lan hostname&#039;i kapsad\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n.<\/li>\n<li>curl -I ve curl -IL ile HTTP durum kodlar\u0131n\u0131 ve y\u00f6nlendirmeleri inceleyin.<\/li>\n<li>DNS sorunu ile web sunucusu sorununu ayr\u0131 test sonu\u00e7lar\u0131yla te\u015fhis edin.<\/li>\n<\/ul>\n<div class=\"aiw-cta\">\n<p>Bir sonraki DNS veya HTTPS sorununda adresi tek par\u00e7a olarak de\u011fil, \u015fema, host, port ve path katmanlar\u0131na ay\u0131rarak inceleyin. \u0130ki dakikal\u0131k bir dig ve curl kontrol\u00fc, panelde uzun s\u00fcre aramaktan daha net bir ba\u015flang\u0131\u00e7 sa\u011flayabilir.<\/p>\n<p class=\"aiw-cta-action\"><a href=\"https:\/\/www.vps.tc\/tr\/vps\">VPS paketlerini inceleyin<\/a><\/p>\n<\/div>\n<h2 id=\"sik-sorulan-sorular\">S\u0131k Sorulan Sorular<\/h2>\n<div class=\"aiw-faq\">\n<details class=\"aiw-faq-item\" open>\n<summary>Domain nedir?<\/summary>\n<p>Domain, internette bir alan\u0131 veya hizmeti insanlar i\u00e7in okunabilir bir adla tan\u0131mlayan isimdir. ornek.com bir domaindir. DNS bu ad\u0131 A, AAAA, MX veya TXT gibi kay\u0131tlarla IP adresi ya da ba\u015fka hizmet bilgilerine ba\u011flar. Domain kayd\u0131 tek ba\u015f\u0131na web sitesi bar\u0131nd\u0131rmaz; site i\u00e7in hosting, VPS veya ba\u015fka bir sunucu hizmeti de gerekir.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>URL nedir?<\/summary>\n<p>URL, belirli bir kayna\u011fa nas\u0131l eri\u015filece\u011fini ve kayna\u011f\u0131n nerede bulundu\u011funu g\u00f6steren tam adrestir. https:\/\/ornek.com\/urun?id=7 \u00f6rne\u011finde https \u015fema, ornek.com host, \/urun path ve id=7 sorgu parametresidir. URL i\u00e7inde domain bulunabilir, fakat URL domainle s\u0131n\u0131rl\u0131 de\u011fildir; port, path ve fragment gibi b\u00f6l\u00fcmler de ta\u015f\u0131yabilir.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Domain ve URL aras\u0131ndaki fark nedir?<\/summary>\n<p>Domain yaln\u0131zca alan ad\u0131 b\u00f6l\u00fcm\u00fcn\u00fc ifade eder; URL ise protokol, host, port, path, sorgu ve fragment bilgilerini bir arada ta\u015f\u0131yabilir. ornek.com domain \u00f6rne\u011fidir. https:\/\/ornek.com\/blog?id=2 tam URL \u00f6rne\u011fidir. Bu nedenle her domain URL&#039;nin bir par\u00e7as\u0131 olabilir, ancak domain tek ba\u015f\u0131na tam URL olmak zorunda de\u011fildir.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>www bir domain midir?<\/summary>\n<p>www \u00e7o\u011fu durumda domainin \u00f6n\u00fcnde kullan\u0131lan bir subdomain veya hostname etiketidir. www.ornek.com tam hostname iken ornek.com k\u00f6k domain olarak adland\u0131r\u0131l\u0131r. Bu iki ad ayn\u0131 IP&#039;ye y\u00f6nlenebilir, farkl\u0131 IP&#039;lere de gidebilir. DNS kay\u0131tlar\u0131 ve TLS sertifikalar\u0131 yap\u0131land\u0131r\u0131l\u0131rken www ile k\u00f6k domainin ayr\u0131 kontrol edilmesi gerekir.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>URL&#039;de domain nerede bulunur?<\/summary>\n<p>URL&#039;de domain, \u015fema olan https:\/\/ veya http:\/\/ b\u00f6l\u00fcm\u00fcnden sonra, ilk e\u011fik \u00e7izgi, soru i\u015fareti ya da diyez i\u015faretinden \u00f6nce yer al\u0131r. https:\/\/blog.ornek.com\/yazi?id=3 adresinde host blog.ornek.com&#039;dur. \/yazi path, id=3 query b\u00f6l\u00fcm\u00fcd\u00fcr. Port yaz\u0131lm\u0131\u015fsa hosttan sonra iki nokta ile ayr\u0131l\u0131r; \u00f6rne\u011fin :8443.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Domain de\u011fi\u015fince URL de de\u011fi\u015fir mi?<\/summary>\n<p>Domain de\u011fi\u015firse URL&#039;nin host b\u00f6l\u00fcm\u00fc de\u011fi\u015fir, fakat path ve sorgu b\u00f6l\u00fcmleri ayn\u0131 kalabilir. \u00d6rne\u011fin eski.com\/urun\/5 adresi yeni.com\/urun\/5 adresine y\u00f6nlendirilebilir. DNS kay\u0131tlar\u0131, TLS sertifikas\u0131, web sunucusu sanal host ayarlar\u0131, uygulaman\u0131n olu\u015fturdu\u011fu ba\u011flant\u0131lar ve gerekirse 301 y\u00f6nlendirmeleri birlikte g\u00fcncellenmelidir.<\/p>\n<\/details>\n<\/div>\n<h2 id=\"kaynaklar\">Kaynaklar<\/h2>\n<ul class=\"aiw-sources\">\n<li><a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc3986\" target=\"_blank\" rel=\"noopener\">IETF RFC 3986 &#8211; Uniform Resource Identifier<\/a> \u2014 rfc-editor.org<\/li>\n<li><a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Learn\/Common_questions\/Web_mechanics\/What_is_a_URL\" target=\"_blank\" rel=\"noopener\">MDN &#8211; What is a URL?<\/a> \u2014 developer.mozilla.org<\/li>\n<li><a href=\"https:\/\/icann.org\/\" target=\"_blank\" rel=\"noopener\">ICANN &#8211; Domain Name Basics<\/a> \u2014 icann.org<\/li>\n<li><a href=\"https:\/\/www.iana.org\/domains\/root\" target=\"_blank\" rel=\"noopener\">IANA &#8211; Root Zone Management<\/a> \u2014 iana.org<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Domain, DNS \u00fczerinde kullan\u0131lan alan ad\u0131d\u0131r; URL ise protokol, host, port ve kaynak yolunu birle\u015ftiren tam web adresidir. Fark\u0131 \u00f6rnekler ve terminal komutlar\u0131yla a\u00e7\u0131kl\u0131yoruz.<\/p>\n","protected":false},"author":2,"featured_media":1015,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[111],"tags":[],"class_list":["post-1017","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-domain"],"lang":"tr","translations":{"tr":1017,"en":1018},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/1017","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/comments?post=1017"}],"version-history":[{"count":1,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/1017\/revisions"}],"predecessor-version":[{"id":1019,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/1017\/revisions\/1019"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media\/1015"}],"wp:attachment":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media?parent=1017"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/categories?post=1017"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/tags?post=1017"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}