Skip to security report
Recorded security signals
Stored VirusTotal result: 3/91 engines flagged. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
ledgrr.com favicon

ledgrr.com

In short

The captured page for ledgrr.com presents a CortexTranslate interface focused on neural real-time translation services. Users are greeted by promotional headings, navigation options, and an interactive demonstration module allowing text input selection between languages for immediate processing and translation testing.

“CortexTranslate | Neural Real-Time Translation”

Registrar
United StatesNameSilo
Resolved IP
Romania185.244.151.84Host Sailor Ltd
Registered
Nov 14, 2024
First observed
Feb 26, 2026
PhishDestroy assessment Critical
78/100
Evidence score
First observed Feb 26, 2026 22:23 UTC · PhishDestroy
VirusTotal detections: 3/91
VirusTotal
engine detections
URLScan
engine verdict · score 98
Page captures
open gallery
Domain age
registered 2024-11-14 according to RDAP · source data differ
Feb 26, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded ledgrr.com on 2026-02-26. Stored VirusTotal result: 3/91 engines flagged. Risk: critical (78/100). Registrar: NameSilo. Hosting: HS Host Sailor Ltd, AE. Do not enter credentials or connect a wallet.

Critical
VirusTotal
3 / 91
Scam type (automated label)
Crypto Scam
Hosting
Romania185.244.151.84Host Sailor Ltd
Registrar
United StatesNameSilo
Registered
Nov 14, 2024
Page captures
2

Capture recorded with this analysis · Stored capture · Exact capture time not retained
SHA-256: 8c31684fb87ba4519c835da617671ce64c8456f4523dff0250227dd98d90cf4a

PhishDestroy analysis, reviewed version

The captured page for ledgrr.com presents a CortexTranslate interface focused on neural real-time translation services. Users are greeted by promotional headings, navigation options, and an interactive demonstration module allowing text input selection between languages for immediate processing and translation testing.

In security evaluations, VirusTotal flagged this record as suspicious, resulting in 3 detections out of 91 total security vendor engines. Specific flagging vendors identifying risks on this URL include CRDF and Gridinsoft, highlighting potential security concerns associated with the domain.

Source evidenceVirusTotal 3 / 91 9 sources

VirusTotal

3 / 91 engine detections

Retrieved / checked:
Open report

URLScan

Malicious · engine verdict · score 98

Open report
URLScanOriginal source recordObserved: 19 fields

Observed: · Retrieved:

Report ID

019cf62f-e7b0-7667-8737-66b4c75ebcbb

Final URL

https://ledgrr.com/

HTTP response

200

IP address

185.244.151.84

Reverse DNS (PTR)

hosting2.ro.hostsailor.com

Contacted domains

  • cdnjs.cloudflare.com
  • connect.facebook.net
  • lifetimeprotect.world

Contacted IP addresses

  • 157.240.0.6
  • 104.17.24.14
  • 104.21.8.4
  • 185.244.151.84

Autonomous systems (ASN)

  • 32934
  • 13335
  • 60117

Server countries

  • DE
  • RO

Document hash

0c78d44fe0e6dc79cb2080be86cffbf829390f09852e88ede4be8e93a356443c

JavaScript globals

  • b
  • inputText
  • outputText
  • sourceLang
  • targetLang
  • translateBtn
  • translations
  • observer

TLS session and certificate

Subject alternative names
  • *.ledgrr.com
  • ledgrr.com
Cipher
AES_128_GCM
Issuer
R13
Subject
*.ledgrr.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

1783

Differs from the registration date in RDAP (2024-11-14), which gives 486 days on the scan date 2026-03-16. The two sources disagree; both values are kept as recorded.

Registered domain age, days

1783

Differs from the registration date in RDAP (2024-11-14), which gives 486 days on the scan date 2026-03-16. The two sources disagree; both values are kept as recorded.

Certificate age, days

41

Certificate validity, days

89

Page requests

6

Provider verdicts

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

HTTP headers

