83
Change the "Website" tool to be a "Domain" tool
T
Tom C.
100% agreed. Works much better.
L
Logan C.
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.
A
Anthony c
Agreed. We're more interested in the domain than the website.
A
Alex H.
Yup exactly this.
C
Chad G.
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.
V
Vincent M.
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.
N
Nancy T.
agreed. also the ability to manually add an expiration
J
Justin D.
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.
M
Michael T.
I absolutely agree with this. Website is not what we are really wanting to track, domains are where we find the issues.
Also the ability either to edit this, or, add a section that are editable for
- Domain Registrar
- DNS Host
This would save creating a new asset for each of these.
Z
Zachary H.
Cannot agree enough. We have a large DNS infrastructure with not much in the name of websites on them.