Skip to content

Leak monitoringSmall businessAdvisers

Find leaked logins before attackers do.

We watch breach data and malware logs for your team's accounts, rank each finding by how urgent it is, and tell you in plain words what to do.

Licensed breach data / Passwords never stored / Set up in 10 minutes

  1. Your team's logins leak: in breaches, malware logs and stolen sessions. Most small businesses never see it happen.
  2. 54% of ransomware victims showed up in malware logs first, days before the attack. Source: SpyCloud on Verizon DBIR 2025.
  3. Security by Mechanism. Find leaked logins before attackers do.
  4. Prove the domain is yours. Nothing is shown until you do.
  5. Six checks, and every finding ranked by how urgent it is.
  6. Plain steps to fix it. The grade moves when you do.
  7. For firms: every client on one page, riskiest first.
  8. Run a free check on your domain.

Knows which leaked logins unlock

  • Microsoft 365
  • Google Workspace
  • Okta
  • QuickBooks
  • Xero
  • AWS
  • Salesforce
  • Slack
Verizon DBIR 2025
22%
of breaches start with stolen or abused logins.Verizon DBIR 2025(opens in a new tab)
SpyCloud on DBIR 2025
54%
of ransomware victims were in malware logs first.SpyCloud on DBIR 2025(opens in a new tab)
Security Magazine
1 in 5
small businesses use any dark-web monitoring.Security Magazine(opens in a new tab)

How it works

From sign-up to your first alert

Ten minutes of setup. After that it runs on its own, and only interrupts you when something matters.

  1. Step 1Minute 0

    Add your domain and prove it's yours

    One DNS record, or a click in an admin inbox like admin@ or security@. Nothing is shown for a domain until then, not even a count.

  2. Step 2Minute 10

    The first check finishes

    Breach data, malware logs and the five outside checks, scored into one grade, with the findings behind it ranked by urgency.

  3. Step 3From then on

    We keep watching

    When a breach or malware-log source loads something new, every verified domain is checked again, so you hear in hours, not months.

  4. Step 4When it matters

    You get an alert, and the fix

    Each finding comes with its reasons, a fix-by date and fixed steps. Tick them off and the grade moves; we check it stays fixed.

What we check

Six checks, one grade

Leaked accounts are the main event. The other five cover the rest of what an outsider can see, at no extra cost.

Outside view5 of 6 flagged
Leaked accountsfinance@ · signed-in sessionCritical
  1. Your people's addresses in breaches and in malware logs, including stolen signed-in sessions, which get past passwords and MFA.

    finance@ · signed-in session

    Malware log · QuickBooks login · found 2 h ago

  2. Whether you, or a supplier you list, appear on a ransomware gang's victim list.

    Listed · northwind-payroll.example

    A supplier you list · posted yesterday

  3. Whether your SPF and DMARC records stop other people sending mail as you.

    DMARC only monitors (p=none)

    Forged mail is reported, but still delivered

  4. Live domains one typo away from yours, the kind used to phish your team and clients.

    harb0rpine.com is live

    Registered 9 days ago · has a mail server

  5. Remote desktop, admin panels and known vulnerabilities open on the servers your domain points at.

    Remote desktop open · port 3389

    On vpn.harborpine.com

  6. Suppliers that have reported a breach to a state attorney general.

    Contoso IT filed a notice

    Oct 2026 · no account data of yours named

Leaked accounts: Critical. finance@ · signed-in session.

Why sessions rank highest

A security key stops a stolen password. It can't stop a stolen session.

Malware that copies a signed-in session gets past the password and every kind of MFA, keys included. The only fix is signing that person out everywhere, which is why we score it critical and put it first.

For firms

Every client, on one page

Accountants, lawyers and IT firms are expected to guard their clients against stolen logins. Security watches each client and keeps the record that shows you did.

  • All clients, worst first

    One page ranks every business you look after by risk.

  • A monthly PDF per client

    What was found, fixed and left, ready to send on.

  • Alerts sized to the problem

    Critical findings straight away, the rest weekly.

  • Fix-by dates on the calendar

    A day for critical, a week for high.

Questions

Questions we get asked

Why do I have to prove I own the domain?

So nobody can look up another company's leaks. Breach data sources work the same way: no proof, no results. The free email check is the exception, because it only reads public DNS records.

Do you see or keep our passwords?

No. We record that a password or session leaked, where, and how it was stored, so we can score it. Passwords, hashes and session cookies are never stored, and nothing is shown for a domain you haven't proven.

What does the AI see?

A redacted record: "User A (Finance), malware log, finance app", never a name, address or secret. It only rewords the explanation. If its answer changes the severity or adds a step, we throw it away and show a fixed template.

What happens when something serious turns up?

Whoever handles security in your team gets an alert straight away, with who is affected and the steps to fix it. The details stay behind sign-in, never in the email.

Can we fix things from here?

You get the steps and track them to done. One-click sign-outs and password resets through Microsoft 365 and Google Workspace come in a later version.

We already use Mechanism. Is this separate?

It's the same account and the same businesses. Security is the focused app for it; the same findings also show inside Mechanism.

We look after many clients. How does that work?

Add each client as its own business. All clients ranks them by risk, and each gets its own monthly report.

Something else? Write to us.

See what's already out there.

Add your domain, prove it's yours, and the first check usually finishes within minutes.

Looking after several clients? Talk to us.