Vai al rapporto di sicurezza
Domain security report
helplistings.blog favicon

helplistings.blog

“Vote”

Verdetto di minaccia
Assessment sources

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

Disponibilità Ultimo attivo conosciuto Ultima osservazione di raggiungibilità memorizzata Osservato · HTTP probe
Rilevamenti VirusTotal: 3/92 Spamhaus DBL: DBL_SPAM Corrispondenze della blocklist memorizzate: 2 Automated brand label: Coinmarketcap Dominio giovane: 3 giorni
16/10/2026 Coinmarketcap 1 Report Sent
API
Registrar
Hosting Concepts
Resolved IP
85.239.149.60
Registered
14/10/2026
3 sources
In this reportGet help
Questo dominio è stato segnalato come dannoso
Motori di sicurezza che segnalano un rilevamento: 3. Blocklist pubbliche che segnalano una corrispondenza: 2. Prestare estrema cautela: non inserire credenziali o informazioni personali.
ABUSE NOTICE · 24H+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@dedik.io. The latest stored availability evidence still shows the domain reachable; 28 hours has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
28 hours
Reports sent
1
Latest case ID
PD-20261016-EDF743
Current status
HTTP 200 at latest stored check
Riepilogo del rapporto

helplistings.blog — Ultimo attivo conosciuto (HTTP 200). Simulazione del marchio: Coinmarketcap; Tipo di truffa: Impersonation. Riepilogo delle prove: VirusTotal 3/92 (alphaMountain.ai, Gridinsoft, SOCRadar); URLScan capture; Spamhaus DBL_SPAM; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 88/100. Registrar: Hosting Concepts.

L’analisi dettagliata di PhishDestroy AI resta in inglese per preservare il rapporto forense originale.

Additional indicators at a glance

Spamhaus DBL
DBL_SPAM
VirusTotal
VirusTotal
3 det.
URLScan
URLScan
Certificato TLS
Within stored validity dates
Let's Encrypt / YR2 · Hostname coverage not recorded
Età
3d Brand New!
Stato osservato
Ultimo attivo conosciuto 200
PhishDestroy
Elenco da eliminare
Presente
Reports Sent
1

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

3 / 92

Segnala
Interpretation & limits

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

Public blocklists

2 external matches

Dettagli
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
Segnala
Interpretation & limits

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

OTX

no community references

Segnala
Interpretation & limits

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

CF Radar

provider verdict: suspicious

Observation time not recorded
Segnala
Interpretation & limits

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

URLScan capture

rapporto memorizzato

View stored capture ↗
Segnala
Interpretation & limits

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

Google Safe Browsing

Checked; no threat flag recorded

Segnala
Interpretation & limits

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

Riepilogo delle prove

Critico
VirusTotal
3/92
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

Assessment

helplistings.blog was recorded on 2026-10-16 with entries on the MetaMask and SEAL external blocklists, providing a dated reference for its listing status. The domain also achieved a PageSpeed performance score of 100 on the same date, reflecting its measured technical efficiency.

Recorded Evidence

On 2026-10-16, helplistings.blog appeared on both the MetaMask and SEAL external blocklists. VirusTotal checked the domain on 2026-10-15, documenting 3 detections out of 92 total scanners. PhishDestroy internally listed the domain, and PageSpeed measured a performance score of 100 on 2026-10-16. The domain was registered through Hosting Concepts B.V. d/b/a Registrar.eu on 2026-10-14.

Interpretation

PhishDestroy contains an internal listing for helplistings.blog, which documents its inclusion in a security intelligence record. VirusTotal provides a measurement of how many security engines detected the domain, offering a view of its evaluation by multiple scanners. The MetaMask and SEAL blocklist entries expand the scope of recorded observations, showing that multiple external sources referenced the domain within a short period.

Recommended Actions

For helplistings.blog, retain the records from PhishDestroy, VirusTotal, MetaMask, and SEAL for future comparison and review. Use the PageSpeed measurement as a technical reference point in subsequent assessments. Continue to monitor these sources for updated or additional entries relating to the domain.

Data coverage & collection

