Preemptive Domain Disruption Stop the attack while it’s still a domain name.

Find and take down attacks before they begin.

Attackers often register a domain hours or days before the first lure. Intrudy scores lookalikes as they’re registered, spots the ones being prepared for an attack and moves to have them suspended or blocklisted before a page goes live.

What changes with Preemptive Domain Disruption.

  • 01

    Caught at registration

    New registrations, certificate logs and first DNS lookups are scored as they appear, so a lookalike is assessed before it hosts anything.

  • 02

    Intent, not just similarity

    A lookalike on name servers tied to past attacks, with a fresh certificate and a staged kit, is no coincidence. We weigh those signals to find the domains being readied.

  • 03

    Blocked from the first visit

    Domains that show intent go to browser and security-vendor blocklists, so if the page launches, visitors can be warned from the start.

  • 04

    No launch, no victims

    An attack stopped before launch has no victims, no complaints and no cleanup. That’s the takedown worth aiming for.

The best time to stop a phishing site is before it exists.

An attack needs infrastructure before it needs victims: a domain, name servers, a certificate, a kit. Each leaves a trace in public data. We read those traces as they appear and move on the domains that add up to an attack, while there’s still nothing for a victim to see.

71%

Malicious lookalikes disrupted before their first page went live Illustrative

How we detect

Three ways Preemptive Domain Disruption sees what others miss.

New registrations, scored as they land

Zone files, registration data, certificate logs and first-seen DNS show new domains as they appear. Each one is compared with your brands by spelling, lookalike characters and how it renders on screen, and scored, often before it hosts anything.

  • Zone files and registration data
  • Certificate transparency logs
  • First-seen DNS resolutions
  • Spelling and visual similarity

Signs of an attack being staged

Similarity alone doesn’t trigger action. We look at what’s being built: name servers and hosts tied to past phishing, batches registered by the same actor, certificates issued for login-style subdomains, mail records set up for sending lures and kit files staged on the server.

  • Infrastructure tied to past attacks
  • Batches registered by the same actor
  • Mail records set up for lures
  • Kit files staged before launch

Disrupted before day one

When the signals add up, the registrar and registry get a suspension request with the evidence of intent, and the domain goes to browser and security-vendor blocklists. If a page goes live anyway, the case moves straight to takedown with the history already on the ticket.

  • Suspension requests with evidence of intent
  • Blocklisting before the first visit
  • Go-live watch on every flagged domain
  • Full history on the public ticket

Takedown

From first signal to gone.

  1. Score at registration

    Each new domain is compared with your brands as it appears in registration data, certificate logs and DNS.

  2. Read the setup

    Name servers, hosting, certificates, mail records and files on the server show what the domain is being prepared for.

  3. Confirm intent

    An analyst reviews the signals before anything is sent. The case gets a public ticket with the evidence.

  4. Request suspension

    The registrar and registry receive the evidence of intent, in the format their abuse teams work from.

  5. Blocklist in parallel

    The domain goes to browser and security-vendor blocklists, so if it launches, visitors can be warned from the first click.

  6. Watch for launch

    If the domain goes live before it’s suspended, the case moves straight to takedown with the full history attached.

What we cover

What we look for before launch

  • Newly registered lookalikes
  • Homoglyph and IDN registrations
  • Brand plus keyword registrations
  • Bulk registrations by one actor
  • Certificates for lookalike hosts
  • Login and support subdomains
  • Phishing kits staged in advance
  • Domains on known attack infrastructure
  • Lookalikes set up to send mail

By the numbers.

4 min

Median time from first sighting of a new domain to its risk score Illustrative

19 h

Median lead time between our flag and the domain’s first live page Illustrative

260,000

New domain registrations scored each day Illustrative

Figures marked “Illustrative” show the kind of measure we report. They will be replaced with audited values.

Questions, answered.

Something else? Ask us in a demo.

Will a registrar suspend a domain that hasn’t hosted anything yet?

Some will, when the evidence of intent is clear, such as a kit staged on the server or links to known attack infrastructure. Others wait for abuse. When a registrar won’t act yet, the domain stays on our blocklist feed and on watch, and the takedown starts as soon as a page appears.

Won’t this flag legitimate domains?

Similarity alone never triggers a request. A domain needs several signals of intent and an analyst’s confirmation before anything is sent. Every case has a public ticket, and the domain’s owner can dispute it there.

How is this different from Domain Protection?

Domain Protection maps the lookalikes that already exist, watches them over time and acts when one is abused. Preemptive Domain Disruption works at the moment of registration, on domains being prepared for an attack. They work best together.

What do you need from us?

Your brands, official domains and the words attackers pair with them, such as login, secure or support. We build the watch list from there and refine it with you.

How is Preemptive Domain Disruption priced?

Pricing depends on the brands and coverage you need. Request a demo for a quote.

Meet the attack at registration, not at launch.

See how Intrudy scores new domains, reads the signs of an attack being staged and acts before a page goes live.