Skip to security report
Recorded security signals
Stored VirusTotal result: 0/92 engines flagged. Analysis time (as stored): 2026-10-10 17:07 UTC. Retrieved (as stored): 2026-11-16 20:45 UTC. Listed by external blocklists: MetaMask, SEAL, PhishFeed. Use caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
en-learn-start-ledgr.pages.dev favicon

en-learn-start-ledgr.pages.dev

In short

On 2026-11-16, the page at en-learn-start-ledgr.pages.dev presents a getting started guide designed to help users set up and manage their digital assets safely. The interface displays an introduction section with welcome instructions and security tips, followed by a detailed step-by-step setup breakdown covering account creation, wallet security, adding assets, exploring features, and understanding overall onboarding requirements.

“Getting Started Guide”

Registrar
United StatesCloudflare
Resolved IP
172.66.44.149
First observed
Nov 16, 2026
PhishDestroy assessment Critical
74/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Stored blocklist matches: 3
VirusTotal
engine detections ·
Blocklist matches
MetaMask, SEAL, PhishFeed
URLScan
engine verdict · score 100
Cloudflare Radar
Page captures
open gallery
Nov 16, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded en-learn-start-ledgr.pages.dev on 2026-11-16. Stored VirusTotal result: 0/92 engines flagged. Analysis time (as stored): 2026-10-10 17:07 UTC. Retrieved (as stored): 2026-11-16 20:45 UTC. Listed by external blocklists: MetaMask, SEAL, PhishFeed. Risk: critical (74/100). Registrar: Cloudflare. Status: Last known active. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
0 / 92
Blocklist matches
3
Hosting
172.66.44.149
Registrar
United StatesCloudflare
Page captures
3

Capture recorded with this analysis · Cloudflare Radar · 2026-11-16T20:37:07Z
SHA-256: 99b7f286a582c83b034d89066fe65589fe8227a93f0f2440f9eb5f16223838c3

PhishDestroy analysis, reviewed version

On 2026-11-16, the page at en-learn-start-ledgr.pages.dev presents a getting started guide designed to help users set up and manage their digital assets safely. The interface displays an introduction section with welcome instructions and security tips, followed by a detailed step-by-step setup breakdown covering account creation, wallet security, adding assets, exploring features, and understanding overall onboarding requirements.

The stored VirusTotal domain result reports 0 detections out of 92 engines.

Source evidenceVirusTotal 0 / 92 7 sources

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 12 fields

Observed: · Retrieved:

UUID

0e7d1c4d-e2b7-4186-8cd5-d3672470440e

Final URL

https://en-learn-start-ledgr.pages.dev/

HTTP response

200

Navigation history

URL: https://en-learn-start-ledgr.pages.dev/; Status: 200

DOM structure hash

b9e0b6ddea9ed7d75c6d011d98963c6a6a72e5d8281223b172a150671f75d3fb

Document hash

b92fac2be772a02fa4eebd1def533966569a02b4168435d096b0898d4d39f85a

Phishing classifier result

phishing

Cloudflare Radar rank

Bucket: >200000

DNS records

Name: en-learn-start-ledgr.pages.dev; Type: A; Value: 172.66.44.149, Name: en-learn-start-ledgr.pages.dev; Type: A; Value: 172.66.47.107, Name: en-learn-start-ledgr.pages.dev; Type: AAAA; Value: 2606:4700:310c::ac42:2c95, Name: en-learn-start-ledgr.pages.dev; Type: AAAA; Value: 2606:4700:310c::ac42:2f6b

DNSSEC valid

✗

IP

172.66.44.149

Registration record

Registrar: CloudFlare, Inc.; Created: 2020-09-02T02:33:29Z; Updated: 2026-06-09T12:00:52Z; Expires: 2027-09-02T02:33:29Z; Nameservers: adi.ns.cloudflare.com, karl.ns.cloudflare.com
Original source fields · JSON
UUID
0e7d1c4d-e2b7-4186-8cd5-d3672470440e
Final URL
https://en-learn-start-ledgr.pages.dev/
Status
200
History
URL: https://en-learn-start-ledgr.pages.dev/; Status: 200
DOM structure hash
b9e0b6ddea9ed7d75c6d011d98963c6a6a72e5d8281223b172a150671f75d3fb
Document hash
b92fac2be772a02fa4eebd1def533966569a02b4168435d096b0898d4d39f85a
Phishing v2
phishing
Radar rank
Bucket: >200000
DNS records
Name: en-learn-start-ledgr.pages.dev; Type: A; Value: 172.66.44.149, Name: en-learn-start-ledgr.pages.dev; Type: A; Value: 172.66.47.107, Name: en-learn-start-ledgr.pages.dev; Type: AAAA; Value: 2606:4700:310c::ac42:2c95, Name: en-learn-start-ledgr.pages.dev; Type: AAAA; Value: 2606:4700:310c::ac42:2f6b
Dnssec valid
✗
IP
172.66.44.149
Registration record
Registrar: CloudFlare, Inc.; Created: 2020-09-02T02:33:29Z; Updated: 2026-06-09T12:00:52Z; Expires: 2027-09-02T02:33:29Z; Nameservers: adi.ns.cloudflare.com, karl.ns.cloudflare.com
Separate stored summary

This summary differs from the dated scan above. It is retained for provenance and does not override the selected source observation.

Source path
phishdestroy.technologies.cf_radar
Scope
Separate stored summary; an absent observation date is not evidence of a clean scan.

URLScan

Malicious · engine verdict · score 100

SHA-256 b92fac2be772a02fa4eebd1def533966569a02b4168435d096b0898d4d39f85a

Open report
URLScanOriginal source recordObserved: 17 fields
Separate monitor record

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

UUID
01a1e60f-e552-73d8-a0a2-14be3e1f529c

VirusTotal

0 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 12 fields
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

Source
VirusTotal
Result state
observed
Numerator
0
Denominator
92
Observed at
2026-10-10 17:07:49
Checked at
2026-11-16 21:45:45
Fetched at
2026-11-16 20:45:46

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

5 / 100 · heuristic score · 0 brand references · 0 classifications

Open report
Separate monitor score · 5 / 100 · 2026-11-16T21:13:43Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

Heuristic score
5
Analyzed at
2026-11-16T21:13:43Z
Source timestamp
2026-11-16 22:13:43

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

Ai title
en-learn-start-ledgr.pages.dev Getting Started Guide
Ai description
PhishDestroy records en-learn-start-ledgr.pages.dev displaying a digital asset getting started guide and step-by-step setup instructions.
Ai summary
On 2026-11-16, the page at en-learn-start-ledgr.pages.dev presents a getting started guide designed to help users set up and manage their digital assets safely. The interface displays an introduction section with welcome instructions and security tips, followed by a detailed step-by-step setup breakdown covering account creation, wallet security, adding assets, exploring features, and understanding overall onboarding requirements. The stored VirusTotal domain result reports 0 detections out of 92 engines.
Ai generated by
threat-v6-gemini
Ai generated at
2026-11-16 22:09:47
Revision
fb7003c832ec3f6fa1c13150af449f5661ffbea20e18ac5d8ecc77d0d61f1310
Mode
reviewed
Interpretation
Selected public package; text generation time is separate from source observation dates.

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

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 21 fields

Mail configuration

Spf lookups: 0

Protective DNS results

Resolvers: 12; Blocked count: 0

Page title and metadata

Title: Getting Started Guide

Trackers

Requests: 1

Forms and mixed content

Third party scripts: 0

HTTP response

Up: ✓; Code: 200; Timings: DNS: 0; Wait: 44; Download: 0; Response ms: 87

TLS connection

Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓

Ports

Open: 80, 443, 8080

Carbon estimate

Bytes: 6225; Co2 grams: 0.0002; Cleaner than: 82

DNS server

NS: (IP: 108.162.194.169; Host: daphne.ns.cloudflare.com), (IP: 173.245.59.120; Host: ivan.ns.cloudflare.com); Zone: en-learn-start-ledgr.pages.dev

Location

IP: 2606:4700:310c::ac42:2c95; ASN: 13335; Org: Cloudflare, Inc.; City: San Francisco; Country: US

SSL

Issuer: Google Trust Services / WE1; Subject: en-learn-start-ledgr.pages.dev

DNS records

A: 172.66.47.107, 172.66.44.149; NS: ivan.ns.cloudflare.com, daphne.ns.cloudflare.com; Soa: Nsname: daphne.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2416967489; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Aaaa: 2606:4700:310c::ac42:2f6b, 2606:4700:310c::ac42:2c95

DNSSEC

Ds: ✗; Rrsig: ✗; Dnskey: ✗

HSTS

Message: Site does not serve any HSTS headers.

HTTP security policies

Xframeoptions: ✗; Referrerpolicy: strict-origin-when-cross-origin; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: nosniff; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗

Web application firewall

Waf: Cloudflare; Has waf: ✓

Get IP

IP: 2606:4700:310c::ac42:2f6b; Family: 6

Redirects

Chain: https://en-learn-start-ledgr.pages.dev

Page links

Internal count: 1

HTTP headers

Headers: Server: cloudflare; Content type: text/html; charset=utf-8; X content type options: nosniff; Referrer policy: strict-origin-when-cross-origin
Original source fields · JSON
Mail configuration
Spf lookups: 0
Protective DNS results
Resolvers: 12; Blocked count: 0
Page title and metadata
Title: Getting Started Guide
Trackers
Requests: 1
Forms and mixed content
Third party scripts: 0
Status
Up: ✓; Code: 200; Timings: DNS: 0; Wait: 44; Download: 0; Response ms: 87
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443, 8080
Carbon
Bytes: 6225; Co2 grams: 0.0002; Cleaner than: 82
DNS server
NS: (IP: 108.162.194.169; Host: daphne.ns.cloudflare.com), (IP: 173.245.59.120; Host: ivan.ns.cloudflare.com); Zone: en-learn-start-ledgr.pages.dev
Location
IP: 2606:4700:310c::ac42:2c95; ASN: 13335; Org: Cloudflare, Inc.; City: San Francisco; Country: US
SSL
Issuer: Google Trust Services / WE1; Subject: en-learn-start-ledgr.pages.dev
DNS records
A: 172.66.47.107, 172.66.44.149; NS: ivan.ns.cloudflare.com, daphne.ns.cloudflare.com; Soa: Nsname: daphne.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2416967489; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Aaaa: 2606:4700:310c::ac42:2f6b, 2606:4700:310c::ac42:2c95
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Message: Site does not serve any HSTS headers.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: strict-origin-when-cross-origin; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: nosniff; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Firewall
Waf: Cloudflare; Has waf: ✓
Get IP
IP: 2606:4700:310c::ac42:2f6b; Family: 6
Redirects
Chain: https://en-learn-start-ledgr.pages.dev
Page links
Internal count: 1
HTTP headers
Headers: Server: cloudflare; Content type: text/html; charset=utf-8; X content type options: nosniff; Referrer policy: strict-origin-when-cross-origin

Questions about en-learn-start-ledgr.pages.dev

Is en-learn-start-ledgr.pages.dev legit?

PhishDestroy rates en-learn-start-ledgr.pages.dev as critical risk (74/100) from the recorded evidence; it was first recorded on 2026-11-16. Stored VirusTotal result: 0/92 engines flagged. Analysis time (as stored): 2026-10-10 17:07 UTC. Retrieved (as stored): 2026-11-16 20:45 UTC. Listed by external blocklists: MetaMask, SEAL, PhishFeed. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is en-learn-start-ledgr.pages.dev safe to connect a wallet?

This report does not record which wallet requests en-learn-start-ledgr.pages.dev makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used en-learn-start-ledgr.pages.dev?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesMetaMask · PhishDestroy · SEAL · PhishFeed · no match in the other 8 4
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source
PhishFeed Listed View source

Last checked

Stored Capture · 3 captures

All capture links and hashes (3)

Domain details

Domain
IP Context 172.66.44.149 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Cloudflare US(US)
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 16, 2026
DOM Analysisanalyzed Nov 16, 2026score 5/100
Submitted URLhttp://en-learn-start-ledgr.pages.dev/
Observed page title
Getting Started Guide
TLS Certificate
Issued by WE1 · stored validity ends in 37 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
172.66.44.149
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • daphne.ns.cloudflare.com
  • ivan.ns.cloudflare.com

SOA

  • nsname: daphne.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2416967489
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

TLS certificate

Issuer
WE1
Valid from
2026-09-25 11:45:43
Valid until
2026-12-24 12:43:21
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint0bde977554bf26fd7a06bd5b2a8f7f3f22c47b3c6c283dd5ea17693520d26db1
Certificate names · 2 SANs
  • en-learn-start-ledgr.pages.dev
  • *.en-learn-start-ledgr.pages.dev

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

Report This Domain Submit evidence & help protect others
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of en-learn-start-ledgr.pages.dev ·

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

Availability observations

Last reachable observation

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

All stored data86
Open complete records

Captured network requests

Network requests: 2 SHA-256 hashes: 2 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-16 20:34 UTC.

Open this scan on URLScan 01a1e60f-e552-73d8-a0a2-14be3e1f529c ↗

Stored observation history1

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

  1. Domain monitor · First collection record

    Reachable

All retained availability observations2

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. Current state backfill
    Observation source
    Current state backfill
    Cause
    Probe inconclusive
    Availability state
    unreachable
    DNS state
    stale
    Monitor confidence
    20
    Provider action verified
    ✗
    Registrar mechanism verified
    ✗
    Linked to a report
    ✗
    Original source timestamp
    2026-11-16 21:33:34.000000
    Evidence SHA-256
    2e7dc78a05efa20827e2ea22c639f9a4fc757cbe9bb3a7c91e4035f322abad9f
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-16 21:33:34
  2. Http observation
    Observation source
    Http observation
    Cause
    Probe inconclusive
    Availability state
    unreachable
    Monitor confidence
    20
    Provider action verified
    ✗
    Registrar mechanism verified
    ✗
    Linked to a report
    ✗
    Original source timestamp
    2026-11-16 21:33:34.000000
    Evidence SHA-256
    2e7dc78a05efa20827e2ea22c639f9a4fc757cbe9bb3a7c91e4035f322abad9f
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-16 21:33:34

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

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

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    en-learn-start-ledgr.pages.dev detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Blocklist Detection · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 6 of 6
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

4 entries
  1. Cloudflare Radar

    Phishing

    View source
  2. Added to PhishDestroy

    en-learn-start-ledgr.pages.dev

    View source
  3. URLScan

    Page captured

    View source
  4. VirusTotal

    0/92 engine detections

    View source
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.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

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

en-learn-start-ledgr.pages.dev

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

2 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Official reporting routes

More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

Report to Your Local Authorities

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

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

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.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

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 en-learn-start-ledgr.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

Stay Informed, Stay Safe

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

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 →
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/en-learn-start-ledgr.pages.dev"
  title="PhishDestroy threat report for en-learn-start-ledgr.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>