Skip to content
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

remove wildcard for .ck, replace with list of 2LDs #2250

Closed
wants to merge 1 commit into from

Conversation

wdhdev
Copy link
Contributor

@wdhdev wdhdev commented Nov 8, 2024

List of 2LDs taken from https://en.wikipedia.org/wiki/.ck#Requirements_of_.ck_registration.

I would recommend removing the wildcard and specifying the 2LDs specifically, just in the event they allow 2nd level registrations, it won't affect anyone attempting to set cookies at the second level.

This PR isn't super urgent, and won't affect any active domains once deployed.

The !www.ck entry has been removed in favour of specifying the TLD itself.

@wdhdev
Copy link
Contributor Author

wdhdev commented Nov 8, 2024

@dnsguru
Copy link
Member

dnsguru commented Nov 9, 2024

please do not add namespace in the upper section based upon unauthoritative information in wikipedia.

@dnsguru dnsguru closed this Nov 9, 2024
@dnsguru dnsguru added the 🚩ICANN (IANA/ICP-3) Section PR changes in the ICANN/IANA section typically reserved for TLDs. label Nov 9, 2024
@wdhdev wdhdev deleted the patch-4 branch November 9, 2024 14:22
@dnsguru dnsguru mentioned this pull request Nov 9, 2024
@simon-friedberger
Copy link
Contributor

@wdhdev Also note that having the wildcard means more domains (potentiially too many) are public suffixes. Which means in terms of site-isolation this is the more secure state. It also requires fewer entries so we should stick with those if we have no need to change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚩ICANN (IANA/ICP-3) Section PR changes in the ICANN/IANA section typically reserved for TLDs.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants