TL;DR: A lookalike domain is registered weeks before the first phishing mail, and the certificate is logged the moment it is issued. That is the earliest free signal a brand gets. A candidate list of 428 plausible names, resolved over DNS-over-HTTPS, takes about twenty seconds — and turns brand protection from a legal process into a monitoring job.
The scenario
Brand protection usually starts too late: someone receives a phishing mail, forwards it, and the question becomes "can we take that domain down?"
By then the domain is registered, the certificate is issued, the mailbox exists and the campaign is running. A takedown request takes days to weeks. The campaign takes hours.
The earlier question is much cheaper: which names near ours exist at all? That question can be answered from DNS, without an account, without WHOIS, without contacting anyone.
How a lookalike is built
No homoglyph tricks are required. The most common pattern is a hyphen plus a plausible word:
brand-support.tld brand-login.tld
brand-billing.tld brand-invoice.tld
brand-portal.tld brand-secure.tld
getbrand.tld mybrand.tld
brand-de.com brand-app.tld
Each one reads like something the brand would own. Each one passes the "does this look official?" test at a glance — which is the only test most recipients apply.
428 candidates, twenty seconds
The monitoring approach is almost embarrassingly simple: generate the patterns, resolve them, keep a baseline.
18 TLDs x 17 affixes x 6 prefixes = 428 candidates
Resolving them over DNS-over-HTTPS takes about twenty seconds. No rate limit, no account, no WHOIS quota. The result is a list of names that exist — and, more importantly, a list that did not exist last week.
The baseline is the product
A single scan tells you almost nothing. A diff tells you everything.
$ ... --update # accept today as the known state
$ ... # weekly
NEW example-login.com 203.0.113.44
new since baseline: 1 <- review
The first run set a baseline of zero resolving candidates. From then on, every new name is an event: a domain was registered that reads like the brand. Most will be harmless — a parked page, a reseller, a coincidence. One will not.
Exit code 1, a cron job, an email. No dashboard needed.
The certificate is the earlier signal
A cousin domain needs TLS to look real. TLS means a certificate. And every certificate is published in a transparency log — by design, so that TLS can be audited.
That makes certificate transparency the second, even earlier signal: the certificate is issued around the same time as the registration, often days before the first mail. Searching the logs for the brand string is a different query than searching DNS, and it catches names the candidate list would never guess.
What a lookalike buys the attacker
| Asset | Value |
|---|---|
dmarc=pass on the cousin domain | it is their domain, correctly configured |
| a clean reputation | new, unburned, no blocklist history |
| a plausible URL | brand + hyphen + word |
| a valid certificate | free and automated |
| time | weeks between registration and first use |
The cost is one registration — roughly the price of a lunch. The defender's cost is a takedown process that starts after the first victim.
Findings
| Signal | When it appears | Cost to check |
|---|---|---|
| DNS candidate list | at registration | seconds |
| CT log entry | at certificate issuance | minutes |
| First mail | at campaign start | too late |
| Abuse report | after a victim reports | days to weeks |
The monitoring loop
weekly candidate diff (20 s)
weekly CT search for the brand string
daily DMARC reports: new source IPs
on hit block at the mail gateway, warn the brand team, keep evidence
None of this stops a determined attacker. All of it shortens the window between "a domain exists" and "someone inside the company knows about it" — and that window is the only part a defender can actually influence.
Closing
The legal route is real, but it is slow. The technical route is small, boring and fast: a list of names, a resolver, a baseline, a diff.
Brand protection is not a court case that starts after the damage. It is a weekly check that notices a registration before the first mail.
Once an attacker gains access, they can perform the following actions: