Flagged newborn domains, Friday, October 16, 2026
16,690 names at tier low or above, highest score first.
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.
many hyphens “3”very long name “29”
many hyphens “3”very long name “29”
ambiguous brand word “kraken”brand name behind Cloudflare “cloudflare.com”
many hyphens “3”very long name “30”
many hyphens “3”very long name “28”
many hyphens “3”very long name “31”
many hyphens “4”very long name “31”
many hyphens “3”very long name “30”
lure words (login, verify, secure…) “track”very long name “28”
lure words (login, verify, secure…) “service”very long name “28”
brand in the name “chatgpt”
brand in the name “chatgpt”
lure words (login, verify, secure…) “service”very long name “28”
many hyphens “6”very long name “53”
lure words (login, verify, secure…) “service”very long name “36”
ambiguous brand word “ledger”brand name behind Cloudflare “cloudflare.com”
many hyphens “3”very long name “40”
many hyphens “4”very long name “45”
many hyphens “3”very long name “44”
many hyphens “3”very long name “44”
ambiguous brand word “ledger”brand name behind Cloudflare “cloudflare.com”
ambiguous brand word “ledger”brand name behind Cloudflare “cloudflare.com”
ambiguous brand word “ledger”brand name behind Cloudflare “cloudflare.com”
ambiguous brand word “ledger”brand name behind Cloudflare “cloudflare.com”
ambiguous brand word “ledger”brand name behind Cloudflare “cloudflare.com”
many hyphens “7”very long name “39”
lure words (login, verify, secure…) “security”very long name “31”
lure words (login, verify, secure…) “service”very long name “32”
ambiguous brand word “ledger”brand name behind Cloudflare “cloudflare.com”
many hyphens “3”very long name “29”
lure words (login, verify, secure…) “portal”very long name “28”
lure words (login, verify, secure…) “access”very long name “29”
lure words (login, verify, secure…) “service”very long name “28”
many hyphens “6”very long name “31”
many hyphens “6”very long name “31”
many hyphens “6”very long name “31”
lure words (login, verify, secure…) “account”very long name “28”
lure words (login, verify, secure…) “service”very long name “34”
many hyphens “5”very long name “30”
lure words (login, verify, secure…) “access”very long name “30”
lure words (login, verify, secure…) “limited”very long name “29”
many hyphens “6”very long name “31”
many hyphens “6”very long name “31”
many hyphens “6”very long name “31”
many hyphens “6”very long name “31”
many hyphens “6”very long name “31”
many hyphens “6”very long name “31”
many hyphens “6”very long name “31”
many hyphens “6”very long name “31”
many hyphens “6”very long name “31”
Same data as JSON: /api/zone/risk?day=2026-10-16&tier=low. Screenshots and the model's reasoning are on each domain's evidence page.