VirusTotal
8 / 89
SegnalaEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
Assessment based on the stored source evidence below. Review sources →
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@gen.xyz.
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.
orbitrelaydata.cfd — Raggiungibile · accesso limitato (HTTP 403). Simulazione del marchio: MetaMask; Tipo di truffa: Impersonation. Riepilogo delle prove: VirusTotal 8/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft); URLQuery 1 alert; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 98/100. Registrar: NameSilo.
L’analisi dettagliata di PhishDestroy AI resta in inglese per preservare il rapporto forense originale.
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.
8 / 89
SegnalaEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
1 threat-system alert
SegnalaAlerts refer to the preserved scan. They do not describe the current state of the site.
2 external matches
DettagliA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
4 community references
SegnalaCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
rapporto memorizzato
View stored capture ↗ SegnalaA preserved page image documents what the collector received; a capture is not a safety verdict.
Analisi completata
SegnalaThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
SegnalaA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | orbitrelaydata.cfd |
malicious | Sinkholed |
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.
Stored evidence for orbitrelaydata.cfd: VirusTotal recorded 4 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 orbitrelaydata.cfd. Each item in this report remains at the scope supplied by its dated source record.
VirusTotal records 4 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.
MetaMask and SEAL are recorded as named external blocklist observations for orbitrelaydata.cfd 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 orbitrelaydata.cfd 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.
The record first observed orbitrelaydata.cfd 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.
For orbitrelaydata.cfd, the registrar field records NameSilo, LLC; this is kept as an exact source value. The source stores 104.21.29.138 as the observed address in this record. The registration date for orbitrelaydata.cfd 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.
The orbitrelaydata.cfd record states that VirusTotal recorded 4 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 orbitrelaydata.cfd, the registrar field records NameSilo, LLC; this remains separate from the other source fields. The observed address field in this record contains 104.21.29.138. The supported conclusion is bounded to the exact stored observations for orbitrelaydata.cfd. Any statement beyond those source values would require additional dated material.
Avoid submitting sensitive information to orbitrelaydata.cfd during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain orbitrelaydata.cfd 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 orbitrelaydata.cfd. The stored record does not justify extending that rule to 104.21.29.138 or to other infrastructure records.
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.
These checks have no retained result. This does not mean they passed or that a scan is running.
2 · external source matches
NameSilo, LLC · 104.21.29.138 · DNS, TLS and retained responses
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
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.
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.
La reputazione Edge-IP non è attribuita a questo dominio.
hope.ns.cloudflare.comnero.ns.cloudflare.comLocation describes the IP network.
665a5e1294da1bee06d336d2d8eca4c7c7fe6ebd3338a631d1289658b26841e6Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of orbitrelaydata.cfd · checked Sep 11, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored browser and crawler observations
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.
cloudflareNota 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
1 · outbound report records
104.21.29.138.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Sconosciuto→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Sconosciuto
probe_inconclusive
Sconosciuto→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Sconosciuto
probe_inconclusive
Sconosciuto→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Sconosciuto
probe_inconclusive
Sconosciuto→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Sconosciuto
probe_inconclusive
Sconosciuto→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Sconosciuto
probe_inconclusive
Sconosciuto→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Sconosciuto
probe_inconclusive
Sconosciuto→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Sconosciuto
probe_inconclusive
Sconosciuto→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Sconosciuto
probe_inconclusive
Non disponibile→Raggiungibile
Raggiungibile→Non disponibile
Raggiungibile
14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Shared hosting, registrar records and related domains
79 domini simili memorizzati
Original reports, independent checks and evidence links
PD-20260911-6199AB Recipient: abuse@gen.xyz 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.
Recovery steps, reporting contacts and complaint drafts
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.
Seleziona il tuo Paese per ottenere contatti ufficiali del crimine informatico o creare una bozza di reclamo →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
orbitrelaydata.cfd)Anche se non conosci tutti i dettagli — sporgere comunque denuncia. Anche le informazioni parziali sono comunque utili alle indagini.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Analisi delle minacce utilizzando blocklist archiviate, WHOIS, DNS e prove di scansione pubblica
Scansiona oraSegnala i domini sospetti al nostro database delle minacce — proteggi la comunità
SegnalaSegnalazioni recenti di phishing e modifiche osservate della disponibilità
MonitoraControlla le minacce in tempo reale oppure contesta questa segnalazione se ritieni che si tratti di un falso positivo
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:02 UTC, orbitrelaydata.cfd ha ricevuto rilevamenti dai motori di sicurezza 8.
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.