Criticalscore 62 · flagged Tuesday, November 3, 2026

meet-google.top

Appeared in the .top zone on Tuesday, November 3, 2026; by the end of that day the census found active website. Full domain report

Signals, not verdicts. A domain appears here because heuristics matched its name, its infrastructure or the page it served on its first day. Where a model has looked at it, that is shown as an opinion with a confidence, not as a finding. Nothing on this page says a site is malicious. Read the evidence and decide for yourself.

Own one of these names and think the listing is wrong? Tell us and a person will look.

What matched

brand in the name
matched: google
+30
TLD with a high abuse rate
matched: top
+8
brand name behind Cloudflare
matched: cloudflare.com
+6
form on a brand-styled page
matched: has_form
+18
Registrar
—
Nameserver provider
Nameservers
pam.ns.cloudflare.com, rudy.ns.cloudflare.com
First-day state
active website
HTTP status
200
Page title
Проверка безопасности
Has a form
yes
Brand echoed
google

Model opinions

Second opinionlooks like abusetarget: Googleconfidence 80%· claude-opus-5-5

The name squats on the Google Meet product on a throwaway .top domain. It serves a self-hosted (nginx/Ubuntu) Russian-language 'security check' page with a fake reCAPTCHA gate and no links, which matches fake-Meet ClickFix and cloaking lures used for malware delivery rather than a genuine Google service.

First passsuspicioustarget: googleconfidence 47%· typesafe/jev-latest

typesafe first pass (gate 0.4): p=suspicious:0.56 phishing:0.19 abuse:0.18 | impersonates=0.89 credential=0.33 parked=0.53 evidence=2.2 | target=google:0.99

A model looked at the screenshot and page text and wrote what it thought. It can be wrong, and it is not a finding.

What the page looked like on Tuesday, November 3, 2026

Screenshot of meet-google.top taken by the zone census on 2026-11-03

Same data as JSON: /api/zone/domain/meet-google.top. This page is not indexed by search engines and does not link to the site it describes.