Registration monitoring
New and transferred registrations resembling your marks are detected across generic, new and country-code extensions.
Solutions
Almost every serious brand attack starts with a domain registration. AuthenScan watches for names built on your marks across the extensions that matter, tracks what happens to them, and tells you which ones have crossed from noise into a threat worth acting on.
The problem
Pulling a list of domains that contain your brand name is easy and almost useless on its own. Most of those registrations will never host anything; a few will become a phishing page or a fake storefront. Treating them identically means either chasing all of them or ignoring all of them.
What separates a dormant typo from an imminent attack is behaviour: a certificate issued against the name, mail records configured, a page appearing where there was none, hosting moving to a bulletproof provider. Those signals arrive days before customers are affected.
AuthenScan monitors registration and behaviour together, so the watchlist is ordered by what is actually happening rather than by how much a string resembles your brand.
Single-character variants that read correctly in an address bar at normal speed.
Your brand with 'login', 'shop', 'secure' or 'support' appended, sized to look like an official subdomain.
The same name re-registered across extensions you never defensively acquired.
A certificate appearing in transparency logs for a name that has nothing on it yet — a strong early warning.
MX configuration on a domain that has no legitimate reason to send mail as you.
A parked registration that suddenly gains hosting, a page and traffic.
Why it matters
6,200+
Domain-name dispute proceedings filed with WIPO in 2025 — a record year.
WIPO Arbitration and Mediation Center
3.8M
Phishing attacks observed worldwide during 2025.
APWG Phishing Activity Trends Report
866
Distinct brands targeted by phishing in a single quarter (Q4 2025).
APWG Phishing Activity Trends Report
Figures are published by the sources named above and are provided for context. They are not AuthenScan performance claims.
What the monitoring covers
A domain becomes dangerous through a sequence of changes. Monitoring the sequence is what turns a list into an early warning.
New and transferred registrations resembling your marks are detected across generic, new and country-code extensions.
Certificates issued against lookalike names are surfaced as they appear, often before any content is published.
Nameserver, A-record and MX changes are tracked, because configuration is what distinguishes a live threat from a parked name.
Pages are checked over time, so a dormant registration that suddenly starts serving a login form is flagged immediately.
Each watched domain carries a risk position based on similarity, configuration, content and registrant history — not on string match alone.
Threshold-crossing domains reach your team promptly, with everything an enforcement or dispute action will need already attached.
How it works
Marks, product names, official domains, common misspellings and the markets and extensions that matter commercially.
New and transferred names matching those patterns are collected continuously across the extension space in scope.
WHOIS, DNS, mail, certificate and hosting signals are attached to each name and turned into a comparable risk position.
Domains stay under observation. Most matter only at the moment their configuration or content changes.
When a domain crosses into active abuse it moves into enforcement with its evidence history already assembled.
Coverage
The .com space and the wider extension landscape where defensive registration is impractical.
Market-specific extensions relevant to where you actually trade.
Public certificate issuance records, a reliable pre-attack signal.
MX and sending setup on names positioned to impersonate you in email.
Where a domain resolves, and whether it has moved to infrastructure associated with abuse.
Other names held by the same registrant, so one detection informs the rest.
What you receive
AuthenScan found and removed infringements we could never police manually.
FAQ
Three layers at once: registration activity for names resembling your marks, configuration signals such as DNS, mail records and certificate issuance, and the content served on those names over time. Watching only the first layer produces a long list nobody can act on; watching all three is what makes the list ordered and useful.
Defensive registration is worth doing for a small, high-value set — your exact mark in your core markets, and the most obvious misspellings. Beyond that it does not scale, because the variant space is effectively infinite and the cost is recurring. Monitoring covers the space you cannot buy.
By combining string similarity with behaviour. A name one character from your brand that has a certificate, mail records and a live page ranks far above a more distant name sitting parked. Registrant history matters too — a registrant already associated with abuse of your brand raises everything else they hold.
Yes, for the markets that matter to you. Country extensions are often where abuse concentrates, because enforcement practice varies and brands defensively register there less often. Scope is agreed up front, since covering every extension in existence is neither practical nor useful.
It moves straight into enforcement with its history attached. Because the domain has been watched since registration, the case file already contains WHOIS history, configuration changes and captures — which is exactly the evidence a registrar abuse report or a UDRP complaint needs, and it removes the delay of assembling it after the fact.
Less than a raw registration feed produces, which is the point. Most matching registrations never do anything, so they sit on the watchlist rather than generating alerts. Your team hears from us when something changes state, not every time a name is registered.
