Skip to content

Contact

Mexico City, Mexico
Available for remote and on-site projects.

Professional networks

LinkedIn · GitHub · Email
Applied engineering, measurable results.

Your brand, cloned in 10,000 fake stores

· 8 min read · Samuel Torres

By Samuel Torres — Software & Cloud Engineer. 23+ production sites.

On November 4, 2026, NordVPN's Threat Intelligence team published research on a network of more than 10,000 counterfeit online stores impersonating 166 fashion and luxury brands across 26 countries. As of November 3, 1,549 of them were fully active, right on time for Black Friday. The most impersonated brand was Adidas, with 52 domains.

In the card testing article I covered bots hitting your checkout. This is the other half: someone puts up a copy of your store on a domain you don't own, charges your customers, and you find out from an angry email. Here's what I would do on the brand side: find the domains imitating you, ask for them to be taken down, and make your official store easy to tell apart.

What NordVPN found

The headline number isn't what struck me. It's how cheap the whole thing is to build. According to NordVPN, every shop in the network is an identical copy of the same WordPress/WooCommerce installation, built with a pirated premium theme. No clever engineering: one template, cloned, with a new logo and language, published on another domain.

They don't run on paid ads either. The press release describes stores built to rank in organic search: each one exposes a sitemap with a median of 1,312 URLs, and 597 domains in the network have Google Search Console verified via DNS. In other words, they do the same technical SEO you do.

And the detail that changes the conversation: when NordVPN ran shopping queries in local languages, Perplexity recommended two of the fake shops as trustworthy stores. It's no longer enough for your customer to "know how to Google." An AI assistant can hand them the wrong link with total confidence.

Step 1: find the domains imitating your brand

You don't need an expensive service to start. Public tools are enough for a weekly check.

Searches and alerts

Start with what your customer sees. Search for your brand plus the bait words these networks rely on: "outlet," "sale," "black friday," "official," "discount." Exclude your own domain with -site::

"yourbrand" outlet -site:yourstore.com
"yourbrand" "black friday" -site:yourstore.com
"yourbrand" official store -site:yourstore.com

Repeat in the language of every country you sell in. Then set up a Google Alert with the same phrases so new results land in your inbox. It won't catch everything, but it's free.

Certificate Transparency (crt.sh)

Almost every fake store needs HTTPS so the browser doesn't flag it, and certificates issued by public authorities are recorded in Certificate Transparency logs. crt.sh lets you search them. % is the wildcard:

# Certificates issued for domains containing "yourbrand"
curl -s "https://crt.sh/?q=%25yourbrand%25&output=json" \
  | grep -o '"common_name":"[^"]*"' | sort -u

Your own subdomains will show up alongside everyone else's; what matters is what you don't recognize. A very short brand name or a common word will bring a lot of noise, and crt.sh sometimes times out on big queries. If that happens, try narrower variants (yourbrand-outlet, yourbrandmx).

Domain variants

dnstwist generates variations of your domain (swapped letters, hyphens, other TLDs) and checks which ones are already registered:

pip install dnstwist
dnstwist --registered yourstore.com

The clones in NordVPN's report don't always rely on typos; plenty pair the brand with "outlet" or a country name. That's why dnstwist complements crt.sh rather than replacing it.

Who's behind it: WHOIS and RDAP

Once you find a suspicious domain, figure out who registered it and where it's hosted. RDAP is the structured successor to WHOIS and almost always includes the registrar's abuse contact:

# Registration data (registrar, dates, abuse contact)
curl -s https://rdap.org/domain/suspicious-domain.com

# Classic WHOIS, if installed
whois suspicious-domain.com

# Which IP it points to, to identify the host
dig +short suspicious-domain.com

The registrant will usually be hidden behind a privacy service. That's fine. What you need is the registrar, the registration date (a two-week-old domain with your brand in it is a clear signal) and the abuse contact.

Step 2: ask for the takedown

