Skip to main content

Impersonally

🏆 Winners of the People’s Choice Award at TravelTech Show 2026              Read our latest research →

Domain Takedown

Domain takedown is an enforcement action that gets a malicious domain suspended, or the abusive content on it removed, through the registrar, registry, host, or platform that controls it, shortening the window of a phishing or impersonation campaign.

What is Domain Takedown?

When brand impersonation shows up as a fake login page or storefront on a domain wearing your name, domain takedown is the work of disabling it at the layer that controls it: the registrar, the registry, the host, or the hosting platform. ICANN contract amendments effective 5 April 2024 require accredited registrars and gTLD registry operators to promptly act on actionable evidence of DNS Abuse, defined as malware, botnets, phishing, pharming, and spam used to deliver one of the other four (ICANN, DNS Abuse amendments, effective 5 April 2024). Before then, the accreditation agreement only required investigation and appropriate response to abuse reports (CORE Association news, October 2024).

Domain takedown gets confused with three neighbors. UDRP and URS are trademark disputes decided by a panel, not abuse reports, and they end in a transfer or a suspension rather than a removal. Typosquatting is a registration tactic, and time to takedown is the metric for how long this takes. The line that matters most: a lookalike that only uses a trademark, with no phishing or malware, falls outside the registrar obligations above and belongs to UDRP, URS, or the courts. Country-code domains such as .uk or .de follow their own registry’s policy, not ICANN’s.

You are hitting this term in incident reports now because attack volume and enforcement both moved in the last two years. Interisle Consulting’s Phishing Landscape 2025, released 9 September 2025 and covering May 2024 to April 2025, counted about 1.96 million phishing attacks, up 182% since 2021, with phishing domains up 38% to over 1.5 million. Enforcement moved too: ICANN’s two-year review published 2 June 2026 reports nearly 530 DNS Abuse investigations launched between 5 April 2024 and 5 April 2026 and over 25,000 abusive domains mitigated directly through them (ICANN blog, 2 June 2026).

How Domain Takedowns work

Find the controller through RDAP

Registration data tells you where to file. Since 28 January 2025, RDAP has been the definitive source for gTLD registration data, replacing the retired WHOIS services. ICANN’s lookup tool at lookup.icann.org shows the sponsoring registrar; nonpublic registrant data goes through ICANN’s Registration Data Request Service for participating registrars, or to the registrar directly (ICANN announcement, 27 January 2025). The registrar field is enough to route a complaint.

Route the report to the layer that controls the content

Not every abusive page lives on the attacker’s own server. When the lure sits on a hosted page under a legitimate domain, the registrar route does not apply; the report goes to the platform hosting the page. Cloudflare’s abuse policy states it is a reverse proxy, not a hosting provider, and cannot remove material hosted by others, but for a substantially complete report it forwards the complaint to the responsible hosting provider and the website owner and can supply the host’s contact details (Cloudflare Abuse Policy).

Match the remedy to what each layer can reach

Removing a page at the host leaves the domain registered and reusable. A registrar or registry suspension stops the whole domain resolving, including every subdomain. A UDRP transfer moves the domain to the brand so the attacker cannot re-register it. Browser lists are weaker still: a Google Safe Browsing listing triggers Chrome’s full-page red warning but does not remove the page or the domain (Chromium blog, ‘All About Safe Browsing’). Pick the layer by what the attacker is actually using.

How to run Domain Takedowns

Verify ownership and preserve evidence before reporting

Confirm the suspicious domain is not your own company, an affiliate, a regional business, or an authorized partner. Then preserve everything before you file: screenshots, timestamps, advertiser details, the displayed address, the resolved landing page, and the full redirect sequence, because campaigns and pages can disappear quickly. Do not wait for a legal conclusion before preserving evidence and blocking confirmed threats.

Report each layer to the service that controls it

Send the ad to the ad platform, the page to the hosted-page provider, the domain to the registrar or host, and the destination to the service being impersonated. One documented case shows the chain: a sponsored result for ‘google anzeigen’ titled ‘Google Analytics’ displayed business.google.com while the advertiser field named an unrelated company, and the login step redirected through a google.com redirect URL to a subdomain of analyticsis.pro with a padlock drawn inside the page.

File complete complaints, and escalate to ICANN if the registrar stalls

ICANN’s guide for DNS Abuse complaints, published 20 November 2025, puts the registrar or registry first and makes ICANN Contractual Compliance the escalation route when they fail to act; ICANN’s authority covers accredited registrars and gTLD registry operators, not hosting providers or website operators. Your ICANN complaint should list the affected domains, include screenshots showing the abuse, and show a prior report to the registrar, because discrepancies between the two filings can delay processing (ICANN announcement, 20 November 2025).

ImpersonAlly packages the evidence for each violation and submits the takedown to the platform or registrar on your behalf; most are actioned within hours of detection.

Switch to UDRP or URS for clear-cut trademark cases

A UDRP win transfers the domain to the mark owner; a URS win suspends it for the rest of the registration term, extendable by one year. The URS covers mainly post-2012 new gTLDs, not .com or .net, and needs a registered or court-validated mark. UDRP rules envision at least 34 days from filing to decision, and URS determinations are due within 21 days (National Law Review; GigaLaw; World Trademark Review).

