Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 11. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
starten-ledgrcdn.created.app favicon

starten-ledgrcdn.created.app

In short

PhishDestroy records the Ledger-branded getting started page captured at starten-ledgrcdn.created.app, showing its main wallet connection interaction.

“Ledger.com/Start® | Getting Started™ | Ledger®”

Review the evidence
Registrar
Created App
Resolved IP
United States216.150.16.193Amazon.com, Inc. · CDN
Registered
Jul 12, 2023
First observed
Oct 31, 2026
PhishDestroy assessment Critical
93/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 11/92
VirusTotal
11 / 92
engine detections ·
URLScan
Malicious
Cloudflare Radar
Phishing
Page captures
4
open gallery
Domain age
1,207 days
registered 2023-07-12 according to RDAP · source data differ
Oct 31, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy records the Ledger-branded getting started page captured at starten-ledgrcdn.created.app, showing its main wallet connection interaction.

Critical
Status
Last known active
VirusTotal
11 / 92
Hosting
United States216.150.16.193Amazon.com, Inc. · CDN
Registrar
Created App
Registered
Jul 12, 2023
Page captures
4
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured page at starten-ledgrcdn.created.app presents itself as a Ledger getting started screen, with a headline inviting visitors to take control of their crypto in Ledger Live Web. The main interaction is a "Connect My Ledger" button paired with a "Mobile App" option, alongside a Coin Management section describing sending, receiving, and tracking coins through the app.

The stored VirusTotal domain result reports 11 detections out of 92 engines. ESET reported "phishing"; VIPRE reported "malware".

Source evidenceVirusTotal 11 / 92 7 sources

VirusTotal

11 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
49
Malicious
10
Suspicious
1
Undetected
32

Vendor labels

ESET
phishing
VIPRE
malware
Webroot
malicious
Emsisoft
phishing
Fortinet
phishing
Netcraft
malicious
SOCRadar
suspicious
Kaspersky
phishing
OpenPhish
phishing
Gridinsoft
phishing
alphaMountain.ai
phishing

Reputation score

0

Registrar

Tucows Domains Inc

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    1800
    Type
    A
    Value
    216.150.1.129
  • TTL, seconds
    1800
    Type
    A
    Value
    216.150.16.193

DNS records observed

JARM fingerprint

3fd3fd00000000000043d43d00043dc3b2afa8a5ec09b510a8559aff7899fb

Certificate

Subject alternative names
  • *.created.app
Issuer
Let's Encrypt / YR2
Serial
5c4e4f88b19405f32ab7ff1b385c0113629
SHA-256
939dcd2ea88a9fb0cdc440fbfa55064376759753b259b34a3242d277c46010eb
Subject
*.created.app
Valid until
Valid from

Registration record

Registrar
Tucows Domains Inc
Registrar IANA ID
69
Registrar URL
http://www.tucows.com
Registered
Updated
Expires
Status
  • ok
