Zero-access security intelligence

What LeakTrace covers for food distributors

We hold no keys to your firm. No login, no install, no mailbox access.

Up to 350 look-alike addresses an attacker could register from your name, checked on each assessment.

75 techniques attackers use against firms like yours, each checked externally on every assessment.

16 routes to your money, your clients, your accounts and your name, checked end to end on each assessment.

Attackers run AI agents in swarms: many at once, each trying the combinations of these routes against any firm it can read. We read for the combinations first.

Everything LeakTrace reads about a firm, area by area, with what the firm receives and what we never do: Capabilities

01

What we read for food distributors

We find each way in, prove it with evidence anyone can re-run, give the exact fix and re-check until it is closed.

An unlit External reading chip means: read with the assessment, not on a free reading.

  • Forged email in your nameThe records that tell inboxes whether to refuse email sent as you (DMARC, SPF and DKIM), read externallyExternal readingAssessmentRe-checked every hour on monitoring.
  • Look-alike namesWeb addresses an attacker could register to look like yours, each checked: is it registered, is it set up for mailExternal readingAssessmentNew ones looked for every hour on monitoring.
  • Fake sign-in addresses an attacker could registerThe sign-in words attackers use (sso, mfa, enroll, activate, passkey, helpdesk, 2fa, internal, register, enable and deploy) joined to your company's nameExternal readingAssessmentNew ones looked for every hour on monitoring.
  • Firm addresses in breach dataBreach records for addresses at your own domain, read externally; nothing inside is touchedExternal readingAssessmentRe-read every day on monitoring.
  • Your other domainsThe email records of every other domain your company owns, read externallyExternal readingAssessmentRe-checked every hour on monitoring.
  • What AI assistants say about your firmWhat AI assistants answer about your company and whether a copy's address or phone is in the answerExternal reading: Read with the assessment, not on a free readingAssessmentAsked again every week on monitoring.A client who asks an AI assistant about your company trusts the answer it gives. Assistants build those answers from pages they crawl. A look-alike address an attacker could register can be built to be crawled: its robots file invites the AI crawlers in and its page claims your name. Attackers manipulate AI answers to send your paying and enquiring clients to their own look-alike page, web address, sign-in page, phone number or email. In 2025, asked for the sign-in pages of 50 brands, an AI assistant gave addresses the brand did not control one time in three. Netcraft research, read on 4 November 2026 The check is built to ask six assistants: Claude, ChatGPT search, Gemini, Perplexity, Grok and Copilot, through Bing. Monitoring asks again every week and tells you when an impostor's phone or address is in an answer.
11 more, each read
  • Your website's certificateThe certificate your website answers with, seen externally: its name, its dates and who issued itExternal readingAssessmentRe-read every day on monitoring.
  • Your website's settingsThe headers and cookies your website sends to every visitor, seen externallyExternal readingAssessmentRe-read every day on monitoring.
  • Files your site should not showCommon addresses for configuration files, code folders and cloud storage, read externally; nothing inside is touchedExternal reading: Read with the assessment, not on a free readingAssessmentRe-read every day on monitoring.
  • Keys in your website's codeThe scripts your front page loads, read externally for keys and passwords left in themExternal readingAssessmentRe-read every day on monitoring.
  • Software versionsThe versions your website and its script libraries show, read externallyExternal readingAssessmentRe-read every day on monitoring.
  • Pages of your siteYour own public pages, read externally the way any visitor sees them, for keys, private files, sign-in pages and formsExternal reading: Read with the assessment, not on a free readingAssessmentRe-read every day on monitoring.
  • Services that answer from the internetThe services your web host answers with on the internet, read externallyExternal reading: Read with the assessment, not on a free readingAssessmentRe-read every day on monitoring.
  • Host names on your domainHost names on your domain, read externally from its own records and public certificate logsExternal readingAssessmentNew names spotted in public certificate records every hour on monitoring.
  • Your domain's registrationIts registry record, read externally: the expiry date and the lock that refuses a move to another registrarExternal readingAssessmentRe-read every day on monitoring.
  • Spam, malware and phishing listsWhether your domain or its server is on a spam, malware or phishing list, read externallyExternal readingAssessmentRe-read every day on monitoring.
  • Code, paste and document searchesPublic code, paste sites and search results that name your domainExternal readingAssessmentRe-read every day on monitoring.
