Highscore 50 · flagged Monday, September 28, 2026

confirmguardlocksecurerapidupdatestatustotal.top

Appeared in the .top zone on Monday, September 28, 2026; by the end of that day the census found blocked the probe. 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

lure words (login, verify, secure…)
matched: confirm,secure,update
+18
very long name
matched: 44
+4
TLD with a high abuse rate
matched: top
+8
brand in page title, not in the name
matched: cloudflare
+20
Registrar
—
Nameserver provider
Nameservers
clyde.ns.cloudflare.com, meadow.ns.cloudflare.com
First-day state
blocked the probe
HTTP status
403
Page title
Attention Required! | Cloudflare
Has a form
no
Brand echoed
—

Model opinions

Second opinionsuspiciousconfidence 60%· claude-opus-5-5

The name is a machine-style chain of lure words (confirm, guard, lock, secure, update, status) on a .top TLD, typical of fake-security or tech-support lure campaigns. The only content is a Cloudflare block page, which is not Cloudflare impersonation and may be cloaking the scanner, so there is no page evidence of deception yet.

First passsuspiciousconfidence 75%· typesafe/jev-latest

typesafe first pass (gate 0.4): p=suspicious:0.80 unreachable:0.11 benign:0.04 | impersonates=0.17 credential=0.04 parked=0.69 evidence=1.1 | target=none:0.65

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

Other days this name was flagged

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