Flagged newborn domains, Friday, October 2, 2026
10,356 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…) “service”very long name “37”TLD with a high abuse rate “click”
many hyphens “4”very long name “30”TLD with a high abuse rate “bond”
many hyphens “4”very long name “28”TLD with a high abuse rate “bond”
lure words (login, verify, secure…) “service,services”form submits over plain HTTP “http://kellyitservices.tech/”
lure words (login, verify, secure…) “service,services,support”
lure words (login, verify, secure…) “tax,update”many hyphens “3”
brand in the name “etsy”very long name “36”
lure words (login, verify, secure…) “service,services,signin”
form on a brand-styled page “has_form”
lure words (login, verify, secure…) “auth,service”many hyphens “3”
lure words (login, verify, secure…) “portal,service,services”
lure words (login, verify, secure…) “billing,service,services”
many hyphens “4”very long name “33”TLD with a high abuse rate “skin”
many hyphens “3”very long name “31”TLD with a high abuse rate “homes”
many hyphens “5”very long name “37”TLD with a high abuse rate “hair”
lure words (login, verify, secure…) “claim,claims,refund”
form on a brand-styled page “has_form”
lure words (login, verify, secure…) “claim,refund,refunds”
lure words (login, verify, secure…) “claim,claims,refund”
lure words (login, verify, secure…) “claim,claims,refund”
form on a brand-styled page “has_form”
many hyphens “3”very long name “34”TLD with a high abuse rate “top”
many hyphens “5”very long name “43”TLD with a high abuse rate “icu”
many hyphens “5”very long name “43”TLD with a high abuse rate “icu”
many hyphens “5”very long name “43”TLD with a high abuse rate “icu”
form on a brand-styled page “has_form”
lure words (login, verify, secure…) “portal”very long name “33”TLD with a high abuse rate “xyz”
many hyphens “3”very long name “31”TLD with a high abuse rate “skin”
lure words (login, verify, secure…) “portal”very long name “29”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “recover,recovery,service,services”
many hyphens “4”very long name “32”TLD with a high abuse rate “top”
lure words (login, verify, secure…) “service”very long name “35”TLD with a high abuse rate “bond”
brand in the name “google”very long name “29”
lure words (login, verify, secure…) “service,services”form submits over plain HTTP “http://redeaglehomeservices.com/”
lure words (login, verify, secure…) “gov,portal”many hyphens “3”
lure words (login, verify, secure…) “alert,alerts,secure”
lure words (login, verify, secure…) “claim,prize,secure,winner”
many hyphens “3”very long name “29”TLD with a high abuse rate “skin”
lure words (login, verify, secure…) “service,services,track”
lure words (login, verify, secure…) “bonus”very long name “30”TLD with a high abuse rate “icu”
lure words (login, verify, secure…) “security,service,services”
lure words (login, verify, secure…) “security,service,services”
many hyphens “3”very long name “29”TLD with a high abuse rate “autos”
ambiguous brand word “booking”TLD with a high abuse rate “xyz”brand name on a rarely-seen nameserver “ezydomain.com”
lure words (login, verify, secure…) “service”very long name “38”TLD with a high abuse rate “homes”
many hyphens “4”very long name “30”TLD with a high abuse rate “xyz”
many hyphens “4”very long name “30”TLD with a high abuse rate “xyz”
many hyphens “4”very long name “30”TLD with a high abuse rate “xyz”
many hyphens “4”very long name “30”TLD with a high abuse rate “xyz”
many hyphens “4”very long name “30”TLD with a high abuse rate “xyz”
Same data as JSON: /api/zone/risk?day=2026-10-02&tier=low. Screenshots and the model's reasoning are on each domain's evidence page.