02

What we fix

Each fix comes as exact steps, in order, with the check that proves it is done. We re-check it externally when you mark it done, every day through your first month of monitoring and every night after that until our re-check confirms it closed. Where a finding cannot be confirmed externally, your assessment says so on that finding and records your confirmation.

We give you the fix for each finding and re-check externally until it is closed. The one change we can make ourselves is to your email records and only when you approve each step, where your DNS host allows it.

One click per step. No code, no password shared.

With our assessment, where your DNS is at Cloudflare, we close forged email with you one click per step, each step on your approval, with a token you supply for that one use.

You approve each step with one click: reporting first, then refusing forged email, about four weeks in all, re-checked externally at every step.

Where we cannot reach your DNS host, you get the exact record to paste.

Ways in17
  • Nothing tells mail servers to refuse email forged in your nameYour DNS settings
  • Your domain asks mail servers to report email forged in your name, not to stop itYour DNS settings
  • Your rule against forged email is written in a way mail servers may ignoreYour DNS settings
  • Another domain of yours publishes no rule against email forged in its nameYour DNS settings
  • Your list of approved email senders approves everyoneYour DNS settings
  • Your domain registration has run outYour domain registrar
  • A look-alike address registered from your company's name is set up for email and has no websiteYour registrar account
  • An address under your domain points at a service nobody controlsYour DNS settings
  • An unencrypted remote-login service on your server answers anyone on the internetYour firewall or web host
  • A file-sharing service on your server answers anyone on the internetYour firewall or web host
  • A remote-desktop service on your server answers anyone on the internetYour firewall or web host
  • A page on your domain is listed as a phishing pageYour website
  • A page on your domain is listed as serving harmful filesYour website
  • A remote-desktop service at your office connection answers anyone on the internetYour office network
  • A file-sharing service at your office connection answers anyone on the internetYour office network
  • An unencrypted remote-login service at your office connection answers anyone on the internetYour office network
  • Addresses on your domain appear in a breach collectionEach account named
Open while your rule against forged email does not enforce, partly closed once it does6
  • Your domain does not say which servers may send its emailYour domain and website settings
  • Your list of approved email senders takes no position on anyone elseYour DNS settings
  • Your list of approved email senders does not say what to do with anyone elseYour DNS settings
  • Your domain lists its approved email senders twice, so mail servers ignore both listsYour DNS settings
  • Your list of approved email senders asks servers to accept others with a warningYour DNS settings
  • Email forged in the name of a service that sends for you would not be refusedYour DNS settings
