CertaDNS
Skip to lesson

The Economics · lesson 2 of 2

The lifecycle of a phishing domain

After this lesson you can

Place a domain on its timeline from registration to abandonment, and say what that implies for response.

Assumes you have read The attacker’s arithmetic.

A phishing domain moves through a predictable sequence, and each stage leaves a different trace. Knowing where a domain sits tells you what you can still do about it.

The stages

StageDurationWhat is observable
RegistrationDay 0An RDAP record appears. Nothing else. Nothing is resolving yet.
InfrastructureDays 0–7Nameservers set, A record appears, sometimes an MX. Still no content.
CertificateHours before useA Certificate Transparency entry. The strongest timing signal available.
ActiveHours to weeksContent served, mail sent. This is the earning window.
BurnedAfter detectionBlocklisted, taken down, or abandoned. Content pulled, registration retained.
Dormant or reusedIndefiniteParked and monetised, or held for a later campaign.

The certificate is the alarm

The gap between registration and use can be days or months — attackers age domains deliberately, because age is a signal defenders weight. The gap between certificate issuance and use is usually hours, because nobody obtains a certificate for a site they are not about to serve.

registered        -> could sit dormant for months
nameservers set   -> preparation, no urgency implied
A record appears  -> getting closer
CERTIFICATE       -> they intend to serve HTTPS, now
MX appears        -> they intend to send or receive mail, now

Those last two are the escalation triggers. Everything before them is a watchlist entry.

What each stage permits

StageAvailable response
Registration onlyWatch. A takedown request against a domain doing nothing gets nowhere.
Infrastructure appearingRaise priority. Prepare evidence. Still nothing to report.
Certificate issuedEscalate. Capture evidence now, before the content changes.
ActiveReport to the hosting provider and the registrar. This is where takedown works.
BurnedToo late to matter. Record it, and check whether the registrant reused infrastructure.

Evidence captured after takedown is worthless

The moment a host suspends the content, the evidence of what it was disappears — and a registrar asked to act on a domain that now serves nothing will decline. Screenshots, DNS snapshots and RDAP records have to be captured while the campaign is live, which means at the moment of detection rather than at the start of the response process.

Knowledge check

Which event most reliably indicates a lookalike domain is about to be used?

Last reviewed