VirusTotal
7 / 91 engine detections
Raporu aç“Google Meet”
Google taklidi: meetcall-liive.online — İçerik kullanılamıyor. Kanıt özeti: VirusTotal 7/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet…
Özgün adli kaydı korumak için aşağıdaki ayrıntılı PhishDestroy AI analizi İngilizce bırakılmıştır.
7 / 91 engine detections
Raporu açDBL_PHISH
no community references
Raporu aç80/100
Raporu açNo threat flag
Raporu açNo malicious flag
Raporu açResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
meetcall-liive.online was registered on 15 July 2026 through Namecheap Inc and is currently active. The domain resolves to the IPv4 address 216.198.79.1 and is served by the registrar‑default nameservers dns1.registrar-servers.com and dns2.registrar-servers.com. It is flagged as a generic phishing site and remains under investigation. VirusTotal indicates the domain has been scanned by 91 security vendors; at the time of analysis no vendor flagged it, though the lack of a detection does not constitute confirmation of safety. No page title, brand reference, or content snapshot is available, so the specific phishing lure and credential‑harvesting mechanisms are not yet known. Infrastructure analysis reveals a single IP endpoint without observable use of CDNs, load balancers, or secondary hosting services, a pattern consistent with short‑lived phishing deployments that rely on minimal exposure. Defenders should assume the domain is malicious until proven otherwise. Recommended mitigation steps include adding the domain and its resolving IP address to network block lists, configuring email gateways to reject messages containing the domain, and monitoring DNS queries for changes to the nameserver records. Correlating any credential submissions or login attempts referencing meetcall-liive.online with existing threat‑intel feeds will aid in assessing campaign scope. Continuous observation of the domain’s DNS and hosting attributes is advised to detect any evolution of the threat infrastructure.
Last checked
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.
Edge-IP itibarı bu etki alanıyla ilişkilendirilmez.
dns1.registrar-servers.comdns2.registrar-servers.comeforward1.registrar-servers.compriority 10eforward2.registrar-servers.compriority 10eforward3.registrar-servers.compriority 10eforward4.registrar-servers.compriority 15eforward5.registrar-servers.compriority 20Location describes the IP network.
3977f913fcadd58803fa0ba27ba4e1fbc79781e0f17aa1defea90e58ed1a4ec5Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
meetcall-liive.online
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
Erişilebilir→Mevcut değil
7/91 engine detections
View sourcePage captured
View sourceNo threat flag
View sourcemeetcall-liive.online
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
Hesap kimlik bilgilerini, kişisel bilgileri veya ödeme bilgilerini girdiyseniz ya da bu alan adından bir dosya indirdiyseniz hemen harekete geçin. Aşağıda olayı bildirmenize ve kendinizi korumanıza yardımcı olacak kaynaklar bulunmaktadır.
resmi siber suç iletişim bilgileri veya şikayet taslağı oluştur → almak için ülkenizi seçin.
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 ↗
meetcall-liive.online)Tüm ayrıntıları bilmeseniz bile — yine de şikayette bulun. Kısmi bilgiler de soruşturmalara yardımcı olmaktadır.
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
Saklanan engelleme listesi, WHOIS, DNS ve genel tarama kanıtlarını kullanarak tehdit analizi
Şimdi TaraŞüpheli alan adlarını tehdit veritabanımıza bildirin — topluluğu koruyun
BildirSon kimlik avı raporları ve gözlemlenen kullanılabilirlik değişiklikleri
İzleCanlı tehditleri izleyin veya bunun yanlış bir uyarı olduğunu düşünüyorsanız bu kayda itiraz edin
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.