Nameservers
  • ns1.vercel-dns.com
  • ns2.vercel-dns.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 49,
    "malicious": 10,
    "suspicious": 1,
    "undetected": 32
}
Vendor labels
{
    "ESET": "phishing",
    "VIPRE": "malware",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "SOCRadar": "suspicious",
    "Kaspersky": "phishing",
    "OpenPhish": "phishing",
    "Gridinsoft": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Registrar
Tucows Domains Inc
Created
2023-07-12T00:44:20Z
Expires
2025-07-12T00:44:20Z
Updated
2025-02-27T20:01:15Z
First seen
2026-10-27T18:23:06Z
DNS records
[
    {
        "ttl": 1800,
        "type": "A",
        "value": "216.150.1.129"
    },
    {
        "ttl": 1800,
        "type": "A",
        "value": "216.150.16.193"
    }
]
Dns at
2026-10-29T16:32:23Z
Jarm
3fd3fd00000000000043d43d00043dc3b2afa8a5ec09b510a8559aff7899fb
Certificate
{
    "san": [
        "*.created.app"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "5c4e4f88b19405f32ab7ff1b385c0113629",
    "sha256": "939dcd2ea88a9fb0cdc440fbfa55064376759753b259b34a3242d277c46010eb",
    "subject": "*.created.app",
    "valid_to": "2026-12-03T08:43:42Z",
    "valid_from": "2026-09-04T08:43:43Z"
}
Registration record
{
    "registrar": "Tucows Domains Inc",
    "registrar_iana_id": "69",
    "registrar_url": "http://www.tucows.com",
    "created": "2023-07-12T00:44:20Z",
    "updated": "2025-02-27T20:01:15Z",
    "expires": "2025-07-12T00:44:20Z",
    "status": [
        "ok"
    ],
    "nameservers": [
        "ns1.vercel-dns.com",
        "ns2.vercel-dns.com"
    ],
    "dnssec": "unsigned"
}
Separate source record · 10 malicious + 1 suspicious / 92 · 2026-10-29 16:31:24 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-29T16:31:24Z
fetched_at
2026-10-31T18:11:52Z
stats
{"timeout":0,"harmless":49,"malicious":10,"suspicious":1,"undetected":32}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Report ID

8e87124f-b269-4495-aa05-cc003723dc40

Final URL

https://starten-ledgrcdn.created.app/

HTTP response

200

Navigation history

  • URL
    https://starten-ledgrcdn.created.app/
    Status
    200

DOM structure hash

b236c17f5b9a361768d55231169b7b7865803768ebc79307df1b822df2a58981

Document hash

58238c48feb0e2e4e817e3f0903fee45f6860140466becefe2a59b4b114dcef7

Phishing classifier result

  • phishing

URL risk categories

  • Phishing

Domain risk categories

  • Phishing
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    starten-ledgrcdn.created.app
    Type
    A
    Value
    216.150.16.65
  • Name
    starten-ledgrcdn.created.app
    Type
    A
    Value
    216.150.16.129

DNSSEC valid

No

IP address

127.0.1.11

127.0.1.11 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
Name.com, Inc.
Registered
Updated
Expires
Nameservers
  • ns1.vercel-dns.com
  • ns2.vercel-dns.com
Original source fields · JSON
Uuid
8e87124f-b269-4495-aa05-cc003723dc40
Final url
https://starten-ledgrcdn.created.app/
Status
200
History
[
    {
        "url": "https://starten-ledgrcdn.created.app/",
        "status": 200
    }
]
DOM structure hash
b236c17f5b9a361768d55231169b7b7865803768ebc79307df1b822df2a58981
Document hash
58238c48feb0e2e4e817e3f0903fee45f6860140466becefe2a59b4b114dcef7
Phishing v2
[
    "phishing"
]
Url risks
[
    "Phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "starten-ledgrcdn.created.app",
        "type": "A",
        "value": "216.150.16.65"
    },
    {
        "name": "starten-ledgrcdn.created.app",
        "type": "A",
        "value": "216.150.16.129"
    }
]
Dnssec valid
false
Ip
127.0.1.11

127.0.1.11 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "Name.com, Inc.",
    "created": "2023-07-12T00:44:20Z",
    "updated": "2026-06-17T01:45:57Z",
    "expires": "2027-07-12T00:44:20Z",
    "nameservers": [
        "ns1.vercel-dns.com",
        "ns2.vercel-dns.com"
    ]
}
Separate stored summary: Not recorded · observation date not recorded

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

verdict
null
categories
[]
observed_at
null
source_path
phishdestroy.technologies.cf_radar
scope
Separate stored summary; an absent observation date is not evidence of a clean scan.

URLScan

Malicious

SHA-256 58238c48feb0e2e4e817e3f0903fee45f6860140466becefe2a59b4b114dcef7

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a1932f-f91c-7438-921a-12573648b192

Final URL

https://starten-ledgrcdn.created.app/

HTTP response

200

IP address

216.150.16.129

Contacted domains

  • i.ibb.co

Contacted IP addresses

  • 45.43.142.4
  • 216.150.16.129

Autonomous systems (ASN)

  • 16276
  • 16509

Server countries

  • GB
  • US

Linked domains

  • zps-1jdsyu.myshopify.com

Document hash

58238c48feb0e2e4e817e3f0903fee45f6860140466becefe2a59b4b114dcef7

