Ownership · Registrar drift

How to monitor domain ownership changes fast.

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.

What “ownership change” means in practice

Legal title, registrar of record, and operational control can diverge.

  • It can mean the name moved to a new registrar, WHOIS contacts changed while the name stayed put, or nameservers changed so someone else effectively controls it.
  • The useful question is: did control of this name leave its expected state?
  • Privacy redaction hides WHOIS contacts, so registrar and nameserver baselines are the reliable signals.
Registrar Unexpected move
NS Authority leaves your set
Access Compromised login
Process Transfer without ops notice

A monitoring stack that matches reality

Prevent where you can. Detect everywhere else.

Locks first

Enable transfer locks and 2FA at every registrar that holds production names. Monitoring does not replace that hygiene.

Baseline alerts

Theft Guard compares live registrar and NS signals to what Aepto learned as normal for each domain.

Named queue

Requires Your Attention names the domain so agencies and hosters do not triage from a vague red badge.

Without monitoringLate

You discover ownership issues from mail failure, SEO collapse, or a client forward of a weird WHOIS screenshot.

With AeptoEarlier

Drift becomes an Attention item with history you can take to the registrar while recovery is still plausible.

What does Theft Guard add?

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.

Monitoring ownership and registrar drift

Which signals mean ownership might be changing?

Every one of these has an innocent explanation. The question is whether anyone planned it.

Ownership change signals
SignalExpected whenTreat as compromise when
Registrar changesYou announced a transferNobody on the team requested it
Nameservers changeA planned DNS migrationThere is no change ticket
Account or registrant email changesA staff change you processedIt now points to an unknown address
Transfer lock removedYou are about to transferNobody unlocked it on purpose

WHOIS contact data is often redacted, so registrar and nameserver baselines are more reliable signals than reading WHOIS records.

What goes in an ownership-change runbook?

Detection without a plan still burns hours.

  1. 01

    Who gets paged

    Security lead, agency account owner or founder. Decide before the first alert.

  2. 02

    Where to escalate

    Registrar support links and the evidence they ask for, saved in one place.

  3. 03

    Expected vs unexpected

    Planned transfers: unlock, move, re-lock, update the baseline. Unplanned: assume compromise.

  4. 04

    Review access

    After any alert, check registrar access logs, even when the change turns out innocent.

What do the transfer rules say?

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

Common questions

What counts as an ownership change signal?

Registrar moves, unexpected transfer activity, WHOIS contact shifts where visible, and nameserver sets leaving your baseline. Exact public fields vary with privacy services.

How does Aepto help?

Theft Guard learns a baseline for domains in your inventory and alerts when registrar or NS signals drift. History supports triage with your registrar.

Can monitoring stop a transfer?

No. Locks and registrar security stop or slow transfers. Monitoring tells you something moved so you can respond faster.

Is Domain Watch for ownership of my names?

Domain Watch is for names you do not own yet. Ownership monitoring of your inventory is Theft Guard and DNS baseline territory.

Why do privacy services complicate WHOIS watching?

Redacted WHOIS hides contacts. That is why Aepto leans on registrar and NS baselines you can still observe, since public WHOIS is often redacted.

What ownership signals should I verify?

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.

How should teams treat ownership email?

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.

See control leave the baseline sooner.

Add domains free. Put registrar and NS drift in Attention.

Aepto Theft Guard showing nameserver and registrar baseline alerts