Add 'al-web.de' and '*.st-srv.eu'

[RiRe]

Public Suffix List (PSL) Submission

Checklist of required steps

• Description of Organization

• Robust Reason for PSL Inclusion

• DNS verification via dig

• 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).

Note: See #2486 - DE domain registration terms cannot exceed 1 month and cannot be publicly queried (EU was extended accordingly). We commit to keep the domains alive.

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.

• A role-based email address has been used and this inbox is actively monitored with a response time of no more than 30 days.

Abuse Contact:

• Abuse contact information (email or web form) is available and easily accessible.

  URL where abuse contact or abuse reporting form can be found: https://al-web.de/ and https://st-srv.eu/

---

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

We are a software development company and focused on the hosting industry. We have clients with customers demanding free subdomains for their product, which may be a webspace, VPS or dedicated server. Our client NUXOA GmbH operates the service ST-Hosting.com and provides webspace with a subdomain of al-web.de and server products below *.st-srv.eu (e.g. example.vps.st-srv.eu). We have been engaged to introduce our DNS and registration platform for both domains while keeping existing subdomains. After discussing the security problems with shared domains, we also should apply for and manage the PSL entry. I am the CEO of sourceWAY GmbH.

Organization Website: https://sourceway.de

Reason for PSL Inclusion

We want to enhance cookie security for clients using applications on the "shared" domains. Another point is the presentation in some browsers: Imagine "example.al-web.de". Some browsers identify "example" as subdomain and reduce the opacity or even do not display it at all.

Number of users this request is being made to serve: Several thousand (combined, most of them under st-srv.eu, however al-web.de has a higher share of subdomains being used for web applications)

DNS Verification

$ for d in al-web.de st-srv.eu; do dig +short txt _psl.$d; done
"https://github.com/publicsuffix/list/pull/2983"
"https://github.com/publicsuffix/list/pull/2983"

[RiRe]

Please re-run the checks

[pencilnav]

Please manually refill the PR message using our latest PR Template:

https://github.com/publicsuffix/list/blob/main/.github/pull_request_template.md

User counts should be the amount of distinct individuals that receives subdomains from submitted entries, and the counts should be listed at a per entry basis.

[simon-friedberger]

Please re-run the checks

Still no DNS records.

[pencilnav]

@RiRe Please provide, at a per entry basis, the current, exact amount of distinct individual users who received subdomains from these submitted entries.