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 wadl.top #1924

Merged
merged 3 commits into from
Apr 10, 2024
Merged

Add wadl.top #1924

merged 3 commits into from
Apr 10, 2024

Conversation

FPVogel
Copy link
Contributor

@FPVogel FPVogel commented Jan 25, 2024

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

  • 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) in the affected section

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 Guidelines were carefully read and understood, and this request conforms
  • 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 etc. and the rollback timing, etc is acceptable. Proceed.

Description of Organization

We are WebWaddle Ltd. And were recently formed by an entertainment technology company (https://glander-vt.de/), whose customers are currently being migrated as an existing customer base. Formerly we mainly provided ticketing solutions web-wise, but now are also building up a general hosting infrastructure. I am the appointed Director of WebWaddle Ltd.

Organization Website:

https://webwaddle.com/

Reason for PSL Inclusion

We are currently working on creating webhosting packages that don't require an own ICANN-registered domain name. As such we have registered the wadl.top domain name (shortened from the Waddle-part of the Company name)

We provide each customer with a unique subdomain of wadl.top

We'd like to have accurate handling by other software, hence this pull request. We would namely like to achieve:

  • Appropriate cookie handling
  • Appropriate highlighting in the browser search bar
  • isolation between our customer's website

Number of users this request is being made to serve: around 1k initially by migrating customers, are expecting about 10k within the next two years.

DNS Verification via dig

λ ~/ dig @1.1.1.1 +short TXT _psl.wadl.top
"https://github.com/publicsuffix/list/pull/1924"

Results of Syntax Checker (make test)

============================================================================
Testsuite summary for libpsl 0.21.5
============================================================================
# TOTAL: 5
# PASS:  5
# SKIP:  0
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0
============================================================================

@FPVogel FPVogel changed the title Update public_suffix_list.dat Add wadl.top Jan 25, 2024
@FPVogel FPVogel marked this pull request as ready for review January 25, 2024 19:35
@simon-friedberger simon-friedberger added ❌FAIL - DOMAIN NOT 2Y+ *ALL* names in PRIVATE section MUST hold terms of 2 years or more registration from PR date #1109 ✔️DNS _psl Validated RFC 8553 Entries were present, matching PR# labels Jan 30, 2024
@FPVogel
Copy link
Contributor Author

FPVogel commented Feb 3, 2024

Thanks @simon-friedberger for adding the tag and bringing this to our attention,
the domain has now been renewed for an additional 2 years (meaning it will now be valid for close to 3 years) and will then auto-renew every two years.

As can be seen in this whois excerpt:

λ ~/ whois wadl.top
Domain Name: wadl.top
Registry Domain ID: D20240124G10001G_16808824-top
Registrar WHOIS Server: whois.ovh.net
Registrar URL: http://www.ovh.com/fr/index.xml
Updated Date: 2024-02-03T18:57:12Z
Creation Date: 2024-01-24T10:46:22Z
Registry Expiry Date: 2027-01-24T10:46:22Z
Registrar: OVH,sas
Registrar IANA ID: 433
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +33.0033972101007
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: WebWaddle Ltd.

@simon-friedberger simon-friedberger removed the ❌FAIL - DOMAIN NOT 2Y+ *ALL* names in PRIVATE section MUST hold terms of 2 years or more registration from PR date #1109 label Feb 5, 2024
@simon-friedberger
Copy link
Contributor

  • wadl.top expires 2027-01-24
  • DNS _psl entries
  • Tests pass
  • Sorting according to guidelines
  • Reasoning/Organization description

@simon-friedberger simon-friedberger added ✔️Sorting Validated https://github.com/publicsuffix/list/wiki/Guidelines#sort-your-submission-correctly-important r=simon-friedberger Marked as approved and ready to merge by @simon-friedberger ❔❔ question Open question, please look / answer / respond labels Feb 5, 2024
@simon-friedberger simon-friedberger removed the ❔❔ question Open question, please look / answer / respond label Feb 5, 2024
@FPVogel
Copy link
Contributor Author

FPVogel commented Apr 8, 2024

Hello everybody,
I understand this is a volunteer-driven project, so I don't want to cause any hassle or anything, but is there anything we can do from our end to move this along?

It's now been two months since the PR was reviewed, so it'd be great to know when we can expect it being merged.

All the best from Germany,
Merlin

@simon-friedberger simon-friedberger merged commit 42b9694 into publicsuffix:master Apr 10, 2024
@FPVogel FPVogel deleted the patch-2 branch April 22, 2024 23:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✔️DNS _psl Validated RFC 8553 Entries were present, matching PR# r=simon-friedberger Marked as approved and ready to merge by @simon-friedberger ✔️Sorting Validated https://github.com/publicsuffix/list/wiki/Guidelines#sort-your-submission-correctly-important
Projects
Status: Done or Won't
Development

Successfully merging this pull request may close these issues.

2 participants