Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 4/92 engines flagged. malicious: 4. suspicious: 0. Analysis time (as stored): 2026-10-13T09:41:08Z. Retrieved (as stored): 2026-10-31T00:47:17Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
ledegers.co.com favicon

ledegers.co.com

In short

The captured page at ledegers.co.com shows a Hostinger-branded landing screen with a Ukrainian heading announcing that the site is ready to work, followed by a short instruction to upload the site's files. Two purple help links open in new tabs: one on moving a site to Hostinger and another on installing WordPress with an auto-installer, each paired with an external-link icon.

“Страница по умолчанию”

Review the evidence
Registrar
Moniker Online Services
Resolved IP
Germany92.113.23.79Hostinger International Limited
First observed
Oct 31, 2026
PhishDestroy assessment Critical
87/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 4/92 Spamhaus DBL: phishing domain
VirusTotal
4 / 92
engine detections ·
URLScan
Malicious
engine verdict · score 99
Page captures
3
open gallery
Oct 31, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded ledegers.co.com on 2026-10-31. Stored VirusTotal result: 4/92 engines flagged. malicious: 4. suspicious: 0. Analysis time (as stored): 2026-10-13T09:41:08Z. Retrieved (as stored): 2026-10-31T00:47:17Z. Risk: critical (87/100). Registrar: Moniker Online Services. Status: Last known active. Hosting: Hostinger International Limited. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
4 / 92
Hosting
Germany92.113.23.79Hostinger International Limited
Registrar
Moniker Online Services
Page captures
3
Page captures Source results Registration record

Capture recorded with this analysis · Cloudflare Radar · 2026-10-31T00:16:31Z
SHA-256: d20de79078d8277956037eaea79398519b82aca2db6d2a5b519984b1442bd414

PhishDestroy analysis, reviewed version

The captured page at ledegers.co.com shows a Hostinger-branded landing screen with a Ukrainian heading announcing that the site is ready to work, followed by a short instruction to upload the site's files. Two purple help links open in new tabs: one on moving a site to Hostinger and another on installing WordPress with an auto-installer, each paired with an external-link icon.

The stored VirusTotal domain result reports 4 detections out of 92 engines. DNS8 reported "phishing"; SOCRadar reported "phishing".

Source evidenceVirusTotal 4 / 92 8 sources

VirusTotal

4 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
56
Malicious
4
Suspicious
0
Undetected
32

Vendor labels

DNS8
phishing
SOCRadar
phishing
Gridinsoft
phishing
alphaMountain.ai
phishing

Reputation score

0

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

Created

Updated

First seen

DNS records

  • TTL, seconds
    60
    Type
    AAAA
    Value
    2a02:4780:4f:c45d:fd8d:e748:3183:ad13
  • TTL, seconds
    3600
    Type
    TXT
    Value
    v=spf1 include:_spf.mail.hostinger.com ~all
  • TTL, seconds
    21600
    Type
    NS
    Value
    apollo.dns-parking.com
  • TTL, seconds
    60
    Type
    A
    Value
    77.37.76.245
  • TTL, seconds
    3600
    Type
    SOA
    Responsible mailbox
    dns.hostinger.com
    Value
    athena.dns-parking.com
  • TTL, seconds
    14400
    Type
    MX
    Value
    mx2.hostinger.com
    Priority
    10
  • TTL, seconds
    21600
    Type
    NS
    Value
    athena.dns-parking.com
  • TTL, seconds
    60
    Type
    A
    Value
    92.112.198.0
  • TTL, seconds
    60
    Type
    AAAA
    Value
    2a02:4780:51:d7c8:ef29:5a0f:f038:99
  • TTL, seconds
    14400
    Type
    MX
    Value
    mx1.hostinger.com
    Priority
    5

DNS records observed

JARM fingerprint

27d40d40d00040d00042d43d000000e1ea2a807a629b496b664cf07ad7c08d

Certificate

