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

  • AnActOfCreation@programming.dev
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    7 months ago

    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!

    • foggy@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      3
      ·
      7 months ago

      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.

      • ReveredOxygen@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        4
        arrow-down
        1
        ·
        7 months ago

        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