Skip to security report
Recorded security signals
Stored VirusTotal result: 0/92 engines flagged. Analysis time (as stored): 2026-09-25 09:49 UTC. Retrieved (as stored): 2026-10-22 19:12 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
official-ledgre-eng-dev.pages.dev favicon

official-ledgre-eng-dev.pages.dev

In short

The page at official-ledgre-eng-dev.pages.dev, captured on 2026-10-22, presents a wallet setup guide titled "Secure Your Wallet: Essential Setup Guide." It is organized into sections with orange headings on a dark background. The first section, "The Foundation of Security: Your Recovery Phrase," describes a 24-word recovery phrase as the backup for private keys and includes a warning against digitizing or photographing it.

“Secure Digital Asset Management - Start Guide”

Registrar
United StatesCloudflare
Resolved IP
United States188.114.97.3Cloudflare, Inc. · CDN
First observed
Oct 22, 2026
PhishDestroy assessment Critical
84/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 99
Page captures
open gallery
Oct 22, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded official-ledgre-eng-dev.pages.dev on 2026-10-22. Stored VirusTotal result: 0/92 engines flagged. Analysis time (as stored): 2026-09-25 09:49 UTC. Retrieved (as stored): 2026-10-22 19:12 UTC. Listed by external blocklists: MetaMask, SEAL, PhishFeed. Risk: critical (84/100). Registrar: Cloudflare. Status: Last known active. Hosting: CloudFLARENET-EU. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
0 / 92
Blocklist matches
3
Scam type (automated label)
Seed Phrase Theft
Hosting
United States188.114.97.3Cloudflare, Inc. · CDN
Registrar
United StatesCloudflare
Page captures
4

Capture recorded with this analysis · URLScan · 2026-10-22T18:27:43Z
SHA-256: ba86410fbe5bd4f3e84aee13a851259b3382d996f0da12fbc42f456649828409

PhishDestroy analysis, reviewed version

The page at official-ledgre-eng-dev.pages.dev, captured on 2026-10-22, presents a wallet setup guide titled "Secure Your Wallet: Essential Setup Guide." It is organized into sections with orange headings on a dark background. The first section, "The Foundation of Security: Your Recovery Phrase," describes a 24-word recovery phrase as the backup for private keys and includes a warning against digitizing or photographing it.

A second section, "Initial Device Setup and PIN Creation," advises choosing a PIN of 4 to 8 digits and avoiding simple sequences. A third section, "The Recovery Phrase Generation Process," outlines steps for writing down each word as it appears on the device screen, with instructions to double-check spelling.

Source evidenceVirusTotal 0 / 92 8 sources

URLScan

Malicious · engine verdict · score 99

SHA-256 b089f64a40a34ad57d4164a54026dcf463ce97e39a9f7280658a86303a825172

Open report
URLScanOriginal source recordObserved: 17 fields
Separate monitor record · 2026-10-23 03:30 UTC

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

UUID
01a164de-6135-71c5-9cc4-c7a674864dbf
Score
0
Malicious
✗
Result at
2026-10-23T03:30:55Z
Enriched at
2026-10-24T08:17:26Z
Source timestamps
Urlscan result at: 2026-10-23 05:30:55; Urlscan enriched at: 2026-10-24 10:17:26

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
4
Denominator
92
Vendors
alphaMountain.ai, Forcepoint ThreatSeeker, LevelBlue, SOCRadar
Checked at
2026-11-05 04:05:41
Fetched at
2026-11-05 03:05:42

URLQuery

checked — no detections recorded

Open report

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

83 / 100 · heuristic score · 1 brand reference · 1 classification

Open report
Separate monitor score · 70 / 100 · 2026-10-22T22:20:13Z

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

Heuristic score
70
Analyzed at
2026-10-22T22:20:13Z
Source timestamp
2026-10-23 00:20:13

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
official-ledgre-eng-dev.pages.dev: Secure Your Wallet Setup Guide
Ai description
PhishDestroy records the page at official-ledgre-eng-dev.pages.dev as a wallet setup guide covering recovery phrases, PIN creation, and phrase generation steps.
Ai summary
The page at official-ledgre-eng-dev.pages.dev, captured on 2026-10-22, presents a wallet setup guide titled "Secure Your Wallet: Essential Setup Guide." It is organized into sections with orange headings on a dark background. The first section, "The Foundation of Security: Your Recovery Phrase," describes a 24-word recovery phrase as the backup for private keys and includes a warning against digitizing or photographing it. A second section, "Initial Device Setup and PIN Creation," advises choosing a PIN of 4 to 8 digits and avoiding simple sequences. A third section, "The Recovery Phrase Generation Process," outlines steps for writing down each word as it appears on the device screen, with instructions to double-check spelling.
Ai generated by
threat-v6-mimo
Ai generated at
2026-11-04 09:27:05
Revision
3baf5175bd4df3005a5ed8ca4793d6b24d6410ae8eb25c10434263f2d94f9334
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

CAA records

Domain: official-ledgre-eng-dev.pages.dev

Protective DNS results

Resolvers: 12; Blocked count: 0

Page title and metadata

Title: Secure Digital Asset Management - Start Guide

Trackers

Requests: 1

Forms and mixed content

Third party scripts: 0

HTTP response

Up: ✓; Code: 200; Timings: DNS: 2; TLS: 20; Wait: 327; Connect: 11; Download: 0; Response ms: 360

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: 6535; Co2 grams: 0.0002; Cleaner than: 81

DNS server

