VirusTotal
6 / 91
“meeting-in.online is registered at Namecheap”
meeting-in.online — Ultimo attivo conosciuto (HTTP 302). Tipo di truffa: Impersonation. Riepilogo delle prove: VirusTotal 6/91 (alphaMountain.ai, Chong Lua Dao, CRDF, Forcepoint ThreatSeeker, Gridinsoft); 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 95/100. Registrar: Namecheap.
L’analisi dettagliata di PhishDestroy AI resta in inglese per preservare il rapporto forense originale.
This domain, meeting-in.online, is currently under investigation as a generic phishing threat. It was registered on July 20, 2026, through NAMECHEAP INC, a registrar commonly used by malicious actors. The domain resolves to IP address 162.255.119.24, which hosts the site. The nameservers are dns1.registrar-servers.com and dns2.registrar-servers.com, typical of NAMECHEAP's default DNS service. As of the report date, July 21, 2026, the domain remains active and has been blocked by PhishDestroy. It appears on one security blocklist, indicating some level of threat recognition. VirusTotal scanned the domain with 91 vendors, but zero currently flag it; however, absence of detections does not confirm safety, as new phishing sites often evade initial detection. The domain’s recent creation (one day before the report) is a common indicator of ephemeral phishing infrastructure, designed for short-term campaigns. No page title, brand target, or scam type was provided, so the exact content of the site has not been analyzed. Defenders should treat this domain as suspicious, monitor for any changes in detection status, and block access at the network level. Further investigation, including manual inspection of the landing page and analysis of any phishing kits, is recommended to confirm the threat profile.
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.
namecheap-nginxNota dello scanner: redirect: raw=redirect_302; http=302; via=http_proxy; location=http://www.meeting-in.online/; server=namecheap-nginx
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.
dns1.registrar-servers.comdns2.registrar-servers.comeforward2.registrar-servers.compriority 10eforward1.registrar-servers.compriority 10eforward3.registrar-servers.compriority 10eforward4.registrar-servers.compriority 15eforward5.registrar-servers.compriority 20Location describes the IP network.
9 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.
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
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