Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 3/92 engines flagged. malicious: 1. suspicious: 2. Analysis time (as stored): 2026-10-29T13:22:46Z. Retrieved (as stored): 2026-10-29T14:31:45Z. Listed by external blocklists: MetaMask, SEAL. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
seller-ledger.ru favicon

seller-ledger.ru

In short

PhishDestroy first recorded seller-ledger.ru on 2026-10-29. Stored VirusTotal result: 3/92 engines flagged. malicious: 1. suspicious: 2. Analysis time (as stored): 2026-10-29T13:22:46Z. Retrieved (as stored): 2026-10-29T14:31:45Z. Listed by external blocklists: MetaMask, SEAL.

“Прибыль по товарам Wildberries и Ozon и сверка выплат — SellerFinance”

Review the evidence
Registrar
RussiaREGRU-RU
Resolved IP
Russia168.113.174.162Andrei Zaitsev
Registered
Oct 25, 2026
First observed
Oct 29, 2026
PhishDestroy assessment Critical
93/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 3/92 Stored blocklist matches: 2 Young domain: 7 days old
VirusTotal
3 / 92
engine detections ·
Blocklist matches
2
MetaMask, SEAL
OTX
2
community references
URLScan
Malicious
engine verdict · score 98
Page captures
3
open gallery
Domain age
7 days
registered 2026-10-25 according to WHOIS
OTX: 2 refs Oct 29, 2026
X Telegram API

Questions about seller-ledger.ru

Is seller-ledger.ru legit?

PhishDestroy rates seller-ledger.ru as critical risk (93/100) from the recorded evidence; it was first recorded on 2026-10-29. Stored VirusTotal result: 3/92 engines flagged. malicious: 1. suspicious: 2. Analysis time (as stored): 2026-10-29T13:22:46Z. Retrieved (as stored): 2026-10-29T14:31:45Z. Listed by external blocklists: MetaMask, SEAL. Treat the site as unsafe.

Is seller-ledger.ru safe to connect a wallet?

This report does not record which wallet requests seller-ledger.ru 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 seller-ledger.ru?

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

Source evidenceVirusTotal 3 / 92 · OTX 2 references 7 sources

VirusTotal

3 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
54
Malicious
1
Suspicious
2
Undetected
35

Vendor labels

CRDF
malicious
Gridinsoft
suspicious
alphaMountain.ai
suspicious

Reputation score

0

Registrar

REGRU-RU

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    ns1.reg.ru
  • TTL, seconds
    21600
    Type
    SOA
    Responsible mailbox
    hostmaster.ns1.reg.ru
    Value
    ns1.reg.ru
  • TTL, seconds
    21600
    Type
    A
    Value
    168.113.174.162
  • TTL, seconds
    21600
    Type
    TXT
    Value
    google-site-verification=-AG0Z3z-gkmoV0hR72Ovyd9pixEy-YI74WGWvoX00UY
  • TTL, seconds
    21600
    Type
    TXT
    Value
    yandex-verification: de96b6486bd2e988
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns2.reg.ru

DNS records observed

JARM fingerprint

28d28d28d00028d00042d42d000000831b6af40378e2dd35eeac4e9311926e

Certificate

Subject alternative names
  • seller-ledger.ru
  • www.seller-ledger.ru
Issuer
Let's Encrypt / YE1
Serial
53ffe03ae896d0c43107b218da2749385ec
SHA-256
e83acf2b7c6c23d377d860f011d11c85e638614143a16779a81d1b5489880582
Subject
seller-ledger.ru
Valid until
Valid from

Registration record

Registrar
REGRU-RU
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 54,
    "malicious": 1,
    "suspicious": 2,
    "undetected": 35
}
Vendor labels
{
    "CRDF": "malicious",
    "Gridinsoft": "suspicious",
    "alphaMountain.ai": "suspicious"
}
Reputation
0
Registrar
REGRU-RU
First seen
2026-10-25T14:22:12Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns1.reg.ru"
    },
    {
        "ttl": 21600,
        "type": "SOA",
        "rname": "hostmaster.ns1.reg.ru",
        "value": "ns1.reg.ru"
    },
    {
        "ttl": 21600,
        "type": "A",
        "value": "168.113.174.162"
    },
    {
        "ttl": 21600,
        "type": "TXT",
        "value": "google-site-verification=-AG0Z3z-gkmoV0hR72Ovyd9pixEy-YI74WGWvoX00UY"
    },
    {
        "ttl": 21600,
        "type": "TXT",
        "value": "yandex-verification: de96b6486bd2e988"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns2.reg.ru"
    }
]
Dns at
2026-10-29T13:26:29Z
Jarm
28d28d28d00028d00042d42d000000831b6af40378e2dd35eeac4e9311926e
Certificate
{
    "san": [
        "seller-ledger.ru",
        "www.seller-ledger.ru"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "53ffe03ae896d0c43107b218da2749385ec",
    "sha256": "e83acf2b7c6c23d377d860f011d11c85e638614143a16779a81d1b5489880582",
    "subject": "seller-ledger.ru",
    "valid_to": "2027-01-25T15:30:31Z",
    "valid_from": "2026-10-27T15:30:32Z"
}
Registration record
{
    "registrar": "REGRU-RU"
}
Separate collector summary

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

source
VirusTotal
scope
unknown
result_state
observed
numerator
11
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","BitDefender","CRDF","Forcepoint ThreatSeeker","Fortinet","G-Data","Gridinsoft","Kaspersky","SOCRadar","Sophos","VIPRE"]
observed_at
null
checked_at
2026-11-02 04:02:11
fetched_at
2026-11-02 03:02:12
time_basis
as stored; legacy timezone not established

Cloudflare Radar

Suspicious

Open report
Cloudflare RadarOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Report ID

8fc9a12b-e377-4576-a190-3b7ef5615858

Final URL

https://seller-ledger.ru/

HTTP response

200

Navigation history

  • URL
    https://seller-ledger.ru/
    Status
    200

DOM structure hash

3bf4fcb4feb3ea25d878aeace99811fe3ab6688eefa46e80bc1efe44b28b7c18

Document hash

43582944984a772b6a7a1f3adc246948f9cd5065e9dcdaade45af0a3bdd95c8a

Domain risk categories

  • Newly Seen Domains
  • Security Risks

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    seller-ledger.ru
    Type
    A
    Value
    168.113.174.162

DNSSEC valid

No

IP address

127.0.1.21

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

Registration record

Registrar
REGRU-RU
Registered
Expires
Nameservers
  • ns1.reg.ru
  • ns2.reg.ru
Original source fields · JSON
Uuid
8fc9a12b-e377-4576-a190-3b7ef5615858
Final url
https://seller-ledger.ru/
Status
200
History
[
    {
        "url": "https://seller-ledger.ru/",
        "status": 200
    }
]
DOM structure hash
3bf4fcb4feb3ea25d878aeace99811fe3ab6688eefa46e80bc1efe44b28b7c18
Document hash
43582944984a772b6a7a1f3adc246948f9cd5065e9dcdaade45af0a3bdd95c8a
Domain risks
[
    "Newly Seen Domains",
    "Security Risks"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "seller-ledger.ru",
        "type": "A",
        "value": "168.113.174.162"
    }
]
Dnssec valid
false
Ip
127.0.1.21

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

Registration record
{
    "registrar": "REGRU-RU",
    "created": "2026-10-25T12:38:45Z",
    "expires": "2027-10-25T12:38:45Z",
    "nameservers": [
        "ns1.reg.ru",
        "ns2.reg.ru"
    ]
}

URLScan

Malicious · engine verdict · score 98

SHA-256 9609711945d8bfca20fc28486bbd270c6e17ea2984235518a84317a2cb6fc8ad

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a187f6-739e-734f-b7fe-dc9eb3c2a247

Final URL

https://seller-ledger.ru/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://seller-ledger.ru/
    From
    http://seller-ledger.ru/
    Status
    307

IP address

168.113.174.162

Contacted IP addresses

  • 168.113.174.162

Autonomous systems (ASN)

  • 211183

Server countries

  • RU

Document hash

ba515094fc019b3374f5aada85d9fdfa1354205723c932739d800a3fd5786c96

Script hashes

  • 0ef3bcb1d3eed313a0a15a6c2f195b586436f110c03cddf99d13f5e23ff309ab
  • f252176e4fcc7ac934cff2315af3431c9102587850872a19fb1e922970d3abc3
  • a349ed3d148896e6eeea5b61fcb9ec13cc34a120738f9c164ee82eb543954a28
  • bc58f85c3593ec28ac7a9592a6d256f7a84178ec4d91e8b1e2f7b160ef9d40ec
  • 2a4be97c86df8f502333c49d16c85f967648a9c825c59b5ed58a3cd1a993d06a

JavaScript globals

  • __VUE_INSTANCE_SETTERS__
  • __VUE_SSR_SETTERS__
  • __VUE__

Cookies

  • XSRF-TOKEN
  • sellerfinance_session

TLS session and certificate

Subject alternative names
  • seller-ledger.ru
  • www.seller-ledger.ru
Cipher
AES_256_GCM
Issuer
YE1
Subject
seller-ledger.ru
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

1

Registered domain age, days

1

Certificate age, days

1

Certificate validity, days

89

Page requests

17

Provider verdicts

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

HTTP headers

Server
nginx
Content-type
text/html; charset=utf-8
X-frame-options
DENY
X-content-type-options
nosniff nosniff
Referrer-policy
no-referrer
Original source fields · JSON
Uuid
01a187f6-739e-734f-b7fe-dc9eb3c2a247
Final url
https://seller-ledger.ru/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://seller-ledger.ru/",
        "from": "http://seller-ledger.ru/",
        "status": 307
    }
]
Ip
168.113.174.162
Contacted IP addresses
[
    "168.113.174.162"
]
Asns
[
    "211183"
]
Countries
[
    "RU"
]
Document hash
ba515094fc019b3374f5aada85d9fdfa1354205723c932739d800a3fd5786c96
Script hashes
[
    "0ef3bcb1d3eed313a0a15a6c2f195b586436f110c03cddf99d13f5e23ff309ab",
    "f252176e4fcc7ac934cff2315af3431c9102587850872a19fb1e922970d3abc3",
    "a349ed3d148896e6eeea5b61fcb9ec13cc34a120738f9c164ee82eb543954a28",
    "bc58f85c3593ec28ac7a9592a6d256f7a84178ec4d91e8b1e2f7b160ef9d40ec",
    "2a4be97c86df8f502333c49d16c85f967648a9c825c59b5ed58a3cd1a993d06a"
]
Globals
[
    "__VUE_INSTANCE_SETTERS__",
    "__VUE_SSR_SETTERS__",
    "__VUE__"
]
Cookies
[
    "XSRF-TOKEN",
    "sellerfinance_session"
]
Tls
{
    "san": [
        "seller-ledger.ru",
        "www.seller-ledger.ru"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YE1",
    "subject": "seller-ledger.ru",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-25T15:30:31Z",
    "valid_from": "2026-10-27T15:30:32Z"
}
Domain age days
1
Apex age days
1
Tls age days
1
Tls valid days
89
Requests
17
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 98,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html; charset=utf-8",
    "x-frame-options": "DENY",
    "x-content-type-options": "nosniff\nnosniff",
    "referrer-policy": "no-referrer"
}
Separate monitor record · 2026-10-30 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a187f6-739e-734f-b7fe-dc9eb3c2a247
score
0
malicious
false
result_at
2026-10-30T04:30:22Z
enriched_at
2026-10-30T09:11:44Z
source_timestamps
{"urlscan_result_at":"2026-10-30 05:30:22","urlscan_enriched_at":"2026-10-30 10:11:44"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

2 community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 10 / 100 · 2026-10-29T14:36:42Z

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
10
analyzed_at
2026-10-29T14:36:42Z
source_timestamp
2026-10-29 15:36:42
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
Website checksOriginal source recordRetrieved: 10 fields

Mail configuration

MX records
  • mail.trekmail.net
SPF record
v=spf1 include:spf.trekmail.net -all
DKIM
  • dkim
DMARC
Yes
DKIM key size, bits
2048
SPF lookups
1

CAA records

Domain
seller-ledger.ru

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Ports

Open ports
  • 22
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    194.58.117.13
    Host
    ns1.reg.ru
  • IP address
    194.58.117.12
    Host
    ns2.reg.ru
DNS zone
seller-ledger.ru

Location

IP address
168.113.174.162
Organization
Andrei Zaitsev
City
Moscow
Country
RU

DNS records

A
  • 168.113.174.162
MX
  • Mail server
    mail.trekmail.net
    Priority
    10
NS
  • ns1.reg.ru
  • ns2.reg.ru
SOA
Primary nameserver
ns1.reg.ru
Hostmaster
hostmaster.ns1.reg.ru
Serial
1793281935
Refresh, seconds
14400
Retry, seconds
3600
Expiry, seconds
604800
Minimum TTL, seconds
10800
TXT
  • google-site-verification=-AG0Z3z-gkmoV0hR72Ovyd9pixEy-YI74WGWvoX00UY
  • v=spf1 include:spf.trekmail.net -all
  • yandex-verification: de96b6486bd2e988

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
168.113.174.162
IP version
4

Registration record

Registrar
REGRU-RU
Registered
Expires
Status
  • REGISTERED, DELEGATED, UNVERIFIED
Nameservers
  • ns1.reg.ru.
  • ns2.reg.ru.
Original source fields · JSON
Mail configuration
{
    "mx": [
        "mail.trekmail.net"
    ],
    "spf": "v=spf1 include:spf.trekmail.net -all",
    "dkim": [
        "dkim"
    ],
    "dmarc": true,
    "dkim_bits": 2048,
    "spf_lookups": 1
}
Caa records
{
    "domain": "seller-ledger.ru"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Ports
{
    "open": [
        22,
        80,
        443
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "194.58.117.13",
            "host": "ns1.reg.ru"
        },
        {
            "ip": "194.58.117.12",
            "host": "ns2.reg.ru"
        }
    ],
    "zone": "seller-ledger.ru"
}
Location
{
    "ip": "168.113.174.162",
    "org": "Andrei Zaitsev",
    "city": "Moscow",
    "country": "RU"
}
DNS records
{
    "A": [
        "168.113.174.162"
    ],
    "MX": [
        "{\"exchange\": \"mail.trekmail.net\", \"priority\": 10}"
    ],
    "NS": [
        "ns1.reg.ru",
        "ns2.reg.ru"
    ],
    "SOA": "{\"nsname\": \"ns1.reg.ru\", \"hostmaster\": \"hostmaster.ns1.reg.ru\", \"serial\": 1793281935, \"refresh\": 14400, \"retry\": 3600, \"expire\": 604800, \"minttl\": 10800}",
    "TXT": [
        "google-site-verification=-AG0Z3z-gkmoV0hR72Ovyd9pixEy-YI74WGWvoX00UY",
        "v=spf1 include:spf.trekmail.net -all",
        "yandex-verification: de96b6486bd2e988"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "168.113.174.162",
    "family": 4
}
Registration record
{
    "registrar": "REGRU-RU",
    "created": "2026-10-25T12:38:45Z",
    "expires": "2027-10-25T12:38:45Z",
    "status": [
        "REGISTERED, DELEGATED, UNVERIFIED"
    ],
    "nameservers": [
        "ns1.reg.ru.",
        "ns2.reg.ru."
    ]
}
Blocklist matchesMetaMask · PhishDestroy · SEAL · no match in the other 9 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Checked, no match

Last checked

Stored Capture · 3 captures

Stored capture 1 / 3
SourceStored capture
Recorded
StateStored capture
Position1 / 3
Open capture Wayback Download
All capture links and hashes (3)
seller-ledger.ru: Ledger impersonation — Blocked by MetaMask, flagged by SEAL, 3/92 VirusTotal engines. PhishDestroy risk score 76/100 (critical).
Social preview card seller-ledger.ru: Ledger impersonation — Blocked by MetaMask, flagged by SEAL, 3/92 VirusTotal engines. PhishDestroy risk score 76/100 (critical). v a0ee22bcbb4a

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 98 report ↗
IP Reputation Russia168.113.174.162 abuse score 0/100 0 reports checked Oct 29, 2026
OTX tags 2026-10all-domainscryptodomainslivemonthlyphishdestroyphishingscam
Registrar REGRU-RU RU(RU)
Abuse contactabuseto@adminvps.ru
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for seller-ledger.ru →
RegistrationCreated Oct 25, 2026 (7d · Very New!) — Expires Oct 25, 2027
WHOIS statusREGISTERED,
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 29, 2026
DOM Analysisanalyzed Oct 29, 2026score 10/1001 brand signal
Submitted URLhttp://seller-ledger.ru/
Favicon Hash
Observed page title
Прибыль по товарам Wildberries и Ozon и сверка выплат — SellerFinance
Automated brand references
Ledger
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 84 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Russia168.113.174.162
Network ASN
AS211183
AS name
AdminVPS AdminVPS OOO, RU
Organization
Andrei Zaitsev
Observed location
RussiaMoscow, RU
Server header
nginx

Nameservers 2

  • ns1.reg.ru
  • ns2.reg.ru

SOA

  • nsname: ns1.reg.ru
  • hostmaster: hostmaster.ns1.reg.ru
  • serial: 1793281935
  • refresh: 14400
  • retry: 3600
  • expire: 604800
  • minttl: 10800

Mail routing 1 MX record

  • mail.trekmail.net

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-10-27 15:30:32
Valid until
2027-01-25 15:30:31
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-29 14:02:09 UTC
Collection source
PhishDestroy collector
Certificate fingerprinte83acf2b7c6c23d377d860f011d11c85e638614143a16779a81d1b5489880582
Certificate names · 2 SANs
  • seller-ledger.ru
  • www.seller-ledger.ru

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

viewdns.info · 168.113.174.162rapiddns.io

Latest Classified Outcome 2026-11-01 23:05:02 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-01 23:05:02 UTC
RDAP registration
Observed timeline last reachable: 2026-11-01 23:34:02 UTC last content: 2026-11-01 23:05:02 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.seller-ledger.ruDomain record
Technologies · 1 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

3 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 3 detections
CRDF
Gridinsoft
alphaMountain.ai

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of seller-ledger.ru · checked Oct 29, 2026

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

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Captured network requests

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

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 14:03 UTC.

Open this scan on URLScan 01a187f6-739e-734f-b7fe-dc9eb3c2a247 ↗

Check for cloaking

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

Page titles differ

Our scanner could not complete this check.

Browser
Прибыль по товарам Wildberries и Ozon и сверка выплат — SellerFinance
Crawler
Разбор отчётов WB и Ozon: начисления и расходы — SellerLedger
seller-ledger.ru
Stored observation history6

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

  1. Availability monitor · Recorded state

    live_content

    content_served

  2. Availability monitor · Recorded state

    redirected→live_content

    content_served

  3. Availability monitor · Recorded state

    redirected

    http_redirect

  4. Availability monitor · Recorded state

    live_content

    content_served

  5. Availability monitor · Recorded state

    live_content

    content_served

Earlier observations 1
  1. Domain monitor · First collection record

    Reachable

All retained availability observations22

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_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 00:05:02.000000
    Evidence SHA-256
    fa0099e6d5fb31cff9adb7a9eb2c103eaa7637b79fd5c4c0ca20274b8e6beca3
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:05:02
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 00:05:02.000000
    Evidence SHA-256
    fa0099e6d5fb31cff9adb7a9eb2c103eaa7637b79fd5c4c0ca20274b8e6beca3
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:05:02
    Evidence reason
    alive_content
  3. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-11-01 23:20:11.055498
    Evidence SHA-256
    7c023747294077bd6e2ec2b080dc137e75a3ed6faf38dbdfcaa23e6958793fa3
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 23:20:11.055498
    Evidence reason
  4. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 12:05:51.000000
    Evidence SHA-256
    4c222a15b75aa2edcca4ee8e4d204076b94ff4724e1164a554003c3c8aa4597e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:05:51
    Evidence reason
    alive_content
  5. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 12:05:51.000000
    Evidence SHA-256
    4c222a15b75aa2edcca4ee8e4d204076b94ff4724e1164a554003c3c8aa4597e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:05:51
    Evidence reason
    alive_content
  6. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 03:49:18.000000
    Evidence SHA-256
    cd37fe9625acef2fc63ae083b63919a9776ccafeff171765212da6d5be188832
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 03:49:18
    Evidence reason
    alive_content
  7. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 03:49:18.000000
    Evidence SHA-256
    cd37fe9625acef2fc63ae083b63919a9776ccafeff171765212da6d5be188832
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 03:49:18
    Evidence reason
    alive_content
  8. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:04:14.000000
    Evidence SHA-256
    4dac3778f70c850982aeacab527779d9d376fe6a2554313f2966448514603dbf
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-01 00:04:14
    Evidence reason
    redirect
  9. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:04:14.000000
    Evidence SHA-256
    4dac3778f70c850982aeacab527779d9d376fe6a2554313f2966448514603dbf
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-01 00:04:14
    Evidence reason
    redirect
  10. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-31 23:20:09.600237
    Evidence SHA-256
    fdac094cb4b92350d9f20b2c0fc69fdcaa33e7da7eb2d1063ea3f2bc257f29ef
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 23:20:09.600237
    Evidence reason
  11. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:04:16.000000
    Evidence SHA-256
    7eaa12f374eafeb4cc8af34c82e77d68aea03686a7cd53d118ea93c5dfb9b400
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:04:16
    Evidence reason
    alive_content
  12. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:04:16.000000
    Evidence SHA-256
    7eaa12f374eafeb4cc8af34c82e77d68aea03686a7cd53d118ea93c5dfb9b400
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:04:16
    Evidence reason
    alive_content
  13. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 00:58:01.000000
    Evidence SHA-256
    4f0c543856604c53df3bf83c500a5a7792160bd52e109cdf791bb0143aac3632
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:58:01
    Evidence reason
    alive_content
  14. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 00:58:01.000000
    Evidence SHA-256
    4f0c543856604c53df3bf83c500a5a7792160bd52e109cdf791bb0143aac3632
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:58:01
    Evidence reason
    alive_content
  15. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-30 17:14:28.389060
    Evidence SHA-256
    21712fa93c42dbe273472efc1fb1dc4b80cb1c93483cea1c8ffec553fe67c289
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 17:14:28.389060
    Evidence reason
  16. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 13:10:23.000000
    Evidence SHA-256
    461fa8e3ef1b6037c4524744f1ee0f7f1273ec16c502f80b67cc5e3c6a7be2e3
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 13:10:23
    Evidence reason
    alive_content
  17. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 13:10:23.000000
    Evidence SHA-256
    461fa8e3ef1b6037c4524744f1ee0f7f1273ec16c502f80b67cc5e3c6a7be2e3
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 13:10:23
    Evidence reason
    alive_content
  18. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 01:23:29.000000
    Evidence SHA-256
    7bf5f2a01af5299cd6a603791974eb72d947d80b175f98aa9cee5e7564b2776a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 01:23:29
    Evidence reason
    alive_content
  19. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 01:23:29.000000
    Evidence SHA-256
    7bf5f2a01af5299cd6a603791974eb72d947d80b175f98aa9cee5e7564b2776a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 01:23:29
    Evidence reason
    alive_content
  20. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-29 15:01:34.000000
    Evidence SHA-256
    9dd72ff349099af5020c443858d5f2264b6fb4742be37920be1f41dc34424a42
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 15:01:34
    Evidence reason
  21. 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-29 15:01:34.000000
    Evidence SHA-256
    9dd72ff349099af5020c443858d5f2264b6fb4742be37920be1f41dc34424a42
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 15:01:34
    Evidence reason
  22. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-29 05:03:37.265303
    Evidence SHA-256
    70428a63b8173a73a74f49b17afd536533730dedaa784f9dc01629701511d2b2
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 05:03:37.265303
    Evidence reason

Threat Response Pipeline

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

Recorded events: 12. 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
    seller-ledger.ru detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Blocklist Detection · OTX Community References · Automated brand label: Ledger · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 10 of 10
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 98
  • 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: 3/92
  • Blocklist Detection
    Found in blocklists: MetaMask, SEAL
  • OTX Community References
    Community publication references on AlienVault OTX: 2. References are not vendor verdicts and are excluded from the evidence score.
  • 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. Wayback Machine

    Page archived

    View source
  2. AlienVault OTX

    2 community references

    View source
  3. Added to PhishDestroy

    seller-ledger.ru

    View source
  4. URLScan

    Page captured

    View source
  5. VirusTotal

    3/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
All stored records by source

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

Download all records as JSON

Lookalike domains

151 stored lookalike domains

Source: dnstwist_results. These are saved variants of target domains. Selection may use older collector labels whose own observation date was not retained. It does not establish impersonation, common ownership or current availability. Dates belong to dnstwist observations; the legacy timezone is not established.

dnstwist_results #601 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledfger.com insertion Internal report A 185.244.151.84MX ledfger.comNS ns3.ro.hostsailor.com dnstwist_results #603 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgfer.com insertion Internal report A 185.244.151.84MX ledgfer.comNS ns3.ro.hostsailor.com dnstwist_results #604 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgher.com insertion Internal report A 185.244.151.84MX ledgher.comNS ns3.ro.hostsailor.com dnstwist_results #640 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgrr.com replacement Internal report A 185.244.151.84MX ledgrr.comNS ns3.ro.hostsailor.com dnstwist_results #609 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lefdger.com insertion Internal report A 185.244.151.84MX lefdger.comNS ns3.ro.hostsailor.com dnstwist_results #611 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lesdger.com insertion Internal report A 185.244.151.84MX lesdger.comNS ns3.ro.hostsailor.com dnstwist_results #613 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lkedger.com insertion Internal report A 185.244.151.84MX lkedger.comNS ns3.ro.hostsailor.com dnstwist_results #614 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lredger.com insertion Internal report A 185.244.151.84MX lredger.comNS ns3.ro.hostsailor.com dnstwist_results #615 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lwedger.com insertion Internal report A 185.244.151.84MX lwedger.comNS ns3.ro.hostsailor.com dnstwist_results #592 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 xn--ledgr-9za.com homoglyph Internal report NS ns-cloud-d1.googledomains.com dnstwist_results #524 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:33 · Last: 2026-03-17 13:39:33 ledgerk.com addition Internal report A 156.250.67.229NS ns1.bdydns.cn dnstwist_results #624 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 edger.com omission A 54.215.31.113NS ns1.dyna-ns.net
Show all (88)
dnstwist_results #652 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 eldger.com transposition A 185.244.151.84MX eldger.comNS ns3.ro.hostsailor.com dnstwist_results #634 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 kedger.com replacement A 13.56.33.8NS ns1.brandbucket.com dnstwist_results #617 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 kledger.com insertion A 20.65.18.151NS ns-1490.awsdns-58.org dnstwist_results #644 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 l3dger.com replacement A 216.198.79.1MX inbound-smtp.eu-west-1.amazonaws.comNS ns1.bluehost.com dnstwist_results #653 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ldeger.com transposition A 185.244.151.84MX ldeger.comNS ns3.ro.hostsailor.com dnstwist_results #621 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ldger.com omission A 13.248.169.48NS ns1.dan.com dnstwist_results #650 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 le.dger.com subdomain A 13.248.169.48NS ns5.afternic.com dnstwist_results #635 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lecger.com replacement A 14.63.215.245NS ns1.hostname.net dnstwist_results #630 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledber.com replacement A 104.21.35.54NS chin.ns.cloudflare.com dnstwist_results #654 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledegr.com transposition A 185.244.151.84MX ledegr.comNS ns3.ro.hostsailor.com dnstwist_results #626 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 leder.com omission A 85.13.132.113MX w01a4668.kasserver.comNS ns5.kasserver.com dnstwist_results #649 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledg3r.com replacement NS ns1.dreamhost.com dnstwist_results #625 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledge.com omission A 54.215.31.113NS ns1.dyna-ns.net dnstwist_results #646 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledged.com replacement A 52.20.84.62NS ns1.atom.com dnstwist_results #619 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgedr.com insertion A 31.43.160.6NS ns6.wixdns.net dnstwist_results #631 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgee.com replacement A 13.248.169.48NS ns3.afternic.com dnstwist_results #629 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgeer.com repetition A 52.20.84.62NS ns1.squadhelp.com dnstwist_results #656 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgercom.com various A 91.215.86.207NS ns3.epik.com dnstwist_results #632 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledget.com replacement A 13.248.169.48NS ns1.afternic.com dnstwist_results #602 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgewr.com insertion A 185.244.151.84MX ledgewr.comNS ns3.ro.hostsailor.com dnstwist_results #627 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgger.com repetition A 13.56.33.8NS ns1.brandbucket.com dnstwist_results #659 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgir.com vowel-swap A 188.114.96.3NS lynn.ns.cloudflare.com dnstwist_results #657 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgor.com vowel-swap A 103.230.136.195MX mxn.mxhichina.comNS ens11.bigwww.com dnstwist_results #622 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgr.com omission A 188.114.96.3NS kim.ns.cloudflare.com dnstwist_results #651 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgre.com transposition A 172.65.185.109NS sp1.gname-dns.com dnstwist_results #605 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgrer.com insertion A 185.244.151.84MX ledgrer.comNS ns3.ro.hostsailor.com dnstwist_results #636 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgsr.com replacement A 14.63.215.245NS ns1.hostname.net dnstwist_results #606 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgwer.com insertion A 185.244.151.84MX ledgwer.comNS ns3.ro.hostsailor.com dnstwist_results #641 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgwr.com replacement A 185.244.151.84MX ledgwr.comNS ns3.ro.hostsailor.com dnstwist_results #639 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledher.com replacement A 15.197.148.33MX mailstore1.secureserver.netNS ns03.domaincontrol.com dnstwist_results #607 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledhger.com insertion A 185.244.151.84MX ledhger.comNS ns3.ro.hostsailor.com dnstwist_results #608 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledsger.com insertion A 185.244.151.84MX ledsger.comNS ns3.ro.hostsailor.com dnstwist_results #616 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledtger.com insertion A 188.114.96.3NS janet.ns.cloudflare.com dnstwist_results #645 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledyer.com replacement A 31.43.160.6MX alt1.aspmx.l.google.comNS ns-1051.awsdns-03.org dnstwist_results #643 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledzer.com replacement A 188.114.96.3NS kimora.ns.cloudflare.com dnstwist_results #620 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 leedger.com insertion MX mxbiz1.qq.comNS dns10.hichina.com dnstwist_results #655 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 legder.com transposition A 64.190.63.222MX localhostNS ns1.sedoparking.com dnstwist_results #623 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 leger.com omission A 216.40.34.37MX mx.netidentity.com.cust.hostedemail.comNS ns1.mailbank.com dnstwist_results #610 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lerdger.com insertion A 185.244.151.84MX lerdger.comNS ns3.ro.hostsailor.com dnstwist_results #633 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lerger.com replacement A 13.248.169.48NS ns1.afternic.com dnstwist_results #642 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lesger.com replacement A 185.244.151.84MX lesger.comNS ns3.ro.hostsailor.com dnstwist_results #612 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lewdger.com insertion A 185.244.151.84MX lewdger.comNS ns3.ro.hostsailor.com dnstwist_results #660 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lidger.com vowel-swap A 66.241.124.184MX route1.mx.cloudflare.netNS erin.ns.cloudflare.com dnstwist_results #628 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lledger.com repetition A 50.254.19.65MX lledger-com.mail.protection.outlook.comNS ns-1532.awsdns-63.org dnstwist_results #658 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lodger.com vowel-swap A 149.210.148.65MX mail.lodger.comNS aron.ns.cloudflare.com dnstwist_results #648 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lrdger.com replacement A 77.247.179.85MX mail.h-email.netNS ns1.badgerdns.com dnstwist_results #637 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lsdger.com replacement A 14.63.215.245NS ns1.hostname.net dnstwist_results #638 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 oedger.com replacement A 14.63.215.245NS ns1.hostname.net dnstwist_results #647 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 pedger.com replacement A 74.220.199.6 dnstwist_results #618 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 pledger.com insertion A 216.40.34.37MX mx.netidentity.com.cust.hostedemail.comNS ns1.mailbank.com dnstwist_results #555 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 dedger.com bitsquatting MX aspmx1.migadu.comNS apollo.ns.cloudflare.com dnstwist_results #547 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 hedger.com bitsquatting A 15.197.225.128MX alt1.aspmx.l.google.comNS ns23.domaincontrol.com dnstwist_results #570 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 iedger.com homoglyph A 217.70.184.38MX fb.mail.gandi.netNS ns-157-c.gandi.net dnstwist_results #596 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 l-edger.com hyphenation A 216.198.79.65NS ns1.vercel-dns.com dnstwist_results #551 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ladger.com bitsquatting A 185.80.2.134MX ladger.comNS ns209.superhosting.bg dnstwist_results #591 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 lcdlger.com homoglyph NS ns2.my-ndns.com dnstwist_results #544 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 lddger.com bitsquatting A 14.63.215.245NS ns1.hostname.net dnstwist_results #560 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 lebger.com homoglyph A 104.247.81.99NS ns1.parkingcrew.net dnstwist_results #589 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 leclger.com homoglyph A 34.42.100.71NS ns-cloud-e1.googledomains.com dnstwist_results #546 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledcer.com bitsquatting A 15.197.148.33MX ledcer-com.mail.protection.outlook.comNS pdns11.domaincontrol.com dnstwist_results #598 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 leddger.com insertion A 13.248.169.48NS ns1.afternic.com dnstwist_results #540 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledeer.com bitsquatting A 13.248.169.48NS ns1.dan.com dnstwist_results #597 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledeger.com insertion A 103.224.182.253MX park-mx.above.comNS ns1.abovedomains.com dnstwist_results #545 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledfer.com bitsquatting A 15.197.142.173MX mailstore1.secureserver.netNS ns11.domaincontrol.com dnstwist_results #595 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledg-er.com hyphenation A 162.255.119.245MX mail.protonmail.chNS dns1.registrar-servers.com dnstwist_results #541 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledgar.com bitsquatting A 13.248.169.48NS ns1.namefind.com dnstwist_results #530 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledger0.com addition A 20.82.12.44MX ledger0-com.mail.protection.outlook.comNS ns1-04.azure-dns.com dnstwist_results #532 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledger1.com addition A 44.232.173.249NS launch1.spaceship.net dnstwist_results #535 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledger4.com addition A 52.201.53.166NS nsg1.namebrightdns.com dnstwist_results #538 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledger5.com addition MX mail.protonmail.chNS ns-1175.awsdns-18.org dnstwist_results #533 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledger6.com addition A 52.20.84.62NS ns1.atom.com dnstwist_results #536 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledgerb.com addition A 91.195.240.82NS ns1dhl.name.com dnstwist_results #528 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledgerc.com addition A 198.185.159.144MX alt1.aspmx.l.google.comNS dns1.p02.nsone.net dnstwist_results #537 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledgerf.com addition A 94.75.193.73MX mail.h-email.netNS ns1.thednscloud.com dnstwist_results #534 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledgeri.com addition A 52.20.84.62NS ns1.atom.com dnstwist_results #527 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledgern.com addition A 192.0.78.162MX ledgern-com.mail.protection.outlook.comNS ns1.wordpress.com dnstwist_results #531 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledgerq.com addition A 31.43.160.6MX ledgerq-com.mail.protection.outlook.comNS ns03.domaincontrol.com dnstwist_results #529 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledgerx.com addition A 198.202.211.1MX usb-smtp-inbound-1.mimecast.comNS alla.ns.cloudflare.com dnstwist_results #549 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledges.com bitsquatting A 170.249.218.186MX ledges-com.mail.protection.outlook.comNS ns47.domaincontrol.com dnstwist_results #554 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledgez.com bitsquatting A 67.23.254.40MX ledgez.comNS ns1.reseller-228.mco2.hostdime.com dnstwist_results #543 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledgur.com bitsquatting A 13.248.243.5MX ledgur-com.mail.protection.outlook.comNS ns23.domaincontrol.com dnstwist_results #565 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 lediger.com homoglyph A 185.225.135.100MX mail02.lediger-consulting.deNS ns1.routing.net dnstwist_results #561 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledqer.com homoglyph A 13.223.25.84NS nsg1.namebrightdns.com dnstwist_results #552 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 leeger.com bitsquatting A 194.191.24.29MX alt1.aspmx.l.google.comNS cns1.cloudpit.de dnstwist_results #562 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 leelger.com homoglyph A 15.197.148.33NS ns69.domaincontrol.com dnstwist_results #539 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 lefger.com bitsquatting A 103.224.182.244MX park-mx.above.comNS ns1.abovedomains.com dnstwist_results #548 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 letger.com bitsquatting A 156.245.108.206NS ns1.dnsowl.com dnstwist_results #550 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ludger.com bitsquatting A 18.195.62.85MX ludger-com.mail.protection.outlook.comNS ns11.worldnic.com

Showing 100 of 151

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 3 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report OTX 2 refs 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?

4 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 seller-ledger.ru)
  • 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/seller-ledger.ru"
  title="PhishDestroy threat report for seller-ledger.ru"
  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>