Differences

This shows you the differences between two versions of the page.

--- system:registrars [2024-10-08T06:03:42+0000] – format correction michael_paoli
+++ system:registrars [2025-01-15T19:58:23+0000] (current) – +RFC 7344 michael_paoli
@@ Line 257: / Line 257: @@
 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. \\
-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
@@ Line 320: / Line 320: @@
 [[https://www.namecheap.com/|Namecheap.com]] - sucky interface,
-and not so competent staff.  Ugh, 2022
+and not so competent staff.\\
+Ugh, 2022
 and they still can't do IPv6 for glue records on their interface ...
 even though they have
 [[https://www.namecheap.com/support/knowledgebase/article.aspx/292/10/how-can-i-update-my-personal-nameservers-ip-address/#comment-601548546|support requests open to do that for more than a decade]]!
 So, have to do support request for that ... ugh, really, in
-... and they're not very competent about handing it at that.
+... and they're not very competent about handing it at that.\\
 Oh, and API ... 2023 and still:
-[[https://www.namecheap.com/support/api/intro/|whitelist at least one IP before your API access will begin to work. Please keep in mind that only IPv4 addresses can be used]].
+[[https://www.namecheap.com/support/api/intro/|whitelist at least one IP before your API access will begin to work. Please keep in mind that only IPv4 addresses can be used]].\\
-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" ...
+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]]).
 ----