DOMAIN SQUAT WATCH · LIVE · DAILY
Your brand.
The right address.
MarkSentry checks newly delegated domains daily for confusable spellings and sound-alikes, then attaches the observed date and registry record exactly as returned.
One brand uses one flexible watch slot · plans from $19/month
- 01Observe
Newly delegated names in supported TLDs. - 02Compare
Confusable spelling and sound-alike signals. - 03Attach
Observed date and registry record as returned.
MEASURED: 8 TLD zones diffed · latest 2026-11-12
What a near-miss looks like
One vowel apart: the kind of newly delegated name the confusable-spelling and sound-alike gate surfaces. The plates below use the reserved .example top-level domain, which can never belong to a real registrant.
EVIDENCE, NOT A GUESS
A daily signal with its provenance intact.
Character swaps, edit distance, and phonetic signals find the names worth a look.
Every zone alert carries the date it appeared in the daily diff.
Registry fields are shown exactly as returned—and left absent when unavailable.
Who it's for
- A brand whose customers arrive by typing its name, and who wants to know when a confusable name goes live in the registries' own zone files.
- A founder who owns the exact-match domain and wants the near-misses (the confusable spellings and sound-alikes) read daily without watching zone files themselves.
- A practitioner or an in-house team watching a handful of brand strings who wants the registry record as returned, the observed date, and the alert, not a portal.
HONEST BOUNDARY
Delegated is not registered.
Zone coverage sees newly delegated names in supported TLDs. A registered name without nameservers may not appear.
COVERAGE & PROOFCoverage, matching method, and operating record
Flags newly delegated domains confusingly close to your brand through daily approved-zone-file reads plus certificate-transparency signals, with the observed source record attached.
Everything included
- Daily zone-file diff across the approved TLDs
- Confusable-spelling and sound-alike gate: character folding, edit distance, phonetic match
- Registry record (RDAP) exactly as the registry returned it: a field it did not state is left absent
- Observed-diff date on every zone alert: the date the name first appeared in our daily zone diff, never a registration date
- Certificate-transparency lookups daily: a source that does not answer is recorded as a skip, never as coverage
- Alert email plus dashboard evidence: RECORD / TRIAGE / YOUR CALL
- Stop or resume watching any time
What runs today
The zone cron runs daily at 06:30 UTC across the approved TLDs, diffing each registry's zone file against the previous day and gating every newly delegated name against your watched brands. Each TLD's coverage line on your dashboard is measured from the days actually ingested (never configured copy), and each candidate's public registry record (RDAP) is recorded exactly as the registry returned it. Certificate-transparency lookups run daily as a second signal and skip honestly when the log source does not respond; a skip is recorded as a skip, never counted as coverage.
MEASURED: 8 TLD zones diffed · latest 2026-11-12
What a watched brand gets
You register a brand name; each day's newly delegated names in the covered TLDs are judged against it for confusable spellings and sound-alike labels: confusable-character folding, edit distance, and phonetic matching, with severity derived from those signals. High- and moderate-severity matches alert you by email with the domain, the date it first appeared in our daily zone diff, and its registry record as returned. When the registry lookup does not answer, the alert says so instead of inventing a card.
How it went live
Before this page said "live", the deployed system had to prove it: on the watch's first real delta day, 2026-08-15, it read 112,922 newly delegated names across seven TLDs, and six real candidates cleared the gate, were alerted, and were recorded with complete evidence chains. The .site delta was independently re-verified against the raw zone snapshots before launch; the dated release and coverage record is published in the customer changelog.
Start watching
FAQ
Which TLDs does the zone layer read?
Today the zone layer reads 8 TLD zones with measured coverage (.site, .shop, .store, .online, .info, .org, .xyz, .net), each diffed daily against the previous day's file, each with its own coverage window on your dashboard. A TLD is listed here only once its zone has actually been read; TLDs added later join the list the same way.
Why do alerts say "delegated" rather than "registered"?
The zone layer diffs the registries' own zone files, and a zone file lists the names that have been delegated (given nameservers). A name that is registered but parked without nameservers never appears there, so this layer cannot see it. We say exactly what the layer sees: a newly delegated name, with the date it first appeared in our daily zone diff (an observation date, not a registration date).
What happens when crt.sh is down?
Certificate-transparency lookups are the second signal, and their source (crt.sh) has outage windows. When it does not answer, that run is recorded as a skip (logged as source unavailable), never as an all-clear and never counted as coverage; the next daily run tries again. The zone-file diff runs on its own schedule and does not depend on it.
MarkSentry provides monitoring and triage, not legal advice. Names in TLDs outside the approved zone set, and names that are registered but not delegated, are not seen by the zone layer.