Back to articles

How to take down a phishing or lookalike domain

A phishing or lookalike domain is a site built to pass as your brand so attackers can steal credentials, payments, or trust. Every hour it stays live adds victims. This guide walks through the six steps to get one removed, what evidence each party needs, and why takedown works best at the campaign level.

Key takeaways

  • Takedown runs through the registrar, the host, browser blocklists, and the channels sending traffic (ads, social, SMS).
  • Evidence comes first. Incomplete evidence is the most common reason a report is delayed or rejected.
  • Steps 2 to 5 should run in parallel, not one after another. Step 6 continues after removal.
  • Removing one domain rarely ends the attack. The same operator re-registers and re-hosts, so map and remove the whole campaign.
  • Outtake confirms 99.4% of the takedowns it files.

What counts as a phishing or lookalike domain

  • Lookalike (typosquat) domains. Near-matches of your brand name, such as swapped letters, added words, or different TLDs.
  • Credential-harvesting pages. Clones of your login portal.
  • Fake storefronts and support pages. Checkout, refund, or help pages on a spoofed domain.
  • Adversary-in-the-middle pages. Proxies that relay your real login and capture session cookies.

Step 1: Collect evidence

Capture this before you file anything, and before the site changes.

Evidence checklist

  • Full URL (path, query string) and domain
  • Timestamped full-page screenshots showing the address bar
  • Source HTML saved and hashed (SHA-256)
  • DNS records and resolved IP addresses
  • WHOIS for the domain and for the IP block
  • The brand or trademark element being impersonated, with registration details
  • Original phishing email (raw .eml with headers) or SMS with sender ID and timestamp
  • Redirect chain and form-post destination
  • Who collected the evidence and when

Step 2: Report to the registrar

Identify the registrar from WHOIS or the ICANN lookup. Send the abuse contact the domain, the specific URLs, your evidence, the brand being impersonated, and the harm. For gTLDs (.com, .net, .org), you can escalate unresponsive registrars through ICANN's DNS abuse complaint process.

Step 3: Report to the hosting provider or CDN

Resolve the domain to its IP and find the network owner and abuse contact. Cite the host's acceptable use policy. If the site sits behind a CDN, report to the CDN and ask it to forward to the origin host. If a host does not act, escalate to its upstream provider or a national CERT.

Step 4: Block it while removal is pending

Submit the URL to Google Safe Browsing, Microsoft SmartScreen, and anti-phishing feeds such as APWG. Blocking protects users within minutes or hours, but it does not remove the site, so it runs alongside Steps 2 and 3.

Step 5: Remove the traffic sources

Report the ads, social profiles, search results, and SMS lures that send victims to the site. Each platform has its own impersonation or abuse form.

Step 6: Monitor for re-registration

Attackers re-register similar domains and redeploy the same kit. Watch for new lookalikes, the same kit on a new URL, and shared infrastructure that ties new domains to the original operator.

Who can remove what

Party What they can do What to send
Registrar / registry Suspend the domain WHOIS, URLs, evidence, brand rights
Host / CDN Take the content offline URLs, logs, screenshots, AUP violation
Browser and email blocklists Warn or block users URL, screenshots
Social, ad, and app platforms Remove profiles, ads, apps Impersonation proof
Search engines De-index results URL, abuse category

Block vs remove

Blocking reduces exposure fast but leaves the infrastructure up. Removal ends the site but depends on third parties. Do both at the same time.

Terms-of-service enforcement is usually the fastest. DMCA notices can remove cloned logos and text. UDRP can transfer or cancel an infringing domain, but takes weeks.

Metrics to track

  • Time to detect
  • Time to block
  • Time from detection to first takedown, and to full removal across every channel
  • Takedown confirmation rate (takedowns confirmed divided by reports submitted)
  • Re-registration rate by the same operator

For what to ask a provider that handles this work for you, see our guide to phishing takedown services.

How Outtake handles takedown

Outtake Brand Protection detects fake domains continuously and maps the campaign behind them: spoofed domains, cloned apps, malicious ads, and impersonation accounts. Remediation agents file takedowns in parallel through integrations with registrars, hosts, social platforms, app stores, and ad networks.

Outtake's takedown confirmation rate is 99.4%. That is the number of alerts taken down divided by the number of reports submitted. An alert counts as taken down when removal is confirmed through remediation-case resolution.

Each takedown feeds Outtake's Digital Reservoir, so repeat variants are triaged against prior intelligence.

Book a demo to see campaign-level takedown on your own brand.

FAQ

How long does a phishing site takedown take?

It varies by registrar and host. Manual reports often take days. Automated, campaign-level takedown can complete in hours.

Can I take down a lookalike domain that has not been used yet?

Registrars generally act on evidence of abuse. Without it, you can monitor the domain and prepare a UDRP filing.

Why does the site come back after takedown?

Operators keep spare domains and reusable kits. Campaign-level removal and monitoring reduce relaunches.

What evidence do registrars and hosts need?

The full URL, timestamped screenshots showing the address bar, saved and hashed page source, DNS and WHOIS records, the brand element being impersonated, and the original phishing message with headers. The full checklist is in Step 1.