What Domain Takedowns cost you

The window, not the war

Most phishing domains are registered fresh for the attack, so a takedown removes one domain while a replacement costs the attacker little. The takedown shortens the window for that campaign rather than ending the operation, so the real cost is the monitoring and filing work that repeats with every new domain, which is why takedown is a standing line item in any digital brand protection program rather than a one-off.

ImpersonAlly detects phishing ads and lookalike domains that copy your login pages, support lines, and partner portals, and takes them down, usually by suspending the domain at the registrar.

Wasted reports in a crowded queue

ICANN’s two-year review says ‘the percentage of valid complaints is low,’ calling it ‘a troubling trend’ (ICANN blog, 2 June 2026). Every malformed report shares a queue with real ones: ICANN’s dashboard counted 1,062 DNS Abuse complaints against registrars in June 2025, 854 of them phishing, validated or not (ICANN Contractual Compliance DNS Abuse dashboard, June 2025). A thin report costs you the days it sits there.

The cost of a wrong takedown

ImpersonAlly research published in September 2026 found a sponsored result using the Exness name and logo on exness.market that turned out to be connected to Exness’s own account system, not an impostor. A takedown filed on a partner or affiliate domain like that costs the relationship, the partner’s legitimate traffic, and your credibility with the registrar.

Common mistakes with Domain Takedowns

Treating a reverse proxy as the host

a proxy cannot remove content it does not host, so the report only gets forwarded. Use the proxy’s abuse channel to learn who the real hosting provider is, then file with the host directly.

Filing thin reports

a report without screenshots and the affected domains is the kind ICANN counts among its invalid complaints, and an escalation that does not match the first filing gets delayed. Attach the full evidence set to the first report.

Reporting before preserving

once the page is taken down or rotated, the evidence you did not capture is gone, along with your case for escalation. Capture screenshots, timestamps, and the redirect chain first, then file.

Using a registrar abuse report for a pure trademark lookalike

with no phishing, malware, or other DNS Abuse, the registrar obligations do not apply, and the report goes nowhere. Use UDRP, URS, or the courts instead.

Where Domain Takedowns are heading

On the enforcement side, ICANN is moving from complaint-driven to proactive: its two-year review says it is building a proactive enforcement framework using indicators such as high concentrations of reported abuse and extended mitigation times (ICANN blog, 2 June 2026). On the registration side, the pressure is concentrating: Interisle’s Phishing Landscape 2025 found 37% of phishing domains were bought through bulk registration services and nearly all phishing domains in .xin came through a single registrar, while blocking measures remain largely unimplemented (Interisle Consulting, 9 September 2025).

Attackers register fresh domains cheaply, so what decides the damage is how fast the right layer acts on each one. The honest limit: no suspension stops the attacker from registering the next lookalike. Each new registration restarts the window, and the report has to be rebuilt from fresh evidence, so brand monitoring that finds the replacement fast matters as much as removing the original. What you can shrink is how long each domain stays live, so plan around windows and measure your time to takedown.

Further reading

Frequently Asked Questions

How fast can a malicious domain actually be taken down?

There is no guaranteed timeline, and the honest answer is that you are shortening a window, not ending a campaign. Since the ICANN amendments effective 5 April 2024, registrars and gTLD registries must promptly act on actionable DNS Abuse evidence (ICANN, DNS Abuse amendments, effective 5 April 2024). What you control is the report: a complete one goes to the right layer, carries screenshots and the affected domains, and leaves the registrar nothing to ask. When registrars did not act and ICANN investigated, about 66% of its nearly 530 investigations ended in direct action such as suspension (ICANN blog, 2 June 2026).

Should I report to the registrar or the web host?

Report to the layer that controls the abuse. The registrar or registry handles domain-level DNS Abuse; ICANN's authority covers accredited registrars and gTLD registry operators, not hosts or site operators (ICANN announcement, 20 November 2025). Use the host for content on its servers and the platform for hosted pages under a legitimate domain. When several layers are involved, file with each in parallel.

Is a domain takedown the same as a UDRP case?

No. A takedown is an abuse report to the registrar, host, or platform, based on evidence of phishing, malware, or other DNS Abuse. UDRP and URS are trademark disputes decided by a panel: a UDRP win transfers the domain to you, a URS win suspends it for the rest of its registration term. Use a takedown when the domain is doing harm now, and UDRP or URS when it only uses your mark, or when you want the domain itself so it cannot come back.

What if the registrar ignores my report?

Escalate to ICANN Contractual Compliance when a registrar or registry fails to act. List the affected domains, attach screenshots showing the abuse, and show your prior report to the registrar, because discrepancies between the two filings can delay processing (ICANN announcement, 20 November 2025). ICANN issued four DNS Abuse-related Notices of Breach in its first two enforcement years (ICANN blog, 2 June 2026).

Enforcement & Takedown

Your Brand Protection Ally

Are your Ads being Impersonated by others?

Use the Fraud Tool on our homepage to check your domain — free, in real time.

Check Here →