Example email report and retest
Invented data throughout. This page contains no real test emails.
The first example has DMARC failure despite SPF and DKIM passing. Its retest changes alignment only; the message fingerprint, workflow and sending IP stay the same.
Example IDs: demo-test-001 and demo-test-002.
DMARC failed
DMARC: fail. SPF and DKIM passed.
In this invented sample, SPF and DKIM passed but neither authenticated domain aligns with the From domain example.com. The retest aligns both domains; DMARC then passes.
This test does not show whether Gmail or Outlook placed your email in the inbox or spam folder.
Delivered to Siglumo’s test address.
DMARC: fail. SPF and DKIM passed.
0 incident reports · 0 blocklist entries returned.
What needs attention.
What happened. Why it matters. Who can help.
DMARC failed
Needs attentionDMARC: fail. SPF and DKIM passed.
Why it matters: Receiving services may reject or filter email when these checks fail.
Your email administrator: In this invented sample, SPF and DKIM passed but neither authenticated domain aligns with the From domain example.com. The retest aligns both domains; DMARC then passes.
Show the evidence
DMARC: fail. SPF and DKIM passed.
- Source
- Amazon SES
- Time
- 10/19/2026, 3:30:00 PM GMT+5:30
Technical details
{
"spf": {
"value": "pass",
"source": "sample",
"evidence": "Synthetic passing result",
"domain": "bounce.example.net"
},
"dkim": {
"value": "pass",
"source": "sample",
"evidence": "Synthetic passing result",
"domain": "example.net"
},
"dmarc": {
"value": "fail",
"source": "sample",
"alignment": {
"from_domain": "example.com",
"spf": false,
"dkim": false
},
"evidence": "Synthetic SPF and DKIM domains do not align with the From domain example.com, DMARC fail"
}
}No history or blocklist warnings returned for the addresses checked.
1 address(es) checked. This lookup does not cover an entire provider pool.
Source and coverage
What looks okay.
Malware scan passed
The receiving service did not flag this test in its malware scan.
Show the evidence
The receiving service did not flag this test in its malware scan.
- Source
- Amazon SES
- Time
- 10/19/2026, 3:30:00 PM GMT+5:30
Technical details
{
"value": "pass",
"source": "sample",
"evidence": "Synthetic passing result"
}Receiver’s spam scan passed
The receiving service did not flag this test in its spam scan.
Show the evidence
The receiving service did not flag this test in its spam scan.
- Source
- Amazon SES
- Time
- 10/19/2026, 3:30:00 PM GMT+5:30
Technical details
{
"value": "pass",
"source": "sample",
"evidence": "Synthetic passing result"
}No past-activity warning was returned
The reputation service returned no history warning for the addresses it checked.
Show the evidence
The reputation service returned no history warning for the addresses it checked.
The sending-history service returned 0 past incident reports. This is not proof of activity from your account.
Subject examples from historical reports
No subject examples were provided.
- Source
- Sending-history service
- Time
- 10/19/2026, 3:30:00 PM GMT+5:30
Technical details
{
"status": "complete",
"input": "192.0.2.24",
"checked_at": "2026-10-19T10:00:00Z",
"checked_ip_count": 1,
"findings": [],
"associated_ips": [],
"blocklists": {
"checked_ip_count": 1,
"reported_listing_count": 0
}
}No blocklist entries were returned
No listings were returned among the service’s completed checks.
Show the evidence
No listings were returned among the service’s completed checks.
- Source
- Sending-history service
- Time
- 10/19/2026, 3:30:00 PM GMT+5:30
Technical details
{
"checked_ip_count": 1,
"reported_listing_count": 0
}Content scan found no spam warning
No content warning was returned.
Show the evidence
No content warning was returned.
- Source
- Message-content scan
- Time
- 10/19/2026, 3:30:00 PM GMT+5:30
Technical details
{
"status": "complete",
"verdict": "HAM",
"checked_at": "2026-10-19T10:00:00Z",
"suggestions": []
}One connection we can confirm.
The last connection into Siglumo is observed by our receiver. Earlier steps are claims in the message headers.
Show the receiving evidence
Source: Amazon SES · 10/19/2026, 3:30:00 PM GMT+5:30
No receiving header saved
Public DNS snapshot not recorded
The receiving authentication results above remain available. A public DNS snapshot was not included in this record.
Unavailable checks and scope
Some public DNS details were not captured
Could not check. See “Your domain, explained” for the missing fields and lookup times. Missing records here do not overturn the receiver’s original verdict.
Know your next step.
Only change a setting after the evidence identifies what needs fixing.
- Your email administrator
In this invented sample, SPF and DKIM passed but neither authenticated domain aligns with the From domain example.com. The retest aligns both domains; DMARC then passes.
- You
Send the same message through the same sending workflow to this test address. The comparison appears above after both arrive. Separately check Inbox or Spam in a Gmail or Outlook test mailbox.
Compared with the previous test: Example baseline. SPF and DKIM domains are not aligned with example.com.
What do the result states mean?
- Passed
- The completed check found no issue within its scope. It is not a delivery guarantee.
- Needs attention
- A completed check returned an issue or warning to review. It does not prove the cause of spam placement.
- Could not check
- A result is missing, incomplete or unavailable. This is not a failed check.
- Not included
- This test does not include that assessment.
Technical details for this test
Original headers, identity checks, IP addresses and recorded values. Earlier header claims are not independently verified.
No receiving header recorded
{
"is_sample": true,
"id": "demo-test-001",
"validator_version": "demo-validator-v1",
"received_at": "2026-10-19T10:00:00Z",
"source": {
"body_sha256": "45e09257b75e8fce102fbffecb899f53fb4e3c44a652021d7fd173628898fec7"
},
"workflow_label": "Outbound test",
"configuration_label": "SPF/DKIM not aligned",
"route": {
"boundary_confirmed": true,
"observed_peer_ip": "192.0.2.24",
"observed_recipient": "sample@receive.example.com"
},
"message": {
"from": "owner@example.com",
"return_path": "bounce.example.net",
"to": [
"sample@receive.example.com"
],
"subject": "Sample campaign"
},
"authentication": {
"spf": {
"value": "pass",
"source": "sample",
"evidence": "Synthetic passing result",
"domain": "bounce.example.net"
},
"dkim": {
"value": "pass",
"source": "sample",
"evidence": "Synthetic passing result",
"domain": "example.net"
},
"dmarc": {
"value": "fail",
"source": "sample",
"alignment": {
"from_domain": "example.com",
"spf": false,
"dkim": false
},
"evidence": "Synthetic SPF and DKIM domains do not align with the From domain example.com, DMARC fail"
}
},
"scans": {
"spam": {
"value": "pass",
"source": "sample",
"evidence": "Synthetic passing result"
},
"virus": {
"value": "pass",
"source": "sample",
"evidence": "Synthetic passing result"
}
},
"infrastructure": {
"status": "complete",
"input": "192.0.2.24",
"checked_at": "2026-10-19T10:00:00Z",
"checked_ip_count": 1,
"findings": [],
"associated_ips": [],
"blocklists": {
"checked_ip_count": 1,
"reported_listing_count": 0
}
},
"content_analysis": {
"status": "complete",
"verdict": "HAM",
"checked_at": "2026-10-19T10:00:00Z",
"suggestions": []
},
"modules": {
"authentication": {
"status": "complete"
},
"content": {
"status": "complete"
}
},
"placement": "unknown"
}Inspect the aligned retest: demo-test-002
Completed checks passed.
The completed checks accepted the sender’s identity.
Send the same message to a Gmail or Outlook test mailbox and record where it appears.
This test does not show whether Gmail or Outlook placed your email in the inbox or spam folder.
Delivered to Siglumo’s test address.
The receiver’s SPF, DKIM and DMARC checks passed.
0 incident reports · 0 blocklist entries returned.
No warning in the completed checks.
Missing checks and checks outside this test’s scope remain below. This is not an overall all clear.
No history or blocklist warnings returned for the addresses checked.
1 address(es) checked. This lookup does not cover an entire provider pool.
Source and coverage
What looks okay.
Malware scan passed
The receiving service did not flag this test in its malware scan.
Show the evidence
The receiving service did not flag this test in its malware scan.
- Source
- Amazon SES
- Time
- 10/19/2026, 3:45:00 PM GMT+5:30
Technical details
{
"value": "pass",
"source": "sample",
"evidence": "Synthetic passing result"
}Email identity checks passed
The completed checks accepted the sender’s identity.
Show the evidence
The completed checks accepted the sender’s identity.
- Source
- Amazon SES
- Time
- 10/19/2026, 3:45:00 PM GMT+5:30
Technical details
{
"spf": {
"value": "pass",
"source": "sample",
"evidence": "Synthetic passing result",
"domain": "bounce.example.com"
},
"dkim": {
"value": "pass",
"source": "sample",
"evidence": "Synthetic passing result",
"domain": "example.com"
},
"dmarc": {
"value": "pass",
"source": "sample",
"alignment": {
"from_domain": "example.com",
"spf": true,
"dkim": true
},
"evidence": "Synthetic aligned SPF and DKIM domains, DMARC pass"
}
}Receiver’s spam scan passed
The receiving service did not flag this test in its spam scan.
Show the evidence
The receiving service did not flag this test in its spam scan.
- Source
- Amazon SES
- Time
- 10/19/2026, 3:45:00 PM GMT+5:30
Technical details
{
"value": "pass",
"source": "sample",
"evidence": "Synthetic passing result"
}No past-activity warning was returned
The reputation service returned no history warning for the addresses it checked.
Show the evidence
The reputation service returned no history warning for the addresses it checked.
The sending-history service returned 0 past incident reports. This is not proof of activity from your account.
Subject examples from historical reports
No subject examples were provided.
- Source
- Sending-history service
- Time
- 10/19/2026, 3:45:00 PM GMT+5:30
Technical details
{
"status": "complete",
"input": "192.0.2.24",
"checked_at": "2026-10-19T10:15:00Z",
"checked_ip_count": 1,
"findings": [],
"associated_ips": [],
"blocklists": {
"checked_ip_count": 1,
"reported_listing_count": 0
}
}No blocklist entries were returned
No listings were returned among the service’s completed checks.
Show the evidence
No listings were returned among the service’s completed checks.
- Source
- Sending-history service
- Time
- 10/19/2026, 3:45:00 PM GMT+5:30
Technical details
{
"checked_ip_count": 1,
"reported_listing_count": 0
}Content scan found no spam warning
No content warning was returned.
Show the evidence
No content warning was returned.
- Source
- Message-content scan
- Time
- 10/19/2026, 3:45:00 PM GMT+5:30
Technical details
{
"status": "complete",
"verdict": "HAM",
"checked_at": "2026-10-19T10:15:00Z",
"suggestions": []
}One connection we can confirm.
The last connection into Siglumo is observed by our receiver. Earlier steps are claims in the message headers.
Show the receiving evidence
Source: Amazon SES · 10/19/2026, 3:45:00 PM GMT+5:30
No receiving header saved
Public DNS snapshot not recorded
The receiving authentication results above remain available. A public DNS snapshot was not included in this record.
Unavailable checks and scope
Some public DNS details were not captured
Could not check. See “Your domain, explained” for the missing fields and lookup times. Missing records here do not overturn the receiver’s original verdict.
Know your next step.
Only change a setting after the evidence identifies what needs fixing.
- You
Send the same message through the same sending workflow to this test address. The comparison appears above after both arrive. Separately check Inbox or Spam in a Gmail or Outlook test mailbox.
Compared with the previous test: SPF and DKIM alignment changed to example.com; DMARC now passes. This outcome is invented.
What do the result states mean?
- Passed
- The completed check found no issue within its scope. It is not a delivery guarantee.
- Needs attention
- A completed check returned an issue or warning to review. It does not prove the cause of spam placement.
- Could not check
- A result is missing, incomplete or unavailable. This is not a failed check.
- Not included
- This test does not include that assessment.
Technical details for this test
Original headers, identity checks, IP addresses and recorded values. Earlier header claims are not independently verified.
No receiving header recorded
{
"is_sample": true,
"id": "demo-test-002",
"validator_version": "demo-validator-v1",
"received_at": "2026-10-19T10:15:00Z",
"source": {
"body_sha256": "45e09257b75e8fce102fbffecb899f53fb4e3c44a652021d7fd173628898fec7"
},
"workflow_label": "Outbound test",
"configuration_label": "SPF/DKIM aligned",
"route": {
"boundary_confirmed": true,
"observed_peer_ip": "192.0.2.24",
"observed_recipient": "sample@receive.example.com"
},
"message": {
"from": "owner@example.com",
"return_path": "bounce.example.com",
"to": [
"sample@receive.example.com"
],
"subject": "Sample campaign"
},
"authentication": {
"spf": {
"value": "pass",
"source": "sample",
"evidence": "Synthetic passing result",
"domain": "bounce.example.com"
},
"dkim": {
"value": "pass",
"source": "sample",
"evidence": "Synthetic passing result",
"domain": "example.com"
},
"dmarc": {
"value": "pass",
"source": "sample",
"alignment": {
"from_domain": "example.com",
"spf": true,
"dkim": true
},
"evidence": "Synthetic aligned SPF and DKIM domains, DMARC pass"
}
},
"scans": {
"spam": {
"value": "pass",
"source": "sample",
"evidence": "Synthetic passing result"
},
"virus": {
"value": "pass",
"source": "sample",
"evidence": "Synthetic passing result"
}
},
"infrastructure": {
"status": "complete",
"input": "192.0.2.24",
"checked_at": "2026-10-19T10:15:00Z",
"checked_ip_count": 1,
"findings": [],
"associated_ips": [],
"blocklists": {
"checked_ip_count": 1,
"reported_listing_count": 0
}
},
"content_analysis": {
"status": "complete",
"verdict": "HAM",
"checked_at": "2026-10-19T10:15:00Z",
"suggestions": []
},
"modules": {
"authentication": {
"status": "complete"
},
"content": {
"status": "complete"
}
},
"placement": "unknown"
}