{"id":129,"date":"2026-10-09T09:01:24","date_gmt":"2026-10-09T06:01:24","guid":{"rendered":"https:\/\/mx1mail.com\/blog\/spf-10-dns-lookup-limiti-include-zinciri-hatalar-spf-flattening\/"},"modified":"2026-10-09T09:01:24","modified_gmt":"2026-10-09T06:01:24","slug":"spf-10-dns-lookup-limiti-include-zinciri-hatalar-spf-flattening","status":"publish","type":"post","link":"https:\/\/mx1mail.com\/blog\/tr\/spf-10-dns-lookup-limiti-include-zinciri-hatalar-spf-flattening\/","title":{"rendered":"SPF 10 DNS Lookup Limiti Nedir? include Zinciri, Hatalar ve SPF Flattening ile \u00c7\u00f6z\u00fcm"},"content":{"rendered":"<h2>SPF 10 DNS lookup limiti ne demektir?<\/h2>\n<p>SPF (Sender Policy Framework), bir alan ad\u0131ndan (domain) e-posta g\u00f6nderme yetkisi olan IP adreslerini ve g\u00f6nderim kaynaklar\u0131n\u0131 DNS \u00fczerinde tan\u0131mlaman\u0131z\u0131 sa\u011flar. Al\u0131c\u0131 posta sunucusu, bir mesaj\u0131n zarf g\u00f6nderen (envelope-from) alan ad\u0131 i\u00e7in SPF kontrol\u00fc yapt\u0131\u011f\u0131nda DNS\u2019teki SPF kayd\u0131n\u0131 okur ve bu kayd\u0131n i\u015faret etti\u011fi kaynaklar\u0131 do\u011frulamak i\u00e7in \u00e7e\u015fitli DNS sorgular\u0131 yapar.<\/p>\n<p>SPF\u2019nin kritik bir kural\u0131 vard\u0131r: SPF de\u011ferlendirmesi s\u0131ras\u0131nda en fazla 10 adet DNS lookup (DNS sorgusu) yap\u0131labilir. Bu limit, \u201cSPF policy evaluation\u201d s\u0131ras\u0131nda yap\u0131lan belirli t\u00fcrdeki sorgular\u0131 kapsar ve a\u015f\u0131ld\u0131\u011f\u0131nda SPF sonucu genellikle PermError (kal\u0131c\u0131 hata) olur. PermError, al\u0131c\u0131 sistemin SPF\u2019i g\u00fcvenle de\u011ferlendiremedi\u011fi anlam\u0131na gelir ve teslim edilebilirli\u011fi olumsuz etkileyebilir; baz\u0131 sistemler mesaj\u0131 reddedebilir, baz\u0131lar\u0131 spam puan\u0131n\u0131 y\u00fckseltebilir.<\/p>\n<p>Bu konu, \u00f6zellikle birden fazla SaaS arac\u0131yla (CRM, helpdesk, pazarlama otomasyonu, fatura sistemi gibi) e-posta g\u00f6nderen i\u015fletmelerde s\u0131k g\u00f6r\u00fcl\u00fcr. Her yeni g\u00f6nderim arac\u0131, SPF kayd\u0131na yeni bir include eklenmesine yol a\u00e7abilir ve include zinciri b\u00fcy\u00fcd\u00fck\u00e7e 10 sorgu limiti a\u015f\u0131labilir.<\/p>\n<h2>Hangi SPF mekanizmalar\u0131 DNS sorgusu say\u0131l\u0131r?<\/h2>\n<p>SPF kayd\u0131nda her ifade (mekanizma) ayn\u0131 maliyete sahip de\u011fildir. 10 lookup limitine dahil olan ba\u015fl\u0131ca mekanizmalar \u015funlard\u0131r:<\/p>\n<ul>\n<li><strong>include:<\/strong> Ba\u015fka bir domainin SPF kayd\u0131n\u0131 i\u00e7eri al\u0131r. Her include en az bir DNS sorgusu demektir ve include edilen kayd\u0131n i\u00e7inde ba\u015fka include\u2019lar varsa toplam sorgu say\u0131s\u0131 h\u0131zla artar.<\/li>\n<li><strong>a<\/strong> ve <strong>mx<\/strong>: Domainin A kayd\u0131n\u0131 veya MX kay\u0131tlar\u0131n\u0131 \u00e7\u00f6z\u00fcmler. Her biri lookup t\u00fcketebilir.<\/li>\n<li><strong>exists<\/strong>: Ko\u015fullu kontrol i\u00e7in DNS sorgusu yapt\u0131r\u0131r, lookup t\u00fcketir.<\/li>\n<li><strong>redirect=<\/strong>: SPF de\u011ferlendirmesini ba\u015fka bir domaine y\u00f6nlendirir, lookup t\u00fcketir.<\/li>\n<\/ul>\n<p>\u00d6te yandan <strong>ip4<\/strong> ve <strong>ip6<\/strong> gibi mekanizmalar do\u011frudan IP aral\u0131klar\u0131 i\u00e7erdi\u011fi i\u00e7in lookup t\u00fcketmez. Bu y\u00fczden sadele\u015ftirme \u00e7al\u0131\u015fmalar\u0131nda \u00e7o\u011fu zaman hedef, include\u2019lar\u0131 azalt\u0131p m\u00fcmk\u00fcn oldu\u011funca ip4\/ip6 ile netle\u015ftirmektir.<\/p>\n<h2>Limit a\u015f\u0131ld\u0131\u011f\u0131nda ne olur? Tipik belirtiler<\/h2>\n<p>10 DNS sorgu limiti a\u015f\u0131ld\u0131\u011f\u0131nda SPF de\u011ferlendirmesi sa\u011fl\u0131kl\u0131 tamamlanamaz. Bu durumun pratikteki belirtileri \u015funlar olabilir:<\/p>\n<ul>\n<li>Al\u0131c\u0131 sistemin loglar\u0131nda veya bounce mesajlar\u0131nda SPF ile ilgili <strong>PermError<\/strong> ifadeleri<\/li>\n<li>\u201cToo many DNS lookups\u201d ya da benzeri hata a\u00e7\u0131klamalar\u0131<\/li>\n<li>Baz\u0131 al\u0131c\u0131larda normal teslim, baz\u0131 al\u0131c\u0131larda spam\/ret gibi tutars\u0131z sonu\u00e7lar<\/li>\n<li>Yeni eklenen bir g\u00f6nderim kayna\u011f\u0131ndan sonra aniden teslim edilebilirlik d\u00fc\u015f\u00fc\u015f\u00fc<\/li>\n<\/ul>\n<p>Bu noktada sorun \u201cSPF yanl\u0131\u015f\u201d olmaktan \u00e7ok \u201cSPF do\u011frulanam\u0131yor\u201d haline gelir. Dolay\u0131s\u0131yla \u00e7\u00f6z\u00fcm, SPF kayd\u0131n\u0131 teknik limitler i\u00e7inde yeniden d\u00fczenlemektir.<\/p>\n<h2>include zinciri neden kontrolden \u00e7\u0131kar?<\/h2>\n<p>\u0130\u015fletmeler genellikle SPF kayd\u0131n\u0131 zaman i\u00e7inde \u201cekleyerek\u201d b\u00fcy\u00fct\u00fcr. \u00d6rne\u011fin pazarlama arac\u0131 bir include ister, destek sistemi bir include ister, bulut ofis servisi bir include ister. Ayr\u0131ca bu servislerin kendi SPF kay\u0131tlar\u0131 da ba\u015fka domainleri include edebilir. B\u00f6ylece siz yaln\u0131zca 3-4 include ekledi\u011finizi san\u0131rken, arka planda 12-15 sorguya \u00e7\u0131kan bir zincir olu\u015fabilir.<\/p>\n<p>Baz\u0131 yayg\u0131n hatal\u0131 yakla\u015f\u0131mlar:<\/p>\n<ul>\n<li>Ayn\u0131 servis i\u00e7in birden fazla include eklemek (dok\u00fcmantasyon farkl\u0131 zamanlarda de\u011fi\u015ftiyse)<\/li>\n<li>Eski servisleri kald\u0131rmamak (kullan\u0131lmayan include\u2019lar)<\/li>\n<li>\u201cmx\u201d veya \u201ca\u201d mekanizmalar\u0131n\u0131 gereksiz yere eklemek<\/li>\n<li>Birden fazla SPF TXT kayd\u0131 olu\u015fturmak (SPF i\u00e7in tek TXT kayd\u0131 olmal\u0131d\u0131r; birden fazlas\u0131 sonu\u00e7lar\u0131 bozabilir)<\/li>\n<\/ul>\n<h2>SPF kayd\u0131 denetimi: Ad\u0131m ad\u0131m pratik kontrol<\/h2>\n<h3>1) G\u00f6nderim kaynaklar\u0131n\u0131 envanterleyin<\/h3>\n<p>\u00d6nce organizasyonunuzun hangi sistemlerden d\u0131\u015far\u0131 e-posta g\u00f6nderdi\u011fini listeleyin. Bu liste genellikle \u015funlar\u0131 i\u00e7erir: kullan\u0131c\u0131lar\u0131n SMTP submission ile g\u00f6nderimleri, uygulama sunucular\u0131, pazarlama platformlar\u0131, helpdesk\/ticket sistemi, \u00e7ok i\u015flevli yaz\u0131c\u0131lar, izleme sistemleri.<\/p>\n<p>Hedef: \u201cGer\u00e7ekte kullan\u0131lan\u201d kaynaklar\u0131 belirlemek. Kullan\u0131lmayan kaynaklar\u0131 SPF\u2019ten \u00e7\u0131karmak \u00e7o\u011fu zaman en h\u0131zl\u0131 kazan\u00e7t\u0131r.<\/p>\n<h3>2) SPF kayd\u0131ndaki mekanizmalar\u0131 okuyun<\/h3>\n<p>SPF kayd\u0131 genellikle \u201cv=spf1 &#8230; -all\u201d bi\u00e7imindedir. Burada yer alan her include, a, mx, exists ve redirect \u00f6\u011fesini not al\u0131n. En sonda kullan\u0131lan nitelendirici de \u00f6nemlidir:<\/p>\n<ul>\n<li><strong>-all<\/strong>: Yetkisiz kaynaklar\u0131 fail ile i\u015faretler (daha kat\u0131)<\/li>\n<li><strong>~all<\/strong>: Softfail \u00fcretir (daha toleransl\u0131)<\/li>\n<\/ul>\n<p>Bu yaz\u0131 \u201changi -all daha iyi\u201d tart\u0131\u015fmas\u0131na odaklanm\u0131yor; as\u0131l ama\u00e7, kayd\u0131n \u00e7al\u0131\u015fabilir s\u0131n\u0131rlar i\u00e7inde olmas\u0131d\u0131r.<\/p>\n<h3>3) Lookup b\u00fct\u00e7esini hesaplay\u0131n<\/h3>\n<p>Sadece sizin SPF kayd\u0131n\u0131zdaki include say\u0131s\u0131 de\u011fil, include edilen domainlerin SPF i\u00e7erikleri de lookup t\u00fcketir. Bu nedenle ger\u00e7ek b\u00fct\u00e7e, zincirin toplam\u0131d\u0131r. Zinciri \u00e7\u00f6z\u00fcmlemeden \u201cbizde 7 include var, sorun yok\u201d demek yan\u0131lt\u0131c\u0131 olabilir.<\/p>\n<h2>SPF flattening nedir ve ne zaman d\u00fc\u015f\u00fcn\u00fclmelidir?<\/h2>\n<p><strong>SPF flattening<\/strong>, include edilen SPF politikalar\u0131n\u0131 \u00e7\u00f6z\u00fcmleyip (resolve) ortaya \u00e7\u0131kan IP aral\u0131klar\u0131n\u0131 do\u011frudan kendi SPF kayd\u0131n\u0131za yazma yakla\u015f\u0131m\u0131d\u0131r. Ama\u00e7, lookup t\u00fcketen include\u2019lar\u0131 azalt\u0131p daha \u00e7ok ip4\/ip6 mekanizmas\u0131 kullanarak 10 lookup limitinin alt\u0131nda kalmakt\u0131r.<\/p>\n<p>Flattening \u015fu durumlarda g\u00fcndeme gelir:<\/p>\n<ul>\n<li>10 lookup limitine yakla\u015f\u0131l\u0131yor veya a\u015f\u0131l\u0131yorsa<\/li>\n<li>Birden fazla g\u00f6nderim hizmeti zorunluysa ve include say\u0131s\u0131n\u0131 d\u00fc\u015f\u00fcrmek m\u00fcmk\u00fcn de\u011filse<\/li>\n<li>Belirli al\u0131c\u0131larda PermError kaynakl\u0131 teslim sorunlar\u0131 ya\u015fan\u0131yorsa<\/li>\n<\/ul>\n<p>Ancak flattening sihirli bir \u00e7\u00f6z\u00fcm de\u011fildir. Dikkat edilmesi gereken \u00f6nemli riskler vard\u0131r.<\/p>\n<h3>Flattening\u2019in art\u0131lar\u0131<\/h3>\n<ul>\n<li>Lookup say\u0131s\u0131 d\u00fc\u015fer, SPF PermError riski azal\u0131r<\/li>\n<li>SPF de\u011ferlendirmesi daha deterministik hale gelir<\/li>\n<li>Gereksiz include zincirlerinden kaynaklanan belirsizlikler azal\u0131r<\/li>\n<\/ul>\n<h3>Flattening\u2019in eksileri ve operasyonel riskleri<\/h3>\n<ul>\n<li>Servis sa\u011flay\u0131c\u0131n\u0131n IP aral\u0131klar\u0131 de\u011fi\u015fti\u011finde sizin SPF kayd\u0131n\u0131z g\u00fcncel kalmayabilir<\/li>\n<li>Yanl\u0131\u015f veya eksik IP eklemek, me\u015fru e-postalar\u0131n SPF fail almas\u0131na neden olabilir<\/li>\n<li>SPF TXT kayd\u0131 \u00e7ok uzayabilir (DNS TXT uzunlu\u011fu ve par\u00e7alama s\u0131n\u0131rlar\u0131na dikkat etmek gerekir)<\/li>\n<\/ul>\n<p>Bu nedenle flattening, \u201cbir kere yapt\u0131m bitti\u201d de\u011fil; d\u00fczenli takip gerektiren bir idari s\u00fcre\u00e7tir.<\/p>\n<h2>Flattening yapmadan \u00f6nce denenebilecek daha basit \u00e7\u00f6z\u00fcmler<\/h2>\n<p>Baz\u0131 durumlarda flattening\u2019e gerek kalmadan da lookup say\u0131s\u0131n\u0131 d\u00fc\u015f\u00fcrmek m\u00fcmk\u00fcnd\u00fcr:<\/p>\n<ul>\n<li><strong>Kullan\u0131lmayan include\u2019lar\u0131 kald\u0131r\u0131n:<\/strong> Eski pazarlama ara\u00e7lar\u0131, eski ticket sistemleri veya art\u0131k kullan\u0131lmayan gateway\u2019ler SPF\u2019te kalm\u0131\u015f olabilir.<\/li>\n<li><strong>Ayn\u0131 sa\u011flay\u0131c\u0131y\u0131 tekrar tekrar include etmeyin:<\/strong> Dok\u00fcmanlar farkl\u0131 alt domainler \u00f6nerse bile \u00e7o\u011fu zaman tek include yeterlidir.<\/li>\n<li><strong>mx\/a kullan\u0131m\u0131n\u0131 sorgulay\u0131n:<\/strong> \u201cmx\u201d mekanizmas\u0131 her zaman gerekli de\u011fildir; sadece MX\u2019ten g\u00f6nderim yap\u0131l\u0131yorsa anlaml\u0131d\u0131r.<\/li>\n<li><strong>G\u00f6nderim domainini ayr\u0131\u015ft\u0131r\u0131n:<\/strong> Pazarlama g\u00f6nderimleri i\u00e7in ayr\u0131 bir alt alan ad\u0131 kullanmak, ana domain SPF\u2019ini sadele\u015ftirir. Bu strateji, marka ve teslim edilebilirlik y\u00f6netiminde de yard\u0131mc\u0131 olabilir.<\/li>\n<\/ul>\n<h2>G\u00fcncelleme ve de\u011fi\u015fiklik y\u00f6netimi: Kesintisiz ilerlemek i\u00e7in<\/h2>\n<p>SPF de\u011fi\u015fiklikleri DNS \u00fczerinden yay\u0131ld\u0131\u011f\u0131 i\u00e7in zaman alabilir. De\u011fi\u015fiklik yaparken \u015fu pratikleri uygulay\u0131n:<\/p>\n<ul>\n<li><strong>DNS TTL planlamas\u0131:<\/strong> B\u00fcy\u00fck de\u011fi\u015fiklik \u00f6ncesi TTL\u2019i makul bir s\u00fcreye indirip, de\u011fi\u015fiklik sonras\u0131 tekrar y\u00fckseltmek ge\u00e7i\u015fi y\u00f6netilebilir k\u0131lar.<\/li>\n<li><strong>A\u015famal\u0131 do\u011frulama:<\/strong> Kritik g\u00f6nderim kaynaklar\u0131n\u0131 tek tek test ederek ilerleyin; bir anda \u00e7ok b\u00fcy\u00fck de\u011fi\u015fiklikler yapmak hata ay\u0131klamay\u0131 zorla\u015ft\u0131r\u0131r.<\/li>\n<li><strong>Dok\u00fcmantasyon:<\/strong> SPF kayd\u0131nda her include veya IP\u2019nin hangi sistem i\u00e7in eklendi\u011fini i\u00e7 s\u00fcre\u00e7lerde kaydedin.<\/li>\n<\/ul>\n<h2>SPF ile DMARC\/DKIM ili\u015fkisi: Tek ba\u015f\u0131na d\u00fc\u015f\u00fcnmeyin<\/h2>\n<p>SPF, g\u00f6nderim kimlik do\u011frulamas\u0131n\u0131n yaln\u0131zca bir par\u00e7as\u0131d\u0131r. DMARC politikalar\u0131 uygulan\u0131yorsa SPF\u2019in \u201cge\u00e7mesi\u201d kadar SPF hizalamas\u0131 (alignment) ve DKIM\u2019in durumu da \u00f6nem kazan\u0131r. SPF PermError ya\u015fand\u0131\u011f\u0131nda, DKIM imzas\u0131 do\u011fru ve hizal\u0131ysa DMARC de\u011ferlendirmesi baz\u0131 senaryolarda yine de ba\u015far\u0131l\u0131 olabilir. Bu y\u00fczden SPF\u2019i iyile\u015ftirirken DKIM\/DMARC b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc de g\u00f6z \u00f6n\u00fcnde bulundurmak gerekir.<\/p>\n<h2>Son kontrol listesi<\/h2>\n<ul>\n<li>Tek bir SPF TXT kayd\u0131 kullan\u0131l\u0131yor mu?<\/li>\n<li>Kullan\u0131lmayan include\/a\/mx\/exists \u00f6\u011feleri kald\u0131r\u0131ld\u0131 m\u0131?<\/li>\n<li>Toplam DNS lookup say\u0131s\u0131 10\u2019un alt\u0131nda m\u0131?<\/li>\n<li>G\u00fcncelleme sonras\u0131 kritik g\u00f6nderim ak\u0131\u015flar\u0131 test edildi mi?<\/li>\n<li>De\u011fi\u015fiklikler i\u00e7 dok\u00fcmantasyona i\u015flendi mi?<\/li>\n<\/ul>\n<h2>MX1Mail ile pratik yakla\u015f\u0131m<\/h2>\n<p>Bir\u00e7ok i\u015fletmede SPF sorunlar\u0131, tek bir ayardan \u00e7ok \u201czamanla biriken karma\u015f\u0131kl\u0131k\u201d nedeniyle ortaya \u00e7\u0131kar. E-posta altyap\u0131n\u0131z\u0131 y\u00f6netirken g\u00f6nderim kaynaklar\u0131n\u0131 netle\u015ftirmek, DNS de\u011fi\u015fikliklerini kontroll\u00fc yapmak ve kimlik do\u011frulama kay\u0131tlar\u0131n\u0131 d\u00fczenli g\u00f6zden ge\u00e7irmek teslim edilebilirli\u011fi korumaya yard\u0131mc\u0131 olur. MX1Mail gibi kurumsal e-posta hizmetleri kullan\u0131rken de domaininizin SPF\/DKIM\/DMARC yap\u0131land\u0131rmalar\u0131n\u0131 periyodik olarak denetlemek, yeni eklenen uygulamalar\u0131n SPF lookup limitini a\u015fmas\u0131na engel olacak \u015fekilde de\u011fi\u015fiklik y\u00f6netimi yapmak iyi bir rutin olu\u015fturur.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>SPF kayd\u0131nda 10 DNS sorgu limitinin ne anlama geldi\u011fini, include zincirlerinin neden k\u0131r\u0131ld\u0131\u011f\u0131n\u0131 ve SPF flattening yakla\u015f\u0131m\u0131yla nas\u0131l sadele\u015ftirme yap\u0131laca\u011f\u0131n\u0131 \u00f6\u011frenin.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[261],"tags":[281,94,99],"class_list":["post-129","post","type-post","status-publish","format-standard","hentry","category-e-posta-kimlik-dogrulama","tag-deliverability","tag-dns","tag-spf"],"_links":{"self":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/129","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/comments?post=129"}],"version-history":[{"count":0,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/129\/revisions"}],"wp:attachment":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/media?parent=129"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/categories?post=129"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/tags?post=129"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}