Flagged newborn domains, Tuesday, October 13, 2026
10,606 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.
lure words (login, verify, secure…) “alert”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “reset”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “invoice”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “payment”TLD with a high abuse rate “xyz”
login form “has_form+login words”
lure words (login, verify, secure…) “portal”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “track”TLD with a high abuse rate “quest”
lure words (login, verify, secure…) “account”TLD with a high abuse rate “xyz”
many hyphens “3”TLD with a high abuse rate “click”
lure words (login, verify, secure…) “portal”TLD with a high abuse rate “xyz”
brand in the name “tmobile”
many hyphens “3”TLD with a high abuse rate “click”
lure words (login, verify, secure…) “portal”TLD with a high abuse rate “click”
login form “has_form+login words”
lure words (login, verify, secure…) “bonus”TLD with a high abuse rate “xyz”
login form “has_form+login words”
brand in the name “ionos”
lure words (login, verify, secure…) “account”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “package”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “access”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “member”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “reward”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “unlock”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “update”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “winner”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “billing”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “billing”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “billing”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “billing”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “billing”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “reset”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “account”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “gov”TLD with a high abuse rate “top”
lure words (login, verify, secure…) “package”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “support”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “access”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “member”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “reward”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “unlock”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “update”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “winner”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “account”TLD with a high abuse rate “xyz”
brand in the name “bybit”
lure words (login, verify, secure…) “id”TLD with a high abuse rate “top”
lure words (login, verify, secure…) “alert”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “reset”TLD with a high abuse rate “xyz”
login form “has_form+login words”
lure words (login, verify, secure…) “reset”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “claim”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “prize”TLD with a high abuse rate “xyz”
Same data as JSON: /api/zone/risk?day=2026-10-13&tier=low. Screenshots and the model's reasoning are on each domain's evidence page.