Choose one of three approaches. The steps for that option appear below.
Choose an option above. On a phone, swipe the tabs left or right to see all options →
Gemini drafts hop tables and findings; you check mail-system evidence and approve proposed edits without changing DNS.
Collect raw headers and exact
Draft the hop table
Check findings and record approved
Use: You
Have ready: raw message headers as text and the domain's SPF, DKIM selector and DMARC TXT records copied exactly as published.
Records are quoted exactly as published; do not reformat or correct them. Check your organisation's rules before placing mail data into any tool.
Use: Gemini
Ask Gemini for hop, server, spf, dkim, dmarc, header_line; check against logs before requesting findings and proposed record edits.
What to paste into the tool
Task: Draft hop and result table (CSV: hop, server, spf, dkim, dmarc, header_line). Parse these raw email headers. Return a table with one row per hop: hop number, server, SPF result, DKIM result, DMARC result, and the exact header line each result comes from. Quote header lines exactly. If a result is absent, write absent. Task: Draft findings on SPF, DKIM and DMARC alignment with proposed record edits. Compare these authentication results with these DNS records. For each finding quote the exact header line or record text it rests on and name the hop where trouble starts; propose a record edit only where the evidence warrants one, otherwise write no edit indicated. Do not invent record values.
Use: You
Check hops against logs and every quoted line against raw headers. Check each proposed edit against the mail system; record current rollback values.
The admin confirms every proposed edit against their mail system before changing DNS, and keeps the old record to roll back. No DNS change is made by the workflow. Discard any finding without a header line or record to back it.
You build the hop table; Perplexity provides cited explanations and findings, then you check every edit without changing DNS.
Write the hop and authentication
Explain mechanisms and draft cited
Check findings and record approved
Use: You
Have ready: raw headers and exact domain TXT records. Write hop, server, spf, dkim, dmarc, header_line by hand.
Confirm hops against the mail system logs and quote each header line exactly.
Use: Perplexity
Ask Perplexity for cited authentication-code and SPF, DKIM, DMARC explanations; open sources before requesting findings with exact header or record citations.
What to paste into the tool
Task: Cited explanations for each code and mechanism. Explain what this authentication result code means and cite the primary specification or documentation. Then explain what this DNS record mechanism does, with citations. Task: Draft findings document with proposed record edits. Using only this material - the hop table, the DNS records pasted exactly, and the cited explanations I confirmed - draft a findings document: what failed, at which hop, the exact header line or record text each finding rests on, and a proposed record edit per finding. Quote every record exactly as pasted. Do not add causes, mechanisms or edits that are not in this material.
Use: You
Check each sentence against the hop table and exact records; approve or rewrite proposals and record current rollback values.
Each finding cites a header line or record text, with records quoted exactly; the admin confirms every proposed edit against their mail system before changing DNS and keeps the old record to roll back. Open each cited source and confirm it says what the answer claims before relying on it. Check every sentence against the hop table and the exact records.
You build the hop table; Mistral Vibe (formerly Le Chat) drafts notes and findings, with your source check between stages.
Write the hop and authentication
Draft a cited note
Check and correct every finding
Draft the findings from checked
Check findings and keep rollback
Use: You
Have ready: raw headers and exact TXT records. Write hop, server, spf, dkim, dmarc, header_line by hand.
Confirm hops against the mail system logs and quote each header line exactly.
Use: Mistral Vibe
Ask Mistral Vibe for each failure, hop, supporting header line or record text and proposed record edit; quote records exactly.
What to paste into the tool
Task: Draft finding notes with proposed edits. Using only this hop table and these DNS records pasted exactly, write a short note per failure: what failed, at which hop, the exact header line or record text it rests on, and a proposed record edit. Quote every record exactly as pasted. Do not add causes or mechanisms that are not in this material.
Use: You
Compare notes with the hop table and exact records; correct or discard wrong notes and check proposed edits.
Each confirmed note cites a header line or record text; records are quoted exactly. Check each note against the hop table and the exact records before confirming it.
Use: Mistral Vibe
Give Mistral Vibe the table, exact records and checked notes; ask for the findings document.
What to paste into the tool
Task: Draft findings document. Draft a findings document from only this material: the hop table, the DNS records and my confirmed notes. Keep every quoted header line and record text exactly as given. Do not add causes, mechanisms or edits that are not in my notes.
Use: You
Check each sentence against the table, records and notes; remove unsupported claims, approve proposals and record current record values.
The admin confirms every proposed edit against their mail system before changing DNS, and keeps the old record to roll back. No DNS change is made by the workflow.
Best when: You want header parsing and cited findings drafted together.
What it does: Gemini drafts; you check and decide
Strong at: Drafts hop and authentication tables with exact header-line references.
Limit: The admin must check each edit against their own mail system.
Free plan: Yes, prompt caps
Best when: You want cited references for unfamiliar authentication results and mechanisms.
What it does: Perplexity drafts; you check and decide
Strong at: Links explanations of authentication codes and DNS mechanisms to sources.
Limit: Every cited source and proposed edit still needs your own check.
Free plan: Yes, limited uploads
Best when: You want to check finding notes before the complete document.
What it does: Mistral Vibe drafts; you check and decide
Strong at: Drafts a findings document from a separately checked set of notes.
Limit: Every proposal needs mail-system confirmation; the workflow makes no DNS changes.
Free plan: Yes, paid Pro for agents
Before you paste into any AI tool, remove any confidential information. Put it back at the end.
Deciding between Gemini and Mistral Vibe for this? See the comparison.
Each finding cites a header line or record text.
Records are quoted exactly.
The admin confirms every proposed edit against their mail system before changing DNS.
Old record values are kept for rollback.
Check data-handling rules before placing mail data into any tool.
Check the result against your original inputs. Approve it before sharing or acting.