Aller au rapport de sécurité
Domain security report
ldg-support.top favicon

ldg-support.top

Verdict de menace
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Disponibilité Non vérifié L'accessibilité actuelle n'est pas vérifiée Observé · HTTP probe
Détections VirusTotal : 10/92 Spamhaus DBL: DBL_SPAM Correspondances de la liste de blocage stockée : 1 Automated brand label: Ledger Domaine jeune : 1 jours Google Safe Browsing: threat flag recorded
OTX: 4 refs 17/10/2026 Ledger CDN
API
Bureau d’enregistrement
Hosting Concepts
Resolved IP
188.114.97.3
Registered
16/10/2026
3 sources
In this reportGet help
Ce domaine a été signalé comme malveillant
Moteurs de sécurité signalant une détection : 10. Listes de blocage publiques signalant une correspondance : 1. Faites preuve d’une extrême prudence – ne saisissez pas d’informations d’identification ou d’informations personnelles.
Résumé du rapport

ldg-support.top — Non vérifié. Usurpation de l'identité de la marque : Ledger; Type d'arnaque : Seed Phrase Theft. Résumé des preuves: VirusTotal 10/92 (BitDefender, CRDF, Ermes, Emsisoft, Fortinet); URLScan capture; Google Safe Browsing flagged; Spamhaus DBL_SPAM; 1 external blocklist match (OpenPhish); PhishDestroy score 100/100. Bureau d’enregistrement: Hosting Concepts.

The evidence summary below uses retained observations. Each source keeps its own collection date.

Additional indicators at a glance

Spamhaus DBL
DBL_SPAM
VirusTotal
VirusTotal
10 det.
OTX references
URLScan
URLScan
Âge
1d Brand New!
PhishDestroy
DestroyList
Répertorié

Source evidence

8 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

10 / 92

Signaler
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

Google Safe Browsing

Threat flag recorded

Signaler
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Public blocklists

1 external matches

Détails
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Spamhaus DBL

DBL_SPAM

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLQuery

Report stored; detailed verdict not recorded

Observation time not recorded
Signaler
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

OTX

4 community references

Signaler
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

URLScan capture

rapport stocké

View stored capture ↗
Signaler
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

CF Radar

Report stored; verdict not recorded

Observation time not recorded
Signaler
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Résumé des preuves

Critique
VirusTotal
10/92
OTX
4 community refs
URLScan
Stored capture

Evidence-based analysis Generated from the observations retained in this report. No stored AI narrative is available for this record. Each source retains its own collection date.

PhishDestroy first observed ldg-support.top on Oct 17, 2026. Stored content metadata identifies Ledger as the apparent target. Stored page analysis classifies the content as seed phrase theft. Current evidence score: 100/100 (critical).

Positive findings are stored from 4 sources: VirusTotal, OpenPhish, Google Safe Browsing, and Spamhaus DBL. On Oct 17, 2026 at 18:28 UTC, VirusTotal recorded 10 detections among 92 engines: BitDefender, CRDF, Ermes, Emsisoft, Fortinet, G-Data, Google Safe Browsing, Lionic, Netcraft, Webroot; Google Safe Browsing flagged the domain: Social Engineering. OpenPhish listed the hostname in the separate external-blocklist snapshot on Oct 17, 2026 at 18:20 UTC. Spamhaus DBL: DBL_SPAM on Oct 17, 2026 at 18:30 UTC. Additional recorded evidence: AlienVault OTX listed 4 community pulse references (not vendor detections) on Oct 17, 2026 at 18:28 UTC. URLScan captured the page on Oct 17, 2026 at 17:28 UTC.

The collector marked the hostname reachable on Oct 17, 2026 at 17:28 UTC, but did not retain the HTTP response code. Latest classified outcome: unknown; cause probe inconclusive on Oct 17, 2026 at 15:28 UTC. Registration records for the domain list Hosting Concepts B.V. d/b/a Registrar.eu as the registrar and Oct 16, 2026 as the creation date. Registration preceded first observation by 1 day. At collection time, the hostname resolved to 188.114.97.3 (AS13335 Cloudflare, Inc.). The IP and ASN identify shared Cloudflare edge infrastructure; the origin server is not established by this address. DOM analysis on Oct 17, 2026 at 18:20 UTC returned 80/100. The evidence archive retains 3 visual captures from PhishDestroy and URLScan; the captures preserve the landing-page appearance.

The content indicators and 4 positive source findings support the current Ledger-themed support phishing classification.

Data coverage & collection

