Skip to security report
Domain security and threat intelligence
dev-ledgr-com-strt-temp-en.pages.dev favicon

dev-ledgr-com-strt-temp-en.pages.dev

In short

dev-ledgr-com-strt-temp-en.pages.dev is a blocklisted domain detected by PhishDestroy on 2026-10-22. Risk: high (66/100). Registrar: Cloudflare. Do not enter credentials or connect a wallet.

Registrar
Cloudflare
Resolved IP
172.66.47.142
PhishDestroy assessment High
First observed Oct 22, 2026 19:22 UTC · PhishDestroy
Stored blocklist matches: 2
Oct 22, 2026 CDN
API
This domain has been flagged as malicious
Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Page captures
open gallery
Source evidence 1 sources

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.

URLScan · 2026-10-22T19:21:24Z

Observed: · Retrieved:

Uuid
01a1650f-84e6-753d-a087-f007b70960d1
Final url
https://dev-ledgr-com-strt-temp-en.pages.dev/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://dev-ledgr-com-strt-temp-en.pages.dev/",
        "from": "http://dev-ledgr-com-strt-temp-en.pages.dev/",
        "status": 307
    }
]
Ip
172.66.44.114
Contacted domains
[
    "cdn.tailwindcss.com",
    "fonts.gstatic.com",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "142.251.20.94",
    "2a00:1450:4001:c13::5f",
    "2606:4700:20::ac43:440b",
    "172.66.44.114"
]
Asns
[
    "15169",
    "13335"
]
Countries
[
    "US",
    "DE"
]
Linked domains
[
    "www.ledger.com"
]
Document hash
80a7637e007eb9877e8f8f6b3e94c8a45f877927da6a8fd82b705bb190470f08
Globals
[
    "tailwind",
    "/template.html"
]
Tls
{
    "san": [
        "dev-ledgr-com-strt-temp-en.pages.dev",
        "*.dev-ledgr-com-strt-temp-en.pages.dev"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "dev-ledgr-com-strt-temp-en.pages.dev",
    "protocol": "QUIC",
    "valid_to": "2026-11-26T12:06:22Z",
    "valid_from": "2026-08-28T11:08:36Z"
}
Domain age days
350
Apex age days
350
Tls age days
55
Tls valid days
90
Requests
5
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8",
    "x-content-type-options": "nosniff",
    "referrer-policy": "strict-origin-when-cross-origin"
}
VirusTotal · 2026-10-22T20:01:50Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 56,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 36
}
Reputation
0
Tags
[
    "dga"
]
Registrar
CloudFlare, Inc.
Created
2020-09-02T02:33:29Z
Expires
2026-09-02T02:33:29Z
Updated
2025-03-17T14:56:22Z
First seen
2025-11-06T08:28:18Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:310c::ac42:2c72"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "kip.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "priscilla.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.66.44.114"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:310c::ac42:2f8e"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "kip.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.66.47.142"
    }
]
Dns at
2026-10-22T20:07:19Z
Jarm
27d40d40d00040d00042d43d00041df04c41293ba84f6efe3a613b22f983e6
Certificate
{
    "san": [
        "dev-ledgr-com-strt-temp-en.pages.dev",
        "*.dev-ledgr-com-strt-temp-en.pages.dev"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "2044529c229ac7ac1321f5586dc18525",
    "sha256": "4da67c058ce2c6ecdbba774f90486969204e1880b50c1f07f3dd4477a959b6e8",
    "subject": "dev-ledgr-com-strt-temp-en.pages.dev",
    "valid_to": "2026-11-26T12:06:22Z",
    "valid_from": "2026-08-28T11:08:36Z"
}
Registration record
{
    "registrar": "CloudFlare, Inc.",
    "registrar_iana_id": "1910",
    "registrar_url": "None",
    "created": "2020-09-02T02:33:29Z",
    "updated": "2023-09-04T18:15:07Z",
    "expires": "2026-09-02T02:33:29Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited",
        "clientdeleteprohibited",
        "clienttransferprohibited",
        "clientupdateprohibited"
    ],
    "nameservers": [
        "adi.ns.cloudflare.com",
        "karl.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}

Questions about dev-ledgr-com-strt-temp-en.pages.dev

Is dev-ledgr-com-strt-temp-en.pages.dev legit?

No. PhishDestroy classifies dev-ledgr-com-strt-temp-en.pages.dev as a blocklisted domain (risk: high, 66/100); it was first detected on 2026-10-22. Treat the site as unsafe.

Is dev-ledgr-com-strt-temp-en.pages.dev safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on dev-ledgr-com-strt-temp-en.pages.dev. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used dev-ledgr-com-strt-temp-en.pages.dev?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 4 captures

Domain details

Domain
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Cloudflare US(US)
Technical detailsProvenance & timestamps
First DetectedOct 22, 2026
Submitted URLhttp://dev-ledgr-com-strt-temp-en.pages.dev/
TLS Certificate
Issued by WE1 · stored validity ends in 34 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
172.66.47.142
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • kip.ns.cloudflare.com
  • priscilla.ns.cloudflare.com

TLS certificate

Issuer
WE1
Valid from
2026-08-28 11:08:36
Valid until
2026-11-26 12:06:22
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint4da67c058ce2c6ecdbba774f90486969204e1880b50c1f07f3dd4477a959b6e8
Certificate names · 2 SANs
  • dev-ledgr-com-strt-temp-en.pages.dev
  • *.dev-ledgr-com-strt-temp-en.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

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
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.

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. Availability monitor · First collection record

    Reachable

Recorded activity

2 entries
  1. Added to PhishDestroy

    dev-ledgr-com-strt-temp-en.pages.dev

    View source
  2. URLScan

    Page captured

    View source

Check for cloaking

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

dev-ledgr-com-strt-temp-en.pages.dev

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked 0 stored notification records Unverified

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 dev-ledgr-com-strt-temp-en.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

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.

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/dev-ledgr-com-strt-temp-en.pages.dev"
  title="PhishDestroy threat report for dev-ledgr-com-strt-temp-en.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>