| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| system:registrars [2024-11-26T21:13:50+0000] – Namecheap.com - spam ... michael_paoli | system:registrars [2025-05-06T17:12:39+0000] (current) – 2025-04-24 web.com rebranding michael_paoli |
|---|
| And yes, not expecting anything on it anytime particularly soon, but they did well understand it and take note, | And yes, not expecting anything on it anytime particularly soon, but they did well understand it and take note, |
| so, rather likely will come in future API and web interface. \\ | so, rather likely will come in future API and web interface. \\ |
| See also: [[https://www.rfc-editor.org/rfc/rfc8078.html|RFC 8078]], etc. | See also: [[https://www.rfc-editor.org/rfc/rfc7344.html|RFC 7344]], [[https://www.rfc-editor.org/rfc/rfc8078.html|RFC 8078]], etc. |
| |
| I might be forgetting some details and further examples, but pretty much | I might be forgetting some details and further examples, but pretty much |
| * They also tend to push lots of announcing clueless offers. Got [[https://www.sf-lug.org/|sf-lug.org]]? How 'bout buy up all these sf-tote.someTLD and sftote.someTLD domains, I mean tote is like lug (as in sf-lug for San Francisco Linux Users' Group), right? Ugh. | * They also tend to push lots of announcing clueless offers. Got [[https://www.sf-lug.org/|sf-lug.org]]? How 'bout buy up all these sf-tote.someTLD and sftote.someTLD domains, I mean tote is like lug (as in sf-lug for San Francisco Linux Users' Group), right? Ugh. |
| * 1997-07-17 they majorly screwed up Internet DNS for com. and net. TLDs, effectively knocking them off The Internet for many/most folks for many many hours. See reports, e.g.: [[https://archive.nytimes.com/www.nytimes.com/library/cyber/week/071797dns.html|The New York Times: Human Error Cripples the Internet]], [[https://groups.google.com/g/comp.protocols.dns.bind/c/rDunynim12U/m/FedJdyxt484J?pli=1|USENET (as seen on Google Groups)]] | * 1997-07-17 they majorly screwed up Internet DNS for com. and net. TLDs, effectively knocking them off The Internet for many/most folks for many many hours. See reports, e.g.: [[https://archive.nytimes.com/www.nytimes.com/library/cyber/week/071797dns.html|The New York Times: Human Error Cripples the Internet]], [[https://groups.google.com/g/comp.protocols.dns.bind/c/rDunynim12U/m/FedJdyxt484J?pli=1|USENET (as seen on Google Groups)]] |
| | * 2025-04-24 [[https://en.wikipedia.org/wiki/Web.com|On April 24, 2025, Web.com announced its merger with Network Solutions, adopting the latter's brand name. This move is part of Newfold Digital's strategy to consolidate its brands, including merging iPage, HostMonster, and FatCow into Bluehost, its primary web hosting brand.]] |
| |
| So, yeah, general experience with NetworkSolutions.com / Web.com has | So, yeah, general experience with NetworkSolutions.com / Web.com has |
| Also much of the information their support staff provides is incorrect ... ugh.\\ | Also much of the information their support staff provides is incorrect ... ugh.\\ |
| Ugh, "spam" - created account there 2024-11-19 (to assist someone with something), and very explicitly opted out of their "marketing" communication. Yet 2024-11-26 they're sending me spam: "Subject: Forgot something? Hot deals inside" and body that starts with: "Namecheap Top deals" ... | Ugh, "spam" - created account there 2024-11-19 (to assist someone with something), and very explicitly opted out of their "marketing" communication. Yet 2024-11-26 they're sending me spam: "Subject: Forgot something? Hot deals inside" and body that starts with: "Namecheap Top deals" ... |
| And "of course", their unsubscribe link tells me: "You’ve already been unsubscribed from newsletter & marketing communications". | And "of course", their unsubscribe link tells me: "You’ve already been unsubscribed from newsletter & marketing communications".\\ |
| | And I vote "no confidence" (at best) on Namecheap.com. As of 2024-12-18 they're still doing DS records with SHA-1 |
| | (see e.g.: [[https://dnsviz.net/d/lunacrescentnails.com/Z2J5fw/dnssec/|lunacrescentnails.com]]), |
| | which is disallowed for new DS records, and has now been for years per [[https://datatracker.ietf.org/doc/html/rfc8624#section-3.3|RFC 8624 Section 3.3]]. |
| | Furthermore, on 2024-12-18 I commented on this matter on their |
| | [[https://www.namecheap.com/support/knowledgebase/article.aspx/9723/2232/managing-dnssec-for-domains-pointed-to-premium-or-basicdns/|Managing DNSSEC for domains pointed to Premium or BasicDNS]] |
| | web page, and "waiting to be approved by Namecheap.com" - well, over 5 days later, not only is the comment not yet approved/visible nor responded to nor an email response, |
| | but sorting comments by most recent, the most recent is about 4 //years// old, |
| | so appears they don't care to accept/post comments nor reply, and very possible they don't even bother to read them. |
| | So, yeah, paint me not surprised - when they've already got open requests that have been open for more than a decade that should've been implemented, |
| | and haven't yet been ... alas, not surprised //at all//. This DS SHA-1 issue //may// be limited to just their "BasicDNS" |
| | (and likely also "Premium DNS") services, and possibly certain domains thereupon, |
| | as it seems to //not// impact (at least some, if not all) domains which are not on their DNS hosting |
| | (e.g. [[https://dnsviz.net/d/savingthedolph.in/Yt3Rhg/dnssec/|savingthedolph.in]]). |
| |
| ---- | ---- |
