Vai al rapporto di sicurezza
Pannello di controllo analitico
Domain security report
orbitrelaylogs.click favicon

orbitrelaylogs.click

Verdetto di minaccia
CriticoRicorso in materia di domini
Assessment sources

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

Disponibilità Raggiungibile · accesso limitato Risposta raggiungibile; il contenuto della pagina non è stato verificato Osservato · HTTP probe
Segnali di rischio
Rilevamenti VirusTotal: 9/89 Corrispondenze della blocklist memorizzate: 2 URLQuery threat systems: 1 alert Automated brand label: MetaMask Ultimo attivo conosciuto
OTX: 3 refs 11/09/2026 MetaMask 1 Report Sent CDN
API
Registrar
NameSilo
Resolved IP
172.67.172.64
Registered
09/09/2026
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: 9. Blocklist pubbliche che segnalano una corrispondenza: 2. Prestare estrema cautela: non inserire credenziali o informazioni personali.
ABUSE NOTICE · 7D+ 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@identitydigital.com. The latest stored availability evidence still shows the domain reachable; 1 month 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
1 month
Reports sent
1
Latest case ID
PD-20260911-D246BD
Current status
HTTP 403 at latest stored check
Riepilogo del rapporto

orbitrelaylogs.click — Raggiungibile · accesso limitato (HTTP 403). Simulazione del marchio: MetaMask; Tipo di truffa: Impersonation. Riepilogo delle prove: VirusTotal 9/89 (alphaMountain.ai, Chong Lua Dao, CRDF, Forcepoint ThreatSeeker, Fortinet); URLQuery 1 alert; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 100/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
9 det.
URLQuery
URLQuery
1 threat alert
OTX references
3 community refs
URLScan
URLScan
Segnala ↗
Certificato TLS
Within stored validity dates
Let's Encrypt / YE2 · Hostname coverage not recorded
Età
1 mo New
Stato osservato
Raggiungibile · accesso limitato 403
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

9 / 89

Segnala
Interpretation & limits

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

URLQuery

1 threat-system alert

Segnala
Interpretation & limits

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

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.

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.

URLScan verdict

Analisi completata

Segnala
Interpretation & limits

This is the recorded automated analysis. Completion alone 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.

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
Threat Detection Systems 1 alert
Detection System Indicator Verdict Alert
DNS4EU orbitrelaylogs.click malicious Sinkholed
Stored URLQuery scan evidence · Sep 11, 2026 10:00 UTC Open source report

Riepilogo delle prove

Critico
VirusTotal
9/89
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

Stored evidence for orbitrelaylogs.click: VirusTotal recorded 5 detections among 89 scanners on 2026-09-11. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for orbitrelaylogs.click. Each item in this report remains at the scope supplied by its dated source record.

Detection Evidence

VirusTotal records 5 detections among 89 scanners in the stored snapshot dated 2026-09-11. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-11 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.

Source Context

MetaMask and SEAL are recorded as named external blocklist observations for orbitrelaylogs.click in the snapshot dated 2026-09-11. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains orbitrelaylogs.click as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.

Reachability and Timeline

The record first observed orbitrelaylogs.click on 2026-09-11. The MetaMask and SEAL blocklist snapshot is dated 2026-09-11 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-09-09. A URLScan reference was stored on 2026-09-11 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.

Registration and Infrastructure

For orbitrelaylogs.click, the registrar field records NameSilo, LLC; this is kept as an exact source value. The source stores 172.67.172.64 as the observed address in this record. The registration date for orbitrelaylogs.click is recorded as 2026-09-09. The SSL issuer is recorded as Let's Encrypt / YE2 in the snapshot dated 2026-09-11. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.

Conclusion

The orbitrelaylogs.click record states that VirusTotal recorded 5 detections among 89 scanners on 2026-09-11. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-11. PhishDestroy remains a separate publisher catalogue entry in the stored record. For orbitrelaylogs.click, the registrar field records NameSilo, LLC; this remains separate from the other source fields. The observed address field in this record contains 172.67.172.64. The supported conclusion is bounded to the exact stored observations for orbitrelaylogs.click. Any statement beyond those source values would require additional dated material.

Recommended Actions

Avoid submitting sensitive information to orbitrelaylogs.click during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain orbitrelaylogs.click as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to orbitrelaylogs.click. The stored record does not justify extending that rule to 172.67.172.64 or to other infrastructure records.

Data coverage & collection

20 · datasets with records / 11 · 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
9 / 89 · engine detections
URLScan analysis
Automated verdict retained
URLQuery
2 · recorded detections / alerts
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
3 · community references
External blocklists
2 · external matches
Cloudflare Radar
pulitoCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
NameSilo, LLCCollection time not recorded
Network & DNS
172.67.172.64 · 2 · nameserversCollection time not recorded
Certificato TLS
Let's Encrypt / YE2
Page captures
3 · retained captures
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
100/100 · mobile performance
Response records
1 · outgoing report records
Availability history
16 · stored state changes
Source observation history
3 · stored source events
Lookalike relationships
79 · retained relationshipsCollection time not recorded
IP reputation
Network-level observations
Not recorded in this report 11

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

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • HTML archives
  • Page analysis
  • Site configuration files
  • Recorded subdomains
  • Segnalazioni della comunità
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

2 · external source matches

Stato della lista di blocco pubblica

Domain, network & archive

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

Domain details

Dominio
URLScan verdict Analisi completata score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden La reputazione Edge-IP non è attribuita a questo dominio.
OTX tags 2026-09all-domainsblocklistcryptodominidrainerfraudlivemonthlyphishdestroyphishingscam
Registrar NameSilo US(US) PhishDestroy Investigation
Contatto abusiabuse@namesilo.com
Registro ICANNICANN Lookup (RDAP) →
Ricerca WHOISICANN RDAP per orbitrelaylogs.click →
RegistrazioneCreato 09/09/2026 (38d · New) — Expires 09/09/2027
Stato HTTP403 Forbidden
Elapsed Since First Report 40h
Cosa conteggiamo Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Raggiungibile · accesso limitato.
Cosa contiene ogni rapporto I record archiviati dei report in uscita possono fare riferimento a prove disponibili in quel momento, come verdetti dei fornitori, dati di registrazione, dettagli di hosting, classificazioni o screenshot. Questa pagina non deduce l'esatto carico utile consegnato, la ricevuta, la conferma o l'azione da parte di un destinatario.
Dettagli tecniciProvenance & timestamps
Rilevato per la prima volta11/09/2026
Submitted URLhttp://orbitrelaylogs.click/
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.

L’accreditamento è un contratto, non un sigillo di sicurezza. Verifica le tariffe ICANN Leggi il RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nulla viene inviato automaticamente.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
172.67.172.64
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

La reputazione Edge-IP non è attribuita a questo dominio.

Nameserver 2
  • lady.ns.cloudflare.com
  • oswald.ns.cloudflare.com

Location describes the IP network.

Certificato TLS

Issuer
Let's Encrypt / YE2
Valid from
2026-09-09 21:55:59
Valid until
2026-12-08 21:55:58
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-09-11 10:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprint0e2b2d07a6e885b8d667bbe8c2a397ab8388178dee2526be4b8ced7a16003051

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

viewdns.info · 172.67.172.64rapiddns.io

Latest Classified Outcome 2026-10-17 01:13:48 UTC

Primary outcome Provider block observed reason: Cloudflare anti-phishing block 95% confidence
Attribution Cloudflare mechanism: Phishing Interstitial source: Current Http Probe
Evidence layers Availability: Provider blocked Content: Provider blocked DNS: Resolved Registration: Unknown
Latest HTTP observation Provider block observed Cloudflare anti-phishing block Cloudflare Phishing Interstitial 95% provider marker verified 2026-10-17 01:13:48 UTC
RDAP registration Sconosciuto
Observed timeline last reachable: 2026-09-15 22:18:06 UTC current episode first observed: 2026-10-01 01:46:21 UTC observed RIP window: 2026-09-15 22:18:06 UTC → 2026-10-01 01:46:21 UTC · 363.47h midpoint estimate ≈ 2026-09-23 12:02:13 UTC · precision low · basis bounded
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.
Tecnologie · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Segnala questo dominio Invia le prove e contribuisci a proteggere gli altri

Analisi di VirusTotal

9 / I fornitori di sicurezza 89 hanno contrassegnato questo dominio
View on VT
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
Chong Lua Dao
CRDF
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
LevelBlue
SOCRadar
VIPRE
Analisi delle prestazioni del sito

Google PageSpeed Insights — mobile performance audit of orbitrelaylogs.click · checked Sep 11, 2026

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

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
363.47
Estimate basis
Bounded by observations
Estimate precision
Low

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
cloudflare

Nota dello scanner: cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial

Risposta del provider durante la scansione: cloudflare_phishing_interstitial

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.
Risultato salvato
Keitaro TDS

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. Domain Status Transition 2026-09-13 22:18:13 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from dead to alive.
  2. Domain Status Transition 2026-09-13 02:23:05 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  3. Threat First Observed 2026-09-11 09:45:19 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 172.67.172.64.
Stored observation history19

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→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  2. Availability monitor · Recorded state

    blocked→Sconosciuto

    probe_inconclusive

  3. Availability monitor · Recorded state

    Sconosciuto→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  4. Availability monitor · Recorded state

    blocked→Sconosciuto

    probe_inconclusive

  5. Availability monitor · Recorded state

    Sconosciuto→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

Earlier observations 14
  1. Availability monitor · Recorded state

    blocked→Sconosciuto

    probe_inconclusive

  2. Availability monitor · Recorded state

    Sconosciuto→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  3. Availability monitor · Recorded state

    blocked→Sconosciuto

    probe_inconclusive

  4. Availability monitor · Recorded state

    Sconosciuto→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  5. Availability monitor · Recorded state

    blocked→Sconosciuto

    probe_inconclusive

  6. Availability monitor · Recorded state

    Sconosciuto→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  7. Availability monitor · Recorded state

    blocked→Sconosciuto

    probe_inconclusive

  8. Availability monitor · Recorded state

    Sconosciuto→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  9. Availability monitor · Recorded state

    blocked→Sconosciuto

    probe_inconclusive

  10. Availability monitor · Recorded state

    Sconosciuto→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  11. Availability monitor · Recorded state

    Sconosciuto

    probe_inconclusive

  12. Availability monitor · Recorded state

    Non disponibile→Raggiungibile

  13. Availability monitor · Recorded state

    Raggiungibile→Non disponibile

  14. Availability monitor · First collection record

    Raggiungibile

Pipeline di risposta alle minacce

Scoperta
Analysis
Notifications
Monitoring

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

Minaccia rilevata
orbitrelaylogs.click rilevati e inseriti in coda per un’analisi completa
11/09/2026
URLScan.io Capture
Memorizzato URLScan report with capture artifacts
11/09/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
9/89 recorded on VirusTotal
13/09/2026
Rilevamento delle liste di blocco
Si trova in 2 blocklists: MetaMask, SEAL
18/10/2026
OTX Community References
3 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
11/09/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 MetaMask
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
11/09/2026
Technical Analysis Recorded
Il report contiene tecnologia archiviata o risultati di analisi forensi.
18/10/2026
Site Came Back Online
Domain is responding again — monitoring resumed
14/09/2026
Content Observed Unavailable
Il monitoraggio ha registrato una risposta non disponibile (HTTP 403); la causa non è stata stabilita in modo indipendente.
13/09/2026
Sent Report Recorded
Stored outgoing record associated with registrar NameSilo, LLC, 1 abuse contact
abuse@namesilo.com
11/09/2026
DestroyList pubblicato
Listed in the public PhishDestroy/DestroyList repository
11/09/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

Domini simili

79 domini simili memorizzati

etamask.io omission Report interno meetamask.io repetition Report interno megamask.io replacement Report interno metam.ask.io subdomain Report interno metamaak.io replacement Report interno metamadk.io replacement Report interno metamaks.io transposition Report interno metamassk.io insertion Report interno metamsask.io insertion Report interno metamssk.io replacement Report interno metanask.io homoglyph Report interno metanmask.io homoglyph Report interno
Mostra tutto (67)
metasmask.io insertion Report interno metramask.io insertion Report interno mewtamask.io insertion Report interno mmetamask.io homoglyph Report interno mtamask.io omission Report interno mwetamask.io insertion Report interno nmetamask.io homoglyph Report interno metamark.io bitsquatting Report interno metamaskj.io addition Report interno metammask.io homoglyph Report interno metamnask.io homoglyph Report interno emtamask.io transposition m-etamask.io hyphenation meamask.io omission meatmask.io transposition meramask.io replacement mertamask.io insertion metaamask.io repetition metaamsk.io transposition metaask.io omission metalmask.io insertion metamaask.io insertion metamadsk.io insertion metamaek.io replacement metamak.io omission metamas.io omission metamasak.io insertion metamasdk.io insertion metamask-io.com various metamasl.io replacement metamasm.io replacement metamsak.io transposition metamsk.io omission metamusk.io vowel-swap metamzsk.io replacement metarnask.io homoglyph metmaask.io transposition metmask.io omission metsamask.io insertion metsmask.io replacement mettamask.io repetition metwmask.io replacement metyamask.io insertion metzmask.io replacement meyamask.io replacement meytamask.io insertion mitamask.io vowel-swap mnetamask.io homoglyph mretamask.io insertion mrtamask.io replacement mstamask.io replacement mteamask.io transposition mwtamask.io replacement rnetamask.io homoglyph matamask.io bitsquatting mdtamask.io bitsquatting metamasi.io bitsquatting metamasj.io bitsquatting metamaska.io addition metamaskk.io addition metamaskl.io addition metamaso.io bitsquatting metamesk.io bitsquatting metamqsk.io bitsquatting metemask.io bitsquatting netamask.io homoglyph xn--metamas-bhb.io homoglyph

Evidence & investigation tools

Original reports, independent checks and evidence links

Dati e relazioni esterne

Analisi della sicurezza
URLScan Analyzed VirusTotal 9 det. ChainPatrol URLQuery 1 threat alert SSL Laboratori Hostname coverage not recorded CF Radar Apri il rapporto OTX 3 refs WOT ScamAdviser Verifica lista nera URLVoid Sucuri SiteCheck Osservatorio MDN
Istantanea delle prove inviate
Sent: Ledger records: 1 Case ID: PD-20260911-D246BD Recipient: abuse@identitydigital.com
Page title stored with report: orbitrelaylogs.click/
PDF notice generated Notice text archived (653 chars)
Abuse notice text as sent to the provider 
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (US):
18 U.S.C. § 1343 - Wire Fraud
18 U.S.C. § 1030 - Computer Fraud and Abuse Act (CFAA)
15 U.S.C. § 45 - FTC Act (Deceptive Practices)
Federal laws prohibit wire fraud, computer fraud, and deceptive business practices.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
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
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?

6 evidence signal groups linked 1 stored notification records Raggiungibile · accesso limitato
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 orbitrelaylogs.click)
  • 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: orbitrelaylogs.click

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.

Al momento di 2026-09-13 02:07:04 UTC, orbitrelaylogs.click ha ricevuto rilevamenti dai motori di sicurezza 9.

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