23 · datasets with records / 8 · 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
3 / 92 · engine detections
URLScan analysis
Capture retained; no provider verdictCollection time not recorded
URLQuery
Stored source recordCollection time not recorded
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
0 · community references
External blocklists
2 · external matches
Cloudflare Radar
suspiciousCollection time not recorded
Spamhaus DBL
DBL_SPAM
Domain registration
Hosting Concepts B.V. d/b/a Registrar.euCollection time not recorded
Network & DNS
85.239.149.60 · 2 · nameserversCollection time not recorded
Certificato TLS
Let's Encrypt / YR2
Page captures
3 · retained captures
HTML archives
1 · retained responses
Page analysis
1 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
Site configuration files
robots.txt · sitemap.xml · security.txt
PageSpeed performance
100/100 · mobile performance
Response records
1 · outgoing report records
Availability history
2 · stored state changes
Source observation history
1 · stored source events
Chainabuse records
1 · recorded reports
IP reputation
Network-level observations
Not recorded in this report 8

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

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • Recorded subdomains
  • Lookalike relationships
  • Segnalazioni della comunità
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

2 · external source matches

Stato della lista di blocco pubblica

Domain, network & archive

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

Domain details

Dominio
Reputazione IP abuse score 2/100 2 reports Open ProxyPort ScanHackingExploited Host checked 16/10/2026
Registrar Hosting Concepts NL(NL)
RegistrazioneCreato 14/10/2026 (3d · Brand New!) — Expires 14/10/2027
Stato HTTP200
Dettagli tecniciProvenance & timestamps
Rilevato per la prima volta16/10/2026
DOM Analysisanalyzed 17/10/2026score 88/1001 brand signal
Submitted URLhttp://helplistings.blog/
Favicon Hash
ID del caso
ICANN OVERSIGHT

Accreditamento e contesto 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 Nulla viene inviato automaticamente.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
85.239.149.60
Network ASN
AS207043
Organization
Dedik Services Limited
Observed location
Frankfurt am Main, DE
Server header
SimpleHTTP/0.6 Python/3.10.12
Nameserver 2
  • amos.ns.cloudflare.com
  • nina.ns.cloudflare.com

Location describes the IP network.

Certificato TLS

Issuer
Let's Encrypt / YR2
Valid from
2026-10-14 19:10:35
Valid until
2027-01-12 19:10:34
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-16 22:02:08 UTC
Collection source
PhishDestroy collector
Certificate fingerprint6b558ee9d9823e8833f312dc2601b05979cc7e341da7e013539ed49f3cbfe665

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

Latest Classified Outcome 2026-10-17 10:00:18 UTC

Primary outcome Contenuto attivo reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Contenuto attivo Ordinary HTTP content served 90% 2026-10-17 10:00:18 UTC
RDAP registration Sconosciuto
Observed timeline last reachable: 2026-10-17 10:00:18 UTC last content: 2026-10-17 10:00:18 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.
Riscontro delle informazioni sulle minacce · source references
ScamAdviser Public lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
View on ScamAdviser
Live-fetched via CF worker proxy pool · cached 24h
Tecnologie · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Segnala questo dominio Invia le prove e contribuisci a proteggere gli altri

Analisi di VirusTotal

3 / I fornitori di sicurezza 92 hanno contrassegnato questo dominio
View on VT
Last analyzed First positive detection
alphaMountain.ai
Gridinsoft
SOCRadar
Analisi delle prestazioni del sito

Google PageSpeed Insights — mobile performance audit of helplistings.blog · checked Oct 16, 2026

100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
0.76s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.75s
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://helplistings.blog/
Vote
Community listing vote on CoinMarketCap.
Risposta
HTTP 200
HTML body
11.0 KB
Compressed
3.6 KB
Links
1 internal · 0 external
Selected response headers
Server: SimpleHTTP/0.6 Python/3.10.12
Content-Type: text/html; charset=utf-8
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: 54e8edf66a7f7fad7d975470fa2ea7cc036757ba7897d05f8edf87f37cd47aab
Open Graph title: Vote
Open Graph description: Community listing vote on CoinMarketCap.
Twitter card: summary_large_image
Saved response-header values · 4
Content-Length
11274
Content-Type
text/html; charset=utf-8
Date
Fri, 16 Oct 2026 19:29:21 GMT
Server
SimpleHTTP/0.6 Python/3.10.12

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

Non trovato
/robots.txt
HTTP response
404
Observed at
2026-10-16 19:29:23 UTC
Fonte
legacy scan archive

The scanner received HTTP 404 or 410 for this file.

Sitemap

Non trovato
/sitemap.xml
HTTP response
404
Observed at
2026-10-16 19:29:23 UTC
Fonte
legacy scan archive

The scanner received HTTP 404 or 410 for this file.

