Skip to security report
Analytics Dashboard
Domain security report
zsdr.pages.dev favicon

zsdr.pages.dev

“Apple”

Threat verdict
CriticalDomain Appeal
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Reachable · access restricted Reachable response; page content was not verified Observed · HTTP probe
Risk signals
VirusTotal detections: 21/91 Automated brand label: Cloudflare Last known active
Jun 15, 2026 Cloudflare CDN
API
Registrar
Cloudflare Pages
Resolved IP
188.114.97.3
Registered
Jun 1, 2026
0 sources

No page capture has been retained for this domain.

In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 21. Exercise extreme caution — do not enter credentials or personal information.

Additional indicators at a glance

VirusTotal
VirusTotal
21 det.
TLS Certificate
Expired or unverified dates -39d
Google Trust Services / WE1 · Hostname coverage not recorded
Age
5 mo
Observed status
Reachable · access restricted 403
PhishDestroy
DestroyList
Listed

Source evidence

5 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

21 / 91

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

OTX

no community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: clean

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Public blocklists

0 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Evidence Summary

Critical
VirusTotal
21/91

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

This domain, zsdr.pages.dev, is actively engaged in credential theft operations targeting users of Cloudflare services. Analysis indicates the site employs deceptive login portals mimicking legitimate Cloudflare authentication pages, designed to harvest usernames, passwords, and session tokens. The threat actors likely exploit the trust associated with the Cloudflare brand to increase the success rate of their phishing campaigns, particularly targeting developers, IT administrators, and organizations utilizing Cloudflare's suite of services. The use of Cloudflare Pages as the hosting infrastructure further complicates detection, as the domain blends in with legitimate traffic originating from the same platform. Infrastructure analysis reveals the domain was registered on June 01, 2026, through Cloudflare Pages, a platform commonly used for static site hosting. As of the latest assessment, 16 out of 95 security vendors on VirusTotal have flagged this domain as malicious, indicating a consensus among a subset of the security community regarding its harmful nature. The domain appears on one security blocklist, though this number is expected to rise as awareness of the threat increases. The discrepancy between the creation date (2026) and current year suggests either a typo in registration data or an attempt to obfuscate the domain's true age, a tactic occasionally employed by threat actors to evade temporal-based detection rules. Users who have visited zsdr.pages.dev or entered credentials on any page hosted under this domain should assume their login details have been compromised. Immediate steps include revoking any active sessions tied to the affected accounts, enabling multi-factor authentication where available, and monitoring for unauthorized access or anomalous activity. Network administrators are advised to block the domain at the perimeter and review logs for connections originating from internal systems. Given the domain's active status, organizations should treat this as an ongoing threat and prioritize user education to prevent further exposure, particularly among teams with access to Cloudflare or other critical infrastructure accounts.

Data coverage & collection

15 · datasets with records / 16 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
21 / 91 · engine detections
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
0 · community references
External blocklists
0 · external matches
Cloudflare Radar
cleanCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
Cloudflare PagesCollection time not recorded
Network & DNS
188.114.97.3 · 0 · nameserversCollection time not recorded
TLS certificate
Google Trust Services / WE1
Detection & evasion
Stored browser and crawler comparison
Availability history
14 · stored state changes
Source observation history
13 · stored source events
Lookalike relationships
100 · retained relationshipsCollection time not recorded
Community reports
Aggregate report counts and dates
IP reputation
Network-level observations
Not recorded in this report 16

These checks have no retained result. This does not mean they passed or that a scan is running.

  • URLScan analysis
  • URLQuery
  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • Page captures
  • HTML archives
  • Page analysis
  • Observed indicators
  • Site configuration files
  • PageSpeed performance
  • Response records
  • Recorded subdomains
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

0 · external source matches

Public Blocklist Status

Domain, network & archive

Cloudflare Pages · 188.114.97.3 · DNS, TLS and retained responses

Domain details

Domain
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Cloudflare Pages US(US)
HTTP Status403 Forbidden
Elapsed Since First Report 27 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 DetectedJun 15, 2026
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.97.3
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-06-11 10:43:11
Valid until
2026-09-09 11:43:10
Hostname coverage
Hostname coverage not recorded
Validity
Stored certificate expired
Collection time
2026-06-26 19:00:10 UTC
Collection source
PhishDestroy collector
Certificate fingerprintf0e5c21dd64c7847d3dcdb505f6c880913077058c1c1129b666bcf5c41b6189f

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

viewdns.info · 188.114.97.3rapiddns.io

Latest Classified Outcome 2026-10-17 01:12:23 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-17 01:12:23 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-08-23 01:16:06 UTC current episode first observed: 2026-10-01 01:37:28 UTC observed RIP window: 2026-08-23 01:16:06 UTC → 2026-10-01 01:37:28 UTC · 936.36h midpoint estimate ≈ 2026-09-11 13:26:47 UTC · precision very 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

VirusTotal Analysis

21 / 91 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 16 detections
ADMINUSLabs
Criminal IP
alphaMountain.ai
BitDefender
Certego
Chong Lua Dao
CyRadar
ESET
Emsisoft
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
MalwareURL
Netcraft
SafeToOpen
Sophos
VIPRE
Webroot
Registration & observation details8

Availability observations

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

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

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking suspected: scanner and visitor titles differ

Not observed No cloaking was observed in the stored scan

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Server header seen by scanner
cloudflare

Scanner note: cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial

Provider response during scan: cloudflare_phishing_interstitial

Title shown to the security scannerSuspected Phishing | Cloudflare
Title shown to a browser visitorApple
Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
Saved result
Cloaked / Filtered

Timeline & response

Collection history, report status and investigation channels

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Domain Status Transition 2026-09-10 22:01:04 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  2. Domain Status Transition 2026-08-18 10:00:20 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  3. Domain Status Transition 2026-08-11 22:00:37 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  4. Domain Status Transition 2026-08-09 22:13:35 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  5. Domain Status Transition 2026-08-07 22:00:17 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  6. Domain Status Transition 2026-08-05 22:00:26 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  7. Domain Status Transition 2026-08-03 10:00:10 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  8. Domain Status Transition 2026-08-01 10:00:08 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  9. Domain Status Transition 2026-07-31 10:00:11 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  10. Domain Status Transition 2026-07-29 22:45:13 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  11. Domain Status Transition 2026-07-27 22:00:33 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  12. Domain Status Transition 2026-07-25 22:01:50 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  13. Cloudflare Radar Scan 2026-07-10 03:26:00 UTC
    Source: Cloudflare Radar
    Event details
    Cloudflare Radar scan registered: View Radar report.
Stored observation history27

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

    blocked→Unknown

    stale_current_evidence

  2. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  3. Availability monitor · Recorded state

    blocked→Unknown

    stale_current_evidence

  4. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  5. Availability monitor · Recorded state

    blocked→Unknown

    stale_current_evidence

Earlier observations 22
  1. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  2. Availability monitor · Recorded state

    blocked→Unknown

    stale_current_evidence

  3. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  4. Availability monitor · Recorded state

    blocked→Unknown

    stale_current_evidence

  5. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  6. Availability monitor · Recorded state

    blocked→Unknown

    stale_current_evidence

  7. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  8. Availability monitor · Recorded state

    Unknown

    stale_current_evidence

  9. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  10. Availability monitor · Recorded state

    Reachable→Unavailable

  11. Availability monitor · Recorded state

    Reachable→Unavailable

  12. Availability monitor · Recorded state

    Reachable→Unavailable

  13. Availability monitor · Recorded state

    Reachable→Unavailable

  14. Availability monitor · Recorded state

    Reachable→Unavailable

  15. Availability monitor · Recorded state

    Reachable→Unavailable

  16. Availability monitor · Recorded state

    Reachable→Unavailable

  17. Availability monitor · Recorded state

    Reachable→Unavailable

  18. Availability monitor · Recorded state

    Reachable→Unavailable

  19. Availability monitor · Recorded state

    Reachable→Unavailable

  20. Availability monitor · Recorded state

    Reachable→Unavailable

  21. Availability monitor · Recorded state

    Reachable→Unavailable

  22. Availability monitor · Recorded state

    https://radar.cloudflare.com/scan/66b85ab9-77ba-43d4-ab86-c1516a6f8f5d

Threat Response Pipeline

Discovery
Analysis
Monitoring

19 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
zsdr.pages.dev detected and queued for full analysis
Jun 15, 2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
VirusTotal
21/91 recorded on VirusTotal
Aug 19, 2026
Brand Impersonation
Impersonation of Cloudflare
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 17, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 403); the cause was not independently established.
Sep 11, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 404); the cause was not independently established.
Aug 18, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 404); the cause was not independently established.
Aug 12, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 404); the cause was not independently established.
Aug 10, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 404); the cause was not independently established.
Aug 8, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 404); the cause was not independently established.
Aug 6, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 404); the cause was not independently established.
Aug 3, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 404); the cause was not independently established.
Aug 1, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 404); the cause was not independently established.
Jul 31, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 404); the cause was not independently established.
Jul 30, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 404); the cause was not independently established.
Jul 28, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 404); the cause was not independently established.
Jul 26, 2026
Cloudflare Radar Scan
Scanned with Cloudflare Radar; network analysis completed.
Jul 10, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Jun 15, 2026
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Related infrastructure

Shared hosting, registrar records and related domains

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

Community records

Retained community reports and observations

Community reports

Reported by 1 community member, first seen Jun 1, 2026

Stored reports
1
Unique reported URLs
1
Accepted1

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
VirusTotal 21 det. ChainPatrol URLQuery SSL Labs Hostname coverage not recorded CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

1 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.

Immediate steps Find reporting contacts
Official reporting routes
PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 zsdr.pages.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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

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
Read the evidence in context

About This Report: zsdr.pages.dev

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “Apple”. Apparent target: Cloudflare.

VirusTotal detections for zsdr.pages.dev: 21 (2026-08-19 02:58:31 UTC).

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

submit an appeal or review the FAQ page.

Embed this report

A 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/zsdr.pages.dev"
  title="PhishDestroy threat report for zsdr.pages.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>