Server
LiteSpeed
Content-type
text/html
Original source fields · JSON
Uuid
019cf62f-e7b0-7667-8737-66b4c75ebcbb
Final url
https://ledgrr.com/
Status
200
Ip
185.244.151.84
Ptr
hosting2.ro.hostsailor.com
Contacted domains
[
    "cdnjs.cloudflare.com",
    "connect.facebook.net",
    "lifetimeprotect.world"
]
Contacted IP addresses
[
    "157.240.0.6",
    "104.17.24.14",
    "104.21.8.4",
    "185.244.151.84"
]
Asns
[
    "32934",
    "13335",
    "60117"
]
Countries
[
    "DE",
    "RO"
]
Document hash
0c78d44fe0e6dc79cb2080be86cffbf829390f09852e88ede4be8e93a356443c
Globals
[
    "b",
    "inputText",
    "outputText",
    "sourceLang",
    "targetLang",
    "translateBtn",
    "translations",
    "observer"
]
Tls
{
    "san": [
        "*.ledgrr.com",
        "ledgrr.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "R13",
    "subject": "*.ledgrr.com",
    "protocol": "TLS 1.3",
    "valid_to": "2026-05-03T19:04:10Z",
    "valid_from": "2026-02-02T19:04:11Z"
}
Domain age days
1783

Differs from the registration date in RDAP (2024-11-14), which gives 486 days on the scan date 2026-03-16. The two sources disagree; both values are kept as recorded.

Apex age days
1783

Differs from the registration date in RDAP (2024-11-14), which gives 486 days on the scan date 2026-03-16. The two sources disagree; both values are kept as recorded.

Tls age days
41
Tls valid days
89
Requests
6
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 98,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "LiteSpeed",
    "content-type": "text/html"
}
Separate monitor record · date not recorded

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

record_source
domain_monitor.urlscan
uuid
019cf62f-e7b0-7667-8737-66b4c75ebcbb
score
null
malicious
null
result_at
null
enriched_at
2026-03-25T12:38:29Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-03-25 13:38:29"}
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: 12 fields

Observed: · Retrieved:

Report ID

9f9c9085-6f8c-44bb-971c-03ef1f2d6a80

Final URL

https://ledgrr.com/

HTTP response

200

Navigation history

  • URL
    https://ledgrr.com/
    Status
    200

DOM structure hash

806fd966904e3b5789cc9def4f5a74295ed1ce5fed8fbc80c740f9cf2bd4ec7e

Document hash

451725d6f8b754d79b4149279eea8881c42d8ffd9f73106bbbcd6b79f685b02e

Domain risk categories

  • Business
  • Business & Economy
  • Technology

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    ledgrr.com
    Type
    A
    Value
    185.244.151.84

DNSSEC valid

No

IP address

185.244.151.84

Registration record

Registrar
NameSilo, LLC
Registered
Updated
Expires
Nameservers
  • ns3.ro.hostsailor.com
  • ns4.ro.hostsailor.com