security.txt

Non trovato
/.well-known/security.txt
HTTP response
404
Observed at
2026-10-16 19:29:23 UTC
Fonte
legacy scan archive

The scanner received HTTP 404 or 410 for this file.

Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Detection & evasion checks

Stored browser and crawler observations

Analisi di rilevamento ed evasione

Verifica del cloaking e della distribuzione del traffico

Non ancora scansionato Non è stata ancora rilevata alcuna differenza tra crawler e browser

Osservazioni archiviate relative al confronto tra crawler e browser per questo host, oltre a una verifica in tempo reale delle impronte digitali per i sistemi di distribuzione del traffico in stile Keitaro.

Flag di occultamento memorizzato
Non ancora scansionato
Ultima scansione di occultamento
Intestazione del server rilevata dallo scanner
SimpleHTTP/0.6 Python/3.10.12
Indirizzamento delle acquisizioni
Local archiviato l'2026-10-16 19:29:23, UTC

Nota dello scanner: alive_content: raw=ok; http=200; via=https_proxy; server=SimpleHTTP/0.6 Python/3.10.12

Verifica delle impronte digitali in tempo reale TDS
Sette indicatori Keitaro e un confronto tra browser e crawler. Una nuova scansione parte solo premendo il pulsante.
Su richiesta

Nessun risultato di verifica live salvato.

Timeline & response

1 · outbound report records

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. Threat First Observed 2026-10-16 19:30:09 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as unknown pointing to IP 85.239.149.60.
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

    Sconosciuto→live_content

    content_served

  2. Availability monitor · Recorded state

    Sconosciuto

    stale_current_evidence

  3. Availability monitor · First collection record

    Sconosciuto

Pipeline di risposta alle minacce

Scoperta
Analysis
Notifications
Monitoring

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

Minaccia rilevata
helplistings.blog rilevati e inseriti in coda per un’analisi completa
16/10/2026
Spamhaus DBL
Spamhaus DBL recorded DBL_SPAM
17/10/2026
URLScan.io Capture
Memorizzato URLScan report with capture artifacts
16/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
3/92 recorded on VirusTotal
16/10/2026
Rilevamento delle liste di blocco
Si trova in 2 blocklists: MetaMask, SEAL
18/10/2026
Brand Impersonation
Impersonation of Coinmarketcap
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
16/10/2026
Technical Analysis Recorded
Il report contiene tecnologia archiviata o risultati di analisi forensi.
18/10/2026
Sent Report Recorded
Stored outgoing record associated with registrar Hosting Concepts B.V. d/b/a Registrar.eu, 2 abuse contacts
abuse@dedik.ioabuse@registrar.eu
16/10/2026
DestroyList pubblicato
16/10/2026
Monitoring Continues
Il dominio rimane raggiungibile o ad accesso limitato; controlli futuri potrebbero aggiornare questa osservazione.
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

Community records

Retained community reports and observations

Intelligence della comunità

1 segnalazione della comunità

CategoriaPHISHING

