Patch 1

[blipper]

Public Suffix List (PSL) Submission

Checklist of required steps

• [X ] Description of Organization

• [ X] Robust Reason for PSL Inclusion

• DNS verification via dig

• [ X] 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:

• [ X] 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!

• [ X] 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.

• [ X] The Guidelines were carefully read and understood, and this request conforms to them.
• [ X] The submission follows the guidelines on formatting and sorting.

• [X ] 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:

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

  URL where abuse contact or abuse reporting form can be found:

Report Abusive Activity from Amazon Web Services Resources

---

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)

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

---

Amazon

Description of Organization

Organization Website:

www.amazon.com

Reason for PSL Inclusion

Number of users this request is being made to serve:

Billiions

DNS Verification

This will improve the security posture for the com.be users. This is primarily intended to support amazon.com.be and make it behalf isomorphically to amazon.com.br, .amazon.com.mx, etc.

[wdhdev]

As you are updating the Amazon section, this should be in #2366, no?

[blipper]

As you are updating the Amazon section, this should be in #2366, no?

Maybe? Maybe not? :) This request is from the Amazon Stores/Ads which isn't same org as AWS. So I'm not sure the correct mechanism here. I will chase internally on this as we need to get the DNS updated anyways.

[wdhdev]

In that case I think how it is done here is fine then. If possible, do you think you can add a website link to the entry, similar to other entries on the list, or would said link just be to amazon.com?

[fakeboboliu]

It seems amazon.com.be is the only publicly accessible subdomain under com.be.
I'm not sure if that counts as a "public suffix".

[dnsguru]

@blipper Please coordinate requests for Amazon via @aph3rson - they have a comprehensive process via AWS

Closing this.

[aph3rson]

@dnsguru / team - thanks for the notification. We've followed-up with the requester internally - apologies for the randomization here.

---

In terms of the AWS / Amazon jurisdiction - our team handles requests from across Amazon. We expect that most of Amazon's PSL suffixes will be related to AWS products and services, though there is (at present) one from outside of AWS within Amazon:

list/public_suffix_list.dat

Lines 12149 to 12153 in 560007a

	// eero
	// Submitted by Yue Kang <[email protected]>
	// Reference: 264afe70-f62c-4c02-8ab9-b5281ed24461
	eero.online
	eero-stage.online

We don't expect the PSL maintainers to need to track the internal business structure of Amazon, such as which teams are in AWS/not. As mentioned in #1605, all of Amazon's PRs will have heads in the aws/public-suffix-list repository.

(If it makes it any clearer, we can look at moving that repository to the @amzn organization if desired.)