• gazby@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    0
    ·
    5 months ago

    Last I used Namecheap they still didn’t support Let’s Encrypt and were charging for DV TLS certs. Noped right back out.

    • sugar_in_your_tea@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      0
      ·
      5 months ago

      The registrar doesn’t have anything to do with TLS. I use LetsEncrypt on my domains through NameCheap, no problems whatsoever. I get my hosting elsewhere (previously Vultr, currently Hetzner).

      • gazby@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        0
        ·
        5 months ago

        A company’s business practices are relevant regardless of which of their services you’re subscribing to.

        • sugar_in_your_tea@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          0
          ·
          edit-2
          5 months ago

          I care if they have poor privacy policies or something in features I don’t use as that can indicate future impact on features I do use, but I don’t care if they have limited product offerings generally. So to me, it’s completely irrelevant.

          You should probably separate your hosting from your registrar anyway so you can switch one without impacting the other. I did just that when I bailed on Vultr due to their unprofessional (IMO) handling of a TOS update (blocked access to my account, so I couldn’t close my account w/o accepting the terms), but I didn’t have to change my registrar and all that, I just spun up an instance at another host and redirected DNS entries. I also separated my DNS mappings from my domain registrar (they’re combined now @ cloudflare, which is a little unfortunate).