Subject alternative names
  • ledegers.co.com
  • www.ledegers.co.com
Issuer
Let's Encrypt / YE1
Serial
59f1c29c56968bda8f290a23fb3b27fa907
SHA-256
f6988de046faec6377287c3cc4fb47eca129fb1a5e09e79646475fca3d1588d7
Subject
ledegers.co.com
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 56,
    "malicious": 4,
    "suspicious": 0,
    "undetected": 32
}
Vendor labels
{
    "DNS8": "phishing",
    "SOCRadar": "phishing",
    "Gridinsoft": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Created
2026-03-20T00:00:00Z
Updated
2026-03-21T00:00:00Z
First seen
2026-03-20T18:10:38Z
DNS records
[
    {
        "ttl": 60,
        "type": "AAAA",
        "value": "2a02:4780:4f:c45d:fd8d:e748:3183:ad13"
    },
    {
        "ttl": 3600,
        "type": "TXT",
        "value": "v=spf1 include:_spf.mail.hostinger.com ~all"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "apollo.dns-parking.com"
    },
    {
        "ttl": 60,
        "type": "A",
        "value": "77.37.76.245"
    },
    {
        "ttl": 3600,
        "type": "SOA",
        "rname": "dns.hostinger.com",
        "value": "athena.dns-parking.com"
    },
    {
        "ttl": 14400,
        "type": "MX",
        "value": "mx2.hostinger.com",
        "priority": 10
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "athena.dns-parking.com"
    },
    {
        "ttl": 60,
        "type": "A",
        "value": "92.112.198.0"
    },
    {
        "ttl": 60,
        "type": "AAAA",
        "value": "2a02:4780:51:d7c8:ef29:5a0f:f038:99"
    },
    {
        "ttl": 14400,
        "type": "MX",
        "value": "mx1.hostinger.com",
        "priority": 5
    }
]
Dns at
2026-10-13T09:47:45Z
Jarm
27d40d40d00040d00042d43d000000e1ea2a807a629b496b664cf07ad7c08d
Certificate
{
    "san": [
        "ledegers.co.com",
        "www.ledegers.co.com"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "59f1c29c56968bda8f290a23fb3b27fa907",
    "sha256": "f6988de046faec6377287c3cc4fb47eca129fb1a5e09e79646475fca3d1588d7",
    "subject": "ledegers.co.com",
    "valid_to": "2026-12-17T03:01:43Z",
    "valid_from": "2026-09-18T03:01:44Z"
}
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
9
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","BitDefender","Forcepoint ThreatSeeker","Fortinet","G-Data","Gridinsoft","Lionic","SOCRadar","VIPRE"]
observed_at
null
checked_at
2026-11-05 04:05:12
fetched_at
2026-11-05 03:05:12
time_basis
as stored; legacy timezone not established

Spamhaus DBL

phishing domain

URLScan

Malicious · engine verdict · score 99

SHA-256 961882f58555aa7c78e0a1eade8e7b158f6a2cc6a46a2867330e788dfe73c105

Open report
URLScanOriginal source recordObserved: 19 fields

Observed: · Retrieved:

Report ID

019ef8d8-4154-720c-9914-2499ea0d48b7

Final URL

https://ledegers.co.com/

HTTP response

200

IP address

147.79.72.46

Contacted domains

  • fonts.googleapis.com
  • hpanel.hostinger.com
  • fonts.gstatic.com
  • assets.hostinger.com

Contacted IP addresses

  • 192.178.218.94
  • 104.16.210.83
  • 142.251.167.95
  • 147.79.72.46

Autonomous systems (ASN)

  • 15169
  • 13335
  • 47583

Server countries

  • US

Linked domains

  • hpanel.hostinger.com
  • support.hostinger.com

Document hash

d189b76f3225c8dadc69205caaa08079a830fd97f7a888a186f527c3cd6a3ad6

Cookies

  • __cf_bm

TLS session and certificate

Subject alternative names
  • ledegers.co.com
  • www.ledegers.co.com
Cipher
AES_128_GCM
Issuer
R13
Subject
ledegers.co.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

95

Registered domain age, days

95

Certificate age, days

34

Certificate validity, days

89

Page requests

6

Provider verdicts

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

HTTP headers

Server
hcdn
Content-type
text/html; charset=UTF-8
X-powered-by
PHP/8.3.31
Content-security-policy
upgrade-insecure-requests
Original source fields · JSON
Uuid
019ef8d8-4154-720c-9914-2499ea0d48b7
Final url
https://ledegers.co.com/
Status
200
Ip
147.79.72.46
Contacted domains
[
    "fonts.googleapis.com",
    "hpanel.hostinger.com",
    "fonts.gstatic.com",
    "assets.hostinger.com"
]
Contacted IP addresses
[
    "192.178.218.94",
    "104.16.210.83",
    "142.251.167.95",
    "147.79.72.46"
]
Asns
[
    "15169",
    "13335",
    "47583"
]
Countries
[
    "US"
]
Linked domains
[
    "hpanel.hostinger.com",
    "support.hostinger.com"
]
Document hash
d189b76f3225c8dadc69205caaa08079a830fd97f7a888a186f527c3cd6a3ad6
Cookies
[
    "__cf_bm"
]
Tls
{
    "san": [
        "ledegers.co.com",
        "www.ledegers.co.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "R13",
    "subject": "ledegers.co.com",
    "protocol": "TLS 1.3",
    "valid_to": "2026-08-19T04:42:59Z",
    "valid_from": "2026-05-21T04:43:00Z"
}
Domain age days
95
Apex age days
95
Tls age days
34
Tls valid days
89
Requests
6
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "hcdn",
    "content-type": "text/html; charset=UTF-8",
    "x-powered-by": "PHP/8.3.31",
    "content-security-policy": "upgrade-insecure-requests"
}
Separate monitor record · 2026-10-31 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
019ef8d8-4154-720c-9914-2499ea0d48b7
score
0
malicious
false
result_at
2026-10-31T04:30:13Z
enriched_at
2026-10-31T09:10:58Z
source_timestamps
{"urlscan_result_at":"2026-10-31 05:30:13","urlscan_enriched_at":"2026-10-31 10:10:58"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Report ID

ad0621af-4b0e-4109-9120-49af62ede65d

Final URL

https://ledegers.co.com/

HTTP response

200

Navigation history

  • URL
    https://ledegers.co.com/
    Status
    200

DOM structure hash

93d14127ff6a54a6bca70f4f691dfd571ce9ab2a2f1c8ac4fbf74c67e284af42

Document hash

d189b76f3225c8dadc69205caaa08079a830fd97f7a888a186f527c3cd6a3ad6

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    ledegers.co.com
    Type
    A
    Value
    2.57.91.87
  • Name
    ledegers.co.com
    Type
    A
    Value
    88.222.222.6
  • Name
    ledegers.co.com
    Type
    AAAA
    Value
    2a02:4780:84:a5f1:69e4:3ab7:facd:9f6d
  • Name
    ledegers.co.com
    Type
    AAAA
    Value
    2a02:4780:84:66a9:d03b:b57d:495e:181e

DNSSEC valid

No

IP address

127.0.1.47

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

Original source fields · JSON
Uuid
ad0621af-4b0e-4109-9120-49af62ede65d
Final url
https://ledegers.co.com/
Status
200
History
[
    {
        "url": "https://ledegers.co.com/",
        "status": 200
    }
]
DOM structure hash
93d14127ff6a54a6bca70f4f691dfd571ce9ab2a2f1c8ac4fbf74c67e284af42
Document hash
d189b76f3225c8dadc69205caaa08079a830fd97f7a888a186f527c3cd6a3ad6
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "ledegers.co.com",
        "type": "A",
        "value": "2.57.91.87"
    },
    {
        "name": "ledegers.co.com",
        "type": "A",
        "value": "88.222.222.6"
    },
    {
        "name": "ledegers.co.com",
        "type": "AAAA",
        "value": "2a02:4780:84:a5f1:69e4:3ab7:facd:9f6d"
    },
    {
        "name": "ledegers.co.com",
        "type": "AAAA",
        "value": "2a02:4780:84:66a9:d03b:b57d:495e:181e"
    }
]
Dnssec valid
false
Ip
127.0.1.47

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

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 10 / 100 · 2026-10-31T00:53:46Z

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-31T00:53:46Z
source_timestamp
2026-10-31 01:53:46
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
ledegers.co.com — Hostinger site-ready landing page
ai_description
PhishDestroy describes the Hostinger-branded site-ready landing page captured at ledegers.co.com with two help links.
ai_summary
The captured page at ledegers.co.com shows a Hostinger-branded landing screen with a Ukrainian heading announcing that the site is ready to work, followed by a short instruction to upload the site's files. Two purple help links open in new tabs: one on moving a site to Hostinger and another on installing WordPress with an auto-installer, each paired with an external-link icon. The stored VirusTotal domain result reports 4 detections out of 92 engines. DNS8 reported "phishing"; SOCRadar reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-31 01:49:53
revision
147e98d1ec03aab2a01c1c6324f748e8d3c4e7c6a6e1cbda43efc3dd1a0bc6fc
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 23 fields

Mail configuration

MX records
  • mx1.hostinger.com
  • mx2.hostinger.com
SPF record
v=spf1 include:_spf.mail.hostinger.com ~all
DKIM
  • hostingermail-a
DMARC
Yes
DKIM key size, bits
2048
SPF lookups
3

CAA records

Domain
ledegers.co.com

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Page title and metadata

Page title
Страница по умолчанию
Description
Страница по умолчанию

Trackers

Requests
6
Observed services
  • Name
    Google Fonts
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    2
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    2

Forms and mixed content

Upgrades insecure requests
Yes
Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
30
TLS
41
Waiting
44
Connection
6
Download
2
Response time, ms
123

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

Carbon estimate

Bytes
16560
CO₂, grams
0.0006
Cleaner than, %
61

DNS servers

Nameservers
  • IP address
    172.64.53.7
    Host
    apollo.dns-parking.com
  • IP address
    172.64.52.164
    Host
    athena.dns-parking.com
DNS zone
ledegers.co.com

Cookies

Cookies
  • Name
    __cf_bm
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    None

Location

IP address
2a02:4780:42:5591:e6b:606:93db:e4eb
ASN
47583
Organization
Hostinger International Limited
City
Frankfurt am Main
Country
DE

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
ledegers.co.com

DNS records

A
  • 92.113.16.145
  • 92.113.23.237
MX
  • Mail server
    mx2.hostinger.com
    Priority
    10
  • Mail server
    mx1.hostinger.com
    Priority
    5
NS
  • apollo.dns-parking.com
  • athena.dns-parking.com
SOA
Primary nameserver
athena.dns-parking.com
Hostmaster
dns.hostinger.com
Serial
2026102901
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
600
TXT
  • v=spf1 include:_spf.mail.hostinger.com ~all
AAAA
  • 2a02:4780:43:c582:34b4:e342:7256:4097
  • 2a02:4780:42:5591:e6b:606:93db:e4eb

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
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
upgrade-insecure-requests
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
2a02:4780:42:5591:e6b:606:93db:e4eb
IP version
6

Redirects

Redirect chain
  • https://ledegers.co.com

Subdomains

Count
2
Subdomains
  • wob1.ledegers.co.com
  • www.ledegers.co.com

Page links

External link addresses
  • https://hpanel.hostinger.com/
  • https://support.hostinger.com/en/articles/4455931-how-can-i-migrate-website-to-hostinger
  • https://support.hostinger.com/en/articles/3220304-how-to-install-wordpress-using-auto-installer
External links
3

HTTP headers

Response headers
Server
hcdn
Content-type
text/html; charset=UTF-8
X-powered-by
PHP/8.3.36
Content-security-policy
upgrade-insecure-requests
Original source fields · JSON
Mail configuration
{
    "mx": [
        "mx1.hostinger.com",
        "mx2.hostinger.com"
    ],
    "spf": "v=spf1 include:_spf.mail.hostinger.com ~all",
    "dkim": [
        "hostingermail-a"
    ],
    "dmarc": true,
    "dkim_bits": 2048,
    "spf_lookups": 3
}
Caa records
{
    "domain": "ledegers.co.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Page title and metadata
{
    "title": "Страница по умолчанию",
    "description": "Страница по умолчанию"
}
Trackers
{
    "requests": 6,
    "trackers": [
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 2
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 2
        }
    ]
}
Forms and mixed content
{
    "upgrade_insecure": true,
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 30,
        "tls": 41,
        "wait": 44,
        "connect": 6,
        "download": 2
    },
    "response_ms": 123
}
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
    ]
}
Carbon
{
    "bytes": 16560,
    "co2_grams": 0.0006,
    "cleaner_than": 61
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.53.7",
            "host": "apollo.dns-parking.com"
        },
        {
            "ip": "172.64.52.164",
            "host": "athena.dns-parking.com"
        }
    ],
    "zone": "ledegers.co.com"
}
Cookies
{
    "cookies": [
        {
            "name": "__cf_bm",
            "secure": true,
            "http_only": true,
            "same_site": "None"
        }
    ]
}
Location
{
    "ip": "2a02:4780:42:5591:e6b:606:93db:e4eb",
    "asn": "47583",
    "org": "Hostinger International Limited",
    "city": "Frankfurt am Main",
    "country": "DE"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "ledegers.co.com"
}
DNS records
{
    "A": [
        "92.113.16.145",
        "92.113.23.237"
    ],
    "MX": [
        "{\"exchange\": \"mx2.hostinger.com\", \"priority\": 10}",
        "{\"exchange\": \"mx1.hostinger.com\", \"priority\": 5}"
    ],
    "NS": [
        "apollo.dns-parking.com",
        "athena.dns-parking.com"
    ],
    "SOA": "{\"nsname\": \"athena.dns-parking.com\", \"hostmaster\": \"dns.hostinger.com\", \"serial\": 2026102901, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 600}",
    "TXT": [
        "v=spf1 include:_spf.mail.hostinger.com ~all"
    ],
    "AAAA": [
        "2a02:4780:43:c582:34b4:e342:7256:4097",
        "2a02:4780:42:5591:e6b:606:93db:e4eb"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": "upgrade-insecure-requests",
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "2a02:4780:42:5591:e6b:606:93db:e4eb",
    "family": 6
}
Redirects
{
    "chain": [
        "https://ledegers.co.com"
    ]
}
Subdomains
{
    "count": 2,
    "subdomains": [
        "wob1.ledegers.co.com",
        "www.ledegers.co.com"
    ]
}
Page links
{
    "external": [
        "https://hpanel.hostinger.com/",
        "https://support.hostinger.com/en/articles/4455931-how-can-i-migrate-website-to-hostinger",
        "https://support.hostinger.com/en/articles/3220304-how-to-install-wordpress-using-auto-installer"
    ],
    "external_count": 3
}
HTTP headers
{
    "headers": {
        "server": "hcdn",
        "content-type": "text/html; charset=UTF-8",
        "x-powered-by": "PHP/8.3.36",
        "content-security-policy": "upgrade-insecure-requests"
    }
}

Questions about ledegers.co.com

Is ledegers.co.com legit?

PhishDestroy rates ledegers.co.com as critical risk (87/100) from the recorded evidence; it was first recorded on 2026-10-31. Stored VirusTotal result: 4/92 engines flagged. malicious: 4. suspicious: 0. Analysis time (as stored): 2026-10-13T09:41:08Z. Retrieved (as stored): 2026-10-31T00:47:17Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is ledegers.co.com safe to connect a wallet?

This report does not record which wallet requests ledegers.co.com 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 ledegers.co.com?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 3 captures

Cloudflare Radar 1 / 3 Used in the analysis Source file SHA-256: d20de79078d8277956037eaea79398519b82aca2db6d2a5b519984b1442bd414 SHA-256 of the prepared copy given to the model: 67703016e0f04e2d34c5ca02fba8e35ebf27a0e1460265b8049fed446e364ed9
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://ledegers.co.com/
Position1 / 3
Open capture Source Report Wayback Download
All capture links and hashes (3)

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 99 report ↗
IP Reputation Germany92.113.23.79 abuse score 0/100 0 reports checked Oct 31, 2026 last reported
Platform provider Moniker Online Services
Abuse contact["abuse@moniker.com"]
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 31, 2026
DOM Analysisanalyzed Oct 31, 2026score 10/1001 brand signal
Submitted URLhttp://ledegers.co.com/
Favicon Hash
Observed page title
Страница по умолчанию
Automated brand references
Wordpress
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 41 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Germany92.113.23.79
Network ASN
AS47583
AS name
AS-HOSTINGER Hostinger International Limited, CY
Organization
Hostinger International Limited
Observed location
GermanyFrankfurt am Main, DE
Server header
hcdn

Nameservers 2

  • apollo.dns-parking.com
  • athena.dns-parking.com

SOA

  • nsname: athena.dns-parking.com
  • hostmaster: dns.hostinger.com
  • serial: 2026102901
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 600

Mail routing 2 MX records

  • mx2.hostinger.compriority 10
  • mx1.hostinger.compriority 5

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-09-18 03:01:44
Valid until
2026-12-17 03:01:43
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintf6988de046faec6377287c3cc4fb47eca129fb1a5e09e79646475fca3d1588d7
Certificate names · 2 SANs
  • ledegers.co.com
  • www.ledegers.co.com

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

viewdns.info · 92.113.23.79rapiddns.io

Latest Classified Outcome 2026-11-05 00:09:31 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-05 00:09:31 UTC
RDAP registration
Observed timeline last reachable: 2026-11-05 00:09:31 UTC last content: 2026-11-05 00:09:31 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 subdomains2

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

  • wob1.ledegers.co.comDomain record
  • www.ledegers.co.comDomain record
Technologies · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

4 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 4 detections
DNS8
SOCRadar
Gridinsoft
alphaMountain.ai

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of ledegers.co.com · checked Oct 31, 2026

100
Good
Performance
FCP
1.52 s
First Contentful Paint
LCP
1.52 s
Largest Contentful Paint
CLS
0.005
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
1.52 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

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

Archived HTTP response HTTP 200
Requested URL: http://ledegers.co.com/
Final URL: https://ledegers.co.com/
Страница по умолчанию
Страница по умолчанию
Response
HTTP 200
HTML body
16.2 KB
Compressed
5.7 KB
Links
0 internal · 3 external
Detected technologies
wordpress
Selected response headers
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/8.3.36
Content-Encoding: gzip
Server: hcdn
Security headers present
Content-Security-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: 7e66be446e47e903d5e13e41eb87953077d3d75f04b874617396a81474e7a108
Saved response-header values · 15
alt-svc
h3=":443"; ma=86400
Connection
keep-alive
Content-Encoding
gzip
Content-Security-Policy
upgrade-insecure-requests
Content-Type
text/html; charset=UTF-8
Date
Sat, 31 Oct 2026 00:16:38 GMT
panel
hpanel
platform
hostinger
Server
hcdn
Transfer-Encoding
chunked
Vary
Accept-Encoding
x-hcdn-cache-status
DYNAMIC
x-hcdn-request-id
5a2ffea3d57868374cd5f37c7cbab940-bnk-edge7
x-hcdn-upstream-rt
0.029
X-Powered-By
PHP/8.3.36

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

Archived
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: 6 SHA-256 hashes: 6 URLScan scan:

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

Open this scan on URLScan 019ef8d8-4154-720c-9914-2499ea0d48b7 ↗

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

    live_content

    content_served

  3. Availability monitor · Recorded state

    live_content

    content_served

  4. Availability monitor · Recorded state

    protected→live_content

    content_served

  5. Availability monitor · Recorded state

    protected

    captcha · challenge

Earlier observations 1
  1. Availability monitor · Recorded state

    live_content

    content_served

All retained availability observations24

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-05 01:09:31.000000
    Evidence SHA-256
    3cae5dcaf4db3d1c5026873e8fb6009801e457233e741e93b9f59d4f61327127
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-05 01:09:31
    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-05 01:09:31.000000
    Evidence SHA-256
    3cae5dcaf4db3d1c5026873e8fb6009801e457233e741e93b9f59d4f61327127
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-05 01:09:31
    Evidence reason
    alive_content
  3. 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-04 13:11:05.000000
    Evidence SHA-256
    049255d3ce1ba7242608d764ebddeef0c59ddccfd1fce34400c7299e8b7a672a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-04 13:11:05
    Evidence reason
    alive_content
  4. 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-04 13:11:05.000000
    Evidence SHA-256
    049255d3ce1ba7242608d764ebddeef0c59ddccfd1fce34400c7299e8b7a672a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-04 13:11:05
    Evidence reason
    alive_content
  5. 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-04 11:21:00.849465
    Evidence SHA-256
    94a9ae3d707b6cefa8168740bcb51c53137079a19bc0cd5bd77154e93c534a76
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-04 11:21:00.849465
    Evidence reason
  6. 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-03 11:20:42.213040
    Evidence SHA-256
    7f511289ea6b6d1520a698f000d7fb3be1609f5f14dbf5ab5bf1c58eb4dbb974
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-03 11:20:42.213040
    Evidence reason
  7. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 12:31:22.000000
    Evidence SHA-256
    3ea72b423cc84182f6ca5d5422dbde6d099f0c92c700ce5b719c05c23cbc1dd8
    Evidence timestamp as recorded
    2026-11-02 12:31:22
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  8. 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 12:31:22.000000
    Evidence SHA-256
    cd7af256ae6f4bc05ad601e9d6c8b2952a12567bbb1b2f7238098c19dca75766
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 12:31:22
    Evidence reason
    alive_content
  9. 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-02 11:20:40.834886
    Evidence SHA-256
    6b72dd67b3184766be6163de1e7b9604e36c85641b1d2618e2bdbe21069459a2
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 11:20:40.834886
    Evidence reason
  10. 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:36.000000
    Evidence SHA-256
    76a1ec3e272146b12bdd186f8232e79ff806c245041e5de6f02f8c848a8f3d6d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:05:36
    Evidence reason
    alive_content
  11. 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:36.000000
    Evidence SHA-256
    76a1ec3e272146b12bdd186f8232e79ff806c245041e5de6f02f8c848a8f3d6d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:05:36
    Evidence reason
    alive_content
  12. 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:06:20.000000
    Evidence SHA-256
    f984c480e47b3b6dbe80c1f0cb61aeda39f5b9c278b7a28e1f5de58d41f00e46
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:06:20
    Evidence reason
    alive_content
  13. 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:06:20.000000
    Evidence SHA-256
    f984c480e47b3b6dbe80c1f0cb61aeda39f5b9c278b7a28e1f5de58d41f00e46
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:06:20
    Evidence reason
    alive_content
  14. 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 11:20:10.198716
    Evidence SHA-256
    b2987bb7a7acc32f1f9011b7a56a5a9a8539c203c0dded9abde43c0e22a9adeb
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 11:20:10.198716
    Evidence reason
  15. 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:44.000000
    Evidence SHA-256
    48a419e36341a1697667057798435029d5d76deb1bbae637549d058b5757eec6
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 03:49:44
    Evidence reason
    alive_content
  16. 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:44.000000
    Evidence SHA-256
    48a419e36341a1697667057798435029d5d76deb1bbae637549d058b5757eec6
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 03:49:44
    Evidence reason
    alive_content
  17. 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 00:04:37.000000
    Evidence SHA-256
    10cd0ae9c4ed46bf9eea0f3c1550916e14376ba934572a5bda1b7b3766339aaf
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:04:37
    Evidence reason
    alive_content
  18. 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 00:04:37.000000
    Evidence SHA-256
    10cd0ae9c4ed46bf9eea0f3c1550916e14376ba934572a5bda1b7b3766339aaf
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:04:37
    Evidence reason
    alive_content
  19. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    captcha
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    403
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:04:56.000000
    Evidence SHA-256
    68fc50f09258e370f32a92f593c3889fe674b6b57b6aee906595c3ad2f1de250
    HTTP probe value as recorded
    403
    Evidence timestamp as recorded
    2026-10-31 12:04:56
    Evidence reason
    captcha
  20. http_observationprotected
    Observation source
    http_observation
    Cause
    captcha
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    403
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:04:56.000000
    Evidence SHA-256
    68fc50f09258e370f32a92f593c3889fe674b6b57b6aee906595c3ad2f1de250
    HTTP probe value as recorded
    403
    Evidence timestamp as recorded
    2026-10-31 12:04:56
    Evidence reason
    captcha
  21. 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 11:20:09.112163
    Evidence SHA-256
    b5c6551e799cfe4d3cb298004536f14652a7bd27158039d9a8bde93b0611124a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 11:20:09.112163
    Evidence reason
  22. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    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 03:00:13.000000
    Evidence SHA-256
    c43e44fc0ebaa1477b9967b81c98c0627fe84e0ffcefe0ebf7398b0b33d8b06f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:00:13
    Evidence reason
    alive_content
  23. 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 03:00:13.000000
    Evidence SHA-256
    c43e44fc0ebaa1477b9967b81c98c0627fe84e0ffcefe0ebf7398b0b33d8b06f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:00:13
    Evidence reason
    alive_content
  24. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 01:19:51.795542
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

Recorded events: 11. 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
    ledegers.co.com detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Automated brand label: Wordpress · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 9 of 9
  • Spamhaus DBL
    Spamhaus DBL recorded: phishing domain
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 99
  • 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: 4/92
  • Automated brand label: Wordpress
    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

4 entries
  1. Wayback Machine

    Page archived

    View source
  2. Added to PhishDestroy

    ledegers.co.com

    View source
  3. VirusTotal

    4/92 engine detections

    View source
  4. URLScan

    Malicious · engine verdict · score 99

    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

Community intelligence

1 community report

CategoryPhishing

Detection Summary The Anti-Phishing Volunteers & Associates Security Incident Response System has flagged this as a domain threat, classified as phishing attack against Ledger. Threat detected at 2026-03-26T00:26:32.234Z.

Check for cloaking

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

ledegers.co.com

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 4 det. ChainPatrol ChainAbuse 1 report URLQuery SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Third-Party Detection — ChainAbuse
1 report filed for ledegers.co.com · category: Phishing · source checked
Flagged by Anti-Phishing Volunteers & Associates · Mar 26, 2026 — automated submission, not a user testimony. Source: ChainAbuse (TRM Labs).
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

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

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

Template-based draft • optional AI wording assistance requires separate consent

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including ledegers.co.com)
  • Communications — emails, texts, phone numbers, usernames the scammer used

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

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

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

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

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

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

Check Any Domain

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

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

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

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/ledegers.co.com"
  title="PhishDestroy threat report for ledegers.co.com"
  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>