Script hashes

  • e72b6b6fe5d9397739f7dbcd7a1fbb7914713a0228943452a814f542a25fde34
  • 8dc2c1d71557b434c654ec58acb1441bc0fb200c520ff548f606d88e689ee643
  • 58e4b11523cc8020cc2cf862b60d9e0a4e8fd2a567a5d623e0cf58f505ca7892
  • 8dd2534f5966e70fd545134c8bcff52ecf8d19086e3bac41924cbb9794e505cb
  • 50e5b9137b7e2d9f84476dd51a74f51290e663834d6b2ff026516200b6e46cd8
  • 7c06449c1312d9468ec41266d638b361c8aca42e8afcda48079ebc0d14da3caa
  • 4db147d306255b23ad70710b7a04c3c2163d61ab779c2a392447e2db3c703144
  • 8976b38e585d08213047b0ddb23de3855a318ec4ebe49a5c955120b95d8d1e6b

JavaScript globals

  • webpackChunk_N_E
  • __next_f
  • next
  • _N_E_STYLE_LOAD

Cookies

  • __Host-authjs.csrf-token
  • __Secure-authjs.callback-url

TLS session and certificate

Subject alternative names
  • *.created.app
  • created.app
Cipher
AES_128_GCM
Issuer
YR1
Subject
*.created.app
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

3

Differs from the registration date in RDAP (2023-07-12), which gives 1207 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Registered domain age, days

1207

Certificate age, days

1

Certificate validity, days

89

Page requests

14

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
84
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • ledger
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Ledger
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
Vercel
Content-type
text/html; charset=utf-8
X-powered-by
Next.js
Strict-transport-security
max-age=63072000
Original source fields · JSON
Uuid
01a1932f-f91c-7438-921a-12573648b192
Final url
https://starten-ledgrcdn.created.app/
Status
200
Ip
216.150.16.129
Contacted domains
[
    "i.ibb.co"
]
Contacted IP addresses
[
    "45.43.142.4",
    "216.150.16.129"
]
Asns
[
    "16276",
    "16509"
]
Countries
[
    "GB",
    "US"
]
Linked domains
[
    "zps-1jdsyu.myshopify.com"
]
Document hash
58238c48feb0e2e4e817e3f0903fee45f6860140466becefe2a59b4b114dcef7
Script hashes
[
    "e72b6b6fe5d9397739f7dbcd7a1fbb7914713a0228943452a814f542a25fde34",
    "8dc2c1d71557b434c654ec58acb1441bc0fb200c520ff548f606d88e689ee643",
    "58e4b11523cc8020cc2cf862b60d9e0a4e8fd2a567a5d623e0cf58f505ca7892",
    "8dd2534f5966e70fd545134c8bcff52ecf8d19086e3bac41924cbb9794e505cb",
    "50e5b9137b7e2d9f84476dd51a74f51290e663834d6b2ff026516200b6e46cd8",
    "7c06449c1312d9468ec41266d638b361c8aca42e8afcda48079ebc0d14da3caa",
    "4db147d306255b23ad70710b7a04c3c2163d61ab779c2a392447e2db3c703144",
    "8976b38e585d08213047b0ddb23de3855a318ec4ebe49a5c955120b95d8d1e6b"
]
Globals
[
    "webpackChunk_N_E",
    "__next_f",
    "next",
    "_N_E_STYLE_LOAD"
]
Cookies
[
    "__Host-authjs.csrf-token",
    "__Secure-authjs.callback-url"
]
Tls
{
    "san": [
        "*.created.app",
        "created.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YR1",
    "subject": "*.created.app",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-28T00:15:39Z",
    "valid_from": "2026-10-30T00:15:40Z"
}
Domain age days
3

Differs from the registration date in RDAP (2023-07-12), which gives 1207 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Apex age days
1207
Tls age days
1
Tls valid days
89
Requests
14
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 84,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "ledger"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Ledger"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "Vercel",
    "content-type": "text/html; charset=utf-8",
    "x-powered-by": "Next.js",
    "strict-transport-security": "max-age=63072000"
}
Separate monitor record · date not recorded

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

record_source
domain_monitor.urlscan
uuid
01a18f65-8b85-74aa-b728-4cf26e09bde1
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

10 / 100 · heuristic score · 1 brand reference · 0 classifications

