Skip to security report
meet-google.club favicon
Domain security and threat intelligence

meet-google.club

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

PhishDestroy first recorded meet-google.club on 2026-11-18. Listed by external blocklists: MetaMask, SEAL.

Page title: “Проверка безопасности”

More about the sources
Recorded security signals

Listed by external blocklists: MetaMask, SEAL. Use caution — do not enter credentials or personal information.

Stored blocklist matches: 2
Registrar
GermanyGname
Resolved IP
Netherlands146.103.106.162Servers Tech Fzco
First seen by PhishDestroy
2026-11-18
Page captures
open gallery
Reports sent
view timeline
2026-11-18 1 Report Sent

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

ABUSE NOTICE · 72H+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is complaint@gname.com. The latest stored availability evidence still shows the domain reachable; 3 days has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
3 days
Reports sent
1
Latest case ID
PD-A5192774769F885FF247
Current status
Observed active at latest stored check

Analysis

Domain summary

PhishDestroy first recorded meet-google.club on 2026-11-18. Listed by external blocklists: MetaMask, SEAL. Risk: high (evidence score 66/100). Registrar: Gname. Hosting: Servers Tech Fzco. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

High
Blocklist matches
2 external + PhishDestroy list
Hosting
Netherlands146.103.106.162Servers Tech Fzco
Registrar
GermanyGname
Page captures
9

Recorded source summary

PhishDestroy first observed meet-google.club on Nov 18, 2026. The hostname explicitly references Google; stored content metadata identifies the same apparent target. The captured page title is “Проверка безопасности”. Current evidence score: 66/100 (high).

Positive findings are stored from 2 sources: MetaMask and SEAL. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Nov 22, 2026 at 11:20 UTC. Additional recorded evidence: VirusTotal recorded 0 detections among 92 engines on Nov 18, 2026 at 01:35 UTC.

The collector marked the hostname reachable on Nov 19, 2026 at 23:08 UTC, but did not retain the HTTP response code. Registration records for the domain list Gname.com Pte. Ltd. as the registrar and Nov 17, 2026 as the creation date. Registration preceded first observation by 1 day. At collection time, the hostname resolved to 146.103.106.162 on AS216071 (Servers Tech Fzco). The recorded endpoint location is Amsterdam, NL. The stored server header is nginx/1.18.0 (Ubuntu). DOM analysis on Nov 18, 2026 at 23:20 UTC returned 0/100; the source detections above were recorded separately. The evidence archive retains 9 visual captures from PhishDestroy, URLScan, Cloudflare Radar, and URLQuery. TLS metadata lists YR2 as the certificate issuer with validity through Feb 16, 2027.

The content indicators and 2 positive source findings support the current Google impersonation and phishing classification. The target field identifies Google.

Source evidence 2 sources

URLScan

Page capture

SHA-256 8e00995b…5ad3265

Open report
URLScanOriginal source recordObserved: 22 fields
Separate monitor record

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

UUID
01a1f020-3ad9-7780-8b4b-893d2822c72c
Enriched at
2026-11-19T09:11:45Z
Source timestamps
Urlscan enriched at: 2026-11-19 10:11:45

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
VirusTotalOriginal source recordObserved: 11 fields
Open complete records
Website checksOriginal source recordRetrieved: 23 fields

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
1972

Page title and metadata

Open Graph URL
https://meet-google.club/
Page title
Проверка безопасности
Open Graph type
website
Open Graph image
/uploads/ogImage-1793282828051-290955807.png
Open Graph title
Meet
Open Graph description
Real-time meetings by Google. Using your browser, share your video, desktop, and presentations with teammates and customers.

Trackers

Requests
2
Observed services
  • Name
    Google
    Company
    Google
    Country
    US
    Category
    Advertising
    Requests
    1
  • Name
    Google Recaptcha
    Company
    Google
    Country
    US
    Category
    Utilities
    Requests
    1

Forms and mixed content

Scripts without SRI
  • https://www.google.com/recaptcha/api.js
Third-party scripts
1

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
0
Waiting
44
Download
0
Response time, ms
146

TLS connection

ALPN
http/1.1
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 22
  • 80
  • 443

Carbon estimate

Bytes
4628
CO₂, grams
0.0002
Cleaner than, %
88

DNS servers

Nameservers
  • IP address
    162.159.44.170
    Host
    mcgrory.ns.cloudflare.com
  • IP address
    108.162.192.126
    Host
    kim.ns.cloudflare.com
DNS zone
meet-google.club

Page quality

Layout shift (CLS)
0.025
SEO score
82
Speed Index, s
0.79
First Contentful Paint (FCP), s
0.79
Largest Contentful Paint (LCP), s
0.79
Total Blocking Time (TBT), ms
528
Performance score
87
Accessibility score
87
Best practices score
96

Location

IP address
146.103.106.162
ASN
216071
Organization
Servers Tech Fzco
City
Amsterdam
Country
NL

TLS certificate

Subject alternative names
  • meet-google.club
  • www.meet-google.club
Key size, bits
2048
Certificate chain
  • meet-google.club
  • YR2
  • Root YR
  • ISRG Root X1
