Highscore 55 · flagged Monday, September 28, 2026

secure-chase-onlinebanking-com.bond

Appeared in the .bond zone on Monday, September 28, 2026; by the end of that day the census found no DNS. 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: chase
+30
lure words (login, verify, secure…)
matched: secure
+26
many hyphens
matched: 3
+6
very long name
matched: 30
+4
TLD with a high abuse rate
matched: bond
+8
brand name behind Cloudflare
matched: cloudflare.com
+6
Registrar
—
Nameserver provider
Nameservers
cullen.ns.cloudflare.com, fish.ns.cloudflare.com
First-day state
no DNS
HTTP status
—
Page title
—
Has a form
no
Brand echoed
chase

Model opinions

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

The name 'secure-chase-onlinebanking-com.bond' imitates Chase's online-banking URL (chase.com), with the lure word 'secure' and 'com' embedded before a cheap .bond TLD. It has no DNS or content yet, so no deception attempt is visible, but the only plausible purpose is a banking brand-squat staged for phishing.

First passsuspicioustarget: chaseconfidence 66%· typesafe/jev-latest

typesafe first pass (gate 0.4): p=suspicious:0.73 abuse:0.16 phishing:0.09 | impersonates=0.90 credential=0.19 parked=0.74 evidence=1.0 | target=chase:1.00

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

Same data as JSON: /api/zone/domain/secure-chase-onlinebanking-com.bond. This page is not indexed by search engines and does not link to the site it describes.