Skip to security report
Domain security and threat intelligence
lispy-rivedfdsr-787c.eugeniebenoits397.workers.dev favicon

lispy-rivedfdsr-787c.eugeniebenoits397.workers.dev

“Suspected Phishing | Cloudflare”

Registrar
Cloudflare Workers
Resolved IP
172.67.204.84
PhishDestroy assessment High
Availability Reachable · access restricted Reachable response; page content was not verified Observed · HTTP probe
Stored PhishDestroy threat listing Automated brand label: Cloudflare Last known active
Sep 10, 2026 CDN
API
Cloudflare Phish — Listed on PhishDestroy
Stored PhishDestroy threat listing. VirusTotal analysis stored; no vendor detections were recorded at check time. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
Source evidenceVirusTotal 0 / 89 4 sources

VirusTotal

0 / 89 engine detections

Open report

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

PhishDestroy threat report

Overview

This Cloudflare Workers subdomain is an impersonation phishing page built to pass as Cloudflare. It targets people who manage websites, DNS or domains through a Cloudflare account. PhishDestroy first flagged it on 2026-09-10. The site has been dead since 2026-09-19 with its content blocked by the hosting provider, and it was still offline at the last check on 2026-10-19.

How the scam works

Cloudflare-branded phishing usually poses as a login prompt, security alert or verification step, and whatever the victim types goes straight to the operator. A stolen Cloudflare account is valuable because it controls DNS, SSL and traffic routing for every site behind it. With that access an attacker can redirect visitors, inject malicious scripts or hijack email records. The page now carries the title "Suspected Phishing | Cloudflare", which is Cloudflare's own warning interstitial rather than a lure, while we classified the page as Cloudflare impersonation.

Evidence

Independent detection was close to nonexistent. VirusTotal returned 0 detections from 89 engines on 2026-09-20, one day after the site went offline, so scanners had little live content left to judge. PhishDestroy is the only blocklist listing it. The provider's block, visible in the current page title, separately shows that the content was treated as phishing.

Infrastructure

The operation ran entirely on Cloudflare Workers under a disposable account subdomain with a random-looking prefix. It resolved to 172.67.204.84 on Cloudflare, Inc.'s network, geolocated to Canada, with a certificate from Google Trust Services. Hosting a fake Cloudflare page on Cloudflare's own platform gave it a plausible address and a valid padlock. It also put the page within reach of the provider, which shut it down nine days after our first sighting.

What to do

If you entered credentials here, change your Cloudflare password right away and turn on or reset two-factor authentication. Revoke any API tokens and keys you cannot account for. Then review the audit log, DNS records, Page Rules, Workers and account members for changes you did not make. Change that password anywhere else you reused it. Defenders should block this domain along with its parent Workers account subdomain, and alert on Cloudflare-themed login pages served from free serverless hosting.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Domain details

Domain
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Cloudflare Workers
HTTP Status403 Forbidden
Elapsed Since First Report 8 days
What we count Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Reachable · access restricted.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedSep 10, 2026

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
172.67.204.84
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-07-22 08:48:53
Valid until
2026-10-20 09:47:18
Hostname coverage
Certificate hostname mismatch
Validity
Validity ends today in stored record
Collection time
2026-09-18 19:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint101f018acbba55c7d2096990a13e77445db068a476ad6aa59b8aaaae12133074
Certificate names · 1 SANs
  • eugeniebenoits397.workers.dev

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-19 01:15:38 UTC

Primary outcome Provider block observed reason: Cloudflare anti-phishing block 95% confidence
Attribution Cloudflare mechanism: Phishing Interstitial source: Current Http Probe
Evidence layers Availability: Provider blocked Content: Provider blocked DNS: Stale Registration: Unknown
Latest HTTP observation Provider block observed Cloudflare anti-phishing block Cloudflare Phishing Interstitial 95% provider marker verified 2026-10-19 01:15:38 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-09-10 18:28:08 UTC current episode first observed: 2026-10-01 01:52:44 UTC observed RIP window: 2026-09-10 18:28:08 UTC → 2026-10-01 01:52:44 UTC · 487.41h midpoint estimate ≈ 2026-09-20 22:10:26 UTC · precision low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of lispy-rivedfdsr-787c.eugeniebenoits397.workers.dev · checked Sep 18, 2026

