googlemeet.ink is a domain that mimics the branding of Google Meet, a legitimate video conferencing service. PhishDestroy first observed this domain on 2026-10-18. The site is currently unreachable, but its infrastructure remains active. The domain was registered the day before on 2026-10-17.
How the scam works
This domain uses Google Meet’s branding to lure users into entering credentials or downloading malicious software under the guise of a meeting link. Victims risk exposing login details, installing malware, or having their accounts hijacked. The page title and branding suggest an attempt to exploit trust in Google’s services.
Evidence
The domain was detected by 1 out of 92 VirusTotal engines, flagged by LevelBlue. PhishDestroy has listed googlemeet.ink since 2026-10-18, and OTX pulses recorded 4 mentions. The site’s content was unreachable at the time of analysis, limiting further technical evidence.
Infrastructure
The domain was registered via PDR Ltd. d/b/a PublicDomainRegistry.com on 2026-10-17. It is hosted on IP address 144.124.249.193 with a TLS certificate issued by Let's Encrypt / YR2.
What to do
If you visited this domain, avoid entering any credentials or downloading files. Run a malware scan on your device. For defenders, block the domain and IP at the network level. Monitor for any unauthorized access to accounts linked to this domain.
RegistrationCreated Oct 17, 2026 (1d · Brand New!)—Expires Oct 17, 2027
HTTP Status302 Found (Temporary)
Technical detailsProvenance & timestamps
First DetectedOct 18, 2026
DOM Analysisanalyzed Oct 19, 2026score 96/100
Submitted URLhttps://googlemeet.ink/
Favicon Hash
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
144.124.249.193
Network ASN
AS216071
Organization
SERVERS TECH FZCO
Observed location
Amsterdam, NL
Server header
nginx/1.28.0
Nameservers 4
ns1.vdsina.com
ns2.vdsina.com
ns3.vdsina.com
ns4.vdsina.com
Mail routing 1 MX record
mx.googlemeet.inkpriority 10
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YR2
Valid from
2026-10-17 11:38:14
Valid until
2027-01-15 11:38:13
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-18 22:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint7003ed24c1727b369cca3e4b02ad9d55ec576e60dd807235929a875a58283894Certificate names · 1 SANs
www.googlemeet.ink
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
6 evidence signal groups linked1 stored notification recordsLast known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including googlemeet.ink)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
About this reportSources, observation dates and corrections
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.
(US)
