CLOUDEK · LOCAL REPORT WORKSPACE

Email review
report draft.

Turn a few reviewed facts into a Markdown draft you can inspect and use while completing the formal report. Download an optional self-contained, print-ready HTML copy. It does not query DNS, connect to a mailbox, or send or save your entries.

✓ Browser memory only✓ One selected message✓ Draft requires analyst review

Prepare one controlled test

Generate a random, low-content subject and a 24-hour UTC search window for the customer-approved sender and recipient. Send the message yourself through the selected service; this page does not send mail or connect to a mailbox.

Exact subject: Not generated
Search window starts (UTC): Not generated
Search window ends (UTC): Not generated

No message has been sent or searched.

Review scope and findings

Use only a domain and service labels. Do not paste message headers, email addresses, DNS exports, message IDs, customer names, or secrets into this prototype. Obvious email addresses, raw header lines, SPF/DKIM/DMARC records and common DNS resource-record lines in free-text fields are blocked; select concise observations from evidence you reviewed separately. This is a best-effort guard, not a sensitive-data detector.

Authorized domain Review date Organization label (optional, no personal names) Reviewer role (optional)

Customer-confirmed sending services Up to three labels; one is tested

Service 1 Service 2 (optional) Service 3 (optional)

The one service tested

Record and receiver-reported results

SPF DNS observation SPF result from receiver DKIM selector lookup DKIM result from receiver DMARC DNS observation DMARC result from receiver Controlled message test outcome

Receiver values are reported claims for one message, not independently verified signatures or an alignment verdict. The generated draft keeps any other receiver-specific signal (such as composite authentication) separate; record a concise reviewed result or mark it unreported/unverified, and never use it as a substitute for SPF, DKIM or DMARC. DNS selections are your recorded observations, not results from this page.

Receiving-system attribution Required in the final report

Attribution status Observed authserv-id (label only; no full header)

Independent attribution basis (or explain why it could not be established)

The authserv-id is supplied by the header and can be forged. A label alone does not identify which system wrote the field. The final report must record the agreed test path and independent basis, or state that attribution could not be established.

Executive summary Optional, written by the analyst Summary for the customer (up to 600 characters; no automatic conclusions)

Write this yourself from the reviewed evidence. The draft does not turn receiver-reported values into an overall pass/fail conclusion.

Findings Choose whether a supported finding is ready to record Finding status

“No findings” applies only to the agreed review scope. It does not clear services that were inventoried but not message-tested.

Basis for no findings (what was checked and the limits; no raw evidence)

Short neutral title (no identifiers) Analyst-assigned priority Finding status Observed evidence summary (what the evidence showed, no raw values) Analyst interpretation (keep uncertainty explicit) Potential impact (specific and conditional; no inbox-placement promise) Recommended next step (state prerequisites and who should act) Verification plan (what should be repeated after an approved change?)

Priority is a human decision based on evidence and business impact; this tool does not assign or recommend it. One selected message cannot establish domain-wide delivery.

Customer decision requested (brief action, or enter “None”) Decision owner role (no personal names) Evidence reference IDs (IDs only, e.g. DNS-01, HDR-01; no evidence content) Agreed decision timing (leave blank if not agreed)

Nothing is generated until you click Generate draft.

Review the draft before using it

Your draft will appear here.

This is a local draft, not a completed assessment or customer report. Add dated evidence references and limitations in the formal template, verify each statement, resolve placeholders and run the final-copy check. No DNS or Microsoft 365 changes are authorized.

Email reviewreport draft.

Prepare one controlled test

Review scope and findings

Review the draft before using it

Email review
report draft.