Looking to see what escalation numbers I may still have...
[Edit]: Sent them what I have but it isn't much. Most human contacts have been replaced by menu's. I hope the last one I sent helps.
It appears someone managed to get NetworkSolutions (now web.com) to put the domain he.net on clientHold for one Phishing complaint, unrelated to he.net meaning someone did a lookup on bgp.he.net and reported he.net instead of the domain they were looking up. If true it means web.com did not do any due diligence, investigation, etc... and just put a very popular domain with many shared services on hold. The domain he.net is used by MANY services and those services are likely going to start breaking. I have no idea what's going on over at web.com.
As a side note, I recently transferred all my domains away from NetSol/web.com as they lost the ability to define custom name servers (glue in the root servers) which is bizarre to me, given many of the meme-style resellers of resellers can still do this. I had many other strange experiences with them, including having to teach their escalation contacts how to use dig outside of their own name servers.
I was with Network Solutions from 1997 to 2023. They were bought by web.com in 2018. They keep the name on the old domain and don't redirect to web.com because they have some non-API automation in place on the old domain.
Wikipedia has it incorrect then, as they list it as "formerly web.com" ("Network Solutions, LLC, formerly Web.com is an American-based technology company"). Thanks for the clarification!
> As a side note, I recently transferred all my domains away from NetSol/web.com as they lost the ability to define custom name servers
FFS is that what happened? They recently bought the registrar I use and a domain of mine with custom nameservers isn't working and I haven't had a chance to troubleshoot.
I doubt they have fixed it and I doubt they have plans to, but in the off chance they have make sure it is prefixed with dns(number) or ns(number) as they will not give you a useful error message if you have not done so. e.g. ns0.yourdomain.tld but that probably won't work either. I used to use bare apex domains for a couple decades but they and several other registrars stopped supporting that. They do not give useful error messages to the clients or to their support. AFAIK there is nobody left that knows how to debug the back-end.
This is just a suggestion but I would consider moving the domains somewhere else. It seems web.com is just hoovering up registrars but not migrating everything to a centralized, modern, maintained system. In my experience and opinion they do not know how the back-end of the old Network Solutions systems work.
[Edit]: Sent them what I have but it isn't much. Most human contacts have been replaced by menu's. I hope the last one I sent helps.
It appears someone managed to get NetworkSolutions (now web.com) to put the domain he.net on clientHold for one Phishing complaint, unrelated to he.net meaning someone did a lookup on bgp.he.net and reported he.net instead of the domain they were looking up. If true it means web.com did not do any due diligence, investigation, etc... and just put a very popular domain with many shared services on hold. The domain he.net is used by MANY services and those services are likely going to start breaking. I have no idea what's going on over at web.com.
As a side note, I recently transferred all my domains away from NetSol/web.com as they lost the ability to define custom name servers (glue in the root servers) which is bizarre to me, given many of the meme-style resellers of resellers can still do this. I had many other strange experiences with them, including having to teach their escalation contacts how to use dig outside of their own name servers.