Vai al rapporto di sicurezza
Pannello di controllo analitico
Domain security report
2hmes.com favicon

2hmes.com

“Secure Document — Soft Edition (Wide)”

Verdetto di minaccia
CriticoRicorso in materia di domini
Assessment sources

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

Disponibilità Ultimo attivo conosciuto Ultima osservazione di raggiungibilità memorizzata Osservato · HTTP probe
Segnali di rischio
Rilevamenti VirusTotal: 2/92 Automated brand label: Documentlure
OTX: 3 refs 16/10/2026 Documentlure
API
Registrar
NameSilo
Resolved IP
176.9.116.24
Registered
30/01/2024
3 sources
The capture source is temporarily unavailable.
1 / 3
Fonte
Primary capture
Collected · UTC
Open capture
In this reportGet help
Questo dominio è stato segnalato come dannoso
Motori di sicurezza che segnalano un rilevamento: 2. Prestare estrema cautela: non inserire credenziali o informazioni personali.
Riepilogo del rapporto

2hmes.com — Ultimo attivo conosciuto (HTTP 200). Simulazione del marchio: Documentlure; Tipo di truffa: Impersonation. Riepilogo delle prove: VirusTotal 2/92 (alphaMountain.ai, DNS8); URLScan malicious verdict; PhishDestroy score 81/100. Registrar: NameSilo.

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

Additional indicators at a glance

VirusTotal
VirusTotal
2 det.
OTX references
3 community refs
URLScan
URLScan
Segnala ↗
Certificato TLS
Within stored validity dates
Let's Encrypt / YR2 · Hostname coverage not recorded
Età
2.7 yr
Stato osservato
Ultimo attivo conosciuto 200
PhishDestroy
Elenco da eliminare
Presente

Source evidence

7 · 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

2 / 92

Segnala
Interpretation & limits

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

URLScan verdict

malicious

Segnala
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

OTX

3 community references

Segnala
Interpretation & limits

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

CF Radar

provider verdict: clean

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.

Public blocklists

0 external matches

Dettagli
Interpretation & limits

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

Informazioni sulla sicurezza di rete 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

Riepilogo delle prove

Critico
VirusTotal
2/92
OTX
3 community refs
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

2hmes.com was observed on 2026-10-16 with an OpenPhish blocklist entry, providing a dated record of external security attention. The domain also received a PageSpeed performance score of 73 on the same date, reflecting a technical measurement.

Recorded Evidence

OpenPhish recorded 2hmes.com on its blocklist as of 2026-10-16. VirusTotal checked the domain on 2026-10-15, documenting 2 detections out of 92 scanners. OTX referenced 2hmes.com in three pulses as of 2026-10-16. PhishDestroy internally listed the domain on 2026-10-16. The domain was registered through NameSilo, LLC on 2024-01-30, and its SSL certificate, issued by Let's Encrypt / YR2, was scanned on 2026-10-16.

Interpretation

PhishDestroy contains an internal listing for 2hmes.com, which records its presence in a security-focused database. VirusTotal provides a quantitative measurement of detections from multiple scanners, while OTX pulses offer community-driven security intelligence. These sources contribute distinct types of technical and reputational data relevant for ongoing monitoring.

Recommended Actions

For 2hmes.com, preserve the OpenPhish, VirusTotal, and OTX records for future reference and comparison. Review the PhishDestroy listing alongside these sources to track any changes in security-related observations. Continue to document and compare these dated records to inform ongoing analysis.

Data coverage & collection

22 · datasets with records / 9 · 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
2 / 92 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
3 · community references
External blocklists
0 · external matches
Cloudflare Radar
pulitoCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
NameSilo, LLCCollection time not recorded
Network & DNS
176.9.116.24 · 4 · nameserversCollection time not recorded
Certificato TLS
Let's Encrypt / YR2
Page captures
3 · retained captures
HTML archives
1 · retained responses
Page analysis
0 · 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
73/100 · mobile performance
Recorded subdomains
11 · retained hostnamesCollection time not recorded
Availability history
4 · stored state changes
Source observation history
1 · stored source events
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 9

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

  • URLQuery
  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • Response records
  • Lookalike relationships
  • Segnalazioni della comunità
  • Chainabuse records
Download the dated observations and supporting metadata.

Blocklist records

0 · external source matches

Stato della lista di blocco pubblica

Domain, network & archive

