{"id":119,"date":"2026-10-06T17:01:16","date_gmt":"2026-10-06T14:01:16","guid":{"rendered":"https:\/\/mx1mail.com\/blog\/dmarc-politikasi-kademeli-uygulama-pct-quarantine-reject\/"},"modified":"2026-10-06T17:01:16","modified_gmt":"2026-10-06T14:01:16","slug":"dmarc-politikasi-kademeli-uygulama-pct-quarantine-reject","status":"publish","type":"post","link":"https:\/\/mx1mail.com\/blog\/tr\/dmarc-politikasi-kademeli-uygulama-pct-quarantine-reject\/","title":{"rendered":"DMARC Politikas\u0131 Nas\u0131l Kademeli Uygulan\u0131r? p=none\u2019dan quarantine ve reject\u2019e Ge\u00e7i\u015f Rehberi"},"content":{"rendered":"<h2>DMARC politikas\u0131n\u0131 \u201ckademeli\u201d uygulamak neden \u00f6nemlidir?<\/h2>\n<p>DMARC, alan ad\u0131n\u0131zdan (domain) g\u00f6nderildi\u011fi iddia edilen e-postalar\u0131n ger\u00e7ekten yetkili sistemlerden \u00e7\u0131k\u0131p \u00e7\u0131kmad\u0131\u011f\u0131n\u0131 do\u011frulamak ve do\u011frulanamayanlar\u0131 nas\u0131l ele alaca\u011f\u0131n\u0131za karar vermek i\u00e7in kullan\u0131lan bir mekanizmad\u0131r. Bir\u00e7ok \u015firket DMARC\u2019\u0131 h\u0131zl\u0131ca \u201creject\u201d seviyesine \u00e7ekmek ister; ancak altyap\u0131daki ger\u00e7ek g\u00f6nderim kaynaklar\u0131 tam olarak g\u00f6r\u00fclmeden bu yap\u0131l\u0131rsa, me\u015fru e-postalar\u0131n teslim edilememesi gibi i\u015f sonu\u00e7lar\u0131 do\u011furabilir.<\/p>\n<p>Kademeli yakla\u015f\u0131m\u0131n amac\u0131; \u00f6nce g\u00f6r\u00fcn\u00fcrl\u00fck kazanmak, sonra kontroll\u00fc \u015fekilde yapt\u0131r\u0131ma ge\u00e7mek ve en sonunda sahtecili\u011fi pratikte engellerken operasyonel riskleri en aza indirmektir. Bu s\u00fcre\u00e7te \u00f6zellikle iki kavram \u00e7ok i\u015fe yarar: p (policy) ve pct (percentage). p, politikan\u0131n seviyesini; pct ise bu politikan\u0131n ne kadar\u0131na uygulanaca\u011f\u0131n\u0131 ifade eder.<\/p>\n<h2>DMARC politika seviyeleri: p=none, p=quarantine, p=reject<\/h2>\n<h3>p=none: izleme ve \u00f6\u011frenme modu<\/h3>\n<p>p=none, e-posta al\u0131c\u0131lar\u0131na \u201csadece raporla, engelleme\/karantinaya alma uygulama\u201d mesaj\u0131 verir. Bu a\u015famada hedef; alan ad\u0131n\u0131zdan e-posta g\u00f6nderen t\u00fcm me\u015fru kaynaklar\u0131 tespit etmektir. \u00d6zellikle \u015fu t\u00fcr kaynaklar g\u00f6zden ka\u00e7abilir: pazarlama otomasyon ara\u00e7lar\u0131, CRM bildirimleri, fatura\/ERP sistemleri, web sunucusu formlar\u0131, helpdesk sistemleri, \u00e7ok fonksiyonlu yaz\u0131c\u0131\/taray\u0131c\u0131lar, \u00fc\u00e7\u00fcnc\u00fc taraf insan kaynaklar\u0131 platformlar\u0131.<\/p>\n<h3>p=quarantine: kontroll\u00fc yapt\u0131r\u0131m<\/h3>\n<p>p=quarantine, DMARC do\u011frulamas\u0131n\u0131 ge\u00e7emeyen iletilerin \u201c\u015f\u00fcpheli\u201d olarak i\u015faretlenmesini \u00f6nerir. Al\u0131c\u0131 sistemler bunu spam klas\u00f6r\u00fcne d\u00fc\u015f\u00fcrme, uyar\u0131 ekleme veya farkl\u0131 filtreleme davran\u0131\u015flar\u0131yla uygulayabilir. Buradaki avantaj, \u201creject\u201d kadar sert bir kesinti yaratmadan ger\u00e7ek d\u00fcnya etkisini g\u00f6rmenizi sa\u011flamas\u0131d\u0131r.<\/p>\n<h3>p=reject: sahte g\u00f6nderimleri g\u00fc\u00e7l\u00fc \u015fekilde engelleme<\/h3>\n<p>p=reject, DMARC\u2019\u0131 ge\u00e7emeyen iletilerin reddedilmesini \u00f6nerir. Bu seviye, alan ad\u0131n\u0131z\u0131n taklit edilmesini pratikte zorla\u015ft\u0131r\u0131r. Ancak \u201ckimin, nereden g\u00f6nderdi\u011fini\u201d tam bilmeden reject\u2019e ge\u00e7mek, \u015firket i\u00e7i ve d\u0131\u015f\u0131 me\u015fru e-postalar\u0131n geri \u00e7evrilmesine yol a\u00e7abilir. Bu y\u00fczden reject genellikle en son ad\u0131md\u0131r.<\/p>\n<h2>pct parametresi nedir ve nas\u0131l kullan\u0131l\u0131r?<\/h2>\n<p>pct, DMARC politikan\u0131z\u0131n yaln\u0131zca belirli bir y\u00fczdelik dilime uygulanmas\u0131n\u0131 sa\u011flar. \u00d6rne\u011fin p=quarantine; pct=20 kullan\u0131rsan\u0131z, DMARC\u2019\u0131 ge\u00e7emeyen iletilerin yakla\u015f\u0131k %20\u2019si karantinaya y\u00f6nlendirilirken geri kalanlar\u0131 izlenmeye devam edebilir. Bu, politikay\u0131 \u201caniden\u201d uygulamak yerine a\u015famal\u0131 y\u00fckseltmenize yard\u0131mc\u0131 olur.<\/p>\n<p>pct kullan\u0131m\u0131nda beklentiyi do\u011fru ayarlamak gerekir: pct bir \u201cgaranti\u201d de\u011fildir, her al\u0131c\u0131 ayn\u0131 \u015fekilde uygulamayabilir ve y\u00fczdeler yakla\u015f\u0131k davran\u0131\u015f g\u00f6sterir. Yine de b\u00fcy\u00fck hacimli alan adlar\u0131nda risk azaltmak i\u00e7in etkilidir.<\/p>\n<h2>Kademeli ge\u00e7i\u015f plan\u0131: pratik bir yol haritas\u0131<\/h2>\n<h3>1) Envanter \u00e7\u0131kar\u0131n: t\u00fcm g\u00f6nderim kaynaklar\u0131<\/h3>\n<p>\u0130lk ad\u0131m, \u015firketiniz ad\u0131na e-posta g\u00f6nderen t\u00fcm sistemlerin listesini \u00e7\u0131karmakt\u0131r. Bu liste yaln\u0131zca \u201ckurumsal e-posta sunucusu\u201d de\u011fildir; uygulamalar, \u00fc\u00e7\u00fcnc\u00fc taraf hizmetler ve cihazlar da dahildir. Her kaynak i\u00e7in \u015fu bilgileri not edin:<\/p>\n<ul>\n<li>Hangi domain\/alt domain ile g\u00f6nderiyor?<\/li>\n<li>G\u00f6nderim IP\u2019leri veya SMTP \u00e7\u0131k\u0131\u015f sa\u011flay\u0131c\u0131s\u0131 nedir?<\/li>\n<li>From adresi hangi formatta? (\u00f6r. billing@, no-reply@, \u00e7al\u0131\u015fan adresleri)<\/li>\n<li>SPF ve DKIM uygulanabiliyor mu?<\/li>\n<\/ul>\n<h3>2) p=none ile raporlama toplay\u0131n ve veriyi anlamland\u0131r\u0131n<\/h3>\n<p>DMARC raporlar\u0131 (aggregate) size hangi kaynaklar\u0131n SPF\/DKIM do\u011frulamas\u0131ndan ge\u00e7ti\u011fini, hangilerinin kald\u0131\u011f\u0131n\u0131 g\u00f6sterir. Bu a\u015famada kritik olan, \u201cba\u015far\u0131s\u0131z\u201d g\u00f6r\u00fcnen trafi\u011fin ger\u00e7ekten sahte mi yoksa yanl\u0131\u015f yap\u0131land\u0131r\u0131lm\u0131\u015f me\u015fru kaynak m\u0131 oldu\u011funu ay\u0131rt etmektir.<\/p>\n<p>Tipik sorun \u00f6rnekleri: SPF kayd\u0131nda eksik g\u00f6nderenler, DKIM imzas\u0131 olmayan \u00fc\u00e7\u00fcnc\u00fc taraflar, From domain\u2019i ile kullan\u0131lan DKIM domain\u2019inin uyu\u015fmamas\u0131, y\u00f6nlendirmeler nedeniyle SPF\u2019in bozulmas\u0131.<\/p>\n<h3>3) SPF ve DKIM\u2019i d\u00fczeltin, m\u00fcmk\u00fcnse iki taraf\u0131 da g\u00fc\u00e7lendirin<\/h3>\n<p>Kademeli uygulama ba\u015far\u0131l\u0131 olacaksa, g\u00f6nderim kaynaklar\u0131n\u0131z\u0131n m\u00fcmk\u00fcn oldu\u011funca hem SPF hem DKIM taraf\u0131nda \u201csa\u011fl\u0131kl\u0131\u201d olmas\u0131 gerekir. Pratik \u00f6neriler:<\/p>\n<ul>\n<li>SPF kayd\u0131n\u0131z\u0131 sade tutun ve ger\u00e7ekten kullan\u0131lan kaynaklar\u0131 ekleyin.<\/li>\n<li>\u00dc\u00e7\u00fcnc\u00fc taraf bir sistem kullan\u0131yorsan\u0131z, o sistemin \u00f6nerdi\u011fi SPF mekanizmas\u0131n\u0131 ve DKIM anahtarlar\u0131n\u0131 uygulay\u0131n.<\/li>\n<li>DKIM anahtar y\u00f6netimini planlay\u0131n: hangi selector kullan\u0131lacak, anahtar rotasyonu nas\u0131l yap\u0131lacak?<\/li>\n<li>Alt domain kullan\u0131m\u0131n\u0131 d\u00fc\u015f\u00fcn\u00fcn: pazarlama trafi\u011fini ayr\u0131 bir subdomain \u00fczerinden y\u00fcr\u00fctmek raporlama ve risk y\u00f6netimini kolayla\u015ft\u0131rabilir.<\/li>\n<\/ul>\n<h3>4) p=quarantine\u2019a ge\u00e7in, pct ile ba\u015flay\u0131n<\/h3>\n<p>p=none a\u015famas\u0131nda beklenmedik me\u015fru kaynak kalmad\u0131\u011f\u0131ndan emin olmaya ba\u015flad\u0131\u011f\u0131n\u0131zda, p=quarantine\u2019a ge\u00e7i\u015f yap\u0131n. \u0130lk a\u015famada d\u00fc\u015f\u00fck bir pct ile ba\u015flamak, \u00f6rne\u011fin 10\u201325 aral\u0131\u011f\u0131nda, ger\u00e7ek d\u00fcnya etkisini g\u00f6zlemlemek i\u00e7in makuld\u00fcr.<\/p>\n<p>Bu a\u015famada izlemeniz gerekenler:<\/p>\n<ul>\n<li>\u015eikayetler: \u201cmailim kar\u015f\u0131 tarafa d\u00fc\u015fm\u00fcyor\u201d geri bildirimleri<\/li>\n<li>\u0130\u015f kritik iletiler: fatura, sipari\u015f, parola s\u0131f\u0131rlama, teklif gibi ak\u0131\u015flar<\/li>\n<li>Raporlar: h\u00e2l\u00e2 DMARC fail g\u00f6r\u00fcnen me\u015fru kaynak var m\u0131?<\/li>\n<\/ul>\n<p>Problemleri d\u00fczelttik\u00e7e pct\u2019yi 25 \u2192 50 \u2192 75 \u2192 100 gibi a\u015famalarla y\u00fckseltebilirsiniz. Her y\u00fckseltmede belirli bir g\u00f6zlem s\u00fcresi b\u0131rakmak (\u00f6rne\u011fin birka\u00e7 g\u00fcn ile birka\u00e7 hafta aras\u0131, trafik hacmine g\u00f6re) daha g\u00fcvenlidir.<\/p>\n<h3>5) p=reject\u2019e kademeli ge\u00e7in<\/h3>\n<p>quarantine a\u015famas\u0131nda pct=100 seviyesinde stabil kald\u0131ysan\u0131z ve raporlarda kalan ba\u015far\u0131s\u0131z trafi\u011fin b\u00fcy\u00fck b\u00f6l\u00fcm\u00fcn\u00fcn sahte\/istenmeyen oldu\u011fundan eminseniz, p=reject\u2019e ge\u00e7i\u015f planlanabilir. Burada da pct kullanarak \u00f6nce s\u0131n\u0131rl\u0131 bir y\u00fczdeyle ba\u015flay\u0131p sonra art\u0131rmak, olas\u0131 s\u00fcrprizleri azalt\u0131r.<\/p>\n<h2>Ge\u00e7i\u015f s\u0131ras\u0131nda s\u0131k yap\u0131lan hatalar<\/h2>\n<h3>\u201cBir kaynak kald\u0131 ama \u00f6nemsiz\u201d varsay\u0131m\u0131<\/h3>\n<p>\u00d6nemsiz g\u00f6r\u00fcnen bir kaynak, kritik bir i\u015f ak\u0131\u015f\u0131n\u0131 besliyor olabilir (\u00f6r. bir \u015fubenin yaz\u0131c\u0131s\u0131 veya eski bir uygulama). p=reject\u2019e ge\u00e7meden \u00f6nce bu \u201ck\u00fc\u00e7\u00fck\u201d kaynaklar\u0131n i\u015f etkisini do\u011frulay\u0131n.<\/p>\n<h3>SPF\u2019e a\u015f\u0131r\u0131 y\u00fcklenmek<\/h3>\n<p>Her \u015feyi SPF\u2019e eklemeye \u00e7al\u0131\u015fmak y\u00f6netimi zorla\u015ft\u0131r\u0131r ve teknik s\u0131n\u0131rlara yakla\u015fabilir. DKIM\u2019i devreye almak ve gerekirse g\u00f6nderimleri alt domain\u2019lere ay\u0131rmak daha s\u00fcrd\u00fcr\u00fclebilir olabilir.<\/p>\n<h3>Alt domain\u2019leri unutmak<\/h3>\n<p>example.com i\u00e7in DMARC uygulaman\u0131z, mail.example.com veya billing.example.com gibi alt domain davran\u0131\u015flar\u0131n\u0131 ayr\u0131 de\u011ferlendirmeyi gerektirebilir. Politika tasar\u0131m\u0131n\u0131 alt domain\u2019leri de kapsayacak \u015fekilde d\u00fc\u015f\u00fcn\u00fcn.<\/p>\n<h2>Operasyonel kontrol listesi<\/h2>\n<ol>\n<li>T\u00fcm g\u00f6nderim kaynaklar\u0131 listelendi mi?<\/li>\n<li>Her kaynak i\u00e7in SPF ve DKIM sorumlusu belli mi?<\/li>\n<li>DMARC p=none raporlar\u0131 d\u00fczenli inceleniyor mu?<\/li>\n<li>Me\u015fru kaynaklarda DMARC ge\u00e7i\u015f oran\u0131 hedefi belirlendi mi?<\/li>\n<li>p=quarantine ve pct art\u0131\u015f\u0131 i\u00e7in takvim haz\u0131r m\u0131?<\/li>\n<li>\u0130\u015f kritik e-posta ak\u0131\u015flar\u0131 test edildi mi?<\/li>\n<li>p=reject\u2019e ge\u00e7i\u015f i\u00e7in \u201chaz\u0131r olma kriterleri\u201d tan\u0131mland\u0131 m\u0131?<\/li>\n<\/ol>\n<h2>Sonu\u00e7: g\u00fcvenlik ve teslim edilebilirli\u011fi birlikte optimize edin<\/h2>\n<p>DMARC\u2019\u0131 kademeli uygulamak, sahtecilik riskini azalt\u0131rken me\u015fru e-postalar\u0131n teslim edilebilirli\u011fini koruman\u0131n en g\u00fcvenli yollar\u0131ndan biridir. p=none ile g\u00f6r\u00fcn\u00fcrl\u00fck kazan\u0131p, p=quarantine ve p=reject\u2019e pct ile kontroll\u00fc ge\u00e7i\u015f yapmak; IT ekiplerinin raporlara dayanarak ilerlemesini sa\u011flar.<\/p>\n<p>E\u011fer kurumsal e-posta altyap\u0131n\u0131z\u0131 y\u00f6netirken alan ad\u0131 do\u011frulama kay\u0131tlar\u0131n\u0131z\u0131 (SPF, DKIM, DMARC) daha d\u00fczenli bir yap\u0131da tutmak ve ge\u00e7i\u015f\/migration d\u00f6nemlerinde riskleri azaltmak istiyorsan\u0131z, MX1Mail gibi y\u00f6netilebilir bir i\u015f e-postas\u0131 platformunda DNS ve g\u00f6nderim kaynaklar\u0131n\u0131 envanter yakla\u015f\u0131m\u0131yla ele almak i\u015finizi kolayla\u015ft\u0131rabilir.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>DMARC\u2019\u0131 p=none ile izleyip, pct ile kademeli uygulayarak quarantine ve reject seviyelerine g\u00fcvenle ge\u00e7mek i\u00e7in pratik ad\u0131mlar ve kontrol listesi.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10],"tags":[109,275,277],"class_list":["post-119","post","type-post","status-publish","format-standard","hentry","category-e-posta-guvenligi","tag-dmarc","tag-e-posta-dogrulama","tag-teslim-edilebilirlik"],"_links":{"self":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/119","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=119"}],"version-history":[{"count":0,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/posts\/119\/revisions"}],"wp:attachment":[{"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/media?parent=119"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/categories?post=119"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mx1mail.com\/blog\/wp-json\/wp\/v2\/tags?post=119"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}