19 · datasets with records / 12 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
10 / 92 · engine detections
URLScan analysis
Capture retained; no provider verdictCollection time not recorded
URLQuery
Stored source recordCollection time not recorded
Google Safe Browsing
Threat flag recorded
OTX publications
4 · community references
External blocklists
1 · external matches
Cloudflare Radar
Report link retainedCollection time not recorded
Spamhaus DBL
DBL_SPAM
Domain registration
Hosting Concepts B.V. d/b/a Registrar.euCollection time not recorded
Network & DNS
188.114.97.3 · 2 · nameserversCollection time not recorded
Page captures
3 · retained captures
HTML archives
1 · retained responses
Page analysis
1 · automated brand labels
Site configuration files
robots.txt · sitemap.xml · security.txt
PageSpeed performance
83/100 · mobile performance
Availability history
1 · stored state changes
Source observation history
2 · stored source events
Lookalike relationships
100 · retained relationshipsCollection time not recorded
IP reputation
Network-level observations
Not recorded in this report 12

These checks have no retained result. This does not mean they passed or that a scan is running.

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • Certificat TLS
  • Observed indicators
  • Detection & evasion
  • Response records
  • Recorded subdomains
  • Signalements communautaires
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

1 · external source matches

Statut de la liste de blocage publique

Domain, network & archive

Hosting Concepts B.V. d/b/a Registrar.eu · 188.114.97.3 · DNS, TLS and retained responses

Domain details

Domaine
Google Safe Browsing Marqué Social engineering checked 17/10/2026
IP Context Cloudflare shared edge origin IP hidden La réputation Edge-IP n’est pas attribuée à ce domaine.
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainesdrainerfraudlivemonthlyphishdestroyphishingscam
Bureau d’enregistrement Hosting Concepts IS(IS)
Contact anti-abusabuse@registrar.eu
Registre de l'ICANNICANN Lookup (RDAP) →
EnregistrementCréé 16/10/2026 (1d · Brand New!) — Expires 16/10/2027
Détails techniquesProvenance & timestamps
Première détection17/10/2026
DOM Analysisanalyzed 17/10/2026score 80/1001 brand signal
Submitted URLhttp://ldg-support.top/
Favicon Hash
ID du dossier
ICANN OVERSIGHT

Contexte de l’accréditation et du RAA

Registrar accreditation and DNS abuse obligations

For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

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

Accountability draft Rien n’est envoyé automatiquement.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.97.3
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US

La réputation Edge-IP n’est pas attribuée à ce domaine.

Serveurs de noms 2
  • ajay.ns.cloudflare.com
  • celine.ns.cloudflare.com

Location describes the IP network.

Latest Classified Outcome 2026-10-17 17:28:15 UTC

Primary outcome Inconnu reason: Probe Inconclusive 20% confidence
Attribution source: Current State Backfill
Evidence layers Availability: Unreachable Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation Inconnu Probe Inconclusive 20% 2026-10-17 17:28:15 UTC
RDAP registration Inconnu
Observed timeline last reachable: 2026-10-17 17:28:15 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Signaler ce domaine Envoyez des éléments de preuve et contribuez à protéger les autres

Analyse VirusTotal

10 / Les fournisseurs de sécurité 92 ont signalé ce domaine
View on VT
Last analyzed Previous stored snapshot: 10 detections
BitDefender
CRDF
Ermes
Emsisoft
Fortinet
G-Data
Google Safe Browsing
Lionic
Netcraft
Webroot
Analyse des performances du site

Google PageSpeed Insights — mobile performance audit of ldg-support.top · checked Oct 17, 2026

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

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

Archived HTTP response HTTP 200
Requested URL: http://ldg-support.top/
Final URL: https://ldg-support.top/
Ledger Live
Réponse
HTTP 200
HTML body
43.8 KB
Compressed
8.4 KB
Links
2 internal · 0 external
Detected technologies
jquerycloudflare
Selected response headers
Content-Type: text/html
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 14
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a4c102729f52f46c-YYZ
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Sat, 17 Oct 2026 17:26:40 GMT
Last-Modified
Fri, 16 Oct 2026 15:59:11 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=MYO1U4GPRNLGEagValb43%2BmpLif%2BC82ad7I5hi2wg3PTeihsZIASPd0ns0w0v33%2FXhtzuPKltNKhETpX0yIPg%2FcV2ALyYobHsyzM%2FIo5eeAIqivAhR%2FtbiV4OLLtJB9SbPU
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Transfer-Encoding
chunked
Vary
Accept-Encoding

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

