[{"data":1,"prerenderedAt":42},["ShallowReactive",2],{"$fu4k55jiwdrs9":3},{"title":4,"seoTitle":5,"description":6,"route":7,"kind":8,"toolKey":9,"intro":10,"indexable":11,"sections":12,"related":39},"DMARC 檢查","DMARC 檢查 | nslookup.online","檢查 DMARC DNS 策略、RFC 9989 探索路徑、欄位及設定問題，區分 DNS 設定與實際郵件驗證。","\u002Fzh-tw\u002Fdmarc-checker\u002F","tool","dmarc","讀取已發布策略與探索過程的 DNS 路徑。",true,[13,20,26,33],{"id":14,"title":15,"paragraphs":16,"code":19},"read-answer","檢查 DNS 策略，而非郵件",[17,18],"輸入寄件網域本身，不加 _dmarc 或電子郵件前綴。工具查詢 _dmarc，必要時依 RFC 9989 樹狀探索繼承策略。","實際 DMARC 依賴 SPF\u002FDKIM 與識別碼對齊。本表單沒有郵件情境，不給單封郵件 pass\u002Ffail 結論。","_dmarc.example.com. 300 IN TXT \"v=DMARC1; p=none\"\n\n文件範例 — 非即時 DNS 回應",{"id":21,"title":22,"paragraphs":23},"discovery","目前的策略探索方式",[24,25],"依據 2026 年 5 月 RFC 9989，而非只用已被取代的 RFC 7489 公共後綴方法。保留名稱、路徑與選中記錄作為證據。","有界探索遵循 psd 邊界，不截最後兩段猜組織網域。子網域策略區分名稱存在與 NXDOMAIN；暫時故障標示未完成。",{"id":27,"title":28,"paragraphs":29},"policy","策略意圖與設定問題",[30,31,32],"none 是監測意圖，不是語法錯誤。quarantine、reject 請求接收方處理失敗郵件，但不測量實際動作。","重複候選、重複標籤與無效值會列出，未知標籤保留並忽略。依 RFC 9989 不把舊版 pct 當執行比例。","策略有誤但 rua 語法有效時說明監測備援。找到記錄並非全面安全認證。",{"id":34,"title":35,"paragraphs":36},"questions","哪些項目未檢查",[37,38],"不查外部報告授權、報告投遞、DKIM 金鑰、識別碼對齊或接收方行為。不請求報告 URI，也不寄測試信。","正式變更應核對原始記錄、探索路徑、郵件平台與現行標準，並監測實際驗證報告。",[40,41],"\u002F","\u002Fguides\u002Fnslookup-command\u002F",1792661399399]