Test receiver
Ready to receive your test email
test@receive.siglumo.comReceiving is separate from Gmail or Outlook inbox placement.
A clearer picture of your email
Your email test, one step at a time.
Copy your private address, send a sample from your usual sending tool, and follow its arrival here.
How the test helps
Send one email to see its receiving, identity, sending-history and content results. Optional: send another sample to compare from the same tool to see whether those observations repeat. Different sending IPs are a route observation, not proof of improvement or shared use.
After making an evidence-backed change, keep your baseline and record what changed before interpreting a retest. Gmail and Outlook folder placement require a separate test mailbox.
Send, review, then compare.
- 1
Use your usual sending tool
Use the same app or service you use to email your customers.
- 2
Send it to the test address
Copy your private address and send your first email there.
- 3
Optional: send another sample to compare
Send another sample to the same address. Compare the observations and record any change you made.
Your test destination
Checking your test…
Loading your test address…
Loading your saved report…
Earlier tests in this browser
This test checks arrival at Siglumo. It does not show whether Gmail or Outlook placed your email in the inbox or spam folder.
Put your email to the test.
Send a test. Get a clear result. Know what to do next.
Ready to receive your test email test@receive.siglumo.com
Loading your reports…
Follow the evidence
Select any step to see what goes in, what comes out, and what is still unverified.
01 — Capture at our boundary
02 — Analyze in parallelPartial results are allowed
Arrows = proposed data flow, not network hopsEvery external result retains its source.
Step 1 of 7. Create a case-specific test address. Select a box to inspect it, or play the sequence.
Selected-step details are directly below the map.
Compare tests
What improved, what stayed a concern and what we cannot compare.
Examples only · invented data
Sample reports
These examples do not describe your email or your setup.
Sample comparison data · invented values
Example: first email and retest. The retest changes SPF and DKIM alignment to example.com; DMARC changes from fail to pass. Message text, sending workflow and observed IP are unchanged in this invented example.
Your evidence / this browser session
Start with a real message.
Import the original .eml file. It stays in memory in this tab; refresh clears it. Imported headers are reported evidence, never trusted receiver observations.
Inspect an original email
No file selected. No uploads or API requests.
Case history
Comparable tests, explicit differences.
Keep workflow and configuration labels consistent. Body fingerprints detect decoded-text changes; they do not establish semantic equivalence.
Settings
Your receiver and integrations. No setup changes are needed to read a report.
Reputation integration
The sending-history service runs in the background.
Check results are recorded in each report.
Credentials are managed on the server and are not shown here.
Content integration
Not includedThe separate content-analysis service is not connected.
Original setup reference · planning tools only
This is reference material. It does not describe a required change to your working receiver.
Receiving infrastructure
A test address needs a real receiver.
A normal mailbox alone does not supply the trusted SMTP evidence in this plan. Use a dedicated receiving subdomain, a managed inbound service, and private storage.
AWS SES Mail Manager
Archive API fields include envelope From / To / HELO, sender IP, receipt timestamp and TLS details. Metadata is optional: validate with real sends before relying on it.
- Choose a dedicated receiving subdomain.
- Provision an ingress endpoint and archive rule.
- Apply the exact provider-supplied DNS records.
- Route opaque case aliases to private evidence records.
- Verify raw MIME, peer IP, TLS and repeat delivery.
Resend Inbound
Receive on an account-provided resend.app subdomain or verified custom domain, then process email.received webhooks. Content and headers are available; trusted peer IP / HELO / TLS parity is not confirmed here.
A forwarded message can describe a forwarding server rather than the original sending connection. Keep that boundary visible.
Official receiving setup ↗Prepare a configuration / does not change DNS
No receiving address has been provisioned.