3 ms·
Thanks so much for the detailed feedback! This is incredibly helpful for our roadmap. I want to address your point about the "duplicates" first, because it’s ac
by robinbaertschi 9mo ago
Thanks so much for the detailed feedback! This is incredibly helpful for our roadmap. I want to address your point about the "duplicates" first, because it’s actually a perfect example of why this tool is necessary.
It’s not your domain—it’s a "Homograph"
Take a very close look at the characters in those "Medium" risk rows. While they look identical to your domain, they are actually using Internationalized Domain Names (IDN).
The tool isn't reporting your own domain; it's reporting spoofed versions that use Greek or Cyrillic characters (like a "c" that is actually a Greek "с").
alℭazarseℭ[.]com
alcazarseℭ[.]com
alℭazarsec[.]com
Why it matters: Phishers use these because they are visually indistinguishable from your real site in a browser address bar. The fact that you thought they were your own site proves exactly why you need to monitor them!
Improving the Onboarding
You’re 100% right on the friction points. We’re taking your notes to heart:
Auto-Generation: We agree. Adding a domain should trigger an immediate scan without navigating away.
Smart Defaults: Defaulting to the email domain for the first scan is a great "quick start" idea.
Trust-based Verification: If you’ve verified your email @company.com, we should absolutely fast-track the verification for company.com.
Status Transparency: We’ll add a "Time to Completion" estimate and a clearer "We will email you" notification so you aren't left staring at a static page.
Thank you for the honest feedback—it’s exactly what we need to make this more than just a security tool, but a great user experience.