Sample report

7.2/10.0 email score

Good foundation, with a few trust and structure fixes before sending.

From
newsletter@example.eu
Subject
July product updates for your workspace
Tested
Jul 1, 2026, 10:30 AM
Passed

Authentication

Core authentication passes and the visible sender aligns with the technical sender.

8.0
OK SPF passesThe sending server is allowed by the domain's SPF policy. Passed

Technical details: Received-SPF: pass for newsletter@example.eu.

OK DKIM signature verifiedThe message has a valid DKIM signature, which helps inboxes trust that it was not changed in transit. Passed

Technical details: DKIM-Signature d=example.eu; result=pass.

! DMARC policy presentDMARC is configured, but the policy is still in monitoring mode. Improve

Suggested fix: Move from p=none to a stricter policy when your normal senders are aligned.

Technical details: _dmarc.example.eu TXT v=DMARC1; p=none; rua=mailto:dmarc@example.eu

Improve

Deliverability

The basics look healthy, but DNS and mail-server identity can be tightened.

6.0
OK DNS records are consistentThe tested domain has the records needed for normal email delivery. Passed

Technical details will be attached by the real analyzer when available.

! Reverse DNS could be clearerThe sending IP has reverse DNS, but it does not clearly match the sending brand. Improve

Suggested fix: Ask your email platform or infrastructure team to align reverse DNS and HELO naming.

Technical details: PTR mail-17.provider.example does not match example.eu.

OK No obvious spam-like signalsThe sample does not show aggressive punctuation, misleading formatting or suspicious header patterns. Passed

Technical details will be attached by the real analyzer when available.

Improve

Content

The message is readable, but link and fallback improvements would make it safer.

6.0
OK Subject length is reasonableThe subject is clear and short enough for most inbox previews. Passed

Technical details will be attached by the real analyzer when available.

! One tracked link needs reviewA tracking URL hides the final destination from readers. Improve

Suggested fix: Use branded tracking domains and make link text describe the destination.

Technical details: https://trk.provider.example/c/873... redirects to example.eu/product

X Plain-text fallback is missingSome recipients and security tools rely on a plain-text version of the message. Critical

Suggested fix: Add a plain-text MIME part that mirrors the HTML content.

Technical details: MIME tree contains text/html but no text/plain alternative.

Passed

Structure

The email is well formed and should be easy for inboxes to parse.

8.0
OK MIME structure is validThe message parts are nested in a standard way. Passed

Technical details: multipart/alternative with text/html.

OK HTML renders cleanly on mobileThe layout uses responsive dimensions and readable text sizes. Passed

Technical details will be attached by the real analyzer when available.

OK No risky attachmentsNo executable or oversized attachments were detected. Passed

Technical details will be attached by the real analyzer when available.

Passed

Compliance & Trust

The sender identity is clear, and unsubscribe support is present.

8.0
OK Unsubscribe header is presentMailbox providers can expose a native unsubscribe action. Passed

Technical details: List-Unsubscribe and List-Unsubscribe-Post headers detected.

OK Sender identity is clearThe From name and domain match the business sending the email. Passed

Technical details will be attached by the real analyzer when available.

! Tracking transparency can improveTracking is present. Make sure your consent and privacy notices explain it clearly. Improve

Suggested fix: Review tracking language in your privacy notice and campaign preferences.

Technical details will be attached by the real analyzer when available.