Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Public blocklists reporting a match: 3. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
qihong-ledger.pages.dev favicon

qihong-ledger.pages.dev

In short

qihong-ledger.pages.dev is a Ledger impersonation page detected by PhishDestroy on 2026-10-27. Risk: critical (75/100). Registrar: Cloudflare. Status: Last known active. Hosting: Cloudflare, Inc. Do not enter credentials or connect a wallet.

Review the evidence
Registrar
United StatesCloudflare
Resolved IP
Canada172.66.47.182Cloudflare, Inc. · CDN
First observed
Oct 27, 2026
PhishDestroy assessment Critical
75/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
Stored blocklist matches: 3 Automated brand label: Ledger Scam type: Impersonation
Blocklist matches
3
MetaMask, SEAL, PhishFeed
URLScan
Malicious
engine verdict · score 100
Page captures
3
open gallery
Oct 27, 2026 CDN
X Telegram API

Questions about qihong-ledger.pages.dev

Is qihong-ledger.pages.dev legit?

No. PhishDestroy classifies qihong-ledger.pages.dev as a Ledger impersonation page (risk: critical, 75/100); it was first detected on 2026-10-27. Treat the site as unsafe.

Is qihong-ledger.pages.dev safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on qihong-ledger.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 qihong-ledger.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

Source evidence 5 sources

URLScan

Malicious · engine verdict · score 100

SHA-256 0231f6ec2e8298b7d49b8dbfb021883409d72bae3b0eafb698cfd72d12b10a73

Open report
URLScanOriginal source recordObserved: 18 fields

Observed: · Retrieved:

Report ID

01a17e88-cc22-712d-8ab0-c84383b1e122

Final URL

https://qihong-ledger.pages.dev/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://qihong-ledger.pages.dev/
    From
    http://qihong-ledger.pages.dev/
    Status
    307

IP address

172.66.47.182

Contacted IP addresses

  • 172.66.47.182

Autonomous systems (ASN)

  • 13335

Document hash

0231f6ec2e8298b7d49b8dbfb021883409d72bae3b0eafb698cfd72d12b10a73

Browser storage keys

  • ledger_v2

TLS session and certificate

Subject alternative names
  • *.qihong-ledger.pages.dev
  • qihong-ledger.pages.dev
Cipher
AES_128_GCM
Issuer
YE1
Subject
qihong-ledger.pages.dev
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

0

Registered domain age, days

0

Certificate age, days

8

Certificate validity, days

89

Page requests

2

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
100
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP 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
Uuid
01a17e88-cc22-712d-8ab0-c84383b1e122
Final url
https://qihong-ledger.pages.dev/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://qihong-ledger.pages.dev/",
        "from": "http://qihong-ledger.pages.dev/",
        "status": 307
    }
]
Ip
172.66.47.182
Contacted IP addresses
[
    "172.66.47.182"
]
Asns
[
    "13335"
]
Document hash
0231f6ec2e8298b7d49b8dbfb021883409d72bae3b0eafb698cfd72d12b10a73
Storage keys
[
    "ledger_v2"
]
Tls
{
    "san": [
        "*.qihong-ledger.pages.dev",
        "qihong-ledger.pages.dev"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "qihong-ledger.pages.dev",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-17T15:48:36Z",
    "valid_from": "2026-10-19T15:48:37Z"
}
Domain age days
0
Apex age days
0
Tls age days
8
Tls valid days
89
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 100,
        "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"
}
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
01a17e88-cc22-712d-8ab0-c84383b1e122
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

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

75 / 100 · heuristic score · 0 brand references · 1 classification

Open report
Separate monitor score · 45 / 100 · 2026-10-27T19:20:14Z

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

record_source
domain_monitor.dom_analysis
heuristic_score
45
analyzed_at
2026-10-27T19:20:14Z
source_timestamp
2026-10-27 20:20:14
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
56
Malicious
0
Suspicious
0
Undetected
36

Reputation score

0

Categories

Sophos
information technology
Forcepoint ThreatSeeker
information technology

Registrar

CloudFlare, Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    blair.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    blair.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    172.66.47.182
  • TTL, seconds
    21600
    Type
    NS
    Value
    stan.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    172.66.44.74
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:310c::ac42:2fb6
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:310c::ac42:2c4a

DNS records observed

JARM fingerprint

27d40d40d00040d00042d43d00041df04c41293ba84f6efe3a613b22f983e6

Certificate

Subject alternative names
  • *.qihong-ledger.pages.dev
  • qihong-ledger.pages.dev
Issuer
Let's Encrypt / YE1
Serial
57473ac10ad82089f6526acf7c7477a2ed4
SHA-256
217a78d06f56f0cee5759e404e6fb8fc9aceafb84af1a8bd0c9a58ce4889d3f9
Subject
qihong-ledger.pages.dev
Valid until
Valid from

Registration record

Registrar
CloudFlare, Inc.
Registrar IANA ID
1910
Registrar URL
None
Registered
Updated
Expires
Status
  • clientDeleteProhibited
  • clientTransferProhibited
  • clientUpdateProhibited
  • clientdeleteprohibited
  • clienttransferprohibited
  • clientupdateprohibited
Nameservers
  • adi.ns.cloudflare.com
  • karl.ns.cloudflare.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 56,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 36
}
Reputation
0
Categories
{
    "Sophos": "information technology",
    "Forcepoint ThreatSeeker": "information technology"
}
Registrar
CloudFlare, Inc.
Created
2020-09-02T02:33:29Z
Expires
2026-09-02T02:33:29Z
Updated
2025-03-17T14:56:22Z
First seen
2026-10-19T17:16:22Z
DNS records
[
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "blair.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "blair.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.66.47.182"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "stan.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.66.44.74"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:310c::ac42:2fb6"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:310c::ac42:2c4a"
    }
]
Dns at
2026-10-19T17:16:22Z
Jarm
27d40d40d00040d00042d43d00041df04c41293ba84f6efe3a613b22f983e6
Certificate
{
    "san": [
        "*.qihong-ledger.pages.dev",
        "qihong-ledger.pages.dev"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "57473ac10ad82089f6526acf7c7477a2ed4",
    "sha256": "217a78d06f56f0cee5759e404e6fb8fc9aceafb84af1a8bd0c9a58ce4889d3f9",
    "subject": "qihong-ledger.pages.dev",
    "valid_to": "2027-01-17T15:48:36Z",
    "valid_from": "2026-10-19T15:48:37Z"
}
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"
}
Website checksOriginal source recordRetrieved: 21 fields

Mail configuration

SPF lookups
0

CAA records

Domain
qihong-ledger.pages.dev

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Page title and metadata

Page title
账本
Theme color
#F6F5F1

Trackers

Requests
3

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
7
TLS
182
Waiting
224
Connection
14
Download
18
Response time, ms
445

TLS connection

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

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
97478
CO₂, grams
0.0036
Cleaner than, %
22

DNS servers

Nameservers
  • IP address
    108.162.194.121
    Host
    blair.ns.cloudflare.com
  • IP address
    173.245.59.235
    Host
    stan.ns.cloudflare.com
DNS zone
qihong-ledger.pages.dev

Location

IP address
2606:4700:310c::ac42:2fb6
ASN
13335
Organization
Cloudflare, Inc.
City
Montreal
Country
CA

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
qihong-ledger.pages.dev

DNS records

A
  • 172.66.44.74
  • 172.66.47.182
NS
  • blair.ns.cloudflare.com
  • stan.ns.cloudflare.com
SOA
Primary nameserver
blair.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2417942562
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2606:4700:310c::ac42:2fb6
  • 2606:4700:310c::ac42:2c4a

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
strict-origin-when-cross-origin
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2606:4700:310c::ac42:2fb6
IP version
6

Redirects

Redirect chain
  • https://qihong-ledger.pages.dev

HTTP headers

Response 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": "qihong-ledger.pages.dev"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Page title and metadata
{
    "title": "账本",
    "themeColor": "#F6F5F1"
}
Trackers
{
    "requests": 3
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 7,
        "tls": 182,
        "wait": 224,
        "connect": 14,
        "download": 18
    },
    "response_ms": 445
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 97478,
    "co2_grams": 0.0036,
    "cleaner_than": 22
}
Dns server
{
    "ns": [
        {
            "ip": "108.162.194.121",
            "host": "blair.ns.cloudflare.com"
        },
        {
            "ip": "173.245.59.235",
            "host": "stan.ns.cloudflare.com"
        }
    ],
    "zone": "qihong-ledger.pages.dev"
}
Location
{
    "ip": "2606:4700:310c::ac42:2fb6",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "Montreal",
    "country": "CA"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "qihong-ledger.pages.dev"
}
DNS records
{
    "A": [
        "172.66.44.74",
        "172.66.47.182"
    ],
    "NS": [
        "blair.ns.cloudflare.com",
        "stan.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"blair.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2417942562, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2606:4700:310c::ac42:2fb6",
        "2606:4700:310c::ac42:2c4a"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": "strict-origin-when-cross-origin",
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2606:4700:310c::ac42:2fb6",
    "family": 6
}
Redirects
{
    "chain": [
        "https://qihong-ledger.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"
    }
}
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

Checked, no match

Last checked

Stored Capture · 3 captures

Primary capture 1 / 3
SourcePrimary capture
Recorded
StateStored capture
Position1 / 3
Open capture Wayback Download
All capture links and hashes (3)
qihong-ledger.pages.dev: Ledger impersonation — Blocked by MetaMask, flagged by SEAL. PhishDestroy risk score 75/100 (critical).
Social preview card qihong-ledger.pages.dev: Ledger impersonation — Blocked by MetaMask, flagged by SEAL. PhishDestroy risk score 75/100 (critical). v 640ada0647ae

Domain details

Domain
IP Context Canada172.66.47.182 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Cloudflare US(US)
Abuse contact["registrar-abuse@cloudflare.com", "256f9e523b2ede94s@"]
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 27, 2026
DOM Analysisanalyzed Oct 27, 2026score 75/100
Submitted URLhttp://qihong-ledger.pages.dev/
Favicon Hash
TLS Certificate
Issued by YE1 · stored validity ends in 81 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada172.66.47.182
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
CanadaMontreal, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • blair.ns.cloudflare.com
  • stan.ns.cloudflare.com

SOA

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

Location describes the IP network.

TLS certificate

Issuer
YE1
Valid from
2026-10-19 15:48:37
Valid until
2027-01-17 15:48:36
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint217a78d06f56f0cee5759e404e6fb8fc9aceafb84af1a8bd0c9a58ce4889d3f9
Certificate names · 2 SANs
  • *.qihong-ledger.pages.dev
  • qihong-ledger.pages.dev

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

viewdns.info · 172.66.47.182rapiddns.io
Report This Domain Submit evidence & help protect others
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. 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_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 19:05:10.000000
    Evidence SHA-256
    efb7594c813cd4aae4fd4773f4d422121f6e27398b8ed0b8fd0a096630a2559a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-27 19:05:10
    Evidence reason
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 19:05:10.000000
    Evidence SHA-256
    efb7594c813cd4aae4fd4773f4d422121f6e27398b8ed0b8fd0a096630a2559a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-27 19:05:10
    Evidence reason

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
    qihong-ledger.pages.dev detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Blocklist Detection · Brand Impersonation · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 6 of 6
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 100
  • Blocklist Detection
    Found in blocklists: MetaMask, SEAL, PhishFeed
  • Brand Impersonation
    Automated brand label: Ledger
  • 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

2 entries
  1. Added to PhishDestroy

    qihong-ledger.pages.dev

    View source
  2. URLScan

    Page captured

    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.

qihong-ledger.pages.dev

Evidence & External Reports

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

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts

Official reporting routes

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

Even if funds were frozen, they cannot be recovered without an official police report or court order. Submitting a complaint is the only path to potential recovery.

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.

  • 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 qihong-ledger.pages.dev)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?
  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?
  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?
  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

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

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

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

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.

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