100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
1.84s
Largest Contentful Paint
CLS
0.001
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.76s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
487.41
Estimate basis
Bounded by observations
Estimate precision
Low

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

lispy-rivedfdsr-787c.eugeniebenoits397.workers.dev
Saved result
Cloaked / Filtered
Stored observation history10

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  2. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  3. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  4. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  5. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

Earlier observations 5
  1. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  2. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  3. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  4. Availability monitor · Recorded state

    Reachable→Unavailable

  5. Availability monitor · First collection record

    Reachable

Recorded activity

3 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    0/89 engine detections

    View source
  3. Added to PhishDestroy

    lispy-rivedfdsr-787c.eugeniebenoits397.workers.dev

    View source

Lookalike domains

142 stored lookalike domains

c.loudflare.com subdomain claudflare.com vowel-swap cloadflare.com vowel-swap cloduflare.com transposition cloodflare.com vowel-swap clou.dflare.com subdomain cloudf.lare.com subdomain cloudfalre.com transposition cloudfla.re.com subdomain cloudflaer.com transposition cloudflarecom.com various cloudflore.com vowel-swap
Show all (88)
cloudflrae.com transposition cloudflure.com vowel-swap cloudflwre.com replacement cloudlfare.com transposition cloufdlare.com transposition cluodflare.com transposition coludflare.com transposition c1oudf1are.com homoglyph c1oudflare.com homoglyph ccloudflare.com repetition cioudfiare.com homoglyph cioudflare.com homoglyph ckoudflare.com replacement cl0udfiare.com homoglyph cliudflare.com replacement clludflare.com replacement clo-udflare.com hyphenation clodflare.com omission clohdflare.com replacement cloidflare.com replacement clooudflare.com insertion cloubflare.com homoglyph clouclflare.com homoglyph cloud-flare.com hyphenation cloudcflare.com insertion cloudclare.com replacement clouddflare.com insertion cloudfare.com omission cloudfflare.com insertion cloudfiare.com homoglyph cloudfla1re.com insertion cloudflaare.com repetition cloudflae.com omission cloudflaee.com replacement cloudflar.com omission cloudflarr.com replacement cloudflarre.com repetition cloudflarz.com replacement cloudflate.com replacement cloudfllare.com repetition cloudflre.com omission cloudflsre.com replacement cloudiflare.com homoglyph cloudlare.com omission cloudlflare.com homoglyph cloudsflare.com insertion cloudtflare.com insertion cloudtlare.com replacement cloudvflare.com insertion cloudxflare.com insertion cloufflare.com bitsquatting clouflare.com omission cloulflare.com bitsquatting clourflare.com replacement clousflare.com replacement cloutflare.com bitsquatting clouudflare.com repetition clowdflare.com bitsquatting cloydflare.com replacement clpudflare.com replacement cludflare.com omission cmoudflare.com bitsquatting cnoudflare.com bitsquatting coudflare.com omission dloudflare.com homoglyph doudflare.com homoglyph gloudflare.com bitsquatting kloudflare.com bitsquatting loudflare.com omission sloudflare.com bitsquatting xn--clodflare-is7d.com homoglyph xn--cloudflae-7fe.com homoglyph xn--cloudflae-7n6d.com homoglyph xn--cloudflar-3f7d.com homoglyph xn--cloudflar-j4a.com homoglyph xn--cloudflre-676d.com homoglyph xn--clouflare-t05d.com homoglyph xn--cludflare-6x3d.com homoglyph xn--cludflare-ml7d.com homoglyph xn--coudflare-0sb.com homoglyph aloudflare.com bitsquatting bloudflare.com bitsquatting cdoudflare.com bitsquatting choudflare.com bitsquatting clgudflare.com bitsquatting clkudflare.com bitsquatting clmudflare.com bitsquatting clnudflare.com bitsquatting

Showing 100 of 142

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

0 evidence signal groups linked 0 stored notification records Reachable · access restricted

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Official reporting routes

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including lispy-rivedfdsr-787c.eugeniebenoits397.workers.dev)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/lispy-rivedfdsr-787c.eugeniebenoits397.workers.dev"
  title="PhishDestroy threat report for lispy-rivedfdsr-787c.eugeniebenoits397.workers.dev"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>