Skip to main content

Change the "Website" tool to be a "Domain" tool

Some customers have a domain for email etc but do not have a website. It would be more practical to have the tool made for domains and also track websites if there is a website associated with that domain.

19 comments

Log in to comment and vote

Comments19

  • Chocolate Melon

    •

    May 21, 2022

    Agreed. The current website tool should be split into three separate tools - Domains, Websites, and SSL Certificates. As others have mentioned, we like/need the registar / DNS lookups for the domain, but domains may not have a website, or may have multiple sites with different hostnames. Websites should be a separate tool since most organizations have an separate outside web developer and/or web host, and those can be different for different sites, so we can track that information per site. I would still like to have the ability to specify to track SSL renewal when adding a website, but if certificate tracking is enabled the certificate should be listed in the SSL Certificates tool. We need to track renewals on certificates that are not tied to one of our domains or websites (I'm thinking of Apple Push Certificates used with MDM solutions as one example), which is why it would be nice to have a separate SSL Certificates tool.

    • Aquamarine Oak

      •

      Apr 25, 2023

      Chad G.: a bit of a dated reply but this 100%. We actually have a custom asset tracking this data right now. Would love to just plug in domains and have the tool scrape data for us.

    • Peach Leopard

      •

      Aug 19, 2024

      Chad G. - Agree. A triple-tool would be nice as you've described above. With websites, an optional snapshot when accessed would be nice to give a visual view.

  • Blue Pinwheel

    •

    Oct 5, 2020

    Cannot agree enough. We have a large DNS infrastructure with not much in the name of websites on them.

  • Apricot Astronaut

    •

    Apr 7, 2023

    Might be more fitting for a separate request, but it would be nice to have the company's website field populate into the tool as well.

  • Turquoise Lake

    •

    Jan 7, 2022

    agreed. also the ability to manually add an expiration

  • Red Spool

    •

    Feb 9, 2021

    This is just an aesthetics issue, no? The tracking options cover all scenarios that I've seen.
    Renaming websites to domains + removing https:// or http:// from the display name would clean up the look and clarify the website/domain usage.

  • Red Pudding

    •

    Mar 5, 2025

    It would be nice to be able to document DNS records (Cloudflare integration?), DNSSEC status, associated services (website, email, etc.), etc.

  • Aqua Toast

    •

    Feb 15, 2025

    BUMP!!! Why so long, no visibility, no activity. This is insanity, for something so basic and logical… no-brainer, should have always been this way…

    Low-hanging fruit here!! Please prioritize, expedite, do the needful!

  • Aqua Toast

    •

    Apr 28, 2023

    100% agreed. Works much better.

  • Red Spool

    •

    Oct 9, 2021

    Another good reason for this is the fact that if I have many domain names that point to the same website, after adding them all to Hudu, the expiration mechanism will send many duplicate expirations that relate to the website, not the domains…

  • Jade Clay

    •

    Apr 4, 2023

    Agreed. We're more interested in the domain than the website.