Before reporting, collect evidence: dated screenshots of the fake store, the full URL, the RDAP output and, if you have it, an email from a customer who bought there. Keep all of it. If the domain goes down and pops up somewhere else, you'll reuse the file.

  1. Registrar. The abuse contact is in RDAP. Explain that the site impersonates your brand and takes payments using your logos; attach the evidence and your trademark registration if you have one.
  2. Hosting provider. With the IP from dig and its RDAP record (https://rdap.org/ip/THE_IP) you can find the provider and its abuse address. Sometimes the host moves faster than the registrar.
  3. Google Safe Browsing. Report it through the Safe Browsing phishing form. If it gets flagged, Chrome and other browsers show a warning before loading the page.
  4. Your customers. State on your site and your official social accounts which domain is yours, and that you don't sell anywhere else. If a customer already paid on the clone, they should call their bank right away; NordVPN's press release gives shoppers the same advice.

An honest caveat: there's no guarantee a domain will come down, or when. NordVPN's press release notes that when shops get blocked, the network redirects those domains to other active shops. Taking one down is necessary but doesn't end the problem, which is why monitoring has to be ongoing.

Step 3: make your official store stand out

You can't stop someone from copying your design. What you can do is give Google, AI assistants and your customers clear signals about which store is the real one.

Organization structured data with sameAs

Declare on your homepage who you are and which profiles are officially yours. sameAs ties your site to your social accounts:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Brand",
  "url": "https://yourstore.com/",
  "logo": "https://yourstore.com/img/logo.png",
  "sameAs": [
    "https://www.instagram.com/yourbrand",
    "https://www.facebook.com/yourbrand",
    "https://www.linkedin.com/company/yourbrand"
  ]
}
</script>

If you use Yoast or Rank Math, they already output an Organization block; fill in your social profiles there instead of duplicating it by hand. Then check the page with the Rich Results Test. Back up and test on staging before touching the <head> of a live store.

Search Console and Merchant Center

Verify your site in Search Console as a domain property (a DNS TXT record) so it covers every subdomain and you can see which searches you appear in. Keep in mind what the press release says: the clones verify Search Console too. Verification shows nothing to the shopper; it gives you the data and control over your listings. Same with Merchant Center: verify and claim your website, keep your product feed current and review your business information. If you sell on Google Shopping and a clone shows up with your products, you want to be the one with the clean history.

Links from your official channels

Put the link to your store in every social bio, in order confirmation emails and on your invoices. Having every profile point to the same domain, spelled the same way, is what gives sameAs its meaning. If you run a store per country, publish the full list on a single "our official stores" page and link it from everywhere.

None of this makes a clone disappear. It reduces ambiguity, for the person searching and for the one comparing.

The real case

I work with footwear retail, like ECCO Walk, which is exactly the kind of brand that shows up on lists like NordVPN's. But to be straight with you: I don't have a documented cloning case on the sites I run, and I won't claim it happened to any client. What I can do is run this review with the same method I always use: I operate 23+ production WordPress sites on AlmaLinux + WHM/cPanel, and any change to the <head> or to DNS goes to one site at a time, with a backup and a tested way back.

What I wouldn't do

I wouldn't send threatening emails to the address listed on the fake store. It belongs to the operators, it won't help, and it tells them you're watching. Reports go to the registrar, the host and Safe Browsing.

I wouldn't buy from the clone "to test it." You'd be handing your card to a network that lives on stealing them. Evidence comes from screenshots and RDAP.

I wouldn't try to knock the site down myself, with aggressive scans or anything else. It's illegal and it makes you the problem.

And I wouldn't panic-register hundreds of variations of my domain. Registering the obvious ones (your brand on .com, .mx and the countries you sell in) makes sense; trying to cover everything is impossible and expensive.

Let's review it together

If you'd like me to check which domains are using your brand, set up a weekly search, and get your store's structured data and verifications in order, reach out through contact. I do it as part of a WordPress security audit or within monthly maintenance. I can't promise every clone will come down, but you'll know which ones exist and what to do about each.

Sources

About the author

Samuel Torres is a Software & Cloud Engineer at Conqr Digital Agency (Mexico City). He runs 23+ production WordPress sites and processed 80,000 documents with OCR + LLM. More at /en/about. Get a quote on WhatsApp in 2 min

Samuel Torres Pichardo

Samuel Torres Pichardo
Software and cloud engineer in Mexico City, with about 3 years of professional experience.
About me · LinkedIn · GitHub · Contact

Got a project in mind?

Hire me: I'll help you build it.

Websites, online stores, custom systems and cloud. Tell me what you need and I'll tell you how I'd build it, what it costs and how long it takes.

  • Mexico City · remote

Menu

Español

[email protected]