Crawler & disclosure files

Site configuration evidence

3 · file checks

Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.

robots.txt

Unverified (legacy)
/robots.txt
HTTP response
301
Observed at
2026-10-17 17:26:41 UTC
Source
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

Sitemap

Unverified (legacy)
/sitemap.xml
HTTP response
301
Observed at
2026-10-17 17:26:41 UTC
Source
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

security.txt

Unverified (legacy)
/.well-known/security.txt
HTTP response
301
Observed at
2026-10-17 17:26:41 UTC
Source
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

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.

Detection & evasion checks

Stored browser and crawler observations

Analyse de la détection et de l'évasion

Vérification du cloaking et de la répartition du trafic

Pas encore numérisé Aucune différence entre les robots d'indexation et les navigateurs n'a encore été constatée

Enregistrement des observations « crawler contre navigateur » pour cet hôte, ainsi qu'une vérification en temps réel des empreintes numériques pour les systèmes de répartition du trafic de type Keitaro.

Indicateur de camouflage enregistré
Pas encore numérisé
Routage de la capture
Local archivé le 2026-10-17 17:26:41 UTC
Vérification en direct des empreintes digitales d'TDS
Sept empreintes Keitaro et une comparaison entre navigateur et robot. Une nouvelle analyse démarre uniquement en cliquant sur le bouton.
À la demande

Aucun résultat de vérification enregistré.

Timeline & response

Collection history, report status and investigation channels

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Status Check 2026-10-17 17:26:43 UTC
    Source: PhishDestroy monitoring
    Event details
    Telemetry event observed.
  2. Threat First Observed 2026-10-17 17:26:34 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 188.114.97.3.
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. Availability monitor · Recorded state

    Inconnu

    probe_inconclusive

  2. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  3. Availability monitor · First collection record

    Accessible

Processus de réponse aux menaces Pipeline

Découverte
Analysis
Monitoring

12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Menace détectée
ldg-support.top détectés et mis en file d'attente en vue d'une analyse complète
17/10/2026
Spamhaus DBL
Spamhaus DBL recorded DBL_SPAM
17/10/2026
URLScan.io Capture
Enregistré URLScan report with capture artifacts
17/10/2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
VirusTotal
10/92 recorded on VirusTotal
17/10/2026
Google Safe Browsing
17/10/2026
Détection des listes noires
Trouvé dans 1 blocklist: OpenPhish
17/10/2026
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
17/10/2026
Brand Impersonation
Impersonation of Ledger
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
17/10/2026
Technical Analysis Recorded
Le rapport contient des résultats de technologie ou d’analyse médico-légale stockés.
17/10/2026
DestroyList publié
17/10/2026
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.

Related infrastructure

Shared hosting, registrar records and related domains

Domaines ressemblants

151 domaines ressemblants enregistrés

Tout afficher (88)
eldger.com transposition kedger.com replacement kledger.com insertion l3dger.com replacement ldeger.com transposition ldger.com omission le.dger.com subdomain lecger.com replacement ledber.com replacement ledegr.com transposition leder.com omission ledg3r.com replacement ledge.com omission ledged.com replacement ledgedr.com insertion ledgee.com replacement ledgeer.com repetition ledgercom.com various ledget.com replacement ledgewr.com insertion ledgger.com repetition ledgir.com vowel-swap ledgor.com vowel-swap ledgr.com omission ledgre.com transposition ledgrer.com insertion ledgsr.com replacement ledgwer.com insertion ledgwr.com replacement ledher.com replacement ledhger.com insertion ledsger.com insertion ledtger.com insertion ledyer.com replacement ledzer.com replacement leedger.com insertion legder.com transposition leger.com omission lerdger.com insertion lerger.com replacement lesger.com replacement lewdger.com insertion lidger.com vowel-swap lledger.com repetition lodger.com vowel-swap lrdger.com replacement lsdger.com replacement oedger.com replacement pedger.com replacement pledger.com insertion dedger.com bitsquatting hedger.com bitsquatting iedger.com homoglyph l-edger.com hyphenation ladger.com bitsquatting lcdlger.com homoglyph lddger.com bitsquatting lebger.com homoglyph leclger.com homoglyph ledcer.com bitsquatting leddger.com insertion ledeer.com bitsquatting ledeger.com insertion ledfer.com bitsquatting ledg-er.com hyphenation ledgar.com bitsquatting ledger0.com addition ledger1.com addition ledger4.com addition ledger5.com addition ledger6.com addition ledgerb.com addition ledgerc.com addition ledgerf.com addition ledgeri.com addition ledgern.com addition ledgerq.com addition ledgerx.com addition ledges.com bitsquatting ledgez.com bitsquatting ledgur.com bitsquatting lediger.com homoglyph ledqer.com homoglyph leeger.com bitsquatting leelger.com homoglyph lefger.com bitsquatting letger.com bitsquatting ludger.com bitsquatting

