MULTICERT root inclusion request for MULTICERT Root Certificate

This case was a Mozilla root inclusion request from MULTICERT for its root certificate. MULTICERT opened the bug and provided CA information, audit statements, CP/CPS documents, and test websites for verification. Mozilla reviewers asked for clarifications and additional evidence over time, including audit authenticity checks, BR self-assessment, email-address validation details, and fixes to test-site and policy issues. MULTICERT responded with updated documents, new audit statements, corrected test sites, and a BR self-assessment attachment. In 2020, Mozilla asked whether MULTICERT still intended to pursue the request, MULTICERT replied that it would submit new RSA and ECC root CA certificates when ready, and MULTICERT then suggested closing this bug and filing a new one later.

1. 2014-07-17 MULTICERT opened a root inclusion request for its root certificate.
2. 2016-02-05 MULTICERT stated it was confirming user email during subject registration and pointed to an updated CP/CPS.
3. 2018-04-10 MULTICERT attached a BR self-assessment for the request.
4. 2020-09-02 MULTICERT said the bug should be closed and a new one filed when ready to restart the process.

1. 2014-07-17 MULTICERT — MULTICERT created the bug and attached general CA information and accreditation material.
2. 2014-07-21 Mozilla representative — Mozilla accepted the bug and asked MULTICERT to clarify whether it was a Super CA.
3. 2015-09-14 Mozilla representative — Mozilla attached an initial CA information document and listed additional information still needed.
4. 2015-10-15 MULTICERT — MULTICERT replied to the requested items, including the audit requirement, email verification, and subordinate CA listing.
5. 2015-12-15 Mozilla representative — Mozilla said it had contacted the revocationcheck site owner about an OCSP-related error and asked for updated CP/CPS timing.
6. 2016-02-05 MULTICERT — MULTICERT said it was now confirming user email on subject registration and cited a CP/CPS page.
7. 2016-02-12 Mozilla representative — Mozilla reported a BR compliance error on a test certificate and asked for it to be resolved.
8. 2016-02-12 MULTICERT — MULTICERT said the problem was solved by issuing a new certificate in the correct profile.
9. 2017-03-31 Mozilla representative — Mozilla requested a BR self-assessment as part of the inclusion process.
10. 2018-04-10 MULTICERT — MULTICERT attached its BR self-assessment document.
11. 2018-08-15 Mozilla representative — Mozilla attached an updated CA information document and listed remaining issues, including audit statement dates, confidentiality clauses, email-control wording, test-site chaining, lint errors, and subordinate CA policy coverage.
12. 2018-11-21 MULTICERT — MULTICERT replied with updated CP/CPS URLs, said it requested the Email trust bit, described email validation, and said it had corrected the test-site hierarchy.
13. 2018-12-07 Mozilla representative — Mozilla pointed to the CCADB case view and asked for reporting instructions, updated audit statements, and resolution of bug 1509002.
14. 2020-08-27 Mozilla representative — Mozilla asked MULTICERT whether it still intended to pursue the root inclusion request.
15. 2020-09-01 Mozilla representative — Mozilla recorded MULTICERT's response that it would submit new RSA and ECC root CA certificates when ready.
16. 2020-09-02 MULTICERT — MULTICERT suggested closing the bug and filing a new one when ready to restart the process.