-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cuba domain .gov.cu not exist, but .gob.cu #1695
Comments
[re-submitting directly below, as email responses do not support markdown](#1695 (comment))
|
Thank you. Probably I keep this ticket open, so it will easier to check whatever there's any related changes. |
Thank you for submitting this. The entry for .cu appears quite old and was likely imported by volunteers along the way. I have presented at various meetings to ccTLD administrators to help expand awareness of the PSL. Following IANA listing for .cu to the nic.cu web page with
There needs to be a Pull Request (PR) to revise the .CU listing. A bias would be to have this come from the NIC.CU to ensure that every change is deliberate and intentional, as it is they who would get support calls if a change breaks anything. There is a preference that the PR would need to place DNS TXT entries that include the Pull Request URL. |
see #1694 for a recent example of what this would need to look like with involvement from the ccTLD administration |
I'll try forwarding an alert of this issue to CITMATEL, the registry operator for .cu, thru LACTLD. I guess they have so many issues as a sanctioned country that they might have not noticed specific applications or services not working for a subset of their domains. Which suggests .ir and .kp as possible occurrences of the same lack of feedback loop. |
Should we update anyway? Current entries:
So to get to https://www.nic.cu/docum_det.php?doc_id=2&opt=1 we want
and we could just skip the removal. |
I think it would be safe to do so. Would it be worth attempting to contact the registry via email to confirm this? |
If we consider the IANA page to be an authoritative source, the listing at http://iana.org/domains/root/db/cu.html designates http://www.nic.cu as the official registry link. Consequently, the domain list available at https://www.nic.cu/docum_det.php?doc_id=2&opt=1 can be regarded as a reliable and authoritative source. In my view, including these domains in the PSL would be a prudent step to benefit Internet users. However, this approach might not be suitable for removing domains unless the removal request comes explicitly from the registries themselves, as some domains may no longer be publicly available for registration but are still operational for existing users (such as |
Google returns no results for |
Are there any certificates in CT for .gov.cu ?
Rubens
Em sex., 6 de set. de 2024, 04:37, William Harrison <
***@***.***> escreveu:
… Google returns no results for site:gov.cu but does for site:gob.cu, and
when searching for subdomains on gov.cu there are no results found using
https://subdomainfinder.c99.nl/.
—
Reply to this email directly, view it on GitHub
<#1695 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA53LCLNSO5MOSEOP4XFYGTZVFLURAVCNFSM6AAAAABNX7HQG2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZTGQZTOMZUGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
The only certificate for So, if we exclude expired certificates, no domains would be found: https://crt.sh/?Identity=gov.cu&exclude=expired |
@kjd Is there a context w gob.cu / gov.cu that could comment on our best path to take here? |
For disclaimer, I am not Cuban, but it seem I can't find any
.gov.cu
domain anywhere, even when I specifically search with "site:gov.cu
" keyword.When I try to search "
Cuban president website
" the top result is "https://www.presidencia.gob.cu
" with.gob.cu
domain. Based on latest Wikipedia edit, it seem the domain indeed it is.gob.cu
.Is there any plan to renew the list about Cuba
.cu
domain to reflect latest changes?NB: My search engine is Google Search.
The text was updated successfully, but these errors were encountered: