We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
nip.io should be at the public suffixes list - https://publicsuffix.org/.
nip.io
This is required mainly to solve issues with Let's Encrypt certificate issuance, but it'll help with Cookie Security in browsers as well.
I'd like you to be aware of this initiative and look for approval from your part.
Here's a relevant PR I created to the public suffix repo - publicsuffix/list#1070. Your assistance is required for DNS-level verification.
The text was updated successfully, but these errors were encountered:
It seems we don't qualify:
From https://github.com/publicsuffix/list/wiki/Guidelines#validation
We do not accept entries for use as DNS wildcards, such that e.g. 1-2-3-4.foo.tld resolves as IP address 1.2.3.4.
We do not accept entries whose sole purpose is to circumvent Let's Encrypt rate limits. They have a form you can use.
We have in the past increased Let's Encrypt rate limits for our domain. If you are hitting this limit, please do raise another issue. :)
Sorry, something went wrong.
No branches or pull requests
nip.io
should be at the public suffixes list - https://publicsuffix.org/.This is required mainly to solve issues with Let's Encrypt certificate issuance, but it'll help with Cookie Security in browsers as well.
I'd like you to be aware of this initiative and look for approval from your part.
Here's a relevant PR I created to the public suffix repo - publicsuffix/list#1070. Your assistance is required for DNS-level verification.
The text was updated successfully, but these errors were encountered: