VirusTotal
4 / 92 engine detections
Apri il rapporto“В Контакте | Добро пожаловать”
Dominio in blocklist: c2n.biz — Non verificato. Riepilogo delle prove: VirusTotal 4/92 (alphaMountain.ai, CRDF, DNS8, SOCRadar); URLQuery 2 det.; 1 external…
L’analisi dettagliata di PhishDestroy AI resta in inglese per preservare il rapporto forense originale.
4 / 92 engine detections
Apri il rapporto2 det.
Apri il rapporto4 community references
Apri il rapportoprovider verdict: clean
Apri il rapportoNo threat flag
Apri il rapportoNo malicious flag
Apri il rapportoResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
PhishDestroy classifies c2n.biz as a suspicious domain based on external scanner detections. The domain was first seen by PhishDestroy on 2026-10-21, returning HTTP 200 with the recorded title “В Контакте | Добро пожаловать”.
The current evidence does not reveal a concrete fraud technique. Domains that receive multiple malicious detections are often used for phishing, credential harvesting, or other deceptive activities, but no such behavior was observed on the captured page.
VirusTotal scanned the domain on 2026-10-21 and returned four detections across 92 engines, including two malicious vendors (CRDF, SOCRadar) and two suspicious. Google Safe Browsing checked the same day and did not flag the domain. urlscan.io performed a scan on 2026-10-21 and reported the site as clean. The external OpenPhish blocklist lists c2n.biz, and PhishDestroy’s internal list marks it as suspicious. OTX recorded four pulses referencing the domain on 2026-10-21.
The domain was registered on 2006-05-15 through PDR Ltd. d/b/a PublicDomainRegistry.com. Hosting records show the domain resolved to IP 195.20.18.201, belonging to AVAHOHST AVA HOST SRL in Moldova. The TLS certificate observed on 2026-10-21 was issued by Let’s Encrypt / YR2.
Visitors should avoid entering any credentials or personal data on the site; if they have already done so, they should change passwords and monitor accounts for unusual activity. Security teams should add c2n.biz to blocklists, review logs for connections to the recorded IP address, and apply appropriate network controls. Continue monitoring threat feeds for any new indicators related to this domain.
Last checked
ns1.helpwebhost.comns2.helpwebhost.comc2n.bizpriority 0Location describes the IP network.
7987cd98dc6af839e924d28df932a98f8cd7a17ef2cdd5dd96cb182d4570165cc3n.infocontent.net.uaSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
cpanel.c2n.bizDomain recordcpcalendars.c2n.bizDomain recordcpcontacts.c2n.bizDomain recordmail.c2n.bizDomain recordmon.c2n.bizDomain recordwebdisk.c2n.bizDomain recordwebmail.c2n.bizDomain recordwww.c2n.bizDomain recordwww.mon.c2n.bizDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of c2n.biz · checked Oct 21, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://c2n.biz/registration/content/ua5384/secs/s42356https://c2n.biz/registration/content/ua5384/secs/s42356/Server: nginxContent-Type: text/htmlContent-Encoding: gzipca786ca2ab4055e2deb9f3e91afd3caf0023a9cc81153bbc120491373b0ccc9bkeep-alivegziptext/htmlWed, 21 Oct 2026 03:25:52 GMTThu, 23 Jan 2014 20:37:02 GMTnginxchunkedAccept-EncodingnosniffEXPIREDEngintron1; mode=blockValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Raggiungibile
4 community references
View sourceNo threat flag
View source4/92 engine detections
View sourcec2n.biz
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
c2n.biz
Listed domains receive at least one abuse report; this entry has no retained notification history.
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 ↗
c2n.biz)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
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.