VIOLATION TYPE / PHISHING

Phishing & Scam Sites

Phishing sites and scam pages impersonate a brand's checkout, login, or support to steal credentials, payment data, or personal information from customers. They're often spun up in waves around product drops, sales events, and earnings announcements.

What it is

Fake checkout, login, or support pages designed to steal data.

Where it happens

Standalone domains, hijacked subdomains, ad-driven landing pages.

How we stop it

Hosting abuse, registrar suspension, browser blocklists, law-enforcement referrals.

Overview

Phishing is one of the highest-velocity threats facing consumer brands. Operators rotate domains daily, host across resilient bulletproof providers, and drive traffic through paid ads and SMS smishing. Effective response requires speed and coverage across the entire stack — hosting, DNS, registrars, browser blocklists, and payment processors.

Real-World Examples

Phishing operations we shut down every day

  • Fake outlet sites on brand-adjacent domains advertising 70–90% off, harvesting card details at checkout.
  • Spoofed support portals linked from SMS messages claiming "package delivery issues" or "account suspension".
  • Counterfeit login pages reproducing customer-account screens to harvest credentials.
  • Crypto / NFT scams impersonating brand partnerships, drops, or "claim" promotions.
  • Fake job-offer pages targeting employees with credential-harvesting onboarding.

How We Enforce

  • Hosting abuse. Reports through the hosting provider's abuse desk with full technical evidence.
  • Registrar suspension. Direct relationships with major registrars accelerate suspension and lock.
  • Browser blocklists. Google Safe Browsing, Microsoft SmartScreen and APWG submissions to neutralize traffic.
  • Ad-network removal. Where phishing is driven by paid ads, we pull the ads at the source.
  • Law-enforcement referral. For organized phishing, we package evidence packs for relevant authorities.

Evidence Required

  • Screenshots and URLs of the phishing pages.
  • Any SMS, email, or social posts driving traffic to them.
  • Any customer reports or stolen-credential indicators.

Typical Timeline

  • Browser blocklist: 1–6 hours from report.
  • Hosting / registrar suspension: 6–48 hours.
  • Persistent operators: 1–4 weeks for infrastructure-level disruption.

FAQ

How fast can a single phishing site go down?
For unsophisticated phishing on mainstream hosts, we routinely see suspension within hours. Bulletproof-hosted sites take longer but are neutralized through blocklists in parallel.
Can you monitor for new phishing variants automatically?
Yes — newly registered brand-adjacent domains are flagged via WHOIS feeds, certificate transparency logs, and DNS heuristics.

Seeing this violation against your brand?

Our enforcement team can issue a takedown notice within hours of evidence submission.

Submit a Case