Highscore 55 · flagged Wednesday, November 11, 2026

wellsfargosecure.support

Appeared in the .support zone on Wednesday, November 11, 2026; by the end of that day the census found empty page. 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: wellsfargo
+30
lure words (login, verify, secure…)
matched: secure
+26
brand name on a rarely-seen nameserver
matched: ndns.cn
+6
Registrar
—
Nameserver provider
Nameservers
ns1.ndns.cn, ns2.ndns.cn
First-day state
empty page
HTTP status
200
Page title
—
Has a form
no
Brand echoed
wellsfargo

Model opinions

Second opinionlooks like abusetarget: Wells Fargoconfidence 82%· claude-opus-5-5

The name pairs the Wells Fargo brand with the lure word 'secure' on a .support TLD, and its nameservers (ndns.cn) are not ones Wells Fargo uses. The page is blank, with no title, form or links, so this is a brand-squat staged for later phishing rather than an active phish.

First passlooks like abusetarget: wellsfargoconfidence 63%· typesafe/jev-latest

typesafe first pass (gate 0.4): p=abuse:0.69 suspicious:0.28 phishing:0.03 | impersonates=0.91 credential=0.07 parked=0.91 evidence=1.0 | target=wellsfargo: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.

What the page looked like on Wednesday, November 11, 2026

Screenshot of wellsfargosecure.support taken by the zone census on 2026-11-11

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