NS: (IP: 172.64.32.103; Host: beth.ns.cloudflare.com), (IP: 162.159.44.200; Host: patrick.ns.cloudflare.com); Zone: official-ledgre-eng-dev.pages.dev

Location

IP: 2a06:98c1:3120::3; ASN: 13335; Org: CloudFLARENET-EU; City: London; Country: GB

SSL

Issuer: Google Trust Services / WE1; Subject: official-ledgre-eng-dev.pages.dev

DNS records

A: 188.114.96.3, 188.114.97.3; NS: beth.ns.cloudflare.com, patrick.ns.cloudflare.com; Soa: Nsname: beth.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2417751735; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Aaaa: 2a06:98c1:3120::3, 2a06:98c1:3121::3

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: 2a06:98c1:3120::3; Family: 6

Redirects

Chain: https://official-ledgre-eng-dev.pages.dev

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
Caa records
Domain: official-ledgre-eng-dev.pages.dev
Protective DNS results
Resolvers: 12; Blocked count: 0
Page title and metadata
Title: Secure Digital Asset Management - Start Guide
Trackers
Requests: 1
Forms and mixed content
Third party scripts: 0
Status
Up: ✓; Code: 200; Timings: DNS: 2; TLS: 20; Wait: 327; Connect: 11; Download: 0; Response ms: 360
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: 6535; Co2 grams: 0.0002; Cleaner than: 81
DNS server
NS: (IP: 172.64.32.103; Host: beth.ns.cloudflare.com), (IP: 162.159.44.200; Host: patrick.ns.cloudflare.com); Zone: official-ledgre-eng-dev.pages.dev
Location
IP: 2a06:98c1:3120::3; ASN: 13335; Org: CloudFLARENET-EU; City: London; Country: GB
SSL
Issuer: Google Trust Services / WE1; Subject: official-ledgre-eng-dev.pages.dev
DNS records
A: 188.114.96.3, 188.114.97.3; NS: beth.ns.cloudflare.com, patrick.ns.cloudflare.com; Soa: Nsname: beth.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2417751735; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Aaaa: 2a06:98c1:3120::3, 2a06:98c1:3121::3
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: 2a06:98c1:3120::3; Family: 6
Redirects
Chain: https://official-ledgre-eng-dev.pages.dev
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 official-ledgre-eng-dev.pages.dev

Is official-ledgre-eng-dev.pages.dev legit?

PhishDestroy rates official-ledgre-eng-dev.pages.dev as critical risk (84/100) from the recorded evidence; it was first recorded on 2026-10-22. Stored VirusTotal result: 0/92 engines flagged. Analysis time (as stored): 2026-09-25 09:49 UTC. Retrieved (as stored): 2026-10-22 19:12 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 official-ledgre-eng-dev.pages.dev safe to connect a wallet?

This report does not record which wallet requests official-ledgre-eng-dev.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 official-ledgre-eng-dev.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 · 4 captures

All capture links and hashes (4)
official-ledgre-eng-dev.pages.dev: Crypto scam — Blocked by MetaMask, flagged by SEAL, 4/92 VirusTotal engines. PhishDestroy risk score 83/100 (critical).
Social preview card official-ledgre-eng-dev.pages.dev: Crypto scam — Blocked by MetaMask, flagged by SEAL, 4/92 VirusTotal engines. PhishDestroy risk score 83/100 (critical). v 7194d6776843

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 99 report ↗
IP Context United States188.114.97.3 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 DetectedOct 22, 2026
DOM Analysisanalyzed Oct 23, 2026score 83/1001 brand signal
Submitted URLhttp://official-ledgre-eng-dev.pages.dev/
Favicon Hash
Observed page title
Secure Digital Asset Management - Start Guide
Automated brand references
Foundation
TLS Certificate
Issued by Google Trust Services / WE1

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States188.114.97.3
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
United StatesSan Francisco, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • beth.ns.cloudflare.com
  • patrick.ns.cloudflare.com

SOA

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

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-08-19 16:11:08
Valid until
2026-11-17 17:11:00
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprinta8514f595a6b2fd7c839ba922e3da3b51af154260b212f3c613cc1a61692b238
Certificate names · 2 SANs
  • official-ledgre-eng-dev.pages.dev
  • *.official-ledgre-eng-dev.pages.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-11-16 11:25:02 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Stale
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-16 11:25:02 UTC
RDAP registration
Observed timeline last reachable: 2026-11-16 11:25:02 UTC last content: 2026-11-16 11:25:02 UTC
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.
Report This Domain Submit evidence & help protect others
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

All stored data98
Open complete records

Captured network requests

Network requests: 3 SHA-256 hashes: 3 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-10-29 02:03 UTC.

Open this scan on URLScan 01a164de-6135-71c5-9cc4-c7a674864dbf ↗

Stored observation history4

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

    live_content

    content_served

  2. Availability monitor · Recorded state

    live_content

    content_served

  3. Availability monitor · Recorded state

    live_content

    content_served

  4. Domain monitor · First collection record

    Reachable

All retained availability observations88
Open complete records

Threat Response Pipeline

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

Recorded events: 7. 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
    official-ledgre-eng-dev.pages.dev detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Blocklist Detection · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 5 of 5
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

3 entries
  1. Added to PhishDestroy

    official-ledgre-eng-dev.pages.dev

    View source
  2. URLScan

    Page captured

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

official-ledgre-eng-dev.pages.dev

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

3 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 official-ledgre-eng-dev.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/official-ledgre-eng-dev.pages.dev"
  title="PhishDestroy threat report for official-ledgre-eng-dev.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>