Motori di sicurezza che segnalano un rilevamento: 6. 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 trustandsafety@support.aws.com.
The latest stored availability evidence still shows the domain reachable; 12 days 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.
Stored evidence for bitnest.finance: VirusTotal recorded 4 detections among 91 scanners on 2026-09-29. 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 bitnest.finance. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 4 detections among 91 scanners in the stored snapshot dated 2026-09-29. 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-29 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 bitnest.finance in the snapshot dated 2026-09-29. 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 bitnest.finance 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 bitnest.finance on 2026-09-29. The MetaMask and SEAL blocklist snapshot is dated 2026-09-29 and remains a separate event in the stored timeline. The registration date is separately recorded as 2024-10-23. 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 bitnest.finance, the registrar field records Amazon Registrar, Inc.; this is kept as an exact source value. The source stores 188.114.97.1 as the observed address in this record. The registration date for bitnest.finance is recorded as 2024-10-23. 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 bitnest.finance record states that VirusTotal recorded 4 detections among 91 scanners on 2026-09-29. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-29. PhishDestroy remains a separate publisher catalogue entry in the stored record. For bitnest.finance, the registrar field records Amazon Registrar, Inc.; this remains separate from the other source fields. The observed address field in this record contains 188.114.97.1. The supported conclusion is bounded to the exact stored observations for bitnest.finance. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to bitnest.finance during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain bitnest.finance 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 bitnest.finance. The stored record does not justify extending that rule to 188.114.97.1 or to other infrastructure records.
Analisi di rilevamento ed evasione
Verifica del cloaking e della distribuzione del traffico
Non ancora scansionatoNon è 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:alive_content: raw=ok; http=200; via=https_direct; server=cloudflare
Verifica delle impronte digitali in tempo reale TDS
Sette impronte digitali di Keitaro più un confronto tra crawler e browser, eseguiti dallo scanner PhishDestroy quando questa finestra è aperta.
DOM Analysisanalyzed 09/10/2026score 90/1007 brand signals
Submitted URLhttps://bitnest.finance/
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationContenuto attivoOrdinary HTTP content served90%2026-10-11 01:41:56 UTC
RDAP registrationSconosciuto
Observed timelinelast reachable: 2026-10-11 01:41:56 UTClast content: 2026-10-11 01:41:56 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.
Tecnologie · 9 identified
A
Amazon Web Services
PaaS
Amazon Web Services (AWS) is a comprehensive cloud services platform offering compute power, database storage, content delivery and other functionality.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Amazon CloudFront is a fast content delivery network (CDN) service that securely delivers data, videos, applications, and APIs to customers globally with low latency, high transfer speeds.
Google PageSpeed Insights — mobile performance audit of bitnest.finance· checked Sep 29, 2026
56
Needs Work
Performance
FCP
9.58s
First Contentful Paint
LCP
14.56s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
43ms
Total Blocking Time
SI
9.58s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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.
Threat First Observed2026-09-29 09:36:24 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 188.114.97.1.
Pipeline di risposta alle minacce
Scoperta
Analysis
Notifications
Monitoring
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Minaccia rilevata
bitnest.finance rilevati e inseriti in coda per un’analisi completa
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.
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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
**Incident Report Summary – Bitnest Crypto Scam Investigation**
An investigation was conducted into a suspected crypto investment scam operating under the name **Bitnest**, primarily involving the domains **bitnest.xin** and **bitnest.me**, along with multiple related domain v
1 report filed for bitnest.finance (1 written by a person) · category: Fake Project · source checked
“**Incident Report Summary – Bitnest Crypto Scam Investigation**
An investigation was conducted into a suspected crypto investment scam operating under the name **Bitnest**, primarily involving the domains **bitnest.xin** and **bitnest.me**, along with multiple related domain variants. The investigation combined domain analysis, IP tracing, DNS history review, blockchain behavior analysis, and open-source intelligence.
**Key Findings:**
1. **Scam Indicators**
* Numerous public vict”
— reported by Anonymous on Jan 12, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
Blocklist hits included with submission:MetaMask, SEAL
PDF notice generated Notice text archived (650 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 (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.
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.
6 evidence signal groups linked1 reports recordedUltimo 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.
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 →
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
Infrastruttura e rapporti correlati
Le relazioni archiviate sono raggruppate in base all'attributo di corrispondenza esatta. Un fornitore o un registrar condiviso da solo non dimostra la proprietà comune.
Link diretto Condivide una registrazione o un kit di phishing identico.
Segnale di supporto Condivide l'infrastruttura o un marchio di riferimento; non costituisce prova della presenza di un unico operatore.
Solo per la scoperta Elencato ai fini della navigazione; nessun attributo in comune con questo host.
Mappa delle infrastrutture · bitnest.finance
Ogni riga rappresenta un motivo per cui un dominio è collegato a questo host. I nodi a dimensione intera indicano rilevamenti di VirusTotal, mentre quelli tratteggiati sono già offline. Di seguito è riportato l'elenco completo.
Risultati corrispondenti4
Stesso hash della favicon o stesso titolo della pagina di questo host.
Questi report si risolvono nello stesso IP edge condiviso. Aiutano con l'individuazione dei report ma non implicano la proprietà comune o un server di origine condiviso.
Registrati tramite lo stesso registrar. Un registrar serve milioni di clienti non collegati tra loro, quindi questo dato indica semplicemente un raggruppamento piuttosto che dimostrare un nesso.
