Phishing Takedown Process Explained

Published • Updated • 7 min read

A phishing takedown is the process of getting a website, domain or account that impersonates a brand removed at its source. It runs in five stages: confirm the threat, collect evidence, find who controls the infrastructure, file the report and follow it until the content is offline, then monitor for its return. If you want PhishFort to run this process for your brand, see our managed takedown service.

This guide is the hub of The Nuance of Takedowns, PhishFort’s series on why takedowns succeed, stall or fail. Each section answers one part of the process and links to the article that covers it in depth.

How does the phishing takedown process work?

A phishing takedown works by proving abuse to the party that controls the malicious infrastructure and following the request until that party acts. The five stages:

  1. Confirm the threat. Check from more than one network and location that the page is live and that it impersonates the brand.
  2. Collect evidence a provider can act on. Screenshots, the full URL, the brand being impersonated, what the page steals (logins, card data, seed phrases), and the domain’s registration and hosting records.
  3. Find who can remove it. The registrar for the domain, the hosting provider for the content, the platform or app store for an account or app, the registry for some country-code domains.
  4. File the report and follow it up. Send it through the provider’s abuse channel and track it until the content is offline. Reports sent to the wrong party, or with incomplete evidence, are the most common reason a takedown stalls.
  5. Block and monitor. Submit the URL to blocklists while the request is open, so browsers can warn users, and watch for the same phishing kit reappearing on a new domain.

Who do you contact to take down a phishing site?

The right contact depends on who controls the part of the attack you want removed. Asking a registrar to act on a hacked legitimate site, or a host to act on a domain the attacker can move in minutes, wastes the first response.

Situation Who can act What they can do Go deeper
The attacker registered the domain Registrar Suspend the domain so it stops resolving Domain suspension factors
The phishing page sits on hosting the attacker rents Hosting provider Remove the content or close the hosting account Domain takedown scenarios
A legitimate site was hacked to host the page Site owner and its hosting provider Remove the malicious files while the site stays online Compromised site takedowns
The domain uses a country-code TLD (.br, .tr, .sg) Registry or local registrar Act under its own national policy and evidence rules ccTLD takedowns
The domain serves malware or controls infected devices Registrar and hosting provider Suspend the domain or disable the server, with technical evidence Malware takedown process
A fake social account or fake app Social platform or app store Remove the profile, page, ad or app Social media takedowns

What is the difference between domain suspension and content removal?

Domain suspension and content removal are two different outcomes of a domain takedown. A suspension is applied by the registrar or registry: the domain stops resolving, so every page on it goes offline at once. Content removal is applied by the hosting provider: the phishing page disappears, but the domain stays registered and the attacker can point it to a new server.

Suspension fits domains registered by the attacker. Content removal fits compromised sites, where suspending the domain would take a legitimate business offline. For how registrars decide on suspensions, read Domain Suspension: Key Factors Behind Modern Takedown Decisions.

Why check that a phishing site is really offline?

A phishing site can look offline to you and still be live for its victims. False offline readings come from:

  • local ISP filtering or a corporate firewall
  • DNS propagation delays
  • CDN routing problems or a temporary hosting outage
  • browser caching
  • geolocation blocking, where the page only loads in the countries being targeted
  • cloaking, where the kit shows the phishing page to victims and a harmless page to scanners, search engines and analysts

Closing a case on a false reading leaves the page collecting credentials. Reopening a case for a page that is really down wastes the provider’s time and your credibility with its abuse team. Checking from several networks and locations, with a mobile user agent when the lure arrives by SMS, avoids both. For the technical checks, see how to check if a website is down.

Why do malware takedowns need different evidence?

Malware takedowns need evidence that a registrar or host can understand without running the malware. A phishing page is easy to judge from a screenshot. A command-and-control server (the machine that sends instructions to infected devices), a domain generation algorithm (code that creates new domains for the malware to contact) or a fast-flux network (one domain rotating across many IP addresses) is not.

A takedown request for malware infrastructure gets accepted faster when it includes:

  • sandbox screenshots and behavior logs
  • detection results from VirusTotal
  • the link between the domain and the payload, callback or redirect chain
  • a short, plain explanation of the harm to users

In PhishFort’s takedown work, how clearly the evidence is presented often matters more than how deep the analysis behind it is. The full method is in Malware Takedown Process.

Why are compromised sites harder to take down?

Compromised sites are harder because the owner of the domain is a victim, not the attacker. Many phishing campaigns run on hacked WordPress sites, hijacked subdomains, abused cloud storage or infected business servers. Providers will not suspend a legitimate customer’s domain over a page the customer did not put there.

The goal changes from removing the domain to getting the malicious files removed while the business stays online. That means reaching the site owner or the host, giving them the exact path of the files, and checking afterwards that the attacker’s access was closed. More in The Challenge of the Compromised Site.

How do ccTLD policies change the takedown?

Country-code top-level domains (ccTLDs), such as .br or .tr, are run by national registries, and each one sets its own abuse rules. Some act on a well-documented abuse report. Others ask for:

  • a court order or law enforcement request
  • evidence in the local language
  • proof of trademark ownership
  • a specific reporting format
  • escalation through a local registrar

A request that works in a generic TLD like .com can be rejected as filed under a ccTLD, so the evidence package has to be built for the registry before the first report. Read Using Country-Code TLDs (ccTLDs).

How long does a phishing takedown take?

Phishing takedown times have no fixed number, because they depend on who has to act. The main factors are how responsive the registrar, host or platform is, whether the evidence is complete on the first report, whether the site is compromised or attacker-owned, and the policy of the registry in ccTLD cases. PhishFort acts on every validated threat right away, 24/7/365, and follows it until it is offline. Resolution times depend on the registrar, host or platform involved.

How PhishFort runs phishing takedowns

PhishFort runs this process as a managed program. Analysts validate each detection, file takedown requests through direct channels with registrars, hosting providers and platforms, and follow every case until the content is offline. PhishFort has a 99%+ takedown success rate.

Every confirmed takedown is added to the PhishFort Blocklist. The PhishFort Blocklist reaches 418M+ users through browsers, DNS providers, antivirus tools and wallets, so users are warned while the request is still open. After removal, Brand Monitoring watches 24/7/365 and re-engages the takedown when a removed threat resurfaces.

Before you file a takedown: a checklist

  1. Did you confirm the page is live from more than one network and location?
  2. Does your evidence show which brand is impersonated and what the page steals?
  3. Are you reporting to the party that controls that part of the attack?
  4. If the domain is a ccTLD, do you know what that registry requires?
  5. Is someone watching for the same kit on a new domain after removal?

Need one phishing site removed now? Request a demo with our team

The Nuance of Takedowns series:

Also on takedowns:

How PhishFort Protects Brands From Phishing

PhishFort finds the phishing sites, fake apps and impersonation accounts that use your brand and takes them down, with evidence for every case.

Book a Demo Explore PhishFort Takedowns