Original source fields · JSON
Uuid
9f9c9085-6f8c-44bb-971c-03ef1f2d6a80
Final url
https://ledgrr.com/
Status
200
History
[
    {
        "url": "https://ledgrr.com/",
        "status": 200
    }
]
DOM structure hash
806fd966904e3b5789cc9def4f5a74295ed1ce5fed8fbc80c740f9cf2bd4ec7e
Document hash
451725d6f8b754d79b4149279eea8881c42d8ffd9f73106bbbcd6b79f685b02e
Domain risks
[
    "Business",
    "Business & Economy",
    "Technology"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "ledgrr.com",
        "type": "A",
        "value": "185.244.151.84"
    }
]
Dnssec valid
false
Ip
185.244.151.84
Registration record
{
    "registrar": "NameSilo, LLC",
    "created": "2024-11-14T22:22:49Z",
    "updated": "2026-02-16T14:16:25Z",
    "expires": "2026-11-14T22:22:49Z",
    "nameservers": [
        "ns3.ro.hostsailor.com",
        "ns4.ro.hostsailor.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

Gridinsoft

No report found

Open report
Stored collection fields

A missing report is not a trust verdict. Legacy zeroes remain in the stored record; the measured trust score is unavailable.

normalized_record
{"trust_score":null,"status":"not_found","signals":[],"report_url":null,"observed_at":null,"rating":null,"review_count":0,"request_url":"https://gridinsoft.com/online-virus-scanner/url/ledgrr-com"}
stored_record
{"gs_trust_score":0,"gs_status":"not_found","gs_signals":null,"gs_url":"https://gridinsoft.com/online-virus-scanner/url/ledgrr-com","gs_rating":null,"gs_reviews":0}

PhishDestroy DOM

78 / 100 · heuristic score · 1 brand reference · 1 classification

Open report
Separate monitor score · 0 / 100 · 2026-07-09T02:21:44Z

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
0
analyzed_at
2026-07-09T02:21:44Z
source_timestamp
2026-07-09 04:21:44
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
ledgrr.com CortexTranslate Neural Translation Page
ai_description
PhishDestroy analyzes ledgrr.com, which hosts a neural real-time translation service interface promoting automated language tools.
ai_summary
The captured page for ledgrr.com presents a CortexTranslate interface focused on neural real-time translation services. Users are greeted by promotional headings, navigation options, and an interactive demonstration module allowing text input selection between languages for immediate processing and translation testing. In security evaluations, VirusTotal flagged this record as suspicious, resulting in 3 detections out of 91 total security vendor engines. Specific flagging vendors identifying risks on this URL include CRDF and Gridinsoft, highlighting potential security concerns associated with the domain.
ai_generated_by
threat-v6-gemini
ai_generated_at
2026-10-29 15:03:09
revision
abb5487cecfc6923f790aa29aeda3f2d51bb3deded5303b3076ce0e86f239953
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
Network Security Intelligence Registrar context
Registrar context NameSilo
Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
Review source investigation

Questions about ledgrr.com

Is ledgrr.com legit?

PhishDestroy rates ledgrr.com as critical risk (78/100) from the recorded evidence; it was first recorded on 2026-02-26. Stored VirusTotal result: 3/91 engines flagged. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is ledgrr.com safe to connect a wallet?

This report does not record which wallet requests ledgrr.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 ledgrr.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

Last checked

Stored Capture · 2 captures

All capture links and hashes (2)
ledgrr.com: caution — 3/91 VirusTotal engines. PhishDestroy risk score 78/100 (critical).
Social preview card ledgrr.com: caution — 3/91 VirusTotal engines. PhishDestroy risk score 78/100 (critical). v 22a9c8c7b743

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 98 report ↗
IP Reputation Romania185.244.151.84 abuse score 0/100 0 reports checked Sep 14, 2026 last reported
Registrar NameSilo US(US) PhishDestroy Investigation
Abuse contactabuse@namesilo.com
RegistrationCreated Nov 14, 2024 — Expires Nov 14, 2026
Elapsed Since First Report 196 days
What we count Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Unverified.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedFeb 26, 2026
DOM Analysisanalyzed Jul 9, 2026score 78/1001 brand signal
Favicon Hash
Observed page title
CortexTranslate | Neural Real-Time Translation
Automated brand references
Ledger
TLS Certificate
Issued by Let's Encrypt / YR2

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Romania185.244.151.84
Network ASN
AS60117
AS name
HS Host Sailor Ltd, AE
Organization
Host Sailor Ltd
Observed location
RomaniaBucharest, RO
Server header
LiteSpeed

Nameservers 1

  • ns4.ro.hostsailor.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-06-08 16:30:24
Valid until
2026-09-06 16:30:23
Hostname coverage
Stored certificate expired or unverified
Validity
Stored certificate expired
Collection time
2026-07-09 01:01:00 UTC
Collection source
PhishDestroy collector
Certificate fingerprint63fdf3a673c40f3a79cfa3c4d0d501075312ad0d28e63cdc8731fbf4e312c639
Certificate names · 2 SANs
  • *.ledgrr.com
  • ledgrr.com

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

Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

3 / 91 security vendors flagged this domain
View on VT
Previous stored snapshot: 3 detections
CRDF
Gridinsoft
SOCRadar
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of ledgrr.com · checked Mar 2, 2026

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

Availability observations

Last reachable observation

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

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-29 05:39 UTC.

Open this scan on URLScan 019cf62f-e7b0-7667-8737-66b4c75ebcbb ↗

Check for cloaking

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

Cloaking could not be checked

The site did not answer our scanner (host unreachable).

ledgrr.com
Saved result
Unreachable
Stored observation history3

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

  1. Domain monitor · Recorded state

    Unavailable→Reachable

  2. Domain monitor · Recorded state

    Reachable→Unavailable

  3. Domain monitor · Recorded state

    https://radar.cloudflare.com/scan/b504cdeb-44c9-4590-a811-e332b47ca32f

Separate monitor HTTP observation

Source: domain_monitor. This stored snapshot does not establish current availability.

Observed · UTC
Recorded HTTP status
No response code recorded
Original source timestamp
2026-02-24 02:16:15
All retained availability observations71

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_probeunknown
    Observation source
    current_http_probe
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-07 04:18:34.000000
    Evidence SHA-256
    40cefd10abfe4989dcd779eb474cc61f91a89d927b959cd13cf0b99bdc53aebf
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 04:18:34
    Evidence reason
    unavailable
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 04:18:34.000000
    Evidence SHA-256
    40cefd10abfe4989dcd779eb474cc61f91a89d927b959cd13cf0b99bdc53aebf
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 04:18:34
    Evidence reason
    unavailable
  3. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-06 23:21:40.556826
    Evidence SHA-256
    2071dfbc1c6ae55fbd72318bd0bd5b8ac6720ae3a22d4fd33ac3fef7bf7b47da
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-06 23:21:40.556826
    Evidence reason
  4. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-05 23:21:20.401484
    Evidence SHA-256
    6561edb8793c530bd35b9930c0ef92bee67e8e1395a2c6e53ebfe984a32e4303
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-05 23:21:20.401484
    Evidence reason
  5. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-05 04:16:17.000000
    Evidence SHA-256
    aa3554a888a66b72d173c7a41cf5616670473331e45f79e7f360c4e13d263def
    Evidence timestamp as recorded
    2026-11-05 04:16:17
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  6. 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-11-05 04:16:17.000000
    Evidence SHA-256
    efe1d93baf6a5717b98c35bd5f8cff42521546a6851aa1cc388850576f606789
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-05 04:16:17
    Evidence reason
    unavailable
  7. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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 23:21:01.569244
    Evidence SHA-256
    23fc21981d3f4a4c85bb59e9f7d4d9f56b19dcaacedad495e573240b5ed9121e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-04 23:21:01.569244
    Evidence reason
  8. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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 23:21:00.551669
    Evidence SHA-256
    93de4ce3edcedd421525733b44961d482bf295f4b8d35b7851f110ca6f86698b
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-03 23:21:00.551669
    Evidence reason
  9. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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 23:20:40.877283
    Evidence SHA-256
    25c5ac0172f94ac6589ba15d57bef64f7b2aa3a7f5fe700edf28b10d7afed8a7
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 23:20:40.877283
    Evidence reason
  10. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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
  11. 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-11-01 03:29:56.000000
    Evidence SHA-256
    441d6a3333d1ad5d453092fcc48fa165e25c02bfcac4085ae54a76c0017ece3e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 03:29:56
    Evidence reason
    unavailable
  12. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-01 03:29:56.000000
    Evidence SHA-256
    c55e1669b2252a12ba75c50bd0c95dd79d48e7945c39bfd90810579a1644e5b0
    Evidence timestamp as recorded
    2026-11-01 03:29:56
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  13. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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
  14. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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 04:06:51.000000
    Evidence SHA-256
    2a0384c876a658b5021b982670ad6d2a659a4cee9d50455baaf71935829f08b9
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 04:06:51
    Evidence reason
    unavailable
  15. 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-31 04:06:51.000000
    Evidence SHA-256
    2a0384c876a658b5021b982670ad6d2a659a4cee9d50455baaf71935829f08b9
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 04:06:51
    Evidence reason
    unavailable
  16. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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:03:05.966399
    Evidence SHA-256
    50a5215b0c566b7822d085a87e391f0469a076c3f7f015e688ebee68afcfcc96
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 17:03:05.966399
    Evidence reason
  17. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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 17:03:05.221734
    Evidence SHA-256
    2f984a79e84ab655d11fb271d10d9444f6b23d40b345ed653cfbb2faf803b616
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 17:03:05.221734
    Evidence reason
  18. 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 04:48:51.000000
    Evidence SHA-256
    20ce0463672bac7a60a09e8e370701b7d78b4d6ad7c7e2785476a96e4c4d9d81
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 04:48:51
    Evidence reason
    unavailable
  19. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-29 04:48:51.000000
    Evidence SHA-256
    bdbc20ca8365543f25784fcc75d003d12cb34a650f16f7c127cf4dcb04be08cd
    Evidence timestamp as recorded
    2026-10-29 04:48:51
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  20. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-28 09:55:10.533471
    Evidence SHA-256
    d7c171c3bc25387a314e97b9f8de814f4cae02ff9867fec22f1e7258a5a26a48
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-28 09:55:10.533471
    Evidence reason
  21. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 09:55:08.586816
    Evidence SHA-256
    fa8e9b8de0fa2ff3f2c60817f493162c8480eb1a7ff0a28e0a7abc823995c62f
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-27 09:55:08.586816
    Evidence reason
  22. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-27 03:43:21.000000
    Evidence SHA-256
    230b2fad15479d031ec61f74d9cee04fe1af74db95ba741b1250342d4c40686e
    Evidence timestamp as recorded
    2026-10-27 03:43:21
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  23. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 03:43:21.000000
    Evidence SHA-256
    798905feae7f55eaa8ba905174823ca67bcd0c6ca04a2c16ced9fbb869ed046f
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-27 03:43:21
    Evidence reason
    unavailable
  24. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-26 09:55:08.299319
    Evidence SHA-256
    37b5c19af06da555fb6055130c267aaeda09ed615e57f17df294ffe2591f7ef9
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-26 09:55:08.299319
    Evidence reason
  25. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-25 09:55:07.418941
    Evidence SHA-256
    f29421045a2f0d44850c6f52d6d8bbdf0829af36630a6ed5c83feca2dfe013b6
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 09:55:07.418941
    Evidence reason
  26. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-25 03:39:16.000000
    Evidence SHA-256
    2d66e7455cceab18931c33574ec54d95e86d2c20626c049fec663cfe3073c2ef
    Evidence timestamp as recorded
    2026-10-25 03:39:16
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  27. 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-25 03:39:16.000000
    Evidence SHA-256
    df041e86cf2b88d8b3500e327442981c359f07ef81cbad7f3e51feb4beb99f31
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 03:39:16
    Evidence reason
    unavailable
  28. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-23 22:56:16.207510
    Evidence SHA-256
    c5f098587335747ecb0284c1aaf394d9a7f57967b624ae64d7c6e3e96d6d5417
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-23 22:56:16.207510
    Evidence reason
  29. 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-23 04:17:46.000000
    Evidence SHA-256
    70c4e1ec88421794732ef9befc4a93a2181abe94ad7d60741c7aec6af17cf29d
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-23 04:17:46
    Evidence reason
    unavailable
  30. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-23 04:17:46.000000
    Evidence SHA-256
    98b61de9be6f1af6a8912f6403a15547d3efe250f328584f8468ec1c2f92bb02
    Evidence timestamp as recorded
    2026-10-23 04:17:46
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  31. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-22 22:55:15.888363
    Evidence SHA-256
    3b646e5bc1bac379c47f59c89fb9159326ef6c40d3366eb6dfd5fa43e677c4aa
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-22 22:55:15.888363
    Evidence reason
  32. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-21 16:53:36.928467
    Evidence SHA-256
    80d44683077929d57cc69d3d485aa4d0ee469673c8067e794714c21730456f32
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-21 16:53:36.928467
    Evidence reason
  33. 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-21 04:08:42.000000
    Evidence SHA-256
    3646db2a660841237334bdb4deca56bbda35d10d19adda55b197f2079a0785fc
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-21 04:08:42
    Evidence reason
    unavailable
  34. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-21 04:08:42.000000
    Evidence SHA-256
    ecf732cb66f7140c05e6d030df15aa887f3f2533f86b859f440322f2f40c4ee3
    Evidence timestamp as recorded
    2026-10-21 04:08:42
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  35. 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-20 10:21:37.183325
    Evidence SHA-256
    f6ebc34c637ae5924f85300e39eeddc978e4821086a9222c87005e67a3b0d797
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-20 10:21:37.183325
    Evidence reason
  36. 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-19 10:21:20.392196
    Evidence SHA-256
    470b54ea6ccbe7f04a3825ada981b64179b616b50f8ee2944c5c5cf09876edf4
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-19 10:21:20.392196
    Evidence reason
  37. 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-19 04:06:52.000000
    Evidence SHA-256
    a63d1187308407e5a2aee3000e0a12ab39474a22e649faee90f0ce008703e858
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-19 04:06:52
    Evidence reason
    unavailable
  38. 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
    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-19 04:06:52.000000
    Evidence SHA-256
    f540baa42a18c92886a623c8603144a504aad6b3ef97acaf07b83fe107e5fafe
    Evidence timestamp as recorded
    2026-10-19 04:06:52
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  39. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-18 10:21:15.144873
    Evidence SHA-256
    d137b34b07ce5d4f8c2c0144bb3a689c0914216b2acecc6045167a7531565b2d
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-18 10:21:15.144873
    Evidence reason
  40. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-17 03:59:33.000000
    Evidence SHA-256
    198030578ec8081dbb232f284c0d2d98f55ce5810967ec58750a9a356a498196
    Evidence timestamp as recorded
    2026-10-17 03:59:33
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  41. 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-17 03:59:33.000000
    Evidence SHA-256
    dbfd53ed40559e111641dbfd812e1e001f3a8eb97dfbe0a0d10b0a2b0be69ef4
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-17 03:59:33
    Evidence reason
    unavailable
  42. 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-16 22:22:38.733165
    Evidence SHA-256
    715151e070bd7bc191e99245412b910620c301fbdb64cf388d91d23b9dbf29da
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-16 22:22:38.733165
    Evidence reason
  43. 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-15 22:22:19.692675
    Evidence SHA-256
    6c278207335eea35544133b166242cb2e0215578c9ef66df1220a947d8ab535c
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-15 22:22:19.692675
    Evidence reason
  44. 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-15 03:59:26.000000
    Evidence SHA-256
    1712aac5424c97f481b2aebe75df5c07266e05ebc462ceb82d857fc719a7d87f
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-15 03:59:26
    Evidence reason
    unavailable
  45. 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
    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-15 03:59:26.000000
    Evidence SHA-256
    603a2458ab5c8d0a85a0a467f832b33a330f11bef62d2176a76e94b4b50e0eb4
    Evidence timestamp as recorded
    2026-10-15 03:59:26
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  46. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-14 22:21:26.687207
    Evidence SHA-256
    84b3890be530ef4dfe4674dbe40cf3c017c8e665cc7af4be1060bb48d22e958e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-14 22:21:26.687207
    Evidence reason
  47. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-13 22:21:07.146269
    Evidence SHA-256
    d402eaa2a918551b0c13724c34dc7c6f5747360d1b3897bd73ccc2aa9d2e9da2
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-13 22:21:07.146269
    Evidence reason
  48. 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-13 03:24:28.000000
    Evidence SHA-256
    90c282f5561d0530105166d1a593ad98089cc363aacfe340d0958857dea7762d
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-13 03:24:28
    Evidence reason
    unavailable
  49. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-13 03:24:28.000000
    Evidence SHA-256
    b2fc235608a541fdf3c306b1249d612dd0da2391b2d5f5e169f0bc255fe069ea
    Evidence timestamp as recorded
    2026-10-13 03:24:28
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  50. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-12 22:20:57.953315
    Evidence SHA-256
    b0927403a99131c7bcdd762cc5daf4b5da8ff49029520964407d00c9043f360e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-12 22:20:57.953315
    Evidence reason
  51. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-11 22:20:50.151913
    Evidence SHA-256
    06138ca909a4f3051eacea3d7a21df5e64801de0f27b809182dd0385032cd5b4
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-11 22:20:50.151913
    Evidence reason
  52. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-11 03:23:20.000000
    Evidence SHA-256
    a9f8869c2fdd0208d8336123009b72713ac5601d338e02203dde9afcf3b8b74d
    Evidence timestamp as recorded
    2026-10-11 03:23:20
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  53. 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-11 03:23:20.000000
    Evidence SHA-256
    db546bae0b31961f01c08f6c7d4b8347ea1192dfe407508ad1efc988e5492efd
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-11 03:23:20
    Evidence reason
    unavailable
  54. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-10 22:20:48.858561
    Evidence SHA-256
    11ef8921e63041943b1b74a04946731f8dff73b042235954f632140452c757a1
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-10 22:20:48.858561
    Evidence reason
  55. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-09 22:20:42.401113
    Evidence SHA-256
    a36a067ca705bb74c2c35205661a07c0cfb9775d48d28db2e1eb50c1eb58d9d2
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-09 22:20:42.401113
    Evidence reason
  56. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-09 03:35:24.000000
    Evidence SHA-256
    58ea8a72acc751f35ab6f3a316d49b5af70fdc0be5718a055460b4277346aea3
    Evidence timestamp as recorded
    2026-10-09 03:35:24
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  57. 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-09 03:35:24.000000
    Evidence SHA-256
    c273570c992c0041bf23df7fb9f7367c4486d30df5af364d1f0105308a193d20
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-09 03:35:24
    Evidence reason
    unavailable
  58. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-08 22:20:32.448533
    Evidence SHA-256
    0da49a5add3e494d62c4dd99eadc9a6eb4fa06348e3d5f894716599a81c8b1a7
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-08 22:20:32.448533
    Evidence reason
  59. http_observationunknown
    Observation source
    http_observation
    Cause
    origin_unreachable
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    502
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    http_5xx
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-07 03:56:52.000000
    Evidence SHA-256
    932f4c26e8869c0cffba235589aa0d701c9162eab6dffea32ac1b77bfcce83a9
    HTTP probe value as recorded
    502
    Evidence timestamp as recorded
    2026-10-07 03:56:52
    Evidence reason
    transient_502
  60. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Recorded HTTP status
    502
    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-07 03:56:52.000000
    Evidence SHA-256
    bcc1887d3479c3118b315eed1fcd1d1faa18b955a6f969e1346a54baae197a59
    Evidence timestamp as recorded
    2026-10-07 03:56:52
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  61. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-07 00:13:39.270476
    Evidence SHA-256
    0f399a21e98e0256f98d43c4d230f6dc7ee0a7a8efd7ef9c6c107be031afd218
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-07 00:13:39.270476
    Evidence reason
  62. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-06 00:13:39.266033
    Evidence SHA-256
    73a145cd4429727962b5329d34695921409b9b9666743d039a9cc9ba9e3526c7
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-06 00:13:39.266033
    Evidence reason
  63. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-05 00:13:35.837561
    Evidence SHA-256
    74452d0282caf7aefe2eabc79f33c87072b1889a11d214b6860e6b3e5f762831
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-05 00:13:35.837561
    Evidence reason
  64. 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-03 18:16:30.317188
    Evidence SHA-256
    70d02346b5dbc706195b1302376a295ce40556bf1954b2c513314c32a40a1aeb
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-03 18:16:30.317188
    Evidence reason
  65. http_observationunknown
    Observation source
    http_observation
    Cause
    origin_unreachable
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    502
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    http_5xx
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-03 03:44:51.000000
    Evidence SHA-256
    2052121eceebcc58826cbf152564da65adcb7c877bfce4bd30f32400e37825a7
    HTTP probe value as recorded
    502
    Evidence timestamp as recorded
    2026-10-03 03:44:51
    Evidence reason
    transient_502
  66. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Recorded HTTP status
    502
    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-03 03:44:51.000000
    Evidence SHA-256
    adc6e0040b3282ad9de1d341b7203e4bae8eafe2e675ec7f3f36e6034250f451
    Evidence timestamp as recorded
    2026-10-03 03:44:51
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  67. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-02 18:16:28.238873
    Evidence SHA-256
    83187e78159518c7977f539ffd2603b7d792d43342363046cf38db99dacb648d
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-02 18:16:28.238873
    Evidence reason
  68. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-01 18:16:25.663717
    Evidence SHA-256
    028c1788389f548aae03eebc6ec364be02a41bf49d956382ace6ac5f6bd2196b
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-01 18:16:25.663717
    Evidence reason
  69. http_observationunknown
    Observation source
    http_observation
    Cause
    origin_unreachable
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    502
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    http_5xx
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-01 03:47:10.000000
    Evidence SHA-256
    37f4bbb8d943b0ad583a8112182db96342afb12bf687ba8dd5449c2c855abe09
    HTTP probe value as recorded
    502
    Evidence timestamp as recorded
    2026-10-01 03:47:10
    Evidence reason
    transient_502
  70. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    Recorded HTTP status
    502
    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-01 03:47:10.000000
    Evidence SHA-256
    8095cc4a05f6fb516784377fd099263f4b03cb93e8c0ae614a3c57b377a8591d
    Evidence timestamp as recorded
    2026-10-01 03:47:10
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  71. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    timeout
    DNS response code
    TIMEOUT
    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-09-30 18:14:55.856480
    Evidence SHA-256
    846116c132129e5b112ba4a0acda2d143f17093abc1c08a35fa0f050bcd750ea
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-09-30 18:14:55.856480
    Evidence reason

Threat Response Pipeline

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

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
    ledgrr.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Registrar Context: NameSilo · Automated brand label: Ledger · Forensic Evidence Collected · Technical Analysis Recorded · Site Came Back Online · Content Observed Unavailable · Cloudflare Radar Scan 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.
  • Registrar Context: NameSilo
    Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
  • 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.
  • Site Came Back Online
    The domain is responding again; monitoring resumed
  • Content Observed Unavailable
    Monitoring recorded an unavailable response; the cause was not independently established.
  • Cloudflare Radar Scan
    Scanned with Cloudflare Radar; network analysis completed.
Publication & AvailabilityDestroyList Published Recorded: 1 of 1

Recorded activity

2 entries
  1. URLScan

    Page captured

    View source
  2. Added to PhishDestroy

    ledgrr.com

    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.

Stored checks and requests

Content check

Status
Alive
Last checked
2026-03-04 19:15:03 UTC
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

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

This domain is a replacement lookalike of ledger.com. dnstwist_results #640 · Target: ledger.com · recorded domain pair · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35
dnstwist_results #601 · Target: ledger.com · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 #609 · Target: ledger.com · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 dnstwist_results #652 · Target: ledger.com · shared recorded target · 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
Show all (88)
dnstwist_results #634 · Target: ledger.com · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 · shared recorded target · 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 dnstwist_results #542 · Target: ledger.com · shared recorded target · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 medger.com bitsquatting A 13.248.169.48NS ns1.namefind.com

Showing 100 of 150

Community reports

Reported by 1 community member, first seen Feb 6, 2026

Stored reports
1
Unique reported URLs
1
Accepted1

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked Unverified
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.

Official reporting routes

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.

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

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.

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/ledgrr.com"
  title="PhishDestroy threat report for ledgrr.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>