Fake "vote to list $TOKEN on the CoinMarketCap Top 100 Leaderboard" posts flood X from what look like hijacked accounts (about 117,000 posts since Oct 12 by X's counts), each linking to helpvote.help (current), helplistings.blog, helplists.blog or listsupport.help with ?contract=

Evidence & investigation tools

Original reports, independent checks and evidence links

Dati e relazioni esterne

Community Scam Report — ChainAbuse
1 report filed for helplistings.blog (1 written by a person) · category: Phishing · source checked
“Fake "vote to list $TOKEN on the CoinMarketCap Top 100 Leaderboard" posts flood X from what look like hijacked accounts (about 117,000 posts since Oct 12 by X's counts), each linking to helpvote.help (current), helplistings.blog, helplists.blog or listsupport.help with ?contract=<token>. The vote page loads a script that reads its command server from BSC contract 0x1AC7d768E37B147c993dE943D704c4e92d7861A1 via getter 0xb68d1809, then downloads and runs remote JavaScript. Owner 0xb88eca7852a5e9b63”
— reported by Anonymous on Oct 17, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
Istantanea delle prove inviate
Sent: Ledger records: 1 Case ID: PD-20261016-EDF743 Recipient: abuse@dedik.io
PDF notice generated Notice text archived (856 chars)
Abuse notice text as sent to the provider
AUP & Terms of Service Violations:
Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices.
Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension.
Applicable Legal Framework (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
Analisi approfondita

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Questo sito ti ha influenzato in qualche modo?

5 evidence signal groups linked 1 stored notification records Ultimo attivo conosciuto
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Se hai inserito credenziali dell'account, informazioni personali o di pagamento oppure hai scaricato un file da questo dominio, agisci immediatamente. Di seguito sono riportate le risorse per aiutarti a segnalare l'incidente e proteggerti.

Official reporting routes
Europol
Trova il canale di segnalazione ufficiale per il tuo paese dell'UE
National police directory
Find your country
Attenzione ai truffatori che promettono il recupero dei fondi! I criminali possono contattare nuovamente le vittime fingendo di essere investigatori, avvocati o agenti di recupero. Non pagare commissioni anticipate né condividere credenziali. Scopri di più sulle frodi relative ai sussidi di recupero →
Segnalalo alle autorità locali

Seleziona il tuo Paese per ottenere contatti ufficiali del crimine informatico o creare una bozza di reclamo →.

Elenco di 97 paesi

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

Bozza assistita dall'intelligenza artificiale: i dettagli dell'incidente vengono elaborati dal fornitore di intelligenza artificiale · Controllalo e invialo tu stesso
After a phishing incident

Raccomandazioni e consigli per le vittime

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

Cosa devo fare subito?

Urgente

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

  • Modifica tutte le password — e-mail, account Exchange, qualsiasi servizio che utilizzi la stessa password
  • Abilita l'autenticazione a due fattori (2FA) utilizzando un'app di autenticazione (non via SMS). Disattiva il recupero tramite SMS
  • Carte congelate se hai inserito i tuoi dati bancari sul sito di phishing

Quali informazioni devo raccogliere per la mia relazione?

Linee guida dell'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.
  • Date e orari esatti — di ogni transazione e del primo contatto con il truffatore
  • Schermate — siti web truffaldini, messaggi in chat, e-mail, transazioni tramite portafoglio digitale, social media
  • Tutti gli URL e i domini utilizzato dal truffatore (tra cui helplistings.blog)
  • Comunicazioni — e-mail, SMS, numeri di telefono, nomi utente utilizzati dal truffatore

Anche se non conosci tutti i dettagli — sporgere comunque denuncia. Anche le informazioni parziali sono comunque utili alle indagini.

A chi devo segnalare la truffa?

  • FBI IC3 — Internet Crime Complaint Center (sistema di segnalazione federale degli Stati Uniti)
  • Europol — Segnalazioni relative alla criminalità informatica in Europa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Polizia locale — crea un documento ufficiale, anche se non è in grado di agire immediatamente

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?

  • Siti web fasulli — cloni perfetti, al pixel, di siti legittimi con domini leggermente modificati
  • Macellazione dei suini — fiducia conquistata nel corso di settimane tramite Telegram/WhatsApp/app di incontri, per poi rubare i soldi
  • Truffe legate al recupero dei fondi — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Truffe basate sull'intelligenza artificiale — i deepfake, il phishing automatizzato e i siti generati dall’intelligenza artificiale rendono più difficile individuare le frodi

Come posso proteggermi in futuro?

  • Aggiungi i siti ufficiali ai preferiti — Non cliccare mai sui link contenuti nelle e-mail, nei messaggi diretti o negli annunci pubblicitari
  • Verifica i domini — controllare PhishDestroy prima di interagire. Verifica l'HTTPS, l'ortografia e l'età del dominio
  • "Troppo bello per essere vero" = truffa — rendimenti garantiti, testimonial di personaggi famosi, scadenze urgenti

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

Rimani informato, rimani al sicuro

Controlla le minacce in tempo reale oppure contesta questa segnalazione se ritieni che si tratti di un falso positivo

Feed in tempo reale sulle minacce Contesta questo annuncio
Read the evidence in context

Informazioni su questo rapporto: helplistings.blog

Questo rapporto presenta le ultime prove archiviate disponibili per PhishDestroy. I timestamp della sorgente vengono mostrati ove disponibili; la disponibilità e i verdetti del fornitore possono cambiare dopo il ritiro.

Il sito catturato mostrava il titolo della pagina “Vote” e potrebbe spacciarsi per Coinmarketcap.

Al momento di 2026-10-16 19:30:15 UTC, helplistings.blog ha ricevuto rilevamenti dai motori di sicurezza 3.

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

Incorpora questo rapporto

Condividi queste informazioni sulle minacce sul tuo sito web o sul tuo blog

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