Open report

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
starten-ledgrcdn.created.app Ledger Live Web Getting Started Page
ai_description
PhishDestroy records the Ledger-branded getting started page captured at starten-ledgrcdn.created.app, showing its main wallet connection interaction.
ai_summary
The captured page at starten-ledgrcdn.created.app presents itself as a Ledger getting started screen, with a headline inviting visitors to take control of their crypto in Ledger Live Web. The main interaction is a "Connect My Ledger" button paired with a "Mobile App" option, alongside a Coin Management section describing sending, receiving, and tracking coins through the app. The stored VirusTotal domain result reports 11 detections out of 92 engines. ESET reported "phishing"; VIPRE reported "malware".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-31 19:13:07
revision
8c57a744d9b1c80e11b01637589f7c04c794d33c19c1e3e068c80d2873c7102f
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: 22 fields

CAA records

Count
3
Domain
created.app
Allowed issuers
  • letsencrypt.org
  • pki.goog
  • sectigo.com

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
3630

Page title and metadata

Open Graph URL
https://walletguard-guide.com
Page title
Ledger.com/Start® | Getting Started™ | Ledger®
Open Graph type
website
Open Graph title
Ledger.com/Start® | Getting Started™ | Ledger®
Keywords
ledger.com/start, ledger wallet setup, ledger getting started, ledger nano x setup, ledger nano s plus, ledger live download, hardware wallet guide, crypto cold storage, ledger recovery phrase
Description
Ledger.com/Start — Official getting started guide for Ledger hardware wallets. Set up your Ledger Nano X, Nano S Plus, or Ledger Stax, secure your 24-word recovery phrase, and manage 5,500+ crypto assets with Ledger Live.
Twitter card
summary
Open Graph description
Official getting started guide for Ledger hardware wallets. Set up your device, secure your phrase, and manage crypto safely.

Trackers

Requests
13

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
80
TLS
32
Waiting
417
Connection
61
Download
0
Response time, ms
590

TLS connection

ALPN
h2
Cipher
TLS_AES_128_GCM_SHA256
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
8267
CO₂, grams
0.0003
Cleaner than, %
76

DNS servers

Nameservers
  • IP address
    198.51.45.13
    Host
    ns2.vercel-dns.com
  • IP address
    198.51.44.13
    Host
    ns1.vercel-dns.com
DNS zone
created.app

Cookies

Cookies
  • Name
    __Host-authjs.csrf-token
    Secure
    Yes
    Session cookie
    Yes
    HTTP-only
    Yes
    SameSite
    Lax
  • Name
    __Secure-authjs.callback-url
    Secure
    Yes
    Session cookie
    Yes
    HTTP-only
    Yes
    SameSite
    Lax

Location

IP address
216.150.16.129
ASN
16509
Organization
Amazon.com, Inc.
City
Walnut
Country
US

TLS certificate

Issuer
Let's Encrypt / YR1
Subject
*.created.app

DNS records

A
  • 216.150.16.129
  • 216.150.16.193

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=63072000
Observation
HSTS header does not include all subdomains.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
max-age=63072000
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
216.150.16.193
IP version
4

Redirects

Redirect chain
  • https://starten-ledgrcdn.created.app

Page links

External link addresses
  • https://zps-1jdsyu.myshopify.com/
External links
1

HTTP headers

Response headers
Server
Vercel
Content-type
text/html; charset=utf-8
X-powered-by
Next.js
Strict-transport-security
max-age=63072000
Original source fields · JSON
Caa records
{
    "count": 3,
    "domain": "created.app",
    "issuers": [
        "letsencrypt.org",
        "pki.goog",
        "sectigo.com"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-31T18:12:06Z",
    "first": "2026-10-31T18:12:06Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 3630
}
Page title and metadata
{
    "ogUrl": "https://walletguard-guide.com",
    "title": "Ledger.com/Start® | Getting Started™ | Ledger®",
    "ogType": "website",
    "ogTitle": "Ledger.com/Start® | Getting Started™ | Ledger®",
    "keywords": "ledger.com/start, ledger wallet setup, ledger getting started, ledger nano x setup, ledger nano s plus, ledger live download, hardware wallet guide, crypto cold storage, ledger recovery phrase",
    "description": "Ledger.com/Start — Official getting started guide for Ledger hardware wallets. Set up your Ledger Nano X, Nano S Plus, or Ledger Stax, secure your 24-word recovery phrase, and manage 5,500+ crypto assets with Ledger Live.",
    "twitterCard": "summary",
    "ogDescription": "Official getting started guide for Ledger hardware wallets. Set up your device, secure your phrase, and manage crypto safely."
}
Trackers
{
    "requests": 13
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 80,
        "tls": 32,
        "wait": 417,
        "connect": 61,
        "download": 0
    },
    "response_ms": 590
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 8267,
    "co2_grams": 0.0003,
    "cleaner_than": 76
}
Dns server
{
    "ns": [
        {
            "ip": "198.51.45.13",
            "host": "ns2.vercel-dns.com"
        },
        {
            "ip": "198.51.44.13",
            "host": "ns1.vercel-dns.com"
        }
    ],
    "zone": "created.app"
}
Cookies
{
    "cookies": [
        {
            "name": "__Host-authjs.csrf-token",
            "secure": true,
            "session": true,
            "http_only": true,
            "same_site": "Lax"
        },
        {
            "name": "__Secure-authjs.callback-url",
            "secure": true,
            "session": true,
            "http_only": true,
            "same_site": "Lax"
        }
    ]
}
Location
{
    "ip": "216.150.16.129",
    "asn": "16509",
    "org": "Amazon.com, Inc.",
    "city": "Walnut",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YR1",
    "subject": "*.created.app"
}
DNS records
{
    "A": [
        "216.150.16.129",
        "216.150.16.193"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=63072000",
    "message": "HSTS header does not include all subdomains."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=63072000",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "216.150.16.193",
    "family": 4
}
Redirects
{
    "chain": [
        "https://starten-ledgrcdn.created.app"
    ]
}
Page links
{
    "external": [
        "https://zps-1jdsyu.myshopify.com/"
    ],
    "external_count": 1
}
HTTP headers
{
    "headers": {
        "server": "Vercel",
        "content-type": "text/html; charset=utf-8",
        "x-powered-by": "Next.js",
        "strict-transport-security": "max-age=63072000"
    }
}

Questions about starten-ledgrcdn.created.app

Is starten-ledgrcdn.created.app legit?

PhishDestroy records the Ledger-branded getting started page captured at starten-ledgrcdn.created.app, showing its main wallet connection interaction.

Is starten-ledgrcdn.created.app safe to connect a wallet?

This report does not record which wallet requests starten-ledgrcdn.created.app 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 starten-ledgrcdn.created.app?

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 matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 4 captures

Cloudflare Radar 1 / 4 Used in the analysis Source file SHA-256: fa922f8f8c21395491f4262d6fa1f866da514355d3aa486329d6c9d1f9e24ef6 SHA-256 of the prepared copy given to the model: caf6357b380162bbe2b0cf586660cc680c6723187cd9faefabcbd71a957bbc12
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://starten-ledgrcdn.created.app/
Position1 / 4
Open capture Source Report Wayback Download
All capture links and hashes (4)
Observed page title
Ledger.com/Start® | Getting Started™ | Ledger®
Automated brand references
Ledger
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 32 days

Domain details

Domain
IP Context United States216.150.16.193 Vercel shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Created App
Abuse contactabuse@vercel.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for created.app →
Hosting abuse contact abuse@vercel.com Amazon.com, Inc. · AS16509
Registration (base domain)created.app · Created Jul 12, 2023
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 31, 2026
DOM Analysisanalyzed Oct 31, 2026score 10/1001 brand signal
Submitted URLhttps://starten-ledgrcdn.created.app/
ICANN OVERSIGHT Registration: created.app

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For the registrable domain created.app behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States216.150.16.193
Network ASN
AS16509
Organization
Amazon.com, Inc.
Observed location
United StatesWalnut, US
Server header
Vercel

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-09-04 08:43:43
Valid until
2026-12-03 08:43:42
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint939dcd2ea88a9fb0cdc440fbfa55064376759753b259b34a3242d277c46010eb
Certificate names · 1 SAN
  • *.created.app

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

viewdns.info · 216.150.16.193rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

11 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
ESET
Emsisoft
Fortinet
Gridinsoft
Kaspersky
Netcraft
OpenPhish
SOCRadar
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: https://starten-ledgrcdn.created.app/
Ledger.com/Start® | Getting Started™ | Ledger®
Ledger.com/Start — Official getting started guide for Ledger hardware wallets. Set up your Ledger Nano X, Nano S Plus, or Ledger Stax, secure your 24-word recovery phrase, and manage 5,500+ crypto assets with Ledger Live.
Response
HTTP 200
HTML body
8.1 KB
Compressed
2.3 KB
Links
0 internal · 1 external
Detected technologies
react
Selected response headers
Cache-Control: s-maxage=31536000
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
Server: Vercel
X-Powered-By: Next.js
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Open Graph title: Ledger.com/Start® | Getting Started™ | Ledger®
Open Graph description: Official getting started guide for Ledger hardware wallets. Set up your device, secure your phrase, and manage crypto safely.
Twitter card: summary
Saved response-header values · 19
Cache-Control
s-maxage=31536000
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Sat, 31 Oct 2026 18:11:04 GMT
Etag
W/"12kgeaqzh3v6cv"
Server
Vercel
Strict-Transport-Security
max-age=63072000
Transfer-Encoding
chunked
Vary
rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch
X-Amzn-Remapped-Content-Length
8267
X-Amzn-Requestid
44aabe3b-4ff6-4cc3-a149-eb5b4660e66c
X-Amzn-Trace-Id
Root=1-6ae62f38-622d13a2627af7bc1d797c91;Parent=4ae8be992f3d34cf;Sampled=0;Lineage=1:d2127c63:0
X-Nextjs-Cache
HIT
X-Nextjs-Prerender
1,1
X-Nextjs-Stale-Time
300
X-Opennext
1
X-Powered-By
Next.js
X-Vercel-Cache
MISS
X-Vercel-Id
fra1::tppdq-1793470264110-c3bb1929a6c5

Values retained by the collector; long values may be shortened during collection.

Archived

Captured network requests

Network requests: 14 SHA-256 hashes: 14 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-31 18:22 UTC.

Open this scan on URLScan 01a1932f-f91c-7438-921a-12573648b192 ↗

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 observations1

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_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 19:11:57.439303
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

Recorded events: 10. 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
    starten-ledgrcdn.created.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Automated brand label: Ledger · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 8 of 8
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan classified the page as malicious · Score: 100
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 11/92
  • Automated brand label: Ledger
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
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

5 entries
  1. URLScan

    Page captured

    View source
  2. Wayback Machine

    Page archived

    View source
  3. Cloudflare Radar

    Phishing

    View source
  4. Added to PhishDestroy

    starten-ledgrcdn.created.app

    View source
  5. VirusTotal

    11/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.

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

Lookalike domains

151 stored lookalike domains

ledfger.com insertion Internal report A 185.244.151.84MX ledfger.comNS ns3.ro.hostsailor.com ledgfer.com insertion Internal report A 185.244.151.84MX ledgfer.comNS ns3.ro.hostsailor.com ledgher.com insertion Internal report A 185.244.151.84MX ledgher.comNS ns3.ro.hostsailor.com ledgrr.com replacement Internal report A 185.244.151.84MX ledgrr.comNS ns3.ro.hostsailor.com lefdger.com insertion Internal report A 185.244.151.84MX lefdger.comNS ns3.ro.hostsailor.com lesdger.com insertion Internal report A 185.244.151.84MX lesdger.comNS ns3.ro.hostsailor.com lkedger.com insertion Internal report A 185.244.151.84MX lkedger.comNS ns3.ro.hostsailor.com lredger.com insertion Internal report A 185.244.151.84MX lredger.comNS ns3.ro.hostsailor.com lwedger.com insertion Internal report A 185.244.151.84MX lwedger.comNS ns3.ro.hostsailor.com xn--ledgr-9za.com homoglyph Internal report NS ns-cloud-d1.googledomains.com ledgerk.com addition Internal report A 156.250.67.229NS ns1.bdydns.cn edger.com omission A 54.215.31.113NS ns1.dyna-ns.net
Show all (88)
eldger.com transposition A 185.244.151.84MX eldger.comNS ns3.ro.hostsailor.com kedger.com replacement A 13.56.33.8NS ns1.brandbucket.com kledger.com insertion A 20.65.18.151NS ns-1490.awsdns-58.org l3dger.com replacement A 216.198.79.1MX inbound-smtp.eu-west-1.amazonaws.comNS ns1.bluehost.com ldeger.com transposition A 185.244.151.84MX ldeger.comNS ns3.ro.hostsailor.com ldger.com omission A 13.248.169.48NS ns1.dan.com le.dger.com subdomain A 13.248.169.48NS ns5.afternic.com lecger.com replacement A 14.63.215.245NS ns1.hostname.net ledber.com replacement A 104.21.35.54NS chin.ns.cloudflare.com ledegr.com transposition A 185.244.151.84MX ledegr.comNS ns3.ro.hostsailor.com leder.com omission A 85.13.132.113MX w01a4668.kasserver.comNS ns5.kasserver.com ledg3r.com replacement NS ns1.dreamhost.com ledge.com omission A 54.215.31.113NS ns1.dyna-ns.net ledged.com replacement A 52.20.84.62NS ns1.atom.com ledgedr.com insertion A 31.43.160.6NS ns6.wixdns.net ledgee.com replacement A 13.248.169.48NS ns3.afternic.com ledgeer.com repetition A 52.20.84.62NS ns1.squadhelp.com ledgercom.com various A 91.215.86.207NS ns3.epik.com ledget.com replacement A 13.248.169.48NS ns1.afternic.com ledgewr.com insertion A 185.244.151.84MX ledgewr.comNS ns3.ro.hostsailor.com ledgger.com repetition A 13.56.33.8NS ns1.brandbucket.com ledgir.com vowel-swap A 188.114.96.3NS lynn.ns.cloudflare.com ledgor.com vowel-swap A 103.230.136.195MX mxn.mxhichina.comNS ens11.bigwww.com ledgr.com omission A 188.114.96.3NS kim.ns.cloudflare.com ledgre.com transposition A 172.65.185.109NS sp1.gname-dns.com ledgrer.com insertion A 185.244.151.84MX ledgrer.comNS ns3.ro.hostsailor.com ledgsr.com replacement A 14.63.215.245NS ns1.hostname.net ledgwer.com insertion A 185.244.151.84MX ledgwer.comNS ns3.ro.hostsailor.com ledgwr.com replacement A 185.244.151.84MX ledgwr.comNS ns3.ro.hostsailor.com ledher.com replacement A 15.197.148.33MX mailstore1.secureserver.netNS ns03.domaincontrol.com ledhger.com insertion A 185.244.151.84MX ledhger.comNS ns3.ro.hostsailor.com ledsger.com insertion A 185.244.151.84MX ledsger.comNS ns3.ro.hostsailor.com ledtger.com insertion A 188.114.96.3NS janet.ns.cloudflare.com ledyer.com replacement A 31.43.160.6MX alt1.aspmx.l.google.comNS ns-1051.awsdns-03.org ledzer.com replacement A 188.114.96.3NS kimora.ns.cloudflare.com leedger.com insertion MX mxbiz1.qq.comNS dns10.hichina.com legder.com transposition A 64.190.63.222MX localhostNS ns1.sedoparking.com leger.com omission A 216.40.34.37MX mx.netidentity.com.cust.hostedemail.comNS ns1.mailbank.com lerdger.com insertion A 185.244.151.84MX lerdger.comNS ns3.ro.hostsailor.com lerger.com replacement A 13.248.169.48NS ns1.afternic.com lesger.com replacement A 185.244.151.84MX lesger.comNS ns3.ro.hostsailor.com lewdger.com insertion A 185.244.151.84MX lewdger.comNS ns3.ro.hostsailor.com lidger.com vowel-swap A 66.241.124.184MX route1.mx.cloudflare.netNS erin.ns.cloudflare.com lledger.com repetition A 50.254.19.65MX lledger-com.mail.protection.outlook.comNS ns-1532.awsdns-63.org lodger.com vowel-swap A 149.210.148.65MX mail.lodger.comNS aron.ns.cloudflare.com lrdger.com replacement A 77.247.179.85MX mail.h-email.netNS ns1.badgerdns.com lsdger.com replacement A 14.63.215.245NS ns1.hostname.net oedger.com replacement A 14.63.215.245NS ns1.hostname.net pedger.com replacement A 74.220.199.6 pledger.com insertion A 216.40.34.37MX mx.netidentity.com.cust.hostedemail.comNS ns1.mailbank.com dedger.com bitsquatting MX aspmx1.migadu.comNS apollo.ns.cloudflare.com hedger.com bitsquatting A 15.197.225.128MX alt1.aspmx.l.google.comNS ns23.domaincontrol.com iedger.com homoglyph A 217.70.184.38MX fb.mail.gandi.netNS ns-157-c.gandi.net l-edger.com hyphenation A 216.198.79.65NS ns1.vercel-dns.com ladger.com bitsquatting A 185.80.2.134MX ladger.comNS ns209.superhosting.bg lcdlger.com homoglyph NS ns2.my-ndns.com lddger.com bitsquatting A 14.63.215.245NS ns1.hostname.net lebger.com homoglyph A 104.247.81.99NS ns1.parkingcrew.net leclger.com homoglyph A 34.42.100.71NS ns-cloud-e1.googledomains.com ledcer.com bitsquatting A 15.197.148.33MX ledcer-com.mail.protection.outlook.comNS pdns11.domaincontrol.com leddger.com insertion A 13.248.169.48NS ns1.afternic.com ledeer.com bitsquatting A 13.248.169.48NS ns1.dan.com ledeger.com insertion A 103.224.182.253MX park-mx.above.comNS ns1.abovedomains.com ledfer.com bitsquatting A 15.197.142.173MX mailstore1.secureserver.netNS ns11.domaincontrol.com ledg-er.com hyphenation A 162.255.119.245MX mail.protonmail.chNS dns1.registrar-servers.com ledgar.com bitsquatting A 13.248.169.48NS ns1.namefind.com ledger0.com addition A 20.82.12.44MX ledger0-com.mail.protection.outlook.comNS ns1-04.azure-dns.com ledger1.com addition A 44.232.173.249NS launch1.spaceship.net ledger4.com addition A 52.201.53.166NS nsg1.namebrightdns.com ledger5.com addition MX mail.protonmail.chNS ns-1175.awsdns-18.org ledger6.com addition A 52.20.84.62NS ns1.atom.com ledgerb.com addition A 91.195.240.82NS ns1dhl.name.com ledgerc.com addition A 198.185.159.144MX alt1.aspmx.l.google.comNS dns1.p02.nsone.net ledgerf.com addition A 94.75.193.73MX mail.h-email.netNS ns1.thednscloud.com ledgeri.com addition A 52.20.84.62NS ns1.atom.com ledgern.com addition A 192.0.78.162MX ledgern-com.mail.protection.outlook.comNS ns1.wordpress.com ledgerq.com addition A 31.43.160.6MX ledgerq-com.mail.protection.outlook.comNS ns03.domaincontrol.com ledgerx.com addition A 198.202.211.1MX usb-smtp-inbound-1.mimecast.comNS alla.ns.cloudflare.com ledges.com bitsquatting A 170.249.218.186MX ledges-com.mail.protection.outlook.comNS ns47.domaincontrol.com ledgez.com bitsquatting A 67.23.254.40MX ledgez.comNS ns1.reseller-228.mco2.hostdime.com ledgur.com bitsquatting A 13.248.243.5MX ledgur-com.mail.protection.outlook.comNS ns23.domaincontrol.com lediger.com homoglyph A 185.225.135.100MX mail02.lediger-consulting.deNS ns1.routing.net ledqer.com homoglyph A 13.223.25.84NS nsg1.namebrightdns.com leeger.com bitsquatting A 194.191.24.29MX alt1.aspmx.l.google.comNS cns1.cloudpit.de leelger.com homoglyph A 15.197.148.33NS ns69.domaincontrol.com lefger.com bitsquatting A 103.224.182.244MX park-mx.above.comNS ns1.abovedomains.com letger.com bitsquatting A 156.245.108.206NS ns1.dnsowl.com ludger.com bitsquatting A 18.195.62.85MX ludger-com.mail.protection.outlook.comNS ns11.worldnic.com

Showing 100 of 151

Check for cloaking

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

starten-ledgrcdn.created.app

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 11 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid 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

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.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
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.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

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 starten-ledgrcdn.created.app)
  • 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

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.

Request a correction or appeal How PhishDestroy works
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/starten-ledgrcdn.created.app"
  title="PhishDestroy threat report for starten-ledgrcdn.created.app"
  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>