Partly closed47
  • Email forged in your name lands in the receiver's spam folder; it is not refusedYour DNS settings
  • Your rule against forged email covers only part of your mailYour DNS settings
  • Email forged in the name of another domain of yours lands in the receiver's spam folder; it is not refusedYour DNS settings
  • An app in your company's name is listed by someone who is not youThe app store or the job site
  • A job ad in your company's name tells applicants to contact someone who is not youThe app store or the job site
  • A domain in the name of someone at your company is registered and liveThe domain registrar
  • A sign-in or admin page on your site can be reached from the open internetYour website
  • A key or token is printed in your site's own sourceYour website
  • A private file or folder on your site can be opened by anyoneYour website
  • Software on your site shows the exact version it runsYour website
  • A form on your site sends what visitors type without protection on the wayYour website
  • Your website carries hidden text written to give instructions to AI toolsYour website
  • A page that lists how your server or application is set up can be opened by anyoneYour website
  • An admin tool or a test copy of your website answers anyone on the open internetYour website
  • A key that signs your email has been withdrawnYour DNS settings
  • A key that signs your email was never filled inYour DNS settings
  • A key that signs your email could not be readYour DNS settings
  • The key that signs your email is shorter than today's standardYour DNS settings
  • A shared sending service is on your approved-sender list, so another of its customers could pass as youYour DNS settings
  • Your approved-sender list is too long for mail servers to read, so it fails for every messageYour DNS settings
  • Browsers stopped trusting the authority behind your certificateYour web host
  • An address one letter away from yours is registered to someone elseYour registrar account
  • An address one letter away from yours is for saleYour registrar account
  • A website sits at a look-alike address registered from your company's nameYour registrar account
  • An address close to your company's name is registered and parkedYour registrar account
  • An online storage folder in your name can be read by anyoneYour website
  • A key or password is written into your website's public codeYour website
  • A file of passwords and keys can be downloaded from your websiteYour website
  • Your website's source code can be downloadedYour website
  • A page meant for administrators opens without a loginYour website
  • A folder of documents on your site can be browsed by anyoneYour website
  • A file-transfer service on your server answers anyone on the internetYour firewall or web host
  • A remote-login service on your server answers anyone on the internetYour firewall or web host
  • A database on your server answers anyone on the internetYour firewall or web host
  • A server-management service answers anyone on the internetYour firewall or web host
  • A service on your server answers anyone on the internetYour firewall or web host
  • The server your site runs on has software with published weaknessesYour website
  • A file-transfer service at your office connection answers anyone on the internetYour office network
  • A remote-login service at your office connection answers anyone on the internetYour office network
  • A database at your office connection answers anyone on the internetYour office network
  • A server-management service at your office connection answers anyone on the internetYour office network
  • A printer at your office connection answers anyone on the internetYour office network
  • A camera or video recorder at your office connection answers anyone on the internetYour office network
  • A screen-sharing service at your office connection answers anyone on the internetYour office network
  • A device at your office connection answers anyone on the internetYour office network
  • Files in public code mention your domain beside sign-in or key wordsYour website
  • Your domain appears on sites where copied data is postedYour website
