Update company & contact email address only

[Slm0n87]

Public Suffix List (PSL) Submission

This PR only updates contact informations.

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

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)

• Cloudflare
• Let's Encrypt
• MAKE SURE UPDATE THE FOLLOWING LIST WITH YOUR LIMITATIONS! REMOVE ENTRIES WHICH DO NOT APPLY AS WELL AS REMOVING THIS LINE!

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

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:

---

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

STACKIT is a strong growing german cloud provider company that offers managed Infrastructure- and Platform as a Service solutions for our customers.
Within the STACKIT DNS service we offer our customers free domains under which the customer can register his own DNS zones as a subdomain
to make his cloud application available. This is why we have to add the new domains.

Organization Website:
https://www.stackit.de/en/

Reason for PSL Inclusion

Our customers share the provided domains registered and owned by us. Every customer has full DNS control over the subdomains.
We need to protect the subdomains from the exchange of cookies between them.

Number of users this request is being made to serve:
over 550k

DNS Verification

dig +short TXT _psl.runs.onstackit.cloud
"https://github.com/publicsuffix/list/pull/2285"
dig +short TXT _psl.stackit.gg
"https://github.com/publicsuffix/list/pull/2285"
dig +short TXT _psl.stackit.rocks
"https://github.com/publicsuffix/list/pull/2285"
dig +short TXT _psl.stackit.run
"https://github.com/publicsuffix/list/pull/2285"
dig +short TXT _psl.stackit.zone
"https://github.com/publicsuffix/list/pull/2285"