{"id":3845,"date":"2025-12-31T20:16:57","date_gmt":"2025-12-31T17:16:57","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/gelismis-spf-yonetimi-10-dns-lookup-limitine-takilmadan-coklu-e-posta-servisi-kullanmak\/"},"modified":"2025-12-31T20:16:57","modified_gmt":"2025-12-31T17:16:57","slug":"gelismis-spf-yonetimi-10-dns-lookup-limitine-takilmadan-coklu-e-posta-servisi-kullanmak","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/gelismis-spf-yonetimi-10-dns-lookup-limitine-takilmadan-coklu-e-posta-servisi-kullanmak\/","title":{"rendered":"Geli\u015fmi\u015f SPF Y\u00f6netimi: 10 DNS Lookup Limitine Tak\u0131lmadan \u00c7oklu E\u2011Posta Servisi Kullanmak"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><p>Alan ad\u0131n\u0131zdan hem kendi sunucunuzdan, hem CRM sisteminizden, hem de pazarlama ara\u00e7lar\u0131n\u0131zdan e\u2011posta g\u00f6nderiyorsan\u0131z, bir noktada SPF kayd\u0131n\u0131n s\u0131n\u0131rlar\u0131na toslaman\u0131z neredeyse ka\u00e7\u0131n\u0131lmazd\u0131r. Test ara\u00e7lar\u0131nda g\u00f6rd\u00fc\u011f\u00fcn\u00fcz &#8216;Too many DNS lookups&#8217; veya &#8216;PermError: DNS lookup limit exceeded&#8217; uyar\u0131lar\u0131, bir yandan teslim edilebilirli\u011fi d\u00fc\u015f\u00fcr\u00fcrken di\u011fer yandan da nereden ba\u015flayaca\u011f\u0131n\u0131z\u0131 bilemedi\u011finiz karma\u015f\u0131k bir tablo yarat\u0131r.<\/p>\n<p>Bu yaz\u0131da, DCHost ekibi olarak sahada en \u00e7ok g\u00f6rd\u00fc\u011f\u00fcm\u00fcz problemler \u00fczerinden gidece\u011fiz ve &#8217;10 DNS lookup limitine tak\u0131lmadan&#8217; birden fazla e\u2011posta servisini ayn\u0131 alan ad\u0131nda nas\u0131l do\u011fru tan\u0131mlayabilece\u011finizi ad\u0131m ad\u0131m anlataca\u011f\u0131z. SPF&#8217;in temel mant\u0131\u011f\u0131ndan \u00e7ok, ger\u00e7ek hayatta kar\u015f\u0131m\u0131za \u00e7\u0131kan senaryolara, tipik yanl\u0131\u015f konfig\u00fcrasyonlara, delegasyon ve ayr\u0131 alan ad\u0131 kullanma stratejilerine, SPF flattening mimarisine ve IPv6 ile birlikte planlama detaylar\u0131na odaklanaca\u011f\u0131z. E\u011fer elinizde \u015fu anda \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olamad\u0131\u011f\u0131n\u0131z, birden fazla &#8216;include&#8217; i\u00e7eren karma\u015f\u0131k bir SPF kayd\u0131 varsa, yaz\u0131n\u0131n sonunda onu sade, okunabilir ve RFC&#8217;ye uygun hale getirebilecek net bir yol haritan\u0131z olacak.<\/p>\n<div id=\"toc_container\" class=\"toc_transparent no_bullets\"><p class=\"toc_title\">\u0130&ccedil;indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#SPF_ve_10_DNS_Lookup_Siniri_Gercekte_Ne_Anlama_Geliyor\"><span class=\"toc_number toc_depth_1\">1<\/span> SPF ve 10 DNS Lookup S\u0131n\u0131r\u0131 Ger\u00e7ekte Ne Anlama Geliyor?<\/a><\/li><li><a href=\"#Birden_Fazla_EPosta_Servisi_Kullanan_Sirketlerin_Tipik_SPF_Sorunlari\"><span class=\"toc_number toc_depth_1\">2<\/span> Birden Fazla E\u2011Posta Servisi Kullanan \u015eirketlerin Tipik SPF Sorunlar\u0131<\/a><\/li><li><a href=\"#10_Lookup_Limitine_Takilmadan_SPF_Kaydi_Tasarlama_Adimlari\"><span class=\"toc_number toc_depth_1\">3<\/span> 10 Lookup Limitine Tak\u0131lmadan SPF Kayd\u0131 Tasarlama Ad\u0131mlar\u0131<\/a><ul><li><a href=\"#1_Tum_Gonderim_Kaynaklarini_Envanterleyin\"><span class=\"toc_number toc_depth_2\">3.1<\/span> 1. T\u00fcm G\u00f6nderim Kaynaklar\u0131n\u0131 Envanterleyin<\/a><\/li><li><a href=\"#2_Include_Yerine_IP_ve_AMX_Kullanabileceginiz_Yerleri_Ayiklayin\"><span class=\"toc_number toc_depth_2\">3.2<\/span> 2. Include Yerine IP ve A\/MX Kullanabilece\u011finiz Yerleri Ay\u0131klay\u0131n<\/a><\/li><li><a href=\"#3_Gereksiz_Include8217lari_Temizleyin\"><span class=\"toc_number toc_depth_2\">3.3<\/span> 3. Gereksiz Include&#8217;lar\u0131 Temizleyin<\/a><\/li><li><a href=\"#4_8216redirect8217_ve_8216exists8217_Mekanizmalarini_Dikkatli_Kullanin\"><span class=\"toc_number toc_depth_2\">3.4<\/span> 4. &#8216;redirect&#8217; ve &#8216;exists&#8217; Mekanizmalar\u0131n\u0131 Dikkatli Kullan\u0131n<\/a><\/li><\/ul><\/li><li><a href=\"#Delegasyon_Ayri_Alan_Adlari_ve_Subdomain_Stratejileri\"><span class=\"toc_number toc_depth_1\">4<\/span> Delegasyon, Ayr\u0131 Alan Adlar\u0131 ve Subdomain Stratejileri<\/a><ul><li><a href=\"#Transactional_Pazarlama_ve_Operasyonel_Mailleri_Ayirin\"><span class=\"toc_number toc_depth_2\">4.1<\/span> Transactional, Pazarlama ve Operasyonel Mailleri Ay\u0131r\u0131n<\/a><\/li><li><a href=\"#DMARC_Hizalamasini_Korumak\"><span class=\"toc_number toc_depth_2\">4.2<\/span> DMARC Hizalamas\u0131n\u0131 Korumak<\/a><\/li><li><a href=\"#Alt_Domainleri_Farkli_SPF_Politikalarina_Yonlendirmek\"><span class=\"toc_number toc_depth_2\">4.3<\/span> Alt Domainleri Farkl\u0131 SPF Politikalar\u0131na Y\u00f6nlendirmek<\/a><\/li><\/ul><\/li><li><a href=\"#SPF_Flattening_Lookup_Sayisini_Dusurmenin_Otomatik_Yolu\"><span class=\"toc_number toc_depth_1\">5<\/span> SPF Flattening: Lookup Say\u0131s\u0131n\u0131 D\u00fc\u015f\u00fcrmenin Otomatik Yolu<\/a><ul><li><a href=\"#Statik_Flattening_Ne_Zaman_Tehlikeli\"><span class=\"toc_number toc_depth_2\">5.1<\/span> Statik Flattening Ne Zaman Tehlikeli?<\/a><\/li><li><a href=\"#Otomatik_Dinamik_SPF_Flattening_Mimarisinin_Mantigi\"><span class=\"toc_number toc_depth_2\">5.2<\/span> Otomatik \/ Dinamik SPF Flattening Mimarisinin Mant\u0131\u011f\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#EPosta_Yonlendirme_SRSARC_ve_SPF_Iliskisi\"><span class=\"toc_number toc_depth_1\">6<\/span> E\u2011Posta Y\u00f6nlendirme, SRS\/ARC ve SPF \u0130li\u015fkisi<\/a><\/li><li><a href=\"#IPv6_ile_SPF_Reverse_DNS_ve_Yedeklilik\"><span class=\"toc_number toc_depth_1\">7<\/span> IPv6 ile SPF, Reverse DNS ve Yedeklilik<\/a><\/li><li><a href=\"#DCHost_Tarafinda_Gelismis_SPF_Yonetimini_Nasil_Kurguluyoruz\"><span class=\"toc_number toc_depth_1\">8<\/span> DCHost Taraf\u0131nda Geli\u015fmi\u015f SPF Y\u00f6netimini Nas\u0131l Kurguluyoruz?<\/a><\/li><li><a href=\"#Ozet_ve_Sonraki_Adimlar\"><span class=\"toc_number toc_depth_1\">9<\/span> \u00d6zet ve Sonraki Ad\u0131mlar<\/a><\/li><\/ul><\/div>\n<h2><span id=\"SPF_ve_10_DNS_Lookup_Siniri_Gercekte_Ne_Anlama_Geliyor\">SPF ve 10 DNS Lookup S\u0131n\u0131r\u0131 Ger\u00e7ekte Ne Anlama Geliyor?<\/span><\/h2>\n<p>SPF (Sender Policy Framework), al\u0131c\u0131 mail sunucular\u0131na &#8216;Bu alan ad\u0131 ad\u0131na e\u2011posta g\u00f6ndermeye kimlerin yetkili oldu\u011funu&#8217; DNS \u00fczerinden ilan etmenin standart yoludur. TXT kayd\u0131 olarak tan\u0131mlanan SPF kayd\u0131, gelen e\u2011postan\u0131n kayna\u011f\u0131n\u0131 kontrol etmek i\u00e7in \u00e7e\u015fitli mekanizmalar kullan\u0131r: ip4, ip6, a, mx, include, exists, ptr, redirect gibi.<\/p>\n<p>RFC 7208&#8217;e g\u00f6re SPF de\u011ferlendirmesi s\u0131ras\u0131nda <strong>en fazla 10 DNS lookup<\/strong> yap\u0131lmas\u0131na izin verilir. Bu s\u0131n\u0131r\u0131 a\u015farsan\u0131z SPF sonucu <strong>PermError<\/strong> olur; yani kay\u0131t &#8216;ge\u00e7ersiz&#8217; kabul edilir. \u00c7o\u011fu al\u0131c\u0131 sunucu PermError durumunda SPF&#8217;i yok sayar; dolay\u0131s\u0131yla DMARC ile SPF&#8217;e g\u00fcveniyorsan\u0131z, teslim edilebilirlik ciddi \u015fekilde zarar g\u00f6rebilir.<\/p>\n<p>Lookup s\u0131n\u0131r\u0131, <strong>DNS sorgusu olu\u015fturan mekanizmalar<\/strong> i\u00e7in ge\u00e7erlidir. Say\u0131lanlar:<\/p>\n<ul>\n<li><strong>include:<\/strong> Ba\u015fka bir alan ad\u0131n\u0131n SPF kayd\u0131n\u0131 i\u00e7e al\u0131r (1 lookup)<\/li>\n<li><strong>a:<\/strong> Alan ad\u0131n\u0131n A\/AAAA kayd\u0131n\u0131 \u00e7\u00f6zer (1 lookup)<\/li>\n<li><strong>mx:<\/strong> MX kayd\u0131n\u0131 ve ard\u0131ndan onun A\/AAAA kay\u0131tlar\u0131n\u0131 \u00e7\u00f6zer (en az 1, \u00e7o\u011fu zaman daha fazla lookup)<\/li>\n<li><strong>exists:<\/strong> Verilen domaini ger\u00e7ekten \u00e7\u00f6z\u00fcp \u00e7\u00f6z\u00fclmedi\u011fini kontrol eder (1 lookup)<\/li>\n<li><strong>ptr:<\/strong> Reverse DNS sorgusu yapar (1 lookup, fakat zaten \u00f6nerilmiyor)<\/li>\n<li><strong>redirect=<\/strong> Ba\u015fka bir alan\u0131n SPF kayd\u0131na y\u00f6nlendirir (1 lookup)<\/li>\n<\/ul>\n<p><strong>ip4, ip6, all<\/strong> gibi mekanizmalar ek DNS sorgusu \u00fcretmez, dolay\u0131s\u0131yla lookup limitini etkilemez. S\u0131n\u0131r\u0131 a\u015fman\u0131za sebep olan genellikle \u00e7ok say\u0131da include ve i\u00e7 i\u00e7e include zincirleridir. Bir servis sizden &#8216;include:spf.servisadi.com&#8217; eklemenizi ister, o SPF kayd\u0131n\u0131n i\u00e7inde de 6\u20137 farkl\u0131 include daha \u00e7\u0131kar ve toplam say\u0131y\u0131 kolayca 10&#8217;un \u00fczerine ta\u015f\u0131rs\u0131n\u0131z.<\/p>\n<h2><span id=\"Birden_Fazla_EPosta_Servisi_Kullanan_Sirketlerin_Tipik_SPF_Sorunlari\">Birden Fazla E\u2011Posta Servisi Kullanan \u015eirketlerin Tipik SPF Sorunlar\u0131<\/span><\/h2>\n<p>DCHost taraf\u0131nda hem <a href=\"https:\/\/www.dchost.com\/tr\/web-hosting\">payla\u015f\u0131ml\u0131 hosting<\/a> hem <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a> hem de kendi MTA&#8217;s\u0131n\u0131 y\u00f6neten kurumsal m\u00fc\u015fterilerle \u00e7al\u0131\u015f\u0131rken en s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz SPF problemlerini \u00f6zetleyelim:<\/p>\n<ul>\n<li>Kendi mail sunucusu + bir CRM + bir pazarlama arac\u0131 + bir yard\u0131m masas\u0131 yaz\u0131l\u0131m\u0131 gibi <strong>3\u20135 farkl\u0131 kaynaktan e\u2011posta g\u00f6nderimi<\/strong><\/li>\n<li>Her servisin d\u00f6k\u00fcmantasyonundaki &#8216;\u015eu include&#8217;u ekleyin&#8217; \u00f6nerilerine k\u00f6r\u00fc k\u00f6r\u00fcne uyup <strong>8\u201310 farkl\u0131 include<\/strong> kullanmak<\/li>\n<li>Her include i\u00e7indeki SPF kayd\u0131n\u0131n da birden fazla include i\u00e7ermesi ve <strong>i\u00e7 i\u00e7e zincirler<\/strong> olu\u015fmas\u0131<\/li>\n<li>Subdomain yerine her \u015feyi k\u00f6k alan ad\u0131nda toplamak; hem g\u00f6nderim domaini, hem Return\u2011Path, hem SPF i\u00e7in tek domain kullanmak<\/li>\n<li>Eski, art\u0131k kullan\u0131lmayan servislerin SPF&#8217;te unutulmas\u0131; yani <strong>teknik bor\u00e7 birikmesi<\/strong><\/li>\n<\/ul>\n<p>Sonu\u00e7 \u00e7o\u011funlukla \u015f\u00f6yle oluyor:<\/p>\n<ul>\n<li>SPF test ara\u00e7lar\u0131nda &#8216;PermError: too many DNS lookups&#8217; veya &#8216;Maximum hops exceeded&#8217; uyar\u0131lar\u0131<\/li>\n<li>DMARC raporlar\u0131nda &#8216;SPF temperror\/permerror&#8217; sat\u0131rlar\u0131n\u0131n artmas\u0131<\/li>\n<li>Baz\u0131 al\u0131c\u0131lara giden maillerin spam&#8217;e d\u00fc\u015fmesi, baz\u0131lar\u0131n\u0131n ise SPF&#8217;i yok saymas\u0131 nedeniyle <strong>tutars\u0131z teslim edilebilirlik<\/strong><\/li>\n<\/ul>\n<p>Temel SPF mant\u0131\u011f\u0131n\u0131 \u00f6\u011frenmek i\u00e7in \u00f6nce <a href=\"https:\/\/www.dchost.com\/blog\/spf-dkim-ve-dmarc-nedir-ozel-alan-adi-ile-e-posta-dogrulamasini-cpanel-ve-vpste-sifirdan-kurmak\/\">SPF, DKIM ve DMARC do\u011frulamas\u0131n\u0131 s\u0131f\u0131rdan kurma rehberimizi<\/a> okuman\u0131z iyi bir ba\u015flang\u0131\u00e7 olur. Bu yaz\u0131da ise <strong>ileri seviye<\/strong> konfig\u00fcrasyona ve optimizasyona odaklanaca\u011f\u0131z.<\/p>\n<h2><span id=\"10_Lookup_Limitine_Takilmadan_SPF_Kaydi_Tasarlama_Adimlari\">10 Lookup Limitine Tak\u0131lmadan SPF Kayd\u0131 Tasarlama Ad\u0131mlar\u0131<\/span><\/h2>\n<h3><span id=\"1_Tum_Gonderim_Kaynaklarini_Envanterleyin\">1. T\u00fcm G\u00f6nderim Kaynaklar\u0131n\u0131 Envanterleyin<\/span><\/h3>\n<p>\u00d6nce hangi sistemlerin hangi alan ad\u0131 ad\u0131na e\u2011posta g\u00f6nderdi\u011fini netle\u015ftirmeniz gerekiyor. S\u0131kl\u0131kla atlanan kaynaklar \u015funlar:<\/p>\n<ul>\n<li>Web sitenizin ileti\u015fim formlar\u0131 (PHP mail, SMTP eklentileri)<\/li>\n<li>E\u2011ticaret sitenizin sipari\u015f, fatura ve bildirim mailleri<\/li>\n<li>CRM ve pazarlama otomasyonu ara\u00e7lar\u0131<\/li>\n<li>Destek\/ticket sistemleri<\/li>\n<li>Sunucu izleme ara\u00e7lar\u0131, backup bildirimleri, cron raporlar\u0131<\/li>\n<\/ul>\n<p>Her biri i\u00e7in \u015fu bilgileri toplay\u0131n:<\/p>\n<ul>\n<li>G\u00f6nderen domain (From: alan\u0131ndaki alan ad\u0131)<\/li>\n<li>Return\u2011Path \/ MAIL FROM alan ad\u0131 (\u00e7o\u011fu zaman farkl\u0131d\u0131r)<\/li>\n<li>Hizmet taraf\u0131ndan \u00f6nerilen SPF include veya IP listesi<\/li>\n<li>Kendi kontrol\u00fcn\u00fczde olan IP&#8217;ler (\u00f6rne\u011fin DCHost \u00fczerindeki VPS veya mail sunucunuz)<\/li>\n<\/ul>\n<h3><span id=\"2_Include_Yerine_IP_ve_AMX_Kullanabileceginiz_Yerleri_Ayiklayin\">2. Include Yerine IP ve A\/MX Kullanabilece\u011finiz Yerleri Ay\u0131klay\u0131n<\/span><\/h3>\n<p>SPF lookup say\u0131s\u0131n\u0131 d\u00fc\u015f\u00fcrmenin en etkili y\u00f6ntemi, <strong>kendi kontrol\u00fcn\u00fczde olan IP adreslerini do\u011frudan SPF&#8217;e yazmakt\u0131r<\/strong>. \u00d6rne\u011fin alan ad\u0131n\u0131z\u0131n mail.sunucu.com gibi bir alt alan\u0131ndan, DCHost \u00fczerindeki bir VPS&#8217;ten e\u2011posta g\u00f6nderiyorsan\u0131z, \u00e7o\u011fu zaman \u015fu se\u00e7enekleriniz vard\u0131r:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">v=spf1 ip4:1.2.3.4 -all\n<\/code><\/pre>\n<p>veya<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">v=spf1 a:mail.sunucu.com -all\n<\/code><\/pre>\n<p>Burada:<\/p>\n<ul>\n<li>ip4 mekanizmas\u0131 ek DNS lookup \u00fcretmez.<\/li>\n<li>a:mail.sunucu.com bir kez lookup yapar, fakat bu alan\u0131n IP&#8217;si sizin elinizdedir.<\/li>\n<\/ul>\n<p>Klasik hata: Ayn\u0131 IP&#8217;yi hem MX, hem A kayd\u0131, hem de SPF include \u00fczerinden dolayl\u0131 yoldan tan\u0131mlamak. \u00d6rne\u011fin:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">v=spf1 mx include:mail.dchost-musteri.com a -all\n<\/code><\/pre>\n<p>Bunun yerine, hangi IP&#8217;lerden ger\u00e7ekten g\u00f6nderim yap\u0131ld\u0131\u011f\u0131n\u0131 tespit edip SPF&#8217;i sadele\u015ftirmek genellikle hem lookup say\u0131s\u0131n\u0131 hem de kar\u0131\u015f\u0131kl\u0131\u011f\u0131 azalt\u0131r.<\/p>\n<h3><span id=\"3_Gereksiz_Include8217lari_Temizleyin\">3. Gereksiz Include&#8217;lar\u0131 Temizleyin<\/span><\/h3>\n<p>Envanterden sonra s\u0131kl\u0131kla g\u00f6rd\u00fc\u011f\u00fcm\u00fcz manzara \u015fu:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">v=spf1 include:_spf1.servis.com include:_spf2.servis.com include:mail1.example.net include:mail2.example.net include:eu.mailhost.com ~all\n<\/code><\/pre>\n<p>Burada her bir include en az bir, \u00e7o\u011fu zaman birka\u00e7 DNS lookup daha olu\u015fturur. Servislerin d\u00f6k\u00fcmantasyonunu dikkatle inceleyin:<\/p>\n<ul>\n<li>Ayn\u0131 servis i\u00e7in birden \u00e7ok include gerekiyormu\u015f gibi g\u00f6r\u00fcnen ama asl\u0131nda eski s\u00fcr\u00fcmler i\u00e7in b\u0131rak\u0131lm\u0131\u015f kay\u0131tlar olabilir.<\/li>\n<li>B\u00f6lgesel include&#8217;lar (eu, us, asia) aras\u0131ndan sadece ger\u00e7ekten kulland\u0131\u011f\u0131n\u0131z\u0131 b\u0131rakabilirsiniz.<\/li>\n<li>Baz\u0131 servisler hem &#8216;include:spf.servis.com&#8217; hem de birka\u00e7 IP aral\u0131\u011f\u0131 veriyorsa, sadece kulland\u0131\u011f\u0131n\u0131z IP blo\u011funu se\u00e7ip do\u011frudan ip4\/ip6 ile yazabilirsiniz.<\/li>\n<\/ul>\n<p>Hedefiniz, b\u00fct\u00fcn servislere ra\u011fmen <strong>toplam 4\u20136 lookup civar\u0131nda kalmak<\/strong> olsun. Geri kalanlar\u0131 flattening veya delegasyon gibi geli\u015fmi\u015f tekniklerle \u00e7\u00f6zece\u011fiz.<\/p>\n<h3><span id=\"4_8216redirect8217_ve_8216exists8217_Mekanizmalarini_Dikkatli_Kullanin\">4. &#8216;redirect&#8217; ve &#8216;exists&#8217; Mekanizmalar\u0131n\u0131 Dikkatli Kullan\u0131n<\/span><\/h3>\n<p>&#8216;redirect=&#8217; parametresi SPF kayd\u0131n\u0131 tamamen ba\u015fka bir alana devreder. \u00d6rne\u011fin:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">example.com:   v=spf1 redirect=_spf.example.com\n_spf.example.com: v=spf1 ip4:1.2.3.4 include:servis.com -all\n<\/code><\/pre>\n<p>Bu, y\u00f6netimi kolayla\u015ft\u0131rabilir ama lookup say\u0131s\u0131n\u0131 azaltmaz; hatta yanl\u0131\u015f kuruldu\u011funda zinciri uzat\u0131p artt\u0131r\u0131r. Benzer \u015fekilde &#8216;exists&#8217; mekanizmas\u0131 da \u00f6l\u00e7\u00fcs\u00fcz kullan\u0131ld\u0131\u011f\u0131nda gereksiz sorgu sebebi olabilir. Lookup limitine yak\u0131nsan\u0131z, <strong>redirect ve exists&#8217;ten ka\u00e7\u0131nmak<\/strong> \u00e7o\u011fu zaman iyi bir fikirdir.<\/p>\n<h2><span id=\"Delegasyon_Ayri_Alan_Adlari_ve_Subdomain_Stratejileri\">Delegasyon, Ayr\u0131 Alan Adlar\u0131 ve Subdomain Stratejileri<\/span><\/h2>\n<p>Geli\u015fmi\u015f SPF y\u00f6netiminde en g\u00fc\u00e7l\u00fc ara\u00e7lardan biri, <strong>ayn\u0131 marka i\u00e7in birden fazla domain veya subdomain kullanmakt\u0131r<\/strong>. Burada kritik nokta, DMARC hizalamas\u0131n\u0131 (alignment) bozmadan SPF&#8217;i sadele\u015ftirmektir.<\/p>\n<h3><span id=\"Transactional_Pazarlama_ve_Operasyonel_Mailleri_Ayirin\">Transactional, Pazarlama ve Operasyonel Mailleri Ay\u0131r\u0131n<\/span><\/h3>\n<p>Genel bir iyi uygulama:<\/p>\n<ul>\n<li>Transactional mailler (\u015fifre s\u0131f\u0131rlama, sipari\u015f onay\u0131) i\u00e7in: mail.example.com veya notify.example.com<\/li>\n<li>Pazarlama\/b\u00fclten mailleri i\u00e7in: news.example.com veya email.example.com<\/li>\n<li>Destek ve ticket mailleri i\u00e7in: support.example.com<\/li>\n<\/ul>\n<p>Her bir subdomain i\u00e7in <strong>ayr\u0131 bir SPF kayd\u0131<\/strong> tan\u0131mlayabilir ve ilgili servisi sadece oraya ba\u011flayabilirsiniz. \u00d6rne\u011fin:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">example.com.        TXT &quot;v=spf1 ip4:203.0.113.10 -all&quot;\nmail.example.com.   TXT &quot;v=spf1 include:spf.transactionalservis.com -all&quot;\nnews.example.com.   TXT &quot;v=spf1 include:spf.marketingservis.com -all&quot;\n<\/code><\/pre>\n<p>Burada \u00f6nemli olan, kulland\u0131\u011f\u0131n\u0131z servislerin Return\u2011Path \/ MAIL FROM domainini bu subdomain&#8217;lere g\u00f6re ayarlayabilmenizdir. \u00c7o\u011fu kurumsal e\u2011posta ve pazarlama servisi, \u00f6zel envelope\u2011from domain tan\u0131m\u0131na izin verir.<\/p>\n<h3><span id=\"DMARC_Hizalamasini_Korumak\">DMARC Hizalamas\u0131n\u0131 Korumak<\/span><\/h3>\n<p>DMARC, SPF veya DKIM sonucunu de\u011ferlendirirken &#8216;alignment&#8217; kavram\u0131n\u0131 kullan\u0131r. SPF alignment, <strong>From ba\u015fl\u0131\u011f\u0131ndaki alan ad\u0131 ile SPF do\u011frulamas\u0131 yap\u0131lan alan ad\u0131n\u0131n ayn\u0131 k\u00f6kten gelmesini<\/strong> ister. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>From: bilgi@example.com<\/li>\n<li>SPF do\u011frulamas\u0131: mail.example.com<\/li>\n<\/ul>\n<p>Bu durumda relaxed alignment alt\u0131nda ge\u00e7erli say\u0131l\u0131r, \u00e7\u00fcnk\u00fc ikisi de ayn\u0131 k\u00f6k alan ad\u0131 (example.com) alt\u0131ndad\u0131r. Yani transactional mailler i\u00e7in MAIL FROM&#8217;u mail.example.com, marketing mailler i\u00e7in MAIL FROM&#8217;u news.example.com yapmak DMARC a\u00e7\u0131s\u0131ndan sorun yaratmaz; tam tersine SPF&#8217;i sadele\u015ftirmeyi kolayla\u015ft\u0131r\u0131r.<\/p>\n<p>DMARC ve SPF hizalamas\u0131n\u0131 daha derin anlamak i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/e-posta-icin-ayri-gonderim-alan-adi-kullanmak-transactional-ve-pazarlama-e-postalari-icin-dogru-domain-ve-dns-stratejisi\/\">transactional ve pazarlama e\u2011postalar\u0131 i\u00e7in ayr\u0131 g\u00f6nderim alan\u0131 kullanma rehberimizi<\/a> da mutlaka okuman\u0131z\u0131 \u00f6neririz.<\/p>\n<h3><span id=\"Alt_Domainleri_Farkli_SPF_Politikalarina_Yonlendirmek\">Alt Domainleri Farkl\u0131 SPF Politikalar\u0131na Y\u00f6nlendirmek<\/span><\/h3>\n<p>E\u011fer \u00e7ok say\u0131da alt alan ad\u0131n\u0131z varsa ve hepsinin ayn\u0131 SPF politikas\u0131n\u0131 kullanmas\u0131n\u0131 istiyorsan\u0131z, redirect kullanarak merkezi bir alan tan\u0131mlayabilirsiniz:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">_spf.example.com.   TXT &quot;v=spf1 ip4:203.0.113.10 include:spf.servis.com -all&quot;\nmail.example.com.   TXT &quot;v=spf1 redirect=_spf.example.com&quot;\nnews.example.com.   TXT &quot;v=spf1 redirect=_spf.example.com&quot;\n<\/code><\/pre>\n<p>Bu yakla\u015f\u0131m y\u00f6netimi kolayla\u015ft\u0131r\u0131r; ama lookup say\u0131s\u0131n\u0131 d\u00fc\u015f\u00fcrmez. Yine de \u00e7ok say\u0131da subdomain&#8217;i tek bir merkezden y\u00f6netmek istiyorsan\u0131z i\u015fe yarar. Lookup optimizasyonunu, merkez kay\u0131t olan _spf.example.com \u00fczerinde yapman\u0131z gerekir.<\/p>\n<h2><span id=\"SPF_Flattening_Lookup_Sayisini_Dusurmenin_Otomatik_Yolu\">SPF Flattening: Lookup Say\u0131s\u0131n\u0131 D\u00fc\u015f\u00fcrmenin Otomatik Yolu<\/span><\/h2>\n<p>Delegasyon ve sadele\u015ftirme sonras\u0131nda h\u00e2l\u00e2 10 lookup s\u0131n\u0131r\u0131na yak\u0131nsan\u0131z, s\u0131radaki ad\u0131m <strong>SPF flattening<\/strong> yakla\u015f\u0131m\u0131d\u0131r. Temel fikir, &#8216;include:spf.servis.com&#8217; gibi kay\u0131tlar\u0131n arkas\u0131ndaki IP ve IP bloklar\u0131n\u0131 \u00f6nceden \u00e7\u00f6z\u00fcp SPF kayd\u0131n\u0131za do\u011frudan ip4\/ip6 olarak yazmakt\u0131r.<\/p>\n<h3><span id=\"Statik_Flattening_Ne_Zaman_Tehlikeli\">Statik Flattening Ne Zaman Tehlikeli?<\/span><\/h3>\n<p>En basit ama riskli y\u00f6ntem: DNS sorgu arac\u0131n\u0131zla include etti\u011finiz domainlerin SPF kay\u0131tlar\u0131n\u0131 \u00e7\u00f6zersiniz, t\u00fcm ip4\/ip6 de\u011ferlerini al\u0131r ve kendi SPF kay\u0131tlar\u0131n\u0131za yap\u0131\u015ft\u0131r\u0131rs\u0131n\u0131z. \u00d6rne\u011fin:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">orijinal:\n  v=spf1 ip4:203.0.113.10 include:spf.marketingservis.com -all\n\nflatten edilmi\u015f:\n  v=spf1 ip4:203.0.113.10 ip4:198.51.100.0\/24 ip4:192.0.2.0\/25 -all\n<\/code><\/pre>\n<p>Bunun iki \u00f6nemli riski var:<\/p>\n<ul>\n<li>Servis, zaman i\u00e7inde IP aral\u0131klar\u0131n\u0131 de\u011fi\u015ftirirse SPF kayd\u0131n\u0131z g\u00fcncel kalmaz.<\/li>\n<li>\u00d6zellikle b\u00fcy\u00fck sa\u011flay\u0131c\u0131lar\u0131n IP aral\u0131klar\u0131 \u00e7ok geni\u015ftir; SPF kayd\u0131n\u0131z gereksiz \u015fi\u015febilir.<\/li>\n<\/ul>\n<p>Bu nedenle statik flattening ancak belirli ko\u015fullarda, <strong>IP aral\u0131klar\u0131 uzun s\u00fcre de\u011fi\u015fmeyecek k\u00fc\u00e7\u00fck veya kurumsal sa\u011flay\u0131c\u0131larda<\/strong> tercih edilmelidir. Daha dinamik ortamlarda, flattening&#8217;i otomatikle\u015ftirmek \u00e7ok daha sa\u011fl\u0131kl\u0131 bir stratejidir.<\/p>\n<h3><span id=\"Otomatik_Dinamik_SPF_Flattening_Mimarisinin_Mantigi\">Otomatik \/ Dinamik SPF Flattening Mimarisinin Mant\u0131\u011f\u0131<\/span><\/h3>\n<p>Daha g\u00fcvenli yakla\u015f\u0131m, SPF flattening&#8217;i bir <strong>otomasyon s\u00fcreci<\/strong> haline getirmektir. \u00d6rne\u011fin:<\/p>\n<ol>\n<li>Bir betik (Python, Bash vb.) belirli aral\u0131klarla (cron, CI\/CD pipeline) \u00e7al\u0131\u015f\u0131r.<\/li>\n<li>Betik, include etti\u011finiz alanlar\u0131n SPF kay\u0131tlar\u0131n\u0131 \u00e7\u00f6zer.<\/li>\n<li>Ortaya \u00e7\u0131kan ip4\/ip6 listelerini konsolide eder, gereksiz tekrarlar\u0131 atar.<\/li>\n<li>Olu\u015fan yeni SPF kayd\u0131n\u0131 DNS sa\u011flay\u0131c\u0131n\u0131za API \u00fczerinden yazar.<\/li>\n<\/ol>\n<p>B\u00f6ylece SPF kayd\u0131n\u0131z <strong>&#8216;ya\u015fayan&#8217;<\/strong> bir kay\u0131t haline gelir; servisler IP adreslerini de\u011fi\u015ftirdik\u00e7e siz de periyodik olarak g\u00fcncellenmi\u015f bir flatten edilmi\u015f kay\u0131t kullan\u0131rs\u0131n\u0131z. Biz DCHost taraf\u0131nda, b\u00fcy\u00fck hacimli g\u00f6nderen baz\u0131 m\u00fc\u015fteriler i\u00e7in bu tarz otomatik flattening ak\u0131\u015flar\u0131 kurgularken, DNS h\u0131z\u0131n\u0131 ve TTL de\u011ferlerini de birlikte planl\u0131yoruz.<\/p>\n<p>Bu konuyu ayr\u0131nt\u0131l\u0131 okuma ve \u00f6rnek bash\/CI pipeline \u015fablonlar\u0131 g\u00f6rmek isterseniz, <a href=\"https:\/\/www.dchost.com\/blog\/spf-flattening-ile-10-lookup-duvarini-nasil-asarsin-ci-cd-ve-workers-ile-yasayan-spf\/\">SPF flattening ile 10 lookup duvar\u0131n\u0131 a\u015fma rehberimizi<\/a> \u00f6zellikle tavsiye ederim.<\/p>\n<h2><span id=\"EPosta_Yonlendirme_SRSARC_ve_SPF_Iliskisi\">E\u2011Posta Y\u00f6nlendirme, SRS\/ARC ve SPF \u0130li\u015fkisi<\/span><\/h2>\n<p>SPF ile ilgili bir ba\u015fka tuzak da <strong>e\u2011posta y\u00f6nlendirme<\/strong> senaryolar\u0131d\u0131r. Kullan\u0131c\u0131 &#8216;info@example.com&#8217; adresine gelen mailleri ki\u015fisel hesab\u0131na y\u00f6nlendirdi\u011finde, y\u00f6nlendiren sunucu orijinal g\u00f6nderen ad\u0131na maili tekrar g\u00f6nderir. SPF, kaynak IP&#8217;ye bakt\u0131\u011f\u0131 i\u00e7in \u00e7o\u011fu zaman bu yeniden g\u00f6nderilen maili yetkisiz olarak g\u00f6r\u00fcr.<\/p>\n<p>Bunu \u00e7\u00f6zmek i\u00e7in geli\u015ftirilen SRS (Sender Rewriting Scheme) ve ARC (Authenticated Received Chain) gibi mekanizmalar, y\u00f6nlendiren sunucunun Mail\u2011From alan\u0131n\u0131 kendine g\u00f6re yeniden yazmas\u0131na veya do\u011frulama zincirini korumas\u0131na izin verir. E\u011fer kendi mail sunucunuzu DCHost \u00fczerindeki bir VPS&#8217;te y\u00f6netiyorsan\u0131z, Postfix\/Dovecot + SRS\/ARC kurulumuyla SPF ve DMARC&#8217;\u0131 bozmadan y\u00f6nlendirme yapman\u0131z m\u00fcmk\u00fcnd\u00fcr.<\/p>\n<p>Detayl\u0131 senaryolar ve pratik kurulum ad\u0131mlar\u0131 i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/e%e2%80%91posta-yonlendirmede-spf-dmarc-neden-kiriliyor-srs-ve-arc-ile-nasil-tatli-tatli-onarirsin\/\">e\u2011posta y\u00f6nlendirmede SPF\/DMARC neden k\u0131r\u0131l\u0131yor, SRS ve ARC ile nas\u0131l d\u00fczeltilir rehberimize<\/a> g\u00f6z atabilirsiniz. SPF&#8217;i optimize ederken y\u00f6nlendirme trafi\u011finizi de hesaba katmay\u0131 unutmay\u0131n.<\/p>\n<h2><span id=\"IPv6_ile_SPF_Reverse_DNS_ve_Yedeklilik\">IPv6 ile SPF, Reverse DNS ve Yedeklilik<\/span><\/h2>\n<p>Giderek daha fazla mail sunucusu IPv6 \u00fczerinden de teslimat yapmaya ba\u015fl\u0131yor. SPF taraf\u0131nda IPv6&#8217;y\u0131 tan\u0131mlamak i\u00e7in <strong>ip6 mekanizmas\u0131n\u0131<\/strong> kullan\u0131yoruz:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">v=spf1 ip4:203.0.113.10 ip6:2001:db8::1234 -all\n<\/code><\/pre>\n<p>IPv6 adresleri i\u00e7in de lookup limitine tak\u0131lmazs\u0131n\u0131z; \u00f6nemli olan, bu adreslerin ger\u00e7ekten sizin mail sunucunuza ait olmas\u0131 ve <strong>reverse DNS (PTR) kay\u0131tlar\u0131n\u0131n do\u011fru tan\u0131mlanm\u0131\u015f<\/strong> olmas\u0131d\u0131r. \u00d6zellikle DCHost \u00fczerindeki VPS ve <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a>larda hem IPv4 hem IPv6 \u00fczerinden e\u2011posta g\u00f6nderecek yap\u0131 kuruyorsan\u0131z, \u015fu ad\u0131mlar\u0131 kontrol etmenizi \u00f6neririz:<\/p>\n<ul>\n<li>IPv6 PTR kayd\u0131: &#8216;mail.example.com&#8217; gibi tutarl\u0131 bir hostname&#8217;e i\u015faret etmeli<\/li>\n<li>Bu hostname i\u00e7in A ve AAAA kay\u0131tlar\u0131 tan\u0131ml\u0131 olmal\u0131<\/li>\n<li>SPF kayd\u0131n\u0131zda ip6: veya a:mail.example.com \u00fczerinden IPv6 da yetkilendirilmi\u015f olmal\u0131<\/li>\n<\/ul>\n<p>IPv6 ile e\u2011posta g\u00f6nderimi ve SPF\/Reverse DNS detaylar\u0131n\u0131 ad\u0131m ad\u0131m ele ald\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/ipv6-ile-e-posta-gonderimi-reverse-dns-spf-ve-teslim-edilebilirlik-rehberi\/\">IPv6 ile e\u2011posta g\u00f6nderimi ve teslim edilebilirlik rehberimizi<\/a> \u00f6zellikle teknik ekipler i\u00e7in \u00f6neriyoruz.<\/p>\n<h2><span id=\"DCHost_Tarafinda_Gelismis_SPF_Yonetimini_Nasil_Kurguluyoruz\">DCHost Taraf\u0131nda Geli\u015fmi\u015f SPF Y\u00f6netimini Nas\u0131l Kurguluyoruz?<\/span><\/h2>\n<p>SPF teorisini bilmek bir yana, bunu canl\u0131 sistemlerde hatas\u0131z uygulamak ayr\u0131 bir uzmanl\u0131k. DCHost taraf\u0131nda farkl\u0131 \u00f6l\u00e7eklerde m\u00fc\u015fteriler i\u00e7in genellikle \u015fu yakla\u015f\u0131m\u0131 izliyoruz:<\/p>\n<ul>\n<li><strong>Payla\u015f\u0131ml\u0131 hosting m\u00fc\u015fterileri<\/strong> i\u00e7in: cPanel DNS edit\u00f6r\u00fc \u00fczerinden sade, do\u011frudan ip4\/ip6 veya a\/mx tan\u0131mlar\u0131 ile gereksiz include&#8217;lar\u0131 temizliyoruz.<\/li>\n<li><strong>VPS ve dedicated m\u00fc\u015fteriler<\/strong> i\u00e7in: Kendi MTA&#8217;lar\u0131n\u0131 y\u00f6nettikleri senaryolarda, mail.example.com gibi ayr\u0131 subdomain&#8217;ler ve m\u00fcmk\u00fcn oldu\u011funca do\u011frudan IP yetkilendirmesi kullan\u0131yoruz.<\/li>\n<li><strong>\u00c7oklu servis kullanan kurumsal yap\u0131lar<\/strong> i\u00e7in: Transactional \/ pazarlama \/ operasyonel mailleri farkl\u0131 subdomain&#8217;lere da\u011f\u0131t\u0131p, gerekiyorsa otomatik SPF flattening pipeline&#8217;\u0131 tasarl\u0131yoruz.<\/li>\n<li><strong>DMARC ve raporlama<\/strong> taraf\u0131nda: SPF&#8217;in DMARC ile hizalamas\u0131n\u0131, RUA\/RUF raporlar\u0131ndan d\u00fczenli olarak takip edip yanl\u0131\u015f yetkilendirilmi\u015f IP&#8217;leri tespit ediyoruz.<\/li>\n<\/ul>\n<p>E\u011fer alan ad\u0131n\u0131z, DNS&#8217;iniz veya mail sunucunuz DCHost \u00fczerinde bar\u0131n\u0131yorsa, destek ekibimizle birlikte SPF kayd\u0131n\u0131z\u0131 g\u00f6zden ge\u00e7irip hangi include&#8217;lar\u0131n ger\u00e7ekten gerekli oldu\u011funu, nerede subdomain veya flattening kullanabilece\u011finizi birlikte planlayabiliriz.<\/p>\n<h2><span id=\"Ozet_ve_Sonraki_Adimlar\">\u00d6zet ve Sonraki Ad\u0131mlar<\/span><\/h2>\n<p>Geli\u015fmi\u015f SPF y\u00f6netimi, sadece TXT kayd\u0131na birka\u00e7 include eklemekten \u00e7ok daha fazlas\u0131. Bir yandan RFC 7208&#8217;in getirdi\u011fi 10 DNS lookup s\u0131n\u0131r\u0131na uymak zorundas\u0131n\u0131z; di\u011fer yandan DMARC hizalamas\u0131n\u0131 bozmadan birden fazla e\u2011posta servisini ayn\u0131 marka \u00e7at\u0131s\u0131 alt\u0131nda y\u00f6netmeniz gerekiyor. Do\u011fru strateji genellikle \u015fu bile\u015fenlerin birle\u015fiminden olu\u015fuyor:<\/p>\n<ul>\n<li>T\u00fcm g\u00f6nderim kaynaklar\u0131n\u0131 envanterleyip gereksiz include&#8217;lar\u0131 temizlemek<\/li>\n<li>Kendi kontrol\u00fcn\u00fczdeki IP&#8217;leri do\u011frudan ip4\/ip6 veya a\/mx ile yetkilendirmek<\/li>\n<li>Transactional, pazarlama ve operasyonel mailleri ayr\u0131 subdomain&#8217;lere ta\u015f\u0131mak<\/li>\n<li>Gerekiyorsa otomatik SPF flattening pipeline&#8217;\u0131 kurmak<\/li>\n<li>Y\u00f6nlendirme, SRS\/ARC ve IPv6 gibi detaylar\u0131 SPF ile uyumlu hale getirmek<\/li>\n<\/ul>\n<p>Bir sonraki ad\u0131mda, mevcut SPF kayd\u0131n\u0131z\u0131 test ara\u00e7lar\u0131yla kontrol edip &#8216;DNS lookups&#8217; say\u0131s\u0131n\u0131 not al\u0131n. Ard\u0131ndan bu yaz\u0131daki ad\u0131mlar\u0131 izleyerek sadele\u015ftirme ve delegasyon denemeleri yap\u0131n. Daha sonra, DMARC raporlar\u0131n\u0131z\u0131 inceleyerek ger\u00e7ek d\u00fcnyada hangi IP&#8217;lerin sizin ad\u0131n\u0131za mail g\u00f6nderdi\u011fini do\u011frulay\u0131n. Bu s\u00fcre\u00e7te rehbere ihtiya\u00e7 duyarsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/spf-dkim-dmarc-ve-rdns-ile-e-posta-teslim-edilebilirligini-nasil-adim-adim-yukseltirsin\/\">e\u2011posta teslim edilebilirli\u011fini SPF, DKIM, DMARC ve rDNS ile ad\u0131m ad\u0131m y\u00fckseltme yaz\u0131m\u0131z<\/a> da yol g\u00f6sterici olacakt\u0131r.<\/p>\n<p>E\u011fer alan ad\u0131n\u0131z\u0131, DNS&#8217;inizi veya mail altyap\u0131n\u0131z\u0131 DCHost&#8217;a ta\u015f\u0131may\u0131 d\u00fc\u015f\u00fcn\u00fcyorsan\u0131z, ekibimiz hem SPF\/DMARC tasar\u0131m\u0131 hem de VPS, dedicated veya colocation taraf\u0131nda ihtiya\u00e7 duyaca\u011f\u0131n\u0131z e\u2011posta mimarisini birlikte planlamaya haz\u0131r. Altyap\u0131 taraf\u0131n\u0131 biz stabilize ederken siz de teslim edilebilirli\u011fi ve marka itibar\u0131n\u0131z\u0131 g\u00fcvenle b\u00fcy\u00fctebilirsiniz.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Alan ad\u0131n\u0131zdan hem kendi sunucunuzdan, hem CRM sisteminizden, hem de pazarlama ara\u00e7lar\u0131n\u0131zdan e\u2011posta g\u00f6nderiyorsan\u0131z, bir noktada SPF kayd\u0131n\u0131n s\u0131n\u0131rlar\u0131na toslaman\u0131z neredeyse ka\u00e7\u0131n\u0131lmazd\u0131r. Test ara\u00e7lar\u0131nda g\u00f6rd\u00fc\u011f\u00fcn\u00fcz &#8216;Too many DNS lookups&#8217; veya &#8216;PermError: DNS lookup limit exceeded&#8217; uyar\u0131lar\u0131, bir yandan teslim edilebilirli\u011fi d\u00fc\u015f\u00fcr\u00fcrken di\u011fer yandan da nereden ba\u015flayaca\u011f\u0131n\u0131z\u0131 bilemedi\u011finiz karma\u015f\u0131k bir tablo yarat\u0131r. Bu yaz\u0131da, DCHost ekibi [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":3846,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-3845","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\/3845","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=3845"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3845\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/3846"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=3845"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=3845"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=3845"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}