Closed zsbee closed 2 weeks ago
craft.me
expires on 2028-08-13T19:02:50Z
(WHOIS Server: whois.nic.me
), which is more than 2 years from now._psl
record resolves to the valid value.site:craft.me
, I discovered several subdomains of craft.me; I spot-checked a few of them, which appear to belong to different users. This aligns with the described need to include this in the PSL for isolation and security reasons. (Similar to #1958)craft.me
itself and all subdomains (*.craft.me
) have already been using Cloudflare's CDN. From the user sites I spot-checked, there is only one valid SSL certificate issued to craft.me
, which means all users probably share craft.me
's Cloudflare-managed SSL certificate issued to craft.me
and *.craft.me
. So, I'm guessing that you are not seeking to bypass third-party limits.Thank you, removed those lines, we indeed do not seek to attempt to bypass any limitations
TY @groundcat !
TY! do you need me to fix the conflict?
Public Suffix List (PSL) Pull Request (PR) Template
Each PSL PR needs to have a description, rationale, indication of DNS validation and syntax checking, as well as a number of acknowledgements from the submitter. This template must be included with each PR, and the submitting party MUST provide responses to all of the elements in order to be considered.
Checklist of required steps
Submitter affirms the following:
For Private section requests that are submitting entries for domains that match their organization website's primary domain, please understand that this can have impacts that may not match the desired outcome and take a long time to rollback, if at all.
To ensure that requested changes are entirely intentional, make sure that you read the affectation and propagation expectations, that you understand them, and confirm this understanding.
PR Rollbacks have lower priority, and the volunteers are unable to control when or if browsers or other parties using the PSL will refresh or update.
(Link: about propagation/expectations)
[x] Yes, I understand. I could break my organization's website cookies etc. and the rollback timing, etc is acceptable. Proceed.
Description of Organization
Docs is an integrated workspace designed for individual consumers, small teams or businesses, offering a suite of tools for documentation, task management, and collaboration. Typically, users can create and modify page content, which can be kept private or effortlessly shared with others within their organization.
Craft Docs is a product that allows users to "publish" (Read-Only) and also "Share" (Google Docs style editing) their pages or documents to the broader web, essentially creating a website without any coding required. Each user can publish pages under their own unique *.craft.me domain or choose a custom one themselves , e.g. Example User might publish https://zsombor-personal.craft.me/ or share with editing permissions like this: https://s.craft.me/HS2ul20nrQXsfB
I am a a staff engineer in the Stability Team at Craft, my work is accross developer teams and I do lots of issue investigations including phishing/security related problems.
Organization Website: https://www.craft.do/
Reason for PSL Inclusion
We'd like craft.me domains to be on the PSL in order to:
DNS Verification via dig
Results of Syntax Checker (
make test
)