Flagged newborn domains, Saturday, October 17, 2026
26 names at tier medium or above in .bond, 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.
brand in the name “usaa”many hyphens “3”TLD with a high abuse rate “bond”brand name behind Cloudflare “cloudflare.com”+1 more
brand in the name “usaa”many hyphens “3”TLD with a high abuse rate “bond”brand name behind Cloudflare “cloudflare.com”+1 more
brand in the name “usaa”many hyphens “3”TLD with a high abuse rate “bond”brand name behind Cloudflare “cloudflare.com”+1 more
brand in the name “usaa”many hyphens “3”TLD with a high abuse rate “bond”brand name behind Cloudflare “cloudflare.com”+1 more
brand in the name “usaa”lure words (login, verify, secure…) “support”TLD with a high abuse rate “bond”brand name behind Cloudflare “cloudflare.com”
brand in the name “usaa”many hyphens “3”very long name “29”TLD with a high abuse rate “bond”+1 more
brand in the name “usaa”many hyphens “3”very long name “30”TLD with a high abuse rate “bond”+1 more
brand in the name “usaa”many hyphens “3”very long name “28”TLD with a high abuse rate “bond”+1 more
brand in the name “usaa”many hyphens “3”very long name “34”TLD with a high abuse rate “bond”+1 more
brand in the name “usaa”many hyphens “3”very long name “29”TLD with a high abuse rate “bond”+1 more
brand in the name “usaa”TLD with a high abuse rate “bond”brand name behind Cloudflare “cloudflare.com”brand name at a retail registrar “NicNames, Inc.”
brand in the name “usaa”TLD with a high abuse rate “bond”brand name behind Cloudflare “cloudflare.com”brand name at a retail registrar “NicNames, Inc.”
brand in the name “usaa”TLD with a high abuse rate “bond”brand name behind Cloudflare “cloudflare.com”brand name at a retail registrar “NicNames, Inc.”
brand in the name “usaa”TLD with a high abuse rate “bond”brand name behind Cloudflare “cloudflare.com”brand name at a retail registrar “NicNames, Inc.”
brand in the name “usaa”TLD with a high abuse rate “bond”brand name behind Cloudflare “cloudflare.com”brand name at a retail registrar “NicNames, Inc.”
brand in the name “usaa”TLD with a high abuse rate “bond”brand name behind Cloudflare “cloudflare.com”brand name at a retail registrar “NicNames, Inc.”
brand in the name “usaa”TLD with a high abuse rate “bond”brand name behind Cloudflare “cloudflare.com”brand name at a retail registrar “NicNames, Inc.”
brand in the name “usaa”TLD with a high abuse rate “bond”brand name behind Cloudflare “cloudflare.com”brand name at a retail registrar “NicNames, Inc.”
brand in the name “usaa”TLD with a high abuse rate “bond”brand name behind Cloudflare “cloudflare.com”brand name at a retail registrar “NicNames, Inc.”
brand in the name “usaa”TLD with a high abuse rate “bond”brand name behind Cloudflare “cloudflare.com”brand name at a retail registrar “NicNames, Inc.”
brand in the name “usaa”TLD with a high abuse rate “bond”brand name behind Cloudflare “cloudflare.com”brand name at a retail registrar “NicNames, Inc.”
brand in the name “usaa”TLD with a high abuse rate “bond”brand name behind Cloudflare “cloudflare.com”brand name at a retail registrar “NicNames, Inc.”
brand in the name “usaa”TLD with a high abuse rate “bond”brand name behind Cloudflare “cloudflare.com”brand name at a retail registrar “NicNames, Inc.”
TLD with a high abuse rate “bond”brand in page title, not in the name “tiktok”form on a brand-styled page “has_form”
Model opinion: looks benign, confidence 54%. An opinion, not a finding.
TLD with a high abuse rate “bond”form on a brand-styled page “has_form”
punycode name “h89和9 scripts=CJK/LATIN”TLD with a high abuse rate “bond”
Same data as JSON: /api/zone/risk?day=2026-10-17&tier=medium. Screenshots and the model's reasoning are on each domain's evidence page.