Flagged newborn domains, Monday, November 2, 2026
7,321 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.
very long name “34”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “recover,recovery”
lure words (login, verify, secure…) “recover,recovery”
very long name “32”TLD with a high abuse rate “xyz”
very long name “32”TLD with a high abuse rate “xyz”
very long name “38”TLD with a high abuse rate “xyz”
very long name “34”TLD with a high abuse rate “xyz”
very long name “33”TLD with a high abuse rate “xyz”
very long name “30”TLD with a high abuse rate “xyz”
very long name “36”TLD with a high abuse rate “xyz”
very long name “29”TLD with a high abuse rate “lol”
very long name “35”TLD with a high abuse rate “xyz”
very long name “34”TLD with a high abuse rate “xyz”
very long name “28”TLD with a high abuse rate “xyz”
very long name “37”TLD with a high abuse rate “xyz”
lure words (login, verify, secure…) “service,services”
very long name “38”TLD with a high abuse rate “xyz”
very long name “39”TLD with a high abuse rate “xyz”
very long name “36”TLD with a high abuse rate “xyz”
very long name “29”TLD with a high abuse rate “xyz”
very long name “39”TLD with a high abuse rate “xyz”
very long name “34”TLD with a high abuse rate “xyz”
very long name “30”TLD with a high abuse rate “xyz”
very long name “56”TLD with a high abuse rate “xyz”
very long name “32”TLD with a high abuse rate “xyz”
very long name “34”TLD with a high abuse rate “xyz”
very long name “29”TLD with a high abuse rate “lol”
random-looking name “H=3.61”form submits over plain HTTP “http://60cyclephotography.com/”
lure words (login, verify, secure…) “account”random-looking name “H=3.79”
many hyphens “4”very long name “37”
many hyphens “4”very long name “37”
many hyphens “4”very long name “37”
many hyphens “5”very long name “29”
many hyphens “3”very long name “28”
lure words (login, verify, secure…) “verify”very long name “45”
lure words (login, verify, secure…) “verify”very long name “44”
lure words (login, verify, secure…) “security”very long name “30”
many hyphens “3”very long name “30”
many hyphens “3”very long name “39”
lure words (login, verify, secure…) “service”very long name “29”
many hyphens “6”very long name “51”
ambiguous brand word “ledger”brand name on a rarely-seen nameserver “gcdn.services”
many hyphens “4”very long name “29”
many hyphens “6”very long name “42”
lure words (login, verify, secure…) “service”very long name “32”
many hyphens “5”very long name “32”
many hyphens “3”very long name “29”
many hyphens “3”very long name “32”
many hyphens “5”very long name “38”
lure words (login, verify, secure…) “service”very long name “33”
Same data as JSON: /api/zone/risk?day=2026-11-02&tier=low. Screenshots and the model's reasoning are on each domain's evidence page.