Locks first
Enable transfer locks and 2FA at every registrar that holds production names. Monitoring does not replace that hygiene.
Monitor
Protect
Manage
By role
Security
Renewals
Ownership · Registrar drift
To monitor domain ownership changes, record a baseline of each domain's registrar and nameservers, check it at least daily, and alert a named person when anything moves. Aepto Theft Guard does this automatically: daily on Free and Starter, twice daily from Professional, hourly on Enterprise.
Legal title, registrar of record, and operational control can diverge.
Prevent where you can. Detect everywhere else.
Enable transfer locks and 2FA at every registrar that holds production names. Monitoring does not replace that hygiene.
Theft Guard compares live registrar and NS signals to what Aepto learned as normal for each domain.
Requires Your Attention names the domain so agencies and hosters do not triage from a vague red badge.
You discover ownership issues from mail failure, SEO collapse, or a client forward of a weird WHOIS screenshot.
Drift becomes an Attention item with history you can take to the registrar while recovery is still plausible.
Aepto cannot block a registry transfer by itself. Theft Guard checks daily on Free and Starter, twice daily on Professional, Business and Agency, and hourly on Enterprise.

Every one of these has an innocent explanation. The question is whether anyone planned it.
| Signal | Expected when | Treat as compromise when |
|---|---|---|
| Registrar changes | You announced a transfer | Nobody on the team requested it |
| Nameservers change | A planned DNS migration | There is no change ticket |
| Account or registrant email changes | A staff change you processed | It now points to an unknown address |
| Transfer lock removed | You are about to transfer | Nobody unlocked it on purpose |
WHOIS contact data is often redacted, so registrar and nameserver baselines are more reliable signals than reading WHOIS records.
Detection without a plan still burns hours.
Security lead, agency account owner or founder. Decide before the first alert.
Registrar support links and the evidence they ask for, saved in one place.
Planned transfers: unlock, move, re-lock, update the baseline. Unplanned: assume compromise.
After any alert, check registrar access logs, even when the change turns out innocent.
ICANN sets these for generic TLDs.
60 days
transfer lock that follows a change of registrant, unless you opt out
Source: ICANN Transfer Policy
5 days
the longest a registrar can take to give you a way to remove a transfer lock
Source: ICANN Transfer Policy
clientTransferProhibited
is the status code behind the usual "registrar lock". It blocks transfers, not DNS edits
Source: ICANN
Registrar moves, unexpected transfer activity, WHOIS contact shifts where visible, and nameserver sets leaving your baseline. Exact public fields vary with privacy services.
Theft Guard learns a baseline for domains in your inventory and alerts when registrar or NS signals drift. History supports triage with your registrar.
No. Locks and registrar security stop or slow transfers. Monitoring tells you something moved so you can respond faster.
Domain Watch is for names you do not own yet. Ownership monitoring of your inventory is Theft Guard and DNS baseline territory.
Redacted WHOIS hides contacts. That is why Aepto leans on registrar and NS baselines you can still observe, since public WHOIS is often redacted.
Unexpected registrant/admin contact changes, unlock or auth-code generation you did not approve, billing profile swaps, and DNS moves arriving with the ownership event.
Like a security ticket: confirm with the people who should own the brand, then tighten locks and 2FA. Pair process with Theft Guard for technical drift.
Add domains free. Put registrar and NS drift in Attention.
