BATech WatchThe method

How BATech Watch works, step by step.

We find the fake copay, savings-card and patient-support sites your patients actually reach, file the takedowns, and hand your counsel evidence they can verify without us.

This page is the whole method, written down: what we search, how every page is read, what we file and will not say, and how the evidence checks out without us.

Every engagement starts the same way: a demo on your own name, what is out there and what we would file, before you commit to anything. The monitoring fee is then set to your scope.

The method, on one client's record Illustration

98pages read and judged, to find the 17 that point at this client

What each dot became

16 point where they shouldThe client's own website. Not a finding.
1 pointed somewhere elseThe finding: a credible third-party record sending readers to a counterfeit.Corrected
81 other pagesRead and judged, and not pointing at this client.

The chip is this one case's outcome, not a step of every sweep. The sweep, step by step

Illustration of the method, not a screenshot of the client portal; one dot per page, in no particular order. The figures are one client's live production record on 10 September 2026, shown with their permission.See the dated record

What we search, and why domain monitoring misses it.

Other people's pages about you are the part a domain scanner cannot see. Most of them send readers to you. The dangerous one sends them somewhere else, and it is dangerous precisely because it is not your site doing it: it is a credible third party lending its authority to a fake.

A domain scanner watches your address

Your domain, spelled wrong.
Look-alike addresses and typo-squatting alerts.

A counterfeit that is not a misspelling of anything never shows up there, and the counterfeit that mattered was not a misspelling of anything.

BATech Watch follows the pages that name you

Directories, registries, databases, press and aggregators: anywhere credible that names you and links somewhere.
Copay, savings-card and patient-support listings, the sources a patient is told to trust.
Where each link actually lands, not where it says it goes.

We search as a patient would

Your watched items, 8–10 on a single-entity engagement, set per engagement.

Your company name
Your product names
The phrases you use
The domains you own
People whose identity could be borrowed

On a live engagement, the one that went elsewhere was a credible third-party record listing a counterfeit as the company's official website.

That is documented third-party confusion, and it is the fact a trademark claim actually succeeds on. We had the record corrected.

The daily sweep, step by step.

Every 24 hours, whether or not there is news. Each step has its own section below, with the rules that bind it.

Search
Your watched items, searched the way someone looking for you would type them. Not just your domain spelled wrong.
What we search
Read
Every page that comes back is opened and classified: does it name you, and where does it send people?
How pages are read
Sort
Each link lands in one of three places: your website, no link we recognise, or not your website. Only the last is a finding.
The three outcomes
Capture
A finding is captured and hashed at the moment it is taken, and the hash is sent to an independent RFC 3161 timestamp authority to be countersigned.
How the evidence verifies
File and chase
We file with whoever can switch it off, then chase each filing to a decision. That is the part that takes weeks.
How filings work
Report
Your page shows which days were covered, what was found, what was filed and what was refused, including the days a check failed.
What you are told

How every page is read and sorted.

Steps 02 and 03 in detail. Reading asks of every page whether it names you and where it sends people; sorting puts each one in exactly one of three places, and only one of them is a finding.

Your website

Not a finding

The page names you and sends people to you. Most of them do.

No link we recognise

Not a finding

The page names you without linking anywhere we can follow.

Not your website

The finding

The page sends readers somewhere that is not yours. This is the one that matters: it becomes a finding, and step 04 captures it.

A product name alone is not a finding.

A page that mentions a product name but nothing else about you is not a finding, and we say so rather than counting it.

How filings work.

Step 05 is the slow one. A filing goes to whoever can switch the fake off and is chased until they decide: that is the part that takes weeks, and the reason this is a service and not a dashboard.

Who we file with

Registrar
Host
DNS and mail provider
Netcraft
Google Safe Browsing
Microsoft SmartScreen
The listing that got it wrong
Escalation to the registry

A managed removal uses every channel above that applies to it. Where a case calls for it, we prepare a URS action (one per plan year is inside the fee; the provider’s filing fee is separate, at cost).

The status on each filing

FiledReported to whoever can act, and waiting on them.
Not respondingThe domain stopped answering. Why that is not called a takedown.
RefusedA channel said no. Every refusal is shown to you as plainly as every win.

If we file against the wrong address, we correct it, and both the complaint and its correction are published to you.

Four things we will not say.