100 affichés sur 151

Evidence & investigation tools

Original reports, independent checks and evidence links

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Ce site vous a-t-il affecté ?

5 evidence signal groups linked 0 stored notification records Non vérifié

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

Si vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.

Official reporting routes
Méfiez-vous des escrocs qui prétendent vous aider à récupérer vos biens ! Les criminels peuvent recontacter leurs victimes tout en se faisant passer pour des enquêteurs, des avocats ou des agents de recouvrement. Ne payez pas de frais initiaux et ne partagez pas vos informations d'identification. En savoir plus sur la fraude liée aux aides à la reprise →
Signalez-le à vos autorités locales

Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.

Annuaire de 97 pays

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

Brouillon assisté par l'IA : les détails de l'incident sont traités par le fournisseur d'IA · Examinez-le et soumettez-le vous-même
After a phishing incident

Recommandations et conseils à l'intention des victimes

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

Que dois-je faire tout de suite ?

Urgent

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

  • Modifier tous les mots de passe — e-mail, comptes Exchange, tout ce qui utilise le même mot de passe
  • Activer l'authentification à deux facteurs (2FA) en utilisant une application d'authentification (et non par SMS). Désactivez la récupération par SMS
  • Cartes « Freeze » si vous avez saisi vos coordonnées bancaires sur le site de hameçonnage

Quelles informations dois-je rassembler pour mon rapport ?

Directives du FBI

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.
  • Dates et horaires exacts — de chaque transaction et du premier contact avec l'escroc
  • Captures d'écran — sites web frauduleux, messages de chat, e-mails, transactions via des portefeuilles numériques, réseaux sociaux
  • Toutes les URL et tous les noms de domaine utilisés par l'escroc (notamment ldg-support.top)
  • Communications — les e-mails, SMS, numéros de téléphone et noms d'utilisateur utilisés par l'escroc

Même si vous ne disposez pas de tous les détails — déposer quand même une plainte. Même des informations partielles peuvent aider les enquêtes.

À qui dois-je signaler cette arnaque ?

  • FBI IC3 — Centre de signalement des délits sur Internet (système fédéral américain de signalement)
  • Europol — Rapports sur la cybercriminalité en Europe (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Police locale — permet de consigner officiellement la situation, même s’ils ne peuvent pas agir immédiatement

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?

  • Faux sites web — des clones identiques au pixel près de sites légitimes, dont les noms de domaine ont été légèrement modifiés
  • Découpe du porc — une relation de confiance établie au fil des semaines via Telegram, WhatsApp ou des applications de rencontre, puis une escroquerie financière
  • Arnaques liées au recouvrement — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Escroqueries basées sur l'IA — les « deepfakes », le hameçonnage automatisé et les sites générés par l'IA, qui rendent la fraude plus difficile à détecter

Comment puis-je me protéger à l'avenir ?

  • Ajouter les sites officiels à vos favoris — Ne cliquez jamais sur les liens contenus dans les e-mails, les messages privés ou les publicités
  • Vérifier les noms de domaine — vérifier si PhishDestroy avant d'entrer en contact. Vérifiez le protocole HTTPS, l'orthographe et l'ancienneté du domaine
  • « Trop beau pour être vrai » = arnaque — des rendements garantis, des témoignages de célébrités, des délais serrés

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

Restez informés, restez en sécurité

Surveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif

Flux d'alertes en temps réel Contester cette annonce
Read the evidence in context

À propos de ce rapport : ldg-support.top

Ce rapport présente les dernières preuves stockées disponibles pour PhishDestroy. Les horodatages sources sont affichés lorsqu'ils sont disponibles ; la disponibilité et les verdicts des fournisseurs peuvent changer après la collecte.

Depuis 2026-10-17 18:28:05 UTC, ldg-support.top avait des détections provenant des moteurs de sécurité 10.

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Intégrer ce rapport

Partagez ces informations sur les menaces sur votre site web ou votre blog

embed.html
<iframe
  src="https://phishdestroy.io/fr/embed/domain/ldg-support.top"
  title="PhishDestroy threat report for ldg-support.top"
  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>