Phishing report - Hosting provider required visual report

Website, Application, Performance
1

What is the name of the domain?

‘www.ovhcloud.com’

What is the error number?

[dc646148e37bd587], [a35819e5ccc741d6], [1da341d5ca960340], [be5202f0821a4745], [9dd9bb1dc6ed46e6], [be5202f0821a4745], [5cb08099f6385a58], [011ffce3df50ffcb], [cba0eb3a9ed47672],

What is the error message?

Hosting provider can not process phishing report

What is the issue you’re encountering

Hosting provider can not process phishing report

What steps have you taken to resolve the issue?

Get phishing feedback of phishing report from hosting provider through Cloudflare Ticket.
"
[dc646148e37bd587]: Cloudflare has responded to your phishing report.
[a35819e5ccc741d6]: Cloudflare has responded to your phishing report.
[1da341d5ca960340]: Cloudflare has responded to your phishing report.
[be5202f0821a4745]: Cloudflare has responded to your phishing report.
[9dd9bb1dc6ed46e6]: Cloudflare has responded to your phishing report
[be5202f0821a4745]: Cloudflare has responded to your phishing report.
[5cb08099f6385a58]: Cloudflare has responded to your phishing report.
[011ffce3df50ffcb]: Cloudflare has responded to your phishing report.
[cba0eb3a9ed47672]: Cloudflare has responded to your phishing report.
[29a4b7151493 7fdc]:Cloudflare has responded to your phishing report.
"

What are the steps to reproduce the issue?

OVH provider:
"
I just got a message from our Abuse team.

This team has told me that for Cloudlfare references, no visual on the status of the request can be obtained from their tool. Your requests have either been processed and closed, or not received.

If your requests are not processed, please check with Cloudflare that they have been sent correctly.
"

ovh - x
ovh - x596×822 28.1 KB

2

OVH provider need image to process phishing process.

3

Hi, I need support.

4

This is something what T&S team has to clear out and get back to you, Community doesn’t have insights, cannot speedup neither cannot help further in such cases.

Sending multiple reports about the same thing just prolongs and slows down the process since they’d end-up in, my best guess, a “bucket” of requests which need to be sorted-out one by one by the “FIFO” principle, meaning we’d have to wait to get our turn in the circle.

5

I understand and I do not spam by multiple report.

Because of HTTP 301 redirections, scammer get phishing caution and redirect to new domain. Also, they have change NS and DNS to remove phishing caution.

So I have to report it again and again.

If I do not report it again, the phishing website keep accessible as normal.

This criminal gets over policy of Cloudflare by redirection and change DNS, NS. I have to report multiple times.

I do not mean to spam and I do not spam.

Sorry my bad english, so I need to explanation to make my idea clearly.

You can check cmctower[.]com now new phishing domain is woodflooring[.]uk[.]com.

They change their NS multiple times to remove phishing caution:

2022 Jun 14:

2025 Mar 13 - 2025 Mar 14:
candy.ns.cloudflare.com
seamus.ns.cloudflare.com

2025 Apr 10:
arnold.ns.cloudflare.com
laylah.ns.cloudflare.com

2025 Apr 21:

johnny.ns.cloudflare.com

cmctower
cmctower1916×990 38.3 KB

6

This topic was automatically closed after 15 days. New replies are no longer allowed.