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

add hrsn.dev #2170

Merged
merged 1 commit into from
Sep 18, 2024
Merged

add hrsn.dev #2170

merged 1 commit into from
Sep 18, 2024

Conversation

wdhdev
Copy link
Contributor

@wdhdev wdhdev commented Sep 18, 2024

Public Suffix List (PSL) Submission

Checklist of required steps

  • Description of Organization

  • Robust Reason for PSL Inclusion

  • DNS verification via dig

  • Run Syntax Checker (make test)

  • Each domain listed in the PRIVATE section has and shall maintain at least two years remaining on registration, and we shall keep the _psl TXT record in place in the respective zone(s).

Submitter affirms the following:

  • We are listing any third-party limits that we seek to work around in our rationale such as those between IOS 14.5+ and Facebook (see Issue #1245 as a well-documented example)
  • This request was not submitted with the objective of working around other third-party limits.
  • The submitter acknowledges that it is their responsibility to maintain the domains within their section. This includes removing names which are no longer used, retaining the _psl DNS entry, and responding to e-mails to the supplied address. Failure to maintain entries may result in removal of individual entries or the entire section.
  • The Guidelines were carefully read and understood, and this request conforms to them.
  • The submission follows the guidelines on formatting and sorting.

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)

  • Yes, I understand. I could break my organization's website cookies and cause other issues, and the rollback timing is acceptable. Proceed anyways.

Description of Organization

I am an individual software engineer who hosts websites, APIs, automation tools, etc for my clients which are usually small businesses or organisations.

Organization Website:

https://wdharrison.com
https://hrsn.net

Reason for PSL Inclusion

  • Cookie security: Preventing super cookies & ensuring sites on subdomains stay separate.
  • URL highlighting: Shows the end user that these subdomains are separate from each other (as different parties manage them)

Same rationale as wdh.app and preview.wdh.app which were added in #2067 and #2119.

Notes:

  • You will not find many SSL certificates under crt.sh?q=hrsn.dev as it is a new domain, and I tend to issue wildcard SSLs as mentioned in my last PR.

Number of users this request is being made to serve:

3k+ monthly visitors.

DNS Verification

dig +short TXT _psl.hrsn.dev
"https://github.com/publicsuffix/list/pull/2170"

Results of Syntax Checker (make test)

All tests passed.

@simon-friedberger simon-friedberger merged commit e6bebce into publicsuffix:master Sep 18, 2024
2 checks passed
@wdhdev wdhdev deleted the patch-4 branch September 18, 2024 23:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants