add deno.net for Deno

[devsnek]

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

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://deno.net

---

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

Deno Deploy a product from Deno Land Inc. Deno Deploy is a serverless JavaScript hosting platform. Customers may bring their own domain or use a subdomain provided by the platform. With respect to this request, I am an full time engineer at Deno Land Inc.

Organization Website: https://deno.com

Reason for PSL Inclusion

Deno Deploy will host discrete customer zones on subdomains of deno.net, which therefore need to be cross origin isolated.

Previous changes for Deno Deploy: #1167

Number of users this request is being made to serve: ~80000

DNS Verification

dig +short TXT _psl.deno.net
"https://github.com/publicsuffix/list/pull/2400"

[groundcat]

• Expiration (Note: Must STAY >2y at all times)
  • deno.net Registry Expiry Date: 2029-01-14T06:52:21Z
• DNS _psl entries (Note: Must STAY in place)
• Sorting
• Reasoning/Organization description
  • Comments: The PR doesn't clearly explain why deno.net is needed when Deno already has deno.dev and deno-staging.dev in the PSL
• Non-personal email address
• Abuse contact
  • Comments: https://deno.net appears to be non-functional at this time

---

1. Would you please clarify why deno.net is needed as a separate entry when Deno already has deno.dev and deno-staging.dev in the PSL? It would be helpful to understand the specific use case that requires an additional domain rather than using the existing PSL entries.
2. I notice that https://deno.net/ is currently not functioning. As per the PSL guidelines, there must be clear and accessible abuse contact information for all domains in the PSL. Could you please confirm that once your service is operational, users will be able to report abuse either through the website at https://deno.net/ or via email at [email protected] as per RFC 2142?

[devsnek]

@groundcat

Would you please clarify why deno.net is needed as a separate entry when Deno already has deno.dev and deno-staging.dev in the PSL? It would be helpful to understand the specific use case that requires an additional domain rather than using the existing PSL entries.

The new version of this service operates very differently and runs on a completely separate infrastructure. At the same time, the existing version of this service will continue to serve existing deployments.

I notice that https://deno.net/ is currently not functioning. As per the PSL guidelines, there must be clear and accessible abuse contact information for all domains in the PSL. Could you please confirm that once your service is operational, users will be able to report abuse either through the website at https://deno.net/ or via email at [email protected] as per RFC 2142?

I can confirm this.

[piscisaureus]

I can confirm that [email protected] is now operational and routed to the appropriate inboxes.