"No, seriously. All those things Google couldn't find anymore? Top of the search pile. Queries that generated pages of spam in Google results? Fucking pristine on Kagi – the right answers, over and ov

Optional@lemmy.world to Technology@lemmy.world – 275 points –
pluralistic.net

cross-posted from: https://lemmy.ml/post/14100831

"No, seriously. All those things Google couldn't find anymore? Top of the search pile. Queries that generated pages of spam in Google results? Fucking pristine on Kagi – the right answers, over and ov

110

You are viewing a single comment

If your subdomains being public is a security issue then I'd argue something else is wrong. Otherwise you're using security through obscurity.

But I appreciate the insight and I see how this was a harder sell back when it happened. Thanks!

Not necessarily. Let's say you're a known contributor to a closed source project. You don't want people knowing you have a locally hosted gitlab instance at gitlab.mydomain.com, for example.

If that's the case, you shouldn't have one on your domain. If someone wants to know your subdomains, they can still brute force them