A message, a domain, or a recurring campaign.
Use the free private checker for a first look, then choose a written review or connected reporting when the stakes are higher.
Email fraud analysis · Vancouver
Meilo turns suspicious email into clear evidence, safer domain settings and one simple reporting action from iPhone or Android.

Two kinds of evidence work
Email security remains our daily work. We also help businesses build a dated record when a public review is contested.
Use the free private checker for a first look, then choose a written review or connected reporting when the stakes are higher.
Compare the public allegation with dated source records. Ask for a specific correction without exposing a customer file on the open web.
Three email routes
One uncertain message
Inspect headers and link domains in your browser, then request a written review if the decision matters.
Open the free checker →Your domain is impersonated
Map legitimate senders and stage SPF, DKIM and DMARC changes without cutting off real mail.
See domain protection →The same scams keep returning
Choose a dedicated reporting folder or review the server-side Junk queue, then receive organized cases instead of forwarding each copy.
See the workflow →
One simple action
Mark suspicious messages as Junk, or move selected messages to Report to Meilo.
Review private candidates and remove any filtering mistakes.
Approve the messages you want processed into organized cases.
Useful answers, without opening the lure
Common questions
Inspect the original sender path, reply address, authentication results and real link domains. A polished logo or a passed authentication check does not establish that the request is safe.
Yes. Choose a dedicated Report to Meilo folder for minimum access, or connect the server-side Junk folder to a private review queue. In Junk review mode, no outside report is prepared until the mailbox owner approves the message in the portal.
Inventory every legitimate sender, align SPF and DKIM, then move DMARC from monitoring toward enforcement with validation and rollback checks. Display-name and lookalike-domain attacks need additional controls.