VirusTotal
3 / 94
SegnalaEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Site is created successfully!”
Assessment based on the stored source evidence below. Review sources →
oauth-consent-v2.digital — Contenuto non disponibile. Tipo di truffa: Credential Phishing. Riepilogo delle prove: VirusTotal 3/94 (alphaMountain.ai, Fortinet, Gridinsoft); URLQuery 1 alert; Spamhaus DBL_PHISH; PhishDestroy score 85/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.
3 / 94
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.
3/12
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
DBL_PHISH
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
checked — no match recorded
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
no community references
SegnalaCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: suspicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
rapporto memorizzato
View stored capture ↗A 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.
0 external matches
DettagliA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Hagezi Threat Feed | oauth-consent-v2.digital |
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.
The domain oauth-consent-v2.digital is flagged by 3 out of 94 vendors on VirusTotal for credential phishing. Despite being taken down, it initially posed a threat by mimicking an OAuth consent page to harvest user credentials. The site was hosted on an IP address managed by CloudFlare, Inc., located in Canada, and registered through NameSilo, LLC.
PhishDestroy detected this domain on the same day it was created, March 29, 2026, highlighting its rapid identification capabilities. The domain also appears on public blocklists from PhishDestroy, MetaMask, and SEAL, indicating its malicious intent and the risk it posed to users. The platform risk score for this domain is 63 out of 100, underscoring its potential danger before it was taken offline.
The phishing operation likely targeted users by presenting a fake OAuth consent screen, a common technique to steal login credentials. The swift takedown of the domain mitigated further damage, but its initial activity highlights the importance of early detection in combating phishing threats. The domain's presence on multiple blocklists shows a coordinated effort to neutralize its impact quickly.
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.
These checks have no retained result. This does not mean they passed or that a scan is running.
0 · external source matches
NameSilo, LLC · 188.114.97.3 · DNS, TLS and retained responses
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.
elisabeth.ns.cloudflare.comLocation describes the IP network.
Saved 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 oauth-consent-v2.digital · checked Mar 29, 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.
Nota dello scanner: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='oauth-consent-v2.digital', port=80): Max retries exceeded with url: / (Caused by NewConnec
Nessun risultato di verifica live salvato.
1 · outbound report records
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
dns_inactive→Sconosciuto
probe_inconclusive
Sconosciuto→dns_inactive
dns_nxdomain
dns_inactive→Sconosciuto
probe_inconclusive
Sconosciuto→dns_inactive
dns_nxdomain
dns_inactive→Sconosciuto
probe_inconclusive
Sconosciuto→dns_inactive
dns_nxdomain
dns_inactive→Sconosciuto
probe_inconclusive
Sconosciuto→dns_inactive
dns_nxdomain
dns_inactive→Sconosciuto
probe_inconclusive
Sconosciuto→dns_inactive
dns_nxdomain
dns_inactive→Sconosciuto
origin_unreachable · http_5xx
Sconosciuto→dns_inactive
dns_nxdomain
dns_inactive→Sconosciuto
origin_unreachable · http_5xx
Sconosciuto→dns_inactive
dns_nxdomain
dns_inactive→Sconosciuto
origin_unreachable · http_5xx
dns_inactive
dns_nxdomain
13 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
Retained community reports and observations
Segnalato da 1 membro della comunità; prima osservazione il 29/03/2026
Original reports, independent checks and evidence links
PD-20260329-1880EB Recipient: abuse@namesilo.com Registrar: NameSilo LLC (United States) Policy Violations: Prohibits “domains and websites engaging in, promoting or facilitating phishing attacks”, spam and malware; abuse reports trigger investigation and suspension Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act 15 U.S.C. §7701–7713
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 ↗
oauth-consent-v2.digital)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.
Il sito acquisito mostrava il titolo della pagina “Site is created successfully!”.
Al momento di 2026-03-30 03:02:06 UTC, oauth-consent-v2.digital ha ricevuto rilevamenti dai motori di sicurezza 3.
Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.
Se ritieni che questo elenco sia impreciso, presentare ricorso. Per conoscere la nostra metodologia, visita Pagina delle domande frequenti.