Issuer
Let's Encrypt / YR2
Serial
05EFCB52C53E2953397F2DAA3F8EB9BB695D
SHA-256
88989555d1758ed0ba44ac2d03a28467f98269387b81f4ec6a464bc513399c82
Subject
meet-google.club
Valid until
Valid from

DNS records

A
  • 146.103.106.162
NS
  • kim.ns.cloudflare.com
  • mcgrory.ns.cloudflare.com
SOA
Primary nameserver
kim.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2420476618
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
146.103.106.162
IP version
4

Redirects

Redirect chain
  • https://meet-google.club

Technology stack

Technologies
  • Node.js
  • Ubuntu
  • Nginx 1.18.0
  • Express
  • reCAPTCHA
  • Open Graph

Registration record

Registrar
Gname.com Pte. Ltd.
Registrar IANA ID
1923
Registrar URL
https://www.gname.com/
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
  • serverTransferProhibited https://icann.org/epp
  • addPeriod https://icann.org/epp
Nameservers
  • kim.ns.cloudflare.com
  • mcgrory.ns.cloudflare.com
DNSSEC
unsigned

HTTP headers

Response headers
Server
nginx/1.18.0 (Ubuntu)
Content-Type
text/html; charset=utf-8
X-Powered-By
Express
Original source fields · JSON
Mail configuration
Spf lookups: 0
Protective DNS results
Resolvers: 12; Blocked count: 0
Web archive observations
Last: 2026-11-18T19:37:24Z; First: 2026-11-18T19:37:24Z; Changes: 0; Days archived: 1; Avg page bytes: 1972
Page title and metadata
Ogurl: https://meet-google.club/; Title: Проверка безопасности; Ogtype: website; Ogimage: /uploads/ogImage-1793282828051-290955807.png; Ogtitle: Meet; Ogdescription: Real-time meetings by Google. Using your browser, share your video, desktop, and presentations with teammates and customers.
Trackers
Requests: 2; Trackers: (Name: Google; Company: Google; Country: US; Category: Advertising; Requests: 1), (Name: Google Recaptcha; Company: Google; Country: US; Category: Utilities; Requests: 1)
Forms and mixed content
No sri: https://www.google.com/recaptcha/api.js; Third party scripts: 1
Status
Up: ✓; Code: 200; Timings: DNS: 0; Wait: 44; Download: 0; Response ms: 146
TLS connection
Alpn: http/1.1; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 22, 80, 443
Carbon
Bytes: 4628; Co2 grams: 0.0002; Cleaner than: 88
DNS server
NS: (IP: 162.159.44.170; Host: mcgrory.ns.cloudflare.com), (IP: 108.162.192.126; Host: kim.ns.cloudflare.com); Zone: meet-google.club
Quality
Cls: 0.025; Seo: 82; Si s: 0.79; Fcp s: 0.79; Lcp s: 0.79; Tbt ms: 528; Performance: 87; Accessibility: 87; Best practices: 96
Location
IP: 146.103.106.162; ASN: 216071; Org: Servers Tech Fzco; City: Amsterdam; Country: NL
SSL
San: meet-google.club, www.meet-google.club; Bits: 2048; Chain: meet-google.club, YR2, Root YR, ISRG Root X1; Issuer: Let's Encrypt / YR2; Serial: 05EFCB52C53E2953397F2DAA3F8EB9BB695D; SHA256: 88989555d1758ed0ba44ac2d03a28467f98269387b81f4ec6a464bc513399c82; Subject: meet-google.club; Valid to: 2027-02-16T07:36:47Z; Valid from: 2026-11-18T07:36:48Z
DNS records
A: 146.103.106.162; NS: kim.ns.cloudflare.com, mcgrory.ns.cloudflare.com; Soa: Nsname: kim.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2420476618; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Message: Site does not serve any HSTS headers.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Get IP
IP: 146.103.106.162; Family: 4
Redirects
Chain: https://meet-google.club
Tech stack
Technologies: Node.js, Ubuntu, Nginx 1.18.0, Express, reCAPTCHA, Open Graph
Registration record
Registrar: Gname.com Pte. Ltd.; Registrar iana ID: 1923; Registrar URL: https://www.gname.com/; Created: 2026-11-17T16:25:08Z; Updated: 2026-11-18T08:27:40Z; Expires: 2027-11-17T16:25:08Z; Status: clientTransferProhibited https://icann.org/epp, serverTransferProhibited https://icann.org/epp, addPeriod https://icann.org/epp; Nameservers: kim.ns.cloudflare.com, mcgrory.ns.cloudflare.com; Dnssec: unsigned
HTTP headers
Headers: Server: nginx/1.18.0 (Ubuntu); Content type: text/html; charset=utf-8; X powered by: Express

Questions about meet-google.club

Is meet-google.club legit?

PhishDestroy rates meet-google.club as high risk (evidence score 66/100) from the recorded evidence; it was first recorded on 2026-11-18. Listed by external blocklists: MetaMask, SEAL. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is meet-google.club safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on meet-google.club. A confirmed blockchain transaction cannot be reversed.