Settings to tidy55
  • A guide to how your site's software talks to other programs can be opened by anyoneYour website
  • A file used to build or run your site can be opened by anyoneYour website
  • A second list of approved email senders starts with a space, so mail servers either ignore it or ignore both listsYour DNS settings
  • Email on its way to you is not required to travel encryptedYour DNS settings
  • You get no reports when email to you fails to arrive securelyYour DNS settings
  • Your list of approved email senders needs more lookups than mail servers allowYour DNS settings
  • Your rule against forged email asks for no reports, so you never see what failsYour DNS settings
  • A domain of yours takes no email and does not say soYour DNS settings
  • Your domain does not name the authority that may issue its certificatesYour domain registrar
  • A document on your site was made with software its maker no longer fixesYour website
  • A document on your site carries a sign-in style name in its detailsYour website
  • Your logo does not show beside your email in the inboxYour DNS settings
  • Your domain can be moved to another registrar without an extra lockYour domain registrar
  • The key behind your certificate can be worked outYour web host
  • Your domain's address records are not signedYour domain registrar
  • Your domain registration runs out soonYour domain registrar
  • Your domain record shows who registered itYour domain registrar
  • Addresses that look almost like yours are registeredYour registrar account
  • Older or internal web addresses of yours are listed in public recordsYour DNS settings
  • Web addresses under your domain that look internal are listed in public recordsYour DNS settings
  • An online storage folder with a name like your company's exists and we cannot tell whose it isYour website
  • Browsers are not told to always use a secure connection to your siteYour website
  • Your site tells browsers they need not use a secure connectionYour website
  • Your site does not limit which scripts may run on its pagesYour website
  • Your site can be shown inside someone else's pageYour website
  • A browser may treat a file from your site as something it is notYour website
  • Your site passes the addresses visitors came from to outside servicesYour website
  • Your site does not limit what outside scripts may ask a visitor's browser forYour website
  • Your website names the software it runs onYour website
  • A cookie from your site can travel without encryptionYour website
  • A cookie from your site can be read by scripts on the pageYour website
  • Your website's security certificate has run outYour web host
  • Your website's security certificate is issued for a different nameYour web host
  • Your website's security certificate is not one browsers trustYour web host
  • Your website's security certificate runs out soonYour web host
  • Your website still accepts outdated encryptionYour web host
  • Your website did not complete a secure connectionYour web host
  • We could not open your website over a secure connectionYour web host
  • Visitors can reach your website without encryptionYour web host
  • Your website runs an outdated code library with published weaknessesYour website
  • A public file on your site lists the addresses of its private areasYour website
  • Your website lists the names of the accounts that can sign in to itYour website
  • Your website publishes the readable source of its codeYour website
  • Your website publishes the map of how its systems are calledYour website
  • There is no published way to report a security problem to youYour website
  • Staff names and addresses on your site make a forged email easy to writeYour website
  • A mail service on your server answers anyone on the internetYour firewall or web host
  • An extra web service on your server answers anyone on the internetYour firewall or web host
  • The internet address your server uses has been reported for abuseYour website
  • Your domain or server address is on a spam blocklistYour website
  • Security products flag your domain as harmfulYour website
  • A mail service at your office connection answers anyone on the internetYour office network
  • A web page at your office connection answers anyone on the internetYour office network
  • Details about your systems appear in public developer forumsYour website
  • Documents from your domain can be found through a web searchYour website
03

What we watch and what happens on a hit

The watch re-reads your email settings, look-alike domains and new host names every hour. It alerts you within the hour when one changes. Everything else is re-checked every day, with the fix for anything new.

The assessment includes your first month of monitoring: the watch starts the day the assessment is released and nothing renews on its own.

What the watch includes11
  • New attacks, matched to you: every day we read newly reported breaches and the way in each one used. When one used a way in that is open on your domain, or software your website shows lands on the list of flaws being used in attacks, we tell you.
  • We read your own website for hidden instructions planted for AI assistants: text your visitors cannot see, written to make AI tools repeat a fake payment change or vouch for a fake sender.
  • We read your site the way an attacker's AI does, before it does.
  • The registrar lock: we read the registry record of your domain and of every other domain your firm owns, for the lock that refuses a move to another registrar.
  • Your office connection: add the internet address of your office from your dashboard and we check it externally each night for printers, cameras, remote desktop and other devices that answer on the internet. Nothing is installed and nothing inside is touched.
  • Fake apps and job ads: we look in the app stores and on the job sites for an app or an ad that uses your firm's name but is not yours. A person at LeakTrace checks each one before it reaches you. We give you the steps to ask the store or job site to remove it. They decide.
  • Domains in your people's names: from the people your own website names, we look for domains registered in their names, such as a partner's name with your line of work. We tell you which ones are live or set up for email, with the steps to warn your clients and ask the registrar to take it down. The registrar decides.
  • Up to 6 look-alike responses a year: takedown requests sent to the registrar and the host in your firm's name on your permission, followed up until they answer and re-checked externally.
  • Supplier watch: name up to ten suppliers or clients you pay or are paid by. When a new domain made from one of their names appears and is worth a look, we email you that day. We suggest the suppliers your own mail records name, such as your payroll provider. Each watched supplier's own rule against forged email is read every day.
  • The call-back sheet: for each supplier you name, the number published on their own website, with the date we read it, read again every night, so a change of bank details can be confirmed on a number you already hold.
  • The inside checklist: a few short checks your own team does inside your own accounts, recorded with their dates beside what we verified externally. We never access your mailboxes or systems.

On a hit

  • If a look-alike is not yours, approve the takedown. On your permission we send the requests to the registrar and the host in your firm's name and follow up until they answer. Your plan includes up to 6 look-alike responses a year. The registrar decides what happens.
  • With standing permission, given once on the monitoring page, the requests for each new look-alike our rules would ask you to approve go within minutes of finding it. The registrar decides what happens to the name.
  • Where a registrar or a host takes reports only through a web form, a person at LeakTrace submits it.
  • We check again externally when you mark a fix done, every day through your first month of monitoring and every night after that until it is closed.
  • Each change is recorded with its date: findings closed, new findings, look-alike cases and takedown steps, newest first, on your page and in one email a month.

What an external reading cannot see

  • Some attacks leave nothing in public view: the call, the code passed on from a fake page, the mailbox someone is already reading.
  • LeakTrace never goes inside a mailbox or a call.
  • Your own step: confirm every change of payment details by a call to a number you already have.
  • Many fake sign-in pages carry no firm name at all and cannot be seen externally. A passkey or security key is what stops those.
  • It reads your firm's own domain and the addresses at it externally, the way an attacker's tools would. It does not read inside your network or your staff's personal email accounts.
What we never see10
  • Laptops, phones and office software: what is installed and whether it is updated
  • Staff clicking a phishing link
  • Passwords in use and whether a second sign-in step is on
  • Backups
  • Who has admin rights
  • Email arriving in the inbox
  • Whether a former employee's account is still switched on
  • A supplier's or client's own security
  • An urgent request from a personal email account pretending to be a partner
  • Phone and text fraud
04

How it reaches a company like yours

Where an attack uses a look-alike address an attacker registered from your name, we see it first.

Where an attack uses a look-alike address an attacker registered from your name, the first sign is the registration. Under the watch, LeakTrace reads the look-alike addresses an attacker could register from your name every hour and the day's public list of new registrations each night.

Four steps from left to right. Someone registers a look-alike address from your name, sets up mail or a sign-in page on it, then a message or a call reaches your people and money or a code goes to them. The watch reads the first two steps. The third is your own step: a call back on a number you already have and telling your customers how you ask for payment.

The watch reads here 1 Someone registers a look-alike address 2 They set up mail or a sign-in page on it 3 A message or a call reaches your people 4 Money or a code goes to them Your step: call back, tell customers The watch reads here 1 Someone registers a look-alike address 2 They set up mail or a sign-in page on it 3 A message or a call reaches your people 4 Money or a code goes to them Your step: call back, tell customers The watch reads here 1 Someone registers a look-alike address 2 They set up mail or a sign-in page on it 3 A message or a call reaches your people Your step: call back, tell customers 4 Money or a code goes to them
The four steps4
  1. A look-alike address is registered

    Someone registers a domain made from your company's name: one letter changed, a word added or another ending.

    Under the watch, a name that shows is dated on your record, with what it showed.

  2. Mail or a sign-in page is set up on it

    Mail is switched on for the name, or it answers with a page that looks like your website or a sign-in page.

    LeakTrace reads its mail and its page and grades it. With the watch, or for the names the look-alike response covers, we send the takedown request in your company's name once you approve it. The registrar decides. Your page shows its answer once it is recorded.

  3. The message or the call reaches a person

    An email from it reaches someone at your company or one of your customers. Or a caller who says they are from IT support sends someone to the sign-in page and asks for the code.

    LeakTrace never goes inside a mailbox or a call. This is the one step only your company can take.

    Tell your customers that you never change payment details by email. Any such note gets a call to a number they already have. Confirm every change of payment details by a call to a number you already have. Sign in with a passkey where your mail system offers one: a code can be passed on from a fake page. A passkey cannot.

  4. The money or the code moves

    A customer sends the money for an invoice to new bank details, or someone at your company makes a supplier payment to new bank details, or a code passed on lets someone else sign in.

    Under the watch, the name's first two steps are dated on your record: when it appeared and what it showed.

    A current case, manufacturers and wholesalers

    A federal prosecutor in Texas announced a sentence on 8 October 2026 in an email scheme that ran from 2020 to 2022. Fraudsters sent emails that appeared to come from known suppliers. A utility trailer company in Mississippi wired $927,080 it believed was going to its trailer supplier. The source does not say how the email was faked.

    IRS Criminal Investigation, release of 8 Oct 2026, on a sentencing in the Southern District of Texas

Cases in your line of work

10 Feb 2026

A lawsuit filed in Manitoba in May 2026 says a Quebec packaging manufacturer wired $203,664 after an email that appeared to come from its insurance broker. The claim says the address ended in "-ca.com" where the broker's ends in ".ca". That is a claim, not a finding.

CP24, reporting a statement of claim filed in Manitoba

28 Sep 2026

A federal prosecutor in Ohio announced a guilty plea on 28 September 2026 in a case from June 2020. A New Jersey health-care provider received emails that claimed to come from its safety-equipment supplier and paid about $1.1 million to a new bank account.

IRS Criminal Investigation, release of 28 Sep 2026, on a guilty plea in the Southern District of Ohio

05

Your rules

United States

  • FTC Act Section 5: Unfair or deceptive security practices
  • State breach notification laws: Notice to affected residents
  • 201 CMR 17.03: Massachusetts residents: a yearly review of your security program

What does each US state's data breach law ask a business to do?

Canada

What breach records does PIPEDA ask a business to keep?

Breach notice, by province and state51

This summarises the public text; it is not legal advice.

06

Your insurer

The external questions cyber insurance applications commonly ask, each with its evidence. Each row is what anyone can see of your firm externally, with the proof under it. Questions about what happens inside your firm are marked "Not visible externally": those are answered from inside your firm. You and your broker answer the application; the insurer makes its own decision.

Does your domain enforce DMARC at quarantine or reject?Forged email in your name
Do you publish an SPF record listing the servers allowed to send your mail?Forged email in your name
Is outgoing email signed with DKIM?Forged email in your name
Are staff email addresses clear of known breach data?Firm addresses in breach data
Are remote-access and database services closed to the internet?Services that answer from the internet
Do you keep internet-facing software patched and up to date?Software versions
Is all web traffic to your site encrypted with a valid certificate?Your website's certificate
Not visible externally4
Do you require multi-factor sign-in for email and remote access?
Do you keep offline or immutable backups and test restoring them?
Is sensitive data encrypted on laptops and servers?
Do you run endpoint protection (EDR) on every computer?

A dated record of what was read externally, verified by a person at LeakTrace before release. LeakTrace Inc. issues it as a company, with a reference and a fingerprint anyone can check at getleaktrace.com/verify/. No individual signs it.

It is not a certification, not a penetration test, not legal or compliance advice and not a statement about your internal systems.

The insurer pack

One download for your broker or insurer: your Assessment Record, the Rules and Insurance Briefing and every fix confirmed closed externally, each with its date.

07

The documents

Owner Summary and Action Brief

For the owners

Technical Evidence and Findings

The evidence and the exact fix

Rules and Insurance Briefing

Privacy rules and insurer questions

Assessment Record

Dated record, issued by LeakTrace Inc.

08

Order

How many people work at your company?

  • Up to 50 people
  • 51 to 200 people
  • 201 to 500 people
  • 501 to 2,000 people
  • More than 2,000 people

Every domain your company owns is included. The assessment includes your first month of monitoring: the watch starts the day the assessment is released and nothing renews on its own.

Your assessment arrives inside 72 hours of payment confirmation. A person checks it before it is released and we email you the moment it is ready.

For a company of more than 2,000 people, write to us and we will price the assessment with you.

Request your firm’s reading