Flagged newborn domains, Monday, October 19, 2026
6,937 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 “7”very long name “51”TLD with a high abuse rate “xyz”
many hyphens “7”very long name “51”TLD with a high abuse rate “xyz”
many hyphens “7”very long name “51”TLD with a high abuse rate “xyz”
many hyphens “7”very long name “48”TLD with a high abuse rate “xyz”
many hyphens “6”very long name “45”TLD with a high abuse rate “xyz”
many hyphens “6”very long name “45”TLD with a high abuse rate “xyz”
many hyphens “6”very long name “45”TLD with a high abuse rate “xyz”
many hyphens “6”very long name “45”TLD with a high abuse rate “xyz”
many hyphens “6”very long name “45”TLD with a high abuse rate “xyz”
brand in the name “shopify”very long name “28”
lure words (login, verify, secure…) “customer,customers,service”
lure words (login, verify, secure…) “customer,customers,support”
lure words (login, verify, secure…) “service”very long name “29”TLD with a high abuse rate “cfd”
lure words (login, verify, secure…) “service”very long name “29”TLD with a high abuse rate “icu”
lure words (login, verify, secure…) “service”very long name “29”TLD with a high abuse rate “sbs”
lure words (login, verify, secure…) “service”very long name “32”TLD with a high abuse rate “lol”
lure words (login, verify, secure…) “account”very long name “31”lure suffix “exxonmobilbusinessaccountonline”
lure words (login, verify, secure…) “portal”very long name “29”TLD with a high abuse rate “loan”
form on a brand-styled page “has_form”
lure words (login, verify, secure…) “security,service,services”
lure words (login, verify, secure…) “security,service,services”
many hyphens “3”very long name “39”TLD with a high abuse rate “top”
lure words (login, verify, secure…) “official,service,services”
lure words (login, verify, secure…) “security,service,services”
lure words (login, verify, secure…) “service,services”many hyphens “3”
lure words (login, verify, secure…) “portal”very long name “50”TLD with a high abuse rate “sbs”
lure words (login, verify, secure…) “official,portal,prize”
many hyphens “4”very long name “32”TLD with a high abuse rate “top”
many hyphens “4”very long name “37”TLD with a high abuse rate “top”
many hyphens “3”very long name “35”TLD with a high abuse rate “autos”
lure words (login, verify, secure…) “security”very long name “35”TLD with a high abuse rate “autos”
many hyphens “3”very long name “33”TLD with a high abuse rate “top”
form on a brand-styled page “has_form”
lure words (login, verify, secure…) “auth,portal,secure”
lure words (login, verify, secure…) “secure”very long name “29”TLD with a high abuse rate “autos”
lure words (login, verify, secure…) “recover,recovery,service”
lure words (login, verify, secure…) “service,services,signin”
form on a brand-styled page “has_form”
lure words (login, verify, secure…) “service”very long name “29”TLD with a high abuse rate “cfd”
lure words (login, verify, secure…) “service”very long name “29”TLD with a high abuse rate “icu”
lure words (login, verify, secure…) “service”very long name “29”TLD with a high abuse rate “sbs”
form on a brand-styled page “has_form”
lure words (login, verify, secure…) “account”very long name “28”lure suffix “staplespersonalaccountonline”
lure words (login, verify, secure…) “alert,alerts,service”
lure words (login, verify, secure…) “alert,alerts,service”
many hyphens “3”very long name “37”TLD with a high abuse rate “work”
punycode name “라-렌 scripts=HANGUL”
punycode name “금-궁 scripts=HANGUL”
punycode name “даём-всем scripts=CYRILLIC”
punycode name “자-자 scripts=HANGUL”
Same data as JSON: /api/zone/risk?day=2026-10-19&tier=low. Screenshots and the model's reasoning are on each domain's evidence page.