What should I do if I used meet-google.club?

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Downloaded a file — do not open it and scan the device with security software

Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matches2 external + PhishDestroy list · MetaMask · PhishDestroy · SEAL 2
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Page captures (9)

All capture links and hashes (9)
Observed page title
Проверка безопасности
TLS Certificate
Issued by YR2 · stored validity ends in 85 days

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 100 report ↗
IP Reputation Netherlands146.103.106.162 0/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worse This IP address has not been reported to the abuse database yet, but the domain itself is recognized as phishing. 0 reports checked 2026-11-18
Registrar Gname DE(DE)
RegistrationExpires 2027-11-17
Registrant countryGermany VirusTotal WHOIS
Registrant1f8f4166599d23eef651612a2f356ad3s@ VirusTotal WHOIS
Technical detailsProvenance & timestamps
First Detected2026-11-18
DOM Analysisanalyzed 2026-11-19score 0/100
Submitted URLhttp://meet-google.club/
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
Netherlands146.103.106.162
Network ASN
AS216071
AS name
VDSINA SERVERS TECH FZCO, AE
Organization
Servers Tech Fzco
Observed location
NetherlandsAmsterdam, NL
Server header
nginx/1.18.0 (Ubuntu)

Nameservers 2

  • kim.ns.cloudflare.com
  • mcgrory.ns.cloudflare.com

SOA

  • nsname: kim.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2420476618
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
YR2
Valid from
2026-11-18 07:36:48
Valid until
2027-02-16 07:36:47
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint88989555d1758ed0ba44ac2d03a28467f98269387b81f4ec6a464bc513399c82
Certificate names · 2 SANs
  • meet-google.club
  • www.meet-google.club

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Technologies · 5 identified
Open complete records

Archived Evidence

Wayback Machine Snapshot
View Archive

Saved snapshots 1

PageSpeed (mobile): 87

Google PageSpeed Insights — mobile performance audit of meet-google.club ·

87
Needs Work
Performance
FCP
0.79 s
First Contentful Paint
LCP
0.79 s
Largest Contentful Paint
CLS
0.025
Cumulative Layout Shift
TBT
528 ms
Total Blocking Time
SI
0.79 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://meet-google.club/
Final URL: https://meet-google.club/
Проверка безопасности
Response
HTTP 200
HTML body
4.5 KB
Compressed
1.4 KB
Links
0 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx/1.18.0 (Ubuntu)
Content-Type: text/html; charset=utf-8
X-Powered-By: Express
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Open Graph title: Meet
Open Graph description: Real-time meetings by Google. Using your browser, share your video, desktop, and presentations with teammates and customers.
Saved response-header values · 10
Access-Control-Allow-Credentials
true
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Wed, 18 Nov 2026 19:29:43 GMT
Etag
W/"1214-9/ZgMANyJROyBCYPpf0vVQBGwGk"
Server
nginx/1.18.0 (Ubuntu)
Transfer-Encoding
chunked
Vary
Origin
X-Powered-By
Express

Values retained by the collector; long values may be shortened during collection.

Registration & observation details1

Availability observations

Last reachable observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

All stored data111
Open complete records

Captured network requests

Network requests: 16 SHA-256 hashes: 14 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-18 23:54 UTC.

Open this scan on URLScan 01a1f113-a1b0-75fe-adce-92c43b6512b8 ↗

Stored observation history3

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Behind a check page or access restriction

    CAPTCHA page · check page

  2. Availability monitor · Recorded state

    Behind a check page or access restriction

    CAPTCHA page · check page

  3. Domain monitor · First collection record

    Reachable

All retained availability observations11
Open complete records

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Notifications · recorded
  4. Monitoring · recorded

Recorded events: 11. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    meet-google.club detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · Blocklist Detection · Automated brand label: Google · Forensic Evidence Collected · Technical Analysis Recorded recorded
Notification RecordsSent Report Recorded recorded
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: Gname.com Pte. Ltd.. Abuse contacts: 1.
    • complaint@gname.com
Publication & AvailabilityDestroyList Published recorded

Recorded activity

4 entries

Lifecycle

  1. Domain registered
  2. Added to PhishDestroy+27 h 2 min
  3. First abuse report sent+4 h 27 min

Reported 31 h 29 min after registration

  1. Abuse report sent

    PD-A5192774769F885FF247 · Receipt 85282

    complaint@gname.com
    +1 min
  2. URLScan

    Page captured

    +4 h 16 min
  3. Wayback Machine

    Page archived

    +9 min
  4. Added to PhishDestroy

    meet-google.club

How we investigate & report

Public scans, evidence and abuse channels

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.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

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.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

meet-google.club

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-A5192774769F885FF247 Recipient: complaint@gname.com
Page title stored with report: Проверка безопасности
PDF notice generated
Deep Analysis

Were You Affected by This Site?

You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

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.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Downloaded a file — do not open it and scan the device with security software
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed

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 meet-google.club)
  • 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)
  • Europol — European cybercrime reporting (EU)
  • 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

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

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 →
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.

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/meet-google.club"
  title="PhishDestroy threat report for meet-google.club"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>