GD - graphic.design

[RohanD-GD]

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

GoDaddy Registry is both a Registry Operator of Top Level Domains, as well as a backend technical registry provider for over 200 Top Level Domains. GoDaddy Registry develops and operates a Domain Registry platform, as well as provides DNS services for multiple ccTLDs, open gTLDs and brand gTLDs.

The submitter, Rohan Durrant, is a manager of engineering teams at GoDaddy Registry, based in Melbourne, Australia.

Organization Website: https://registry.godaddy

Reason for PSL Inclusion

GoDaddy Registry will be opening graphic.design to individual registrations, through a global network of authorised Registrars, similar to a standard open gTLD. This inclusion in the PSL is to ensure the correct operation of the zone as an open TLD, such that providers including website, email and Certificate Authorities recognise the individual ownership of the registered domains within the graphic.design DNS zone.

The graphic.design zone is registered by GoDaddy registry for 10 years. GoDaddy is also the operator of the .design TLD (as Registry Services LLC) and has both reserved the name, as well as placed Server locks on the name at the top level within .design Registry.

Number of users this request is being made to serve: 5,000 to 10,000+

DNS Verification via dig

$dig TXT _psl.graphic.design 

_psl.graphic.design.	3600	IN	TXT	"https://github.com/publicsuffix/list/pull/1940"

Results of Syntax Checker (make test)

All tests passed

PASS: libpsl_icu_load_dafsa_fuzzer
PASS: libpsl_icu_fuzzer
PASS: libpsl_icu_load_fuzzer
PASS: test-is-public-all
PASS: test-is-public
PASS: test-is-public-builtin
PASS: test-is-cookie-domain-acceptable
PASS: test-registrable-domain

[simon-friedberger]

If you are officially operating .design, shouldn't this go through ICANN or IANA?
cc @dnsguru

[dnsguru]

Good q and friction while learning. If this were in the ##ICANN section maybe.

The request placed in the ##PRIVATE section, to me, seems like looping ICANN/IANA would be unnecessary, as it is more akin to .us.com or other "jump point" etld+

[simon-friedberger]

• Expiration (Note: Must STAY >2y at all times)
  • graphic.design expires 2034-02-28
• DNS _psl entries (Note: Must STAY in place)
• Tests pass
• Sorting
• Reasoning/Organization description

[dnsguru]

This is approved @RohanD-GD but see #1951 - it is published to the github repository copy of the dat file but it appears Mozilla needs to re-connect the CDN publishing that makes the file available at publicsuffix.org