# Website cloning

**URL:** <https://community.letsencrypt.org/t/website-cloning/248308>\
**Category:** Help\
**Created:** [June 20, 2026, 12:57pm UTC](https://community.letsencrypt.org/t/website-cloning/248308 "2026-06-20T12:57:41Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![RobT](https://avatars.discourse-cdn.com/v4/letter/r/7ba0ec/32.png) [@RobT](https://community.letsencrypt.org/u/RobT)\
**Post date:** [June 20, 2026, 12:57pm UTC](https://community.letsencrypt.org/t/website-cloning/248308/1 "2026-06-20T12:57:41Z")

</div>

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. [crt.sh | example.com](https://crt.sh/?q=example.com)), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: [www.bridgehousefarm.com](http://www.bridgehousefarm.com), which is currently being cloned by [www.bridgehouse-farm.co.uk](http://www.bridgehouse-farm.co.uk). Please can the security publishing certificates be revoked as [www.bridgehouse-farm.co.uk](http://www.bridgehouse-farm.co.uk) is trying to pass off as [www.bridgehouse-farm.com](http://www.bridgehouse-farm.com) by trying to establish fake supplier contracts

I ran this command:

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know):

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you're using Certbot):

---

<div class="post-metadata">

**Author:** ![RobT](https://avatars.discourse-cdn.com/v4/letter/r/7ba0ec/32.png) [@RobT](https://community.letsencrypt.org/u/RobT)\
**Post date:** [June 20, 2026, 1:01pm UTC](https://community.letsencrypt.org/t/website-cloning/248308/2 "2026-06-20T13:01:19Z")

</div>

Unfortunately I do not have the domain details requested, but would be grateful for any help that you could provide

---

<div class="post-metadata">

**Author:** ![MaxHearnden](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/maxhearnden/32/87555_2.png) [@MaxHearnden](https://community.letsencrypt.org/u/MaxHearnden)\
**Post date:** [June 20, 2026, 1:03pm UTC](https://community.letsencrypt.org/t/website-cloning/248308/3 "2026-06-20T13:03:31Z")

</div>

I suggest you follow the process on the Nominet (the registry for the .uk TLD) complaints page for domain names used in connection with criminal activity. [Complaints - Nominet](https://nominet.uk/complaints/)

---

<div class="post-metadata">

**Author:** ![danb35](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/danb35/32/70869_2.png) [@danb35](https://community.letsencrypt.org/u/danb35)\
**Post date:** [June 20, 2026, 1:29pm UTC](https://community.letsencrypt.org/t/website-cloning/248308/4 "2026-06-20T13:29:21Z")

</div>

> **[The CA's Role in Fighting Phishing and Malware](https://letsencrypt.org/2015/10/29/phishing-and-malware)**
>
> Since we announced Let’s Encrypt we’ve often been asked how we’ll ensure that we don’t issue certificates for phishing and malware sites. The concern most commonly expressed is that having valid HTTPS certificates helps these sites look more...

---

<div class="post-metadata">

**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\
**Post date:** [June 20, 2026, 2:39pm UTC](https://community.letsencrypt.org/t/website-cloning/248308/5 "2026-06-20T14:39:28Z")

</div>

Upon discovering criminal activity within a building do you...

A. Report the criminal activity to the manufacturer of the building's locks and petition for removal of the locks.

B. Report the criminal activity to the appropriate law enforcement authorities and petition for cessation of the criminal activity.

---

<div class="post-metadata">

**Author:** ![sebastiannielsen](https://avatars.discourse-cdn.com/v4/letter/s/e9bcb4/32.png) [@sebastiannielsen](https://community.letsencrypt.org/u/sebastiannielsen)\
**Post date:** [June 21, 2026, 7:31pm UTC](https://community.letsencrypt.org/t/website-cloning/248308/6 "2026-06-21T19:31:23Z")

</div>

> [@griffin](#):
>
> Report the criminal activity to the manufacturer of the building's locks and petition for removal of the locks.

I disagree kinda with comparing SSL certificates with a "lock". Its more like a business license, like a grocery store license, alcohol sales license or resturant license.

And thus, it becomes more resonable to petition for its removal. However, since Lets encrypt is a "business license" anyone can get (SHALL-ISSUE), it becomes like described in "The CA's role in fighting phishing and malware".

Think like a CCW (gun license) with shall-issue - but more business related. So while you are right that Lets encrypt wont revoke the "shall-issue business license" from the malicious page, its kinda wrong to compare it to a lock.

---

<div class="post-metadata">

**Author:** ![petercooperjr](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/petercooperjr/32/84698_2.png) [@petercooperjr](https://community.letsencrypt.org/u/petercooperjr)\
**Post date:** [June 21, 2026, 11:40pm UTC](https://community.letsencrypt.org/t/website-cloning/248308/7 "2026-06-21T23:40:10Z")

</div>

Well, I agree it's not really a lock, but I also don't think it's like a business license. It's more like the company that provided the house address number sign for the building, so that people could know whether they were at the address they thought they were. But it doesn't really have anything to do with what goes on in the building.

---

<div class="post-metadata">

**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\
**Post date:** [June 22, 2026, 3:18am UTC](https://community.letsencrypt.org/t/website-cloning/248308/8 "2026-06-22T03:18:55Z")

</div>

To the best of my knowledge, a CA in no way, shape, or form ever issues a license of any kind to any entity to permit any activity of that entity as a CA in no way, shape, or form possesses the sovereignty to govern the activities of any entity aside from itself via the service it provides based upon associated agreements. Therefore, petitioning a CA to cease providing its service to any entity in no way resembles enforceable denial of that entity's ability to continue performing the activities upon which the petition is based. Such a petition is, to me, little different from a petition upon a mobile phone service provider to cease providing its service to a criminal organization in hopes of halting said criminal organization's criminal activities. It is, to me, an ineffective and subversive approach to DIY law enforcement that walks a very thin line, much like having the power shut off to a neighbor's home because their electric fence is (possibly rightly) perceived as a threat to neighborhood children and pets. In my experience, denial of service rarely prevents crime; it merely shifts how crime is committed.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [July 22, 2026, 3:19am UTC](https://community.letsencrypt.org/t/website-cloning/248308/9 "2026-07-22T03:19:44Z")

</div>

Closed on July 22, 2026, 3:19am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