NameSilo, LLC · 176.9.116.24 · DNS, TLS and retained responses

Domain details

Dominio
URLScan verdict Malevolo score 100 Phishing brand: Documentlure report ↗
Reputazione IP abuse score 0/100 1 report Bad Web BotWeb App Attack checked 16/10/2026
OTX tags 2026-10all-domainsblocklistcryptodominidrainerfraudlivemonthlyphishdestroyphishingscam
Registrar NameSilo US(US) PhishDestroy Investigation
Contatto abusiabuse@namesilo.com, ammari77@gmail.com, abuse@hetzner.com
Registro ICANNICANN Lookup (RDAP) →
Ricerca WHOISICANN RDAP per 2hmes.com →
RegistrazioneCreato 30/01/2024 — Expires 30/01/2027
Stato HTTP200
Dettagli tecniciProvenance & timestamps
Rilevato per la prima volta16/10/2026
DOM Analysisanalyzed 16/10/2026score 81/100
Submitted URLhttp://2hmes.com/schwartzmfg/schwartzmfg.html
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
176.9.116.24
Network ASN
AS24940
Organization
Hetzner Online GmbH
Observed location
Falkenstein, DE
Server header
LiteSpeed
Nameserver 4
  • ns1.capconnect.com
  • ns2.capconnect.com
  • ns3.capconnect.com
  • ns4.capconnect.com
Mail routing 1 MX record
  • 2hmes.compriority 0

Location describes the IP network.

Certificato TLS

Issuer
Let's Encrypt / YR2
Valid from
2026-09-17 04:27:51
Valid until
2026-12-16 04:27:50
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-16 01:02:06 UTC
Collection source
PhishDestroy collector
Certificate fingerprint082898961dbcde4349d9681b8d2e02e52facbaf53778fa80479baeb57b688ec9

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

viewdns.info · 176.9.116.24rapiddns.io

Latest Classified Outcome 2026-10-17 22:46:35 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 22:46:35 UTC
RDAP registration Sconosciuto
Observed timeline last reachable: 2026-10-17 22:46:35 UTC last content: 2026-10-17 22:46:35 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
Recorded subdomains11

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

  • ammari.2hmes.comDomain record
  • cpanel.2hmes.comDomain record
  • cpcalendars.2hmes.comDomain record
  • cpcontacts.2hmes.comDomain record
  • mail.2hmes.comDomain record
  • rima-unicos.2hmes.comDomain record
  • webdisk.2hmes.comDomain record
  • webmail.2hmes.comDomain record
  • www.2hmes.comDomain record
  • www.ammari.2hmes.comDomain record
  • www.rima-unicos.2hmes.comDomain record

The original observation time is not recorded for these hostnames.

Tecnologie · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Segnala questo dominio Invia le prove e contribuisci a proteggere gli altri

Analisi di VirusTotal

2 / I fornitori di sicurezza 92 hanno contrassegnato questo dominio
View on VT
Last analyzed First positive detection
alphaMountain.ai
DNS8

Prove archiviate

Wayback Machine Snapshot
È disponibile un'istantanea storica per la revisione delle prove
View Archive
Analisi delle prestazioni del sito

Google PageSpeed Insights — mobile performance audit of 2hmes.com · checked Oct 16, 2026

73
Needs Work
Performance
FCP
2.55s
First Contentful Paint
LCP
5.7s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
4.36s
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://2hmes.com/schwartzmfg/schwartzmfg.html
One moment, please...
Risposta
HTTP 200
HTML body
11.6 KB
Compressed
5.0 KB
Links
0 internal · 0 external
Selected response headers
Server: openresty/1.31.1.1
Content-Type: text/html
Cache-Control: private, no-cache, no-store, must-revalidate, max-age=0
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 7
Cache-Control
private, no-cache, no-store, must-revalidate, max-age=0
cf-edge-cache
no-cache
Connection
keep-alive
Content-Length
11926
Content-Type
text/html
Date
Fri, 16 Oct 2026 00:28:56 GMT
Server
openresty/1.31.1.1

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

Archived
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

Reachable (legacy)
/robots.txt
HTTP response
200
Observed at
2026-10-16 00:28:57 UTC
Fonte
legacy scan archive

A legacy scan recorded a successful response. The file contents were not retained.

Sitemap

Reachable (legacy)
/sitemap.xml
HTTP response
200
Observed at
2026-10-16 00:28:57 UTC
Fonte
legacy scan archive

A legacy scan recorded a successful response. The file contents were not retained.

security.txt

Reachable (legacy)
/.well-known/security.txt
HTTP response
200
Observed at
2026-10-16 00:28:57 UTC
Fonte
legacy scan archive

A legacy scan recorded a successful response. The file contents were not retained.

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

Sospetto cloaking: i titoli dello scanner e quelli dei visitatori non corrispondono

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
openresty/1.31.1.1
Indirizzamento delle acquisizioni
Local archiviato l'2026-10-16 00:28:57, UTC

Nota dello scanner: alive_content: raw=ok; http=200; via=https_proxy; server=openresty/1.31.1.1

Titolo visualizzato sullo scanner di sicurezzaOne moment, please...
Titolo visualizzato agli utenti che visitano il sito tramite browserSecure Document — Soft Edition (Wide)
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

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. Threat First Observed 2026-10-16 00:30:05 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 176.9.116.24.
Stored observation history5

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

    live_content→Sconosciuto

    probe_inconclusive

  3. Availability monitor · Recorded state

    Sconosciuto→live_content

    content_served

  4. Availability monitor · First collection record

    Raggiungibile

  5. Availability monitor · Recorded state

    Sconosciuto

    probe_inconclusive

Pipeline di risposta alle minacce

Scoperta
Analysis
Monitoring

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

Minaccia rilevata
2hmes.com rilevati e inseriti in coda per un’analisi completa
16/10/2026
URLScan.io Capture
Memorizzato URLScan report with capture artifacts
16/10/2026
URLScan Verdict
URLScan returned a malicious verdict · score 100
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.
Web Archive
Preserved in Wayback Machine — historical evidence archived
16/10/2026
VirusTotal
2/92 recorded on VirusTotal
16/10/2026
OTX Community References
3 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
16/10/2026
Registrar Context: NameSilo
Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
Brand Impersonation
Impersonation of Documentlure
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
16/10/2026
Technical Analysis Recorded
Il report contiene tecnologia archiviata o risultati di analisi forensi.
18/10/2026
DestroyList pubblicato
Listed in the public PhishDestroy/DestroyList repository
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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecRecensione del sito AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Related infrastructure

Shared hosting, registrar records and related domains

Evidence & investigation tools

Original reports, independent checks and evidence links

Dati e relazioni esterne

Analisi della sicurezza
URLScan Malevolo VirusTotal 2 det. ChainPatrol URLQuery SSL Laboratori Hostname coverage not recorded CF Radar Apri il rapporto OTX 3 refs WOT ScamAdviser Verifica lista nera URLVoid Sucuri SiteCheck Osservatorio MDN
OSINT e intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certificati WHOIS Wayback Archived
DNS e rete
nslookup.io DNS bgp.tools ASN /Percorso
SEO e dominio
SpyFu Moz DA/PA Ahrefs Backlink
Analisi approfondita
Analisi approfondita

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Questo sito ti ha influenzato in qualche modo?

4 evidence signal groups linked 0 stored notification records Ultimo attivo conosciuto

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.

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.

Immediate steps Find reporting contacts
Official reporting routes
Europol
Trova il canale di segnalazione ufficiale per il tuo paese dell'UE
National police directory
Find your country
PhishDestroy listing review Non un rapporto delle forze dell'ordine
Ricorso in materia di domini
Richiedi una revisione se possiedi questo dominio e ritieni che l'elenco non sia corretto
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 2hmes.com)
  • 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

Verifica qualsiasi dominio

Analisi delle minacce utilizzando blocklist archiviate, WHOIS, DNS e prove di scansione pubblica

Scansiona ora

Segnala un tentativo di phishing

Segnala i domini sospetti al nostro database delle minacce — proteggi la comunità

Segnala

Feed in tempo reale sulle minacce

Segnalazioni recenti di phishing e modifiche osservate della disponibilità

Monitora

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: 2hmes.com

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 “Secure Document — Soft Edition (Wide)” e potrebbe spacciarsi per Documentlure.

Al momento di 2026-10-16 01:03:29 UTC, 2hmes.com ha ricevuto rilevamenti dai motori di sicurezza 2.

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.

Se ritieni che questo elenco sia impreciso, presentare ricorso. Per conoscere la nostra metodologia, visita Pagina delle domande frequenti.

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