[{"data":1,"prerenderedAt":605},["ShallowReactive",2],{"email-header-analyzer":3,"mdc-awsl5d-key":57,"mdc-ckvmsy-key":160,"mdc-mjy7dp-key":303,"mdc-7xswuu-key":479,"mdc--x763jl-key":534,"mdc-akdjaq-key":542,"mdc--k0q1eh-key":550,"mdc--p3r214-key":558,"mdc-6qp1g6-key":566},{"id":4,"title":5,"body":6,"cta":7,"description":6,"extension":12,"faq":13,"hero":31,"lastUpdated":35,"meta":36,"navigation":37,"path":38,"sections":39,"seo":52,"stem":55,"__hash__":56},"headerAnalyzer\u002Ftools\u002Femail-header-analyzer.yml","Email Header Analyzer",null,{"title":8,"description":9,"label":10,"to":11},"Send and answer email across all your domains","Mailyond receives mail on every domain you connect directly, so it doesn't pass through a forwarder that breaks SPF, and sends from the same domains. From $10\u002Fmonth: Basic $10 for up to 5 domains, Pro $20 for up to 10, Agency $40 for up to 30. Basic and Pro start with a 7-day free trial.","Start your free trial","\u002Fsignup","yml",{"title":14,"items":15},"FAQ",[16,19,22,25,28],{"title":17,"description":18},"What does an email header analyzer show?","The technical lines your mail app hides: which servers a message passed through and when, what the receiving server recorded for SPF, DKIM and DMARC, and which domains those checks ran on. This one also compares those domains with the From address, flags hops that took over a minute, and spots forwarding.",{"title":20,"description":21},"Is it safe to paste my email headers here?","Yes. The analyzer runs in your browser, and nothing you paste is sent to our server or stored, not even in your browser's storage. Our analytics only records the verdict and the number of hops. Headers hold addresses, server names and IP addresses, not the message body. If you paste a whole message source, only the header part, up to the first blank line, is read.",{"title":23,"description":24},"Why does SPF pass but DMARC fail?","Because SPF passed for a different domain than the one in From. Sending services often use their own bounce domain as the envelope sender, so SPF passes for that domain, which doesn't align with yours. DMARC then needs DKIM to pass for your From domain, and if the service signs with its own domain, or doesn't sign at all, DMARC fails. The fix is DKIM signing with your own domain, or a custom Return-Path domain at your sending service.",{"title":26,"description":27},"Why did my forwarded email fail SPF?","The forwarder sent it on from its own IP address, which isn't in the original sender's SPF record. If the forwarder uses SRS, SPF passes for the forwarder's domain instead, which doesn't align with From. Either way, DMARC depends on the original DKIM signature surviving the forward, and ARC lets the final receiver see the results from before it.",{"title":29,"description":30},"How do I find the DKIM selector in a header?","Look at the `DKIM-Signature` header: `s=` is the selector and `d=` is the signing domain. The analyzer lists both for every signature in the message. With those two, the DKIM checker shows the key published at `\u003Cselector>._domainkey.\u003Cdomain>`.",{"title":32,"description":33,"note":34},"Email header analyzer","Paste a message's headers into this free email header analyzer to see where it went, how long each hop took, and whether SPF, DKIM and DMARC passed.","No signup. Your headers never leave your browser.","2026-11-14",{},true,"\u002Ftools\u002Femail-header-analyzer",[40,43,46,49],{"title":41,"content":42},"How to use the email header analyzer","Paste a message's full headers, or its whole source, into the box at the top of this page. The results show up as soon as you paste, and the **Analyze** button runs it again after an edit. No message at hand? Click **Example** to load a forwarded message with every card filled in.\n\nThe results come in cards:\n\n- **Verdict**: one line that says whether the message was delivered clean, passed with a warning, or failed authentication, and why.\n- **SPF, DKIM and DMARC**: the result the receiving server recorded for each check, and the domain it checked.\n- **Alignment**: the From domain next to the domains SPF and DKIM checked, and whether they match.\n- **Hops**: every server the message passed through, oldest first, with the delay at each one.\n- **Forwarding**: shown when the message was forwarded, with what that did to SPF.\n- **Key fields**: From, To, Delivered-To, Reply-To, Subject, Date and Message-ID.\n\nEverything runs in your browser. The headers you paste aren't sent anywhere or saved.\n",{"title":44,"content":45},"How to get the full headers","You need the full headers, not just the From and To lines your mail app shows.\n\n**Gmail** (on a computer): open the message, then next to **Reply** click **More** (the three dots), then **Show original**. The full header opens in a new window. Click **Copy to clipboard**, then paste it here.\n\n**Outlook**: in the new Outlook for Windows and in Outlook on the web or Outlook.com, open the message, select **More actions** (the three dots) at the top of the message window, then **View** > **View message details**. Select the header text and copy it. In classic Outlook for Windows, double-click the message to open it in its own window, then click **File** > **Properties**. The headers are in the **Internet headers** box: click in the box, select all and press Ctrl+C.\n\n**Apple Mail on Mac**: open the message and choose **View** > **Message** > **All Headers**, then select the header lines and copy them. To go back, choose **View** > **Message** > **Default Headers**.\n",{"title":47,"content":48},"How to read the results","Start with the verdict:\n\n- **Delivered clean** (green): SPF and DKIM both passed for the From domain, DMARC passed or wasn't checked, and no hop took over a minute.\n- **Passed with a warning** (amber): the message got through, but something is fragile. SPF failed or passed for another domain, DKIM didn't pass for the From domain, the domain has no DMARC policy or publishes `p=none`, a hop took over a minute, or the receiver recorded no results at all.\n- **Failed authentication** (red): DMARC failed, or neither SPF nor DKIM passed.\n\nThe SPF, DKIM and DMARC cards show what the receiving server wrote in its `Authentication-Results` header. The analyzer reads the topmost one, because the last server to handle a message adds its header on top. SPF checks the envelope sender (the `Return-Path`, shown as `smtp.mailfrom`). DKIM checks a signature made for the `d=` domain. DMARC passes when one of the two passed for a domain that aligns with the From address.\n\nAlignment is where most surprises are. Under relaxed alignment, the default, two domains align when they share an organizational domain: `bounces.yourdomain.com` aligns with `yourdomain.com`, but `mail.yoursender.net` doesn't. The analyzer takes the organizational domain from the last two labels, or three for suffixes like `co.uk`, so treat it as a close guide rather than the full public suffix list.\n\nWhen a check fails or doesn't align, the card links to the matching checker with the domain filled in, and only the domain goes into that link. The [SPF checker](\u002Ftools\u002Fspf-checker) shows the record and its lookup count, the [DKIM checker](\u002Ftools\u002Fdkim-checker) looks for the key at common selectors, and the [DMARC checker](\u002Ftools\u002Fdmarc-checker) reads the policy and alignment settings.\n\nHops read from oldest to newest, the reverse of the raw header, since each server adds its `Received` line on top. The first delay is measured from the `Date` header, and each later one from the hop before it. A hop over 1 minute gets a flag: that's usually a queue, greylisting or a retry. A negative delay means two servers' clocks disagree, so it shows as 0 with a clock skew note.\n",{"title":50,"content":51},"Why SPF fails on forwarded mail","A forwarder sends the message on from its own IP address. That address isn't in the original sender's SPF record, so SPF fails for the original domain.\n\nMost forwarders rewrite the envelope sender with SRS (Sender Rewriting Scheme), so the `Return-Path` looks like `SRS0=hash=tt=yourdomain.com=alice@forwarder.example.net`. SPF then passes, but for the forwarder's domain, which doesn't align with the From domain. Either way, DMARC depends on DKIM surviving the forward: if the forwarder leaves the signed parts of the message alone, the original DKIM signature still passes, and DMARC passes with it.\n\nARC (Authenticated Received Chain) carries the results from before the forward. The forwarder records what SPF, DKIM and DMARC said when the message reached it and seals that record, so the final receiver can choose to trust those results when its own SPF check fails. The analyzer counts the ARC sets and shows the latest seal's `cv=` value.\n\nCloudflare Email Routing is a common case: it rewrites the envelope sender with SRS and adds ARC. Our guide to [Cloudflare email forwarding](\u002Fblog\u002Fcloudflare-email-forwarding) covers the setup and why a forwarded test email never shows up.\n",{"title":53,"description":54},"Email Header Analyzer: Trace Hops and Check SPF, DKIM, DMARC","Free email header analyzer. Paste the headers of any message to see every hop, the SPF, DKIM and DMARC results and why mail failed. Runs in your browser.","tools\u002Femail-header-analyzer","jz2U0_6H4J99bq-O0Siz7402XQ0gXnxZchvNTe3tVAo",{"data":58,"body":59},{},{"type":60,"children":61},"root",[62,85,90,155],{"type":63,"tag":64,"props":65,"children":66},"element","p",{},[67,70,76,78,83],{"type":68,"value":69},"text","Paste a message's full headers, or its whole source, into the box at the top of this page. The results show up as soon as you paste, and the ",{"type":63,"tag":71,"props":72,"children":73},"strong",{},[74],{"type":68,"value":75},"Analyze",{"type":68,"value":77}," button runs it again after an edit. No message at hand? Click ",{"type":63,"tag":71,"props":79,"children":80},{},[81],{"type":68,"value":82},"Example",{"type":68,"value":84}," to load a forwarded message with every card filled in.",{"type":63,"tag":64,"props":86,"children":87},{},[88],{"type":68,"value":89},"The results come in cards:",{"type":63,"tag":91,"props":92,"children":93},"ul",{},[94,105,115,125,135,145],{"type":63,"tag":95,"props":96,"children":97},"li",{},[98,103],{"type":63,"tag":71,"props":99,"children":100},{},[101],{"type":68,"value":102},"Verdict",{"type":68,"value":104},": one line that says whether the message was delivered clean, passed with a warning, or failed authentication, and why.",{"type":63,"tag":95,"props":106,"children":107},{},[108,113],{"type":63,"tag":71,"props":109,"children":110},{},[111],{"type":68,"value":112},"SPF, DKIM and DMARC",{"type":68,"value":114},": the result the receiving server recorded for each check, and the domain it checked.",{"type":63,"tag":95,"props":116,"children":117},{},[118,123],{"type":63,"tag":71,"props":119,"children":120},{},[121],{"type":68,"value":122},"Alignment",{"type":68,"value":124},": the From domain next to the domains SPF and DKIM checked, and whether they match.",{"type":63,"tag":95,"props":126,"children":127},{},[128,133],{"type":63,"tag":71,"props":129,"children":130},{},[131],{"type":68,"value":132},"Hops",{"type":68,"value":134},": every server the message passed through, oldest first, with the delay at each one.",{"type":63,"tag":95,"props":136,"children":137},{},[138,143],{"type":63,"tag":71,"props":139,"children":140},{},[141],{"type":68,"value":142},"Forwarding",{"type":68,"value":144},": shown when the message was forwarded, with what that did to SPF.",{"type":63,"tag":95,"props":146,"children":147},{},[148,153],{"type":63,"tag":71,"props":149,"children":150},{},[151],{"type":68,"value":152},"Key fields",{"type":68,"value":154},": From, To, Delivered-To, Reply-To, Subject, Date and Message-ID.",{"type":63,"tag":64,"props":156,"children":157},{},[158],{"type":68,"value":159},"Everything runs in your browser. The headers you paste aren't sent anywhere or saved.",{"data":161,"body":162},{},{"type":60,"children":163},[164,169,207,258],{"type":63,"tag":64,"props":165,"children":166},{},[167],{"type":68,"value":168},"You need the full headers, not just the From and To lines your mail app shows.",{"type":63,"tag":64,"props":170,"children":171},{},[172,177,179,184,186,191,193,198,200,205],{"type":63,"tag":71,"props":173,"children":174},{},[175],{"type":68,"value":176},"Gmail",{"type":68,"value":178}," (on a computer): open the message, then next to ",{"type":63,"tag":71,"props":180,"children":181},{},[182],{"type":68,"value":183},"Reply",{"type":68,"value":185}," click ",{"type":63,"tag":71,"props":187,"children":188},{},[189],{"type":68,"value":190},"More",{"type":68,"value":192}," (the three dots), then ",{"type":63,"tag":71,"props":194,"children":195},{},[196],{"type":68,"value":197},"Show original",{"type":68,"value":199},". The full header opens in a new window. Click ",{"type":63,"tag":71,"props":201,"children":202},{},[203],{"type":68,"value":204},"Copy to clipboard",{"type":68,"value":206},", then paste it here.",{"type":63,"tag":64,"props":208,"children":209},{},[210,215,217,222,224,229,231,236,238,243,244,249,251,256],{"type":63,"tag":71,"props":211,"children":212},{},[213],{"type":68,"value":214},"Outlook",{"type":68,"value":216},": in the new Outlook for Windows and in Outlook on the web or Outlook.com, open the message, select ",{"type":63,"tag":71,"props":218,"children":219},{},[220],{"type":68,"value":221},"More actions",{"type":68,"value":223}," (the three dots) at the top of the message window, then ",{"type":63,"tag":71,"props":225,"children":226},{},[227],{"type":68,"value":228},"View",{"type":68,"value":230}," > ",{"type":63,"tag":71,"props":232,"children":233},{},[234],{"type":68,"value":235},"View message details",{"type":68,"value":237},". Select the header text and copy it. In classic Outlook for Windows, double-click the message to open it in its own window, then click ",{"type":63,"tag":71,"props":239,"children":240},{},[241],{"type":68,"value":242},"File",{"type":68,"value":230},{"type":63,"tag":71,"props":245,"children":246},{},[247],{"type":68,"value":248},"Properties",{"type":68,"value":250},". The headers are in the ",{"type":63,"tag":71,"props":252,"children":253},{},[254],{"type":68,"value":255},"Internet headers",{"type":68,"value":257}," box: click in the box, select all and press Ctrl+C.",{"type":63,"tag":64,"props":259,"children":260},{},[261,266,268,272,273,278,279,284,286,290,291,295,296,301],{"type":63,"tag":71,"props":262,"children":263},{},[264],{"type":68,"value":265},"Apple Mail on Mac",{"type":68,"value":267},": open the message and choose ",{"type":63,"tag":71,"props":269,"children":270},{},[271],{"type":68,"value":228},{"type":68,"value":230},{"type":63,"tag":71,"props":274,"children":275},{},[276],{"type":68,"value":277},"Message",{"type":68,"value":230},{"type":63,"tag":71,"props":280,"children":281},{},[282],{"type":68,"value":283},"All Headers",{"type":68,"value":285},", then select the header lines and copy them. To go back, choose ",{"type":63,"tag":71,"props":287,"children":288},{},[289],{"type":68,"value":228},{"type":68,"value":230},{"type":63,"tag":71,"props":292,"children":293},{},[294],{"type":68,"value":277},{"type":68,"value":230},{"type":63,"tag":71,"props":297,"children":298},{},[299],{"type":68,"value":300},"Default Headers",{"type":68,"value":302},".",{"data":304,"body":305},{},{"type":60,"children":306},[307,312,354,391,428,458],{"type":63,"tag":64,"props":308,"children":309},{},[310],{"type":68,"value":311},"Start with the verdict:",{"type":63,"tag":91,"props":313,"children":314},{},[315,325,344],{"type":63,"tag":95,"props":316,"children":317},{},[318,323],{"type":63,"tag":71,"props":319,"children":320},{},[321],{"type":68,"value":322},"Delivered clean",{"type":68,"value":324}," (green): SPF and DKIM both passed for the From domain, DMARC passed or wasn't checked, and no hop took over a minute.",{"type":63,"tag":95,"props":326,"children":327},{},[328,333,335,342],{"type":63,"tag":71,"props":329,"children":330},{},[331],{"type":68,"value":332},"Passed with a warning",{"type":68,"value":334}," (amber): the message got through, but something is fragile. SPF failed or passed for another domain, DKIM didn't pass for the From domain, the domain has no DMARC policy or publishes ",{"type":63,"tag":336,"props":337,"children":339},"code",{"className":338},[],[340],{"type":68,"value":341},"p=none",{"type":68,"value":343},", a hop took over a minute, or the receiver recorded no results at all.",{"type":63,"tag":95,"props":345,"children":346},{},[347,352],{"type":63,"tag":71,"props":348,"children":349},{},[350],{"type":68,"value":351},"Failed authentication",{"type":68,"value":353}," (red): DMARC failed, or neither SPF nor DKIM passed.",{"type":63,"tag":64,"props":355,"children":356},{},[357,359,365,367,373,375,381,383,389],{"type":68,"value":358},"The SPF, DKIM and DMARC cards show what the receiving server wrote in its ",{"type":63,"tag":336,"props":360,"children":362},{"className":361},[],[363],{"type":68,"value":364},"Authentication-Results",{"type":68,"value":366}," header. The analyzer reads the topmost one, because the last server to handle a message adds its header on top. SPF checks the envelope sender (the ",{"type":63,"tag":336,"props":368,"children":370},{"className":369},[],[371],{"type":68,"value":372},"Return-Path",{"type":68,"value":374},", shown as ",{"type":63,"tag":336,"props":376,"children":378},{"className":377},[],[379],{"type":68,"value":380},"smtp.mailfrom",{"type":68,"value":382},"). DKIM checks a signature made for the ",{"type":63,"tag":336,"props":384,"children":386},{"className":385},[],[387],{"type":68,"value":388},"d=",{"type":68,"value":390}," domain. DMARC passes when one of the two passed for a domain that aligns with the From address.",{"type":63,"tag":64,"props":392,"children":393},{},[394,396,402,404,410,412,418,420,426],{"type":68,"value":395},"Alignment is where most surprises are. Under relaxed alignment, the default, two domains align when they share an organizational domain: ",{"type":63,"tag":336,"props":397,"children":399},{"className":398},[],[400],{"type":68,"value":401},"bounces.yourdomain.com",{"type":68,"value":403}," aligns with ",{"type":63,"tag":336,"props":405,"children":407},{"className":406},[],[408],{"type":68,"value":409},"yourdomain.com",{"type":68,"value":411},", but ",{"type":63,"tag":336,"props":413,"children":415},{"className":414},[],[416],{"type":68,"value":417},"mail.yoursender.net",{"type":68,"value":419}," doesn't. The analyzer takes the organizational domain from the last two labels, or three for suffixes like ",{"type":63,"tag":336,"props":421,"children":423},{"className":422},[],[424],{"type":68,"value":425},"co.uk",{"type":68,"value":427},", so treat it as a close guide rather than the full public suffix list.",{"type":63,"tag":64,"props":429,"children":430},{},[431,433,440,442,448,450,456],{"type":68,"value":432},"When a check fails or doesn't align, the card links to the matching checker with the domain filled in, and only the domain goes into that link. The ",{"type":63,"tag":434,"props":435,"children":437},"a",{"href":436},"\u002Ftools\u002Fspf-checker",[438],{"type":68,"value":439},"SPF checker",{"type":68,"value":441}," shows the record and its lookup count, the ",{"type":63,"tag":434,"props":443,"children":445},{"href":444},"\u002Ftools\u002Fdkim-checker",[446],{"type":68,"value":447},"DKIM checker",{"type":68,"value":449}," looks for the key at common selectors, and the ",{"type":63,"tag":434,"props":451,"children":453},{"href":452},"\u002Ftools\u002Fdmarc-checker",[454],{"type":68,"value":455},"DMARC checker",{"type":68,"value":457}," reads the policy and alignment settings.",{"type":63,"tag":64,"props":459,"children":460},{},[461,463,469,471,477],{"type":68,"value":462},"Hops read from oldest to newest, the reverse of the raw header, since each server adds its ",{"type":63,"tag":336,"props":464,"children":466},{"className":465},[],[467],{"type":68,"value":468},"Received",{"type":68,"value":470}," line on top. The first delay is measured from the ",{"type":63,"tag":336,"props":472,"children":474},{"className":473},[],[475],{"type":68,"value":476},"Date",{"type":68,"value":478}," header, and each later one from the hop before it. A hop over 1 minute gets a flag: that's usually a queue, greylisting or a retry. A negative delay means two servers' clocks disagree, so it shows as 0 with a clock skew note.",{"data":480,"body":481},{},{"type":60,"children":482},[483,488,508,521],{"type":63,"tag":64,"props":484,"children":485},{},[486],{"type":68,"value":487},"A forwarder sends the message on from its own IP address. That address isn't in the original sender's SPF record, so SPF fails for the original domain.",{"type":63,"tag":64,"props":489,"children":490},{},[491,493,498,500,506],{"type":68,"value":492},"Most forwarders rewrite the envelope sender with SRS (Sender Rewriting Scheme), so the ",{"type":63,"tag":336,"props":494,"children":496},{"className":495},[],[497],{"type":68,"value":372},{"type":68,"value":499}," looks like ",{"type":63,"tag":336,"props":501,"children":503},{"className":502},[],[504],{"type":68,"value":505},"SRS0=hash=tt=yourdomain.com=alice@forwarder.example.net",{"type":68,"value":507},". SPF then passes, but for the forwarder's domain, which doesn't align with the From domain. Either way, DMARC depends on DKIM surviving the forward: if the forwarder leaves the signed parts of the message alone, the original DKIM signature still passes, and DMARC passes with it.",{"type":63,"tag":64,"props":509,"children":510},{},[511,513,519],{"type":68,"value":512},"ARC (Authenticated Received Chain) carries the results from before the forward. The forwarder records what SPF, DKIM and DMARC said when the message reached it and seals that record, so the final receiver can choose to trust those results when its own SPF check fails. The analyzer counts the ARC sets and shows the latest seal's ",{"type":63,"tag":336,"props":514,"children":516},{"className":515},[],[517],{"type":68,"value":518},"cv=",{"type":68,"value":520}," value.",{"type":63,"tag":64,"props":522,"children":523},{},[524,526,532],{"type":68,"value":525},"Cloudflare Email Routing is a common case: it rewrites the envelope sender with SRS and adds ARC. Our guide to ",{"type":63,"tag":434,"props":527,"children":529},{"href":528},"\u002Fblog\u002Fcloudflare-email-forwarding",[530],{"type":68,"value":531},"Cloudflare email forwarding",{"type":68,"value":533}," covers the setup and why a forwarded test email never shows up.",{"data":535,"body":536},{},{"type":60,"children":537},[538],{"type":63,"tag":64,"props":539,"children":540},{},[541],{"type":68,"value":18},{"data":543,"body":544},{},{"type":60,"children":545},[546],{"type":63,"tag":64,"props":547,"children":548},{},[549],{"type":68,"value":21},{"data":551,"body":552},{},{"type":60,"children":553},[554],{"type":63,"tag":64,"props":555,"children":556},{},[557],{"type":68,"value":24},{"data":559,"body":560},{},{"type":60,"children":561},[562],{"type":63,"tag":64,"props":563,"children":564},{},[565],{"type":68,"value":27},{"data":567,"body":568},{},{"type":60,"children":569},[570],{"type":63,"tag":64,"props":571,"children":572},{},[573,575,581,583,589,591,596,598,604],{"type":68,"value":574},"Look at the ",{"type":63,"tag":336,"props":576,"children":578},{"className":577},[],[579],{"type":68,"value":580},"DKIM-Signature",{"type":68,"value":582}," header: ",{"type":63,"tag":336,"props":584,"children":586},{"className":585},[],[587],{"type":68,"value":588},"s=",{"type":68,"value":590}," is the selector and ",{"type":63,"tag":336,"props":592,"children":594},{"className":593},[],[595],{"type":68,"value":388},{"type":68,"value":597}," is the signing domain. The analyzer lists both for every signature in the message. With those two, the DKIM checker shows the key published at ",{"type":63,"tag":336,"props":599,"children":601},{"className":600},[],[602],{"type":68,"value":603},"\u003Cselector>._domainkey.\u003Cdomain>",{"type":68,"value":302},1794941737384]