These are the four words where monitoring overclaims. The published complaint about the category is false positives: legitimate sellers flagged, and wrongful takedowns that leave the brand that sent them with real legal exposure. Each rule is enforced in the running code, and each exists because getting it wrong would have been easier.

“Taken down”

Reporting is not removal, so a filing stays filed until somebody actually acts. A domain that has merely stopped answering is not responding: from outside, a takedown and a nameserver blip look identical, and calling it the first would be a promise made by a scheduler.

“Registered”

Whether a mark of yours is registered is your assertion, taken from your own material, and a ™ is never upgraded to an ®. We once had to withdraw a registration claim in writing, which is why this is a rule and not a preference.

“Nothing found”

Not looked at is not nothing found. When a sweep runs out of budget, your page prints how many pages went unread, so a zero is never banked as reassurance.

“Unlimited”

An unstated limit is one you discover by being refused. Your rate buys a stated number of searches and pages read per sweep, marks and seats, each printed on your own page beside the coverage it bounds.

Evidence that checks out without us.

A screenshot proves nothing on its own; anyone can produce one. Practitioner guidance on domain disputes is blunt about it: panels discount static images with no system-generated metadata, and what carries weight is a cryptographic hash paired with a signed timestamp from an independent authority.

From capture to counsel, in five steps

We do
Hash each capture at the moment it is taken.
Send the hash to a public RFC 3161 timestamping authority. The signed token that comes back binds the hash to a time on that authority's clock, under its certificate.
Your counsel does, without us
Download the capture and its token (the .tsr file) from your portal.
Take the authority's certificates from the authority itself; it publishes them, not us.
Run one command. Verification: OK means the file is byte for byte the one the authority countersigned. Alter it by sixteen bytes and the same token fails.

As of 10 September 2026, our live engagement holds fourteen captures, each countersigned by an authority that is not us. The dated record

$ openssl ts -verify -data capture.html -in capture.html.tsr \
    -CAfile cacert.pem -untrusted tsa.crt
Verification: OK

# the same token, against a copy altered by sixteen bytes
Verification: FAILED message imprint mismatch

Step five, as counsel runs it. The file and token come from your portal and the certificates from the authority; no part of the check runs through BATech.

What a pass proves

The file existed, byte for byte, no later than the time on the token.
So it rules out evidence produced after an argument started.

What it does not prove

That the capture happened at that instant. Where the two times differ, your portal says which is which.
Notarisation, or a person witnessing it. We will not describe it as though it were.

The allowance the sweep runs inside, and the fee.

Every step above runs inside a written allowance, set per engagement and printed on your own page next to your usage against it. Asking for more is a request a person reads and answers, never an automatic change to what you are billed.

1: legal entity, and every mark it owns
8–10: watched items
24h: between sweeps
5: logins at your company

A single-entity engagement, as published. What each figure covers, and why there is a line.

Inside the fee

The daily sweep.
Each capture hashed at the moment it is taken.
The client portal.
Up to five managed removals a month, each run end to end across every channel that applies.
Preparation of one URS action per plan year (the provider’s filing fee is separate, at cost).

Terms

One flat monthly fee, set to your scope after a demo, on a six- or twelve-month term, or a custom one. The setup fee is credited against month one. Beyond five in a month, removals are priced per domain, end to end on the same footing, normally added to the next monthly invoice; a removal without the plan is priced per domain too. The fee does not move with what is found: some months will have a handful to take down and other months will be completely dead quiet, and the month we find nothing costs the same to run.

When something goes wrong, you are told.

Each case below has a fixed place on your page, and a step or rule above that puts it there. Follow the link to where it comes from.

A check fails.The day is drawn as missed.Step 06, Report
A channel refuses us.The filing shows Refused.Filing status
We file against the wrong address.Complaint and correction both published.How filings work
A sweep runs out of budget.The unread pages are counted.“Nothing found”
We get a registration claim wrong.Withdrawn in writing.“Registered”
You need more than the allowance.A person answers the request.The allowance

See the method run on your own name.

Send your company name, your product names and the phrases you use. In the demo we take you through a first sweep on your name in the order this page describes: what we searched, how each page was sorted, and what we would file. If the answer is nothing, which it often is, that is worth knowing too.

BATech Watch: [email protected]
The product: BATech Watch, in short One client's dated record Plans and demo