Services

Choose the result you need.

Meilo covers three separate problems: deciding whether one message is fraudulent, reducing forged use of a business domain, and turning repeated scam email into organized evidence.

Decision support

Phishing email analysis

Best for one invoice, DocuSign request, account warning, payment notice or unfamiliar link.

What goes in

The original .eml file or complete source, plus the business context that makes the request believable or unexpected.

What comes back

A written finding covering visible and technical sender identities, SPF, DKIM and DMARC, reply paths, real link destinations, likely objective, evidence limits and the safest next action.

Example: a message displayed one name, authenticated through an unrelated Gmail account, and used a hosted object to begin a multi-provider redirect chain.

See the complete analysis scope →

Domain controls

Email spoofing protection

Best when customers receive mail that appears to come from your exact domain.

What goes in

The business domain, representative legitimate mail and a list of systems that send invoices, forms, newsletters, support mail or employee messages.

What comes back

A sender inventory, SPF/DKIM/DMARC findings, alignment examples and a staged enforcement plan with validation and rollback instructions.

The plan separates exact-domain spoofing from display-name impersonation, lookalike domains and compromised legitimate accounts because each needs a different control.

Understand the domain review →

Ongoing operations

Connected reporting

Best when the same scams reach several addresses or return under changing sender names.

What goes in

You choose one of two permission boundaries: only a synchronized Report to Meilo folder, or the server-side Junk folder feeding a private approval queue. Apple Mail, Gmail and Outlook display the provider folders for the connected account.

What comes back

Preserved originals, duplicate grouping, infrastructure roles, provider-ready evidence and a visible follow-up record. Junk review does not treat a filter decision as a complaint; the owner must approve each candidate first.

A recent case preserved a fake health-benefit email, mapped its redirect and subscription funnel, sent role-specific reports and recorded when the first hosted object became unavailable.

Read the documented case →

What every service has in common

Meilo separates direct observations from inference, keeps technical service attribution separate from claims about a person, and records the limits of every finding. Evidence sent to a provider is tailored to the role that provider controls. Enforcement remains the provider's decision.

When to start with the free checker

Use the browser checker when you need a private first look at headers and domains. Choose a paid review when the decision affects money, credentials, a customer, an incident record or a provider complaint.