Public Suffix List/Procedures

This page lists the procedures involved in maintenance of the Public Suffix List.

At the moment, the master copy of the list lives in the mozilla-central tree at Mozilla, although there are plans to change that. It is mirrored regularly to publicsuffix.org, and people should download it from there.

People wanting changes to the PSL are encouraged to file bugs.
Sometimes, requests still come in by email, in which case you should file a bug to track that request.
We also need to regularly file bugs for the new gTLDs being created by ICANN. Jothan's spreadsheet has the details. Copy column H to get the data to paste into the PSL file at the appropriate point, to make the patch.

Here's the bug list of open PSL bugs.

Make sure the person making the request is permitted to do so. In the case of private domains, that means either that they have a Bugzilla account with an official-looking email address, or you do a manual exchange of emails with such an address. Be more careful with domains where it is clear that email addresses can be acquired by members of the public.
In the case of ICANN domains, make sure that the request matches the published material on the registry website, and/or other sources such as Wikipedia.

Once you are satisfied the request is legitimate, make a patch.
If possible, you should run the PSL tests to make sure you haven't broken the format of the list. When we move to our own repo, that will be easier. For now, you need to build Firefox and then run:

  $ ./mach xpcshell-test netwerk/test/unit/test_psl.js
  $ ./mach xpcshell-test netwerk/test/unit/test_bug414122.js

To validate syntax of your local changes on effective_tld_names.dat you can use the prepare_tlds.py script (published in mozilla-central repository):

  $ python ./netwerk/dns/prepare_tlds.py netwerk/dns/effective_tld_names.dat

Output of this script is a list of all parsed entries.

Upload the patch to the bug, and set the "review" flag, with the target being gerv@mozilla.org.

Gerv will apply the patches and check them in to mozilla-central or mozilla-inbound (an integration branch tracking mozilla-central).

Contents