VirusTotal
7 / 91
“Google Meet”
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.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='meetcall-liive.online', port=80): Max retries exceeded with url: / (Caused by NewConnectio
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 reputation is not attributed to this domain.
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.
12 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.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive