Cloudflare Radar
Suspicious
Open reportPhishDestroy first recorded meet-google.club on 2026-11-18. Listed by external blocklists: MetaMask, SEAL.
Page title: “Проверка безопасности”
Listed by external blocklists: MetaMask, SEAL. Use caution — do not enter credentials or personal information.
Risk score, higher = worse · How this score works
Pick what happened and tick the steps as you go. The ticks are kept only in this browser.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
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.
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.
Suspicious
Open reportPage capture
SHA-256 8e00995b…5ad3265
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
| 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 |
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.
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.
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.
Last checked
a7ebdd3d3035542e8eec715e269d16742b08a8a93234207c239bf0e20baff9c0 · 60274 bytes a7ebdd3d3035542e8eec715e269d16742b08a8a93234207c239bf0e20baff9c0 · 60274 bytes ae61327e7b784eff025c62fadaa33f0c3b665196a5f60968fbcdef17551499e9 · 60603 bytes ae61327e7b784eff025c62fadaa33f0c3b665196a5f60968fbcdef17551499e9 · 60603 bytes ae61327e7b784eff025c62fadaa33f0c3b665196a5f60968fbcdef17551499e9 · 60603 bytes c3b9c7a884d1c852f24d9b707d2c3c0b84f57be4d885d5e20f01e66c11ed4ec0 · 599434 bytes 81677083ac791a5a0a12a883a1dec5dbee540c7c5deef019f7168960d50770f8 · 67194 bytes 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.
kim.ns.cloudflare.commcgrory.ns.cloudflare.comnsname: kim.ns.cloudflare.comhostmaster: dns.cloudflare.comserial: 2420476618refresh: 10000retry: 2400expire: 604800minttl: 1800Location describes the IP network.
88989555d1758ed0ba44ac2d03a28467f98269387b81f4ec6a464bc513399c82meet-google.clubwww.meet-google.clubSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of meet-google.club ·
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://meet-google.club/https://meet-google.club/Server: nginx/1.18.0 (Ubuntu)Content-Type: text/html; charset=utf-8X-Powered-By: ExpressContent-Encoding: gziptruekeep-alivegziptext/html; charset=utf-8Wed, 18 Nov 2026 19:29:43 GMTW/"1214-9/ZgMANyJROyBCYPpf0vVQBGwGk"nginx/1.18.0 (Ubuntu)chunkedOriginExpressValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
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 ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Behind a check page or access restriction
CAPTCHA page · check page
Behind a check page or access restriction
CAPTCHA page · check page
Reachable
Recorded events: 11. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
Reported 31 h 29 min after registration
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.
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| ID | Stored data |
|---|
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
meet-google.club PD-A5192774769F885FF247 Recipient: complaint@gname.com 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.
The draft stays only with you.
First secure your money: call your bank or revoke wallet approvals. Immediate steps →
Emergency help from security researchers when a crypto wallet is being drained right now.
Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Choose 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 ↗
meet-google.club)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
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
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
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.