groundcat
commented
3 months ago - The sorting looks good to me.
- Expiry: The
.mpregistry (Saipan DataCom, Inc.) at http://get.mp doesn't have a WHOIS service to check expiry. - The
_pslrecord exists and is valid. - The registry website http://www.registry.com.mp/ provides subdomain registration services, matching the organization description provided.
Under the third-party limits, you have listed both Cloudflare and Let's Encrypt. If you are trying to get around limitations by Cloudflare and Let's Encrypt, you should contact them. If not, you should remove those entries, as per the guidelines.
Number of users this request is being made to serve: com.mp domains population is about 826, As so far.
Per crt.sh records of com.mp indicating the dates of SSL certificate issuance, which isn't a rigorous approach but usually indicative of a SLD/website's lifecycle, the registry's website www.registry.com.mp appears to be newly established today on 2024-06-08. So far, there have been 6 subdomains with separate SSL certificates issued, compared to the "826" reported by the submitter. As of today, there is 1 entry observed through Google site:com.mp, suggesting a potentially low user count, so there might be a relevance issue.
serverless-domain-registry
simon-friedberger
dnsguru
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
[x] Description of Organization
[x] Robust Reason for PSL Inclusion
[x] DNS verification via dig
[x] Run Syntax Checker (make test)
[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) in the affected section
Submitter affirms the following:
[x] This request was not submitted with the objective of working around other third-party limits
[x] The Guidelines were carefully read and understood, and this request conforms
[x] 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)
[x] Yes, I understand. I could break my organization's website cookies etc. and the rollback timing, etc is acceptable. Proceed.
Description of Organization
The Com.mp Registry is a free domain name provider, and we'd like to offer domain to every people in each corner of the world, for free.
Organization Website:
www.registry.com.mp
Reason for PSL Inclusion
We need to be admitted and accepted by DNS providers, And most of them is respecting PSL.
Number of users this request is being made to serve:
com.mp domains' registration number is about 826 before PR created. And according to Certificate Transparency Log(https://crt.sh/?q=%25.com.mp), com.mp subdomain requested ssl certificate for 34 domains until 12th Jun(excluded com.mp itself).
DNS Verification via dig
Results of Syntax Checker (
make test)