# GlobalSign: Belgian-Japanese CA, roots R3–R46 and ACME > GlobalSign, the CA founded in Belgium in 1996 and owned by Japan's GMO group: its R3, R5, R6, R46 and E46 roots, paid ACME and Chrome's removal of Root CA R1. Source: https://ssl.sh/cas/globalsign/ Last updated: 2026-11-10 GlobalSign is one of the oldest public certificate authorities, founded in Belgium in 1996 and owned by Japan's GMO Internet group. It sells DV, OV and EV certificates, S/MIME, code and document signing, and supports ACME on its paid enterprise platform; it has no free TLS certificates. ## Owner and headquarters GlobalSign NV was established in Belgium in 1996. According to the corporate history of GMO GlobalSign Holdings, it became a subsidiary of the GMO group in October 2006. The operating companies use the GMO GlobalSign name, and the CCADB lists the CA owner as "GlobalSign nv-sa", the Belgian entity. ## Root certificates As of November 2026, CCADB lists six GlobalSign roots in the TLS report. Five are trusted for TLS by Chrome, Mozilla, Apple and Microsoft: three roots whose common name is only "GlobalSign" (the R3 RSA 2048 root valid until 2029-03-18, the R5 ECDSA P-384 root until 2038-01-19 and the R6 RSA 4096 root until 2034-12-10), and the newer GlobalSign Root R46 (RSA 4096) and E46 (ECDSA P-384), valid until 2046-03-20. The sixth, GlobalSign Root CA from 1998, is no longer in Chrome's store. A former GlobalSign ECC root is now listed under [Google Trust Services](https://ssl.sh/cas/google-trust-services/) in the CCADB, under the same "GlobalSign" name. ## Certificate products DV (including the AlphaSSL brand), OV and EV TLS certificates in wildcard and multi-domain variants, S/MIME, code signing, document signing, Verified Mark Certificates for BIMI and managed private PKI, sold through its Atlas platform and resellers. ## ACME support GlobalSign offers ACME for its paid certificates through Atlas, so standard ACME clients can request and renew them with account credentials. There's no anonymous public ACME endpoint. ## Free certificates GlobalSign doesn't offer free publicly trusted TLS certificates. ## Notable incidents and changes The main recent change is in the root stores: Chrome has dropped the 1998 GlobalSign Root CA (R1), which expires on 2028-01-28 anyway, while GlobalSign's newer R46 and E46 roots are trusted everywhere. If your chain still ends at GlobalSign Root CA, ask GlobalSign for a chain to a current root so Chrome users can still build a trusted path. ## Root certificates (CCADB) GlobalSign has 6 root certificate(s) in the CCADB TLS report. Together they have signed 568 intermediate CA certificates, 237 of them still valid. | Root certificate | Key | Expires | Chrome | Mozilla | Apple | Microsoft | Intermediates | SHA-256 | |---|---|---|---|---|---|---|---|---| | GlobalSign | RSA 2048 | 2029-03-18 | Included | Included | Included | Included | 216 | CBB522D7B7F127AD6A0113865BDF1CD4102E7D0759AF635A7CF4720DC963C53B | | GlobalSign | ECDSA P-384 | 2038-01-19 | Included | Included | Included | Included | 93 | 179FBC148A3DD00FD24EA13458CC43BFA7F59C8182D783A513F6EBEC100C8924 | | GlobalSign | RSA 4096 | 2034-12-10 | Included | Included | Included | Included | 60 | 2CABEAFE37D06CA22ABA7391C0033D25982952C453647349763A3AB5AD6CCF69 | | GlobalSign Root CA | RSA 2048 | 2028-01-28 | Removed | Included | Included | Included | 73 | EBD41040E4BB3EC742C9E381D31EF2A41A48B6685C96E7CEF3C1DF6CD4331C99 | | GlobalSign Root E46 | ECDSA P-384 | 2046-03-20 | Included | Included | Included | Included | 52 | CBB9C44D84B8043E1050EA31A69F514955D7BFD2E2C6B49301019AD61D9F5058 | | GlobalSign Root R46 | RSA 4096 | 2046-03-20 | Included | Included | Included | Included | 74 | 4FA3126D8D3A11D1C4855A4F807CBAD6CF919D3A5A88B03BEA2C6372D93C40C9 | ## CAA records The CCADB lists 1 CAA issuer domain(s) recognized by the currently valid intermediate certificates of GlobalSign. One issue record with any of them lets GlobalSign issue for your domain. Domains that contain the CA's name come first, the rest by how many valid intermediates recognize them. ``` example.com. CAA 0 issue "globalsign.com" ``` ## Audits Audit data the CCADB records for the TLS roots of GlobalSign. Auditor(s): KPMG. The most recent audit period ended on 2026-03-31. - Standard audit: WebTrust 2025-04-01 – 2026-03-31 (https://www.cpacanada.ca/api/getPDFWebTrust?attachmentId=bbae26a8-947d-40ab-8879-4b9454874bd7) - Network security: WebTrust 2025-04-01 – 2026-03-31 (https://www.cpacanada.ca/api/getPDFWebTrust?attachmentId=9a2e997e-6fe0-41ba-aeef-6c3bc5404409) - TLS Baseline Requirements: WebTrust 2025-04-01 – 2026-03-31 (https://www.cpacanada.ca/api/getPDFWebTrust?attachmentId=04c52423-fae9-4bff-a02e-cb9f608939b6) - TLS EV Guidelines: WebTrust 2025-04-01 – 2026-03-31 (https://www.cpacanada.ca/api/getPDFWebTrust?attachmentId=6523d9f3-41f8-481a-becb-3d71f9e85897) ## CP/CPS documents Certificate Policy and Certification Practice Statement links that GlobalSign has disclosed in the CCADB for its TLS roots, with effective dates: - CP/CPS: https://www.globalsign.com/en/repository/GlobalSign-Generic-CPCPS-v1.1.pdf - CP/CPS: https://www.globalsign.com/en/repository/GlobalSign-eIDAS-CPCPS-v1.1.pdf ## Report a certificate problem To report a mis-issued certificate, a compromised private key or other abuse, use the channels GlobalSign lists in the CCADB (replace [at] and [dot] in addresses): - report-abuse[at]globalsign[dot]com ## Incident reports CAs in Mozilla's root program file compliance incident reports in Mozilla's Bugzilla (product CA Program, component CA Certificate Compliance). This search lists the bugs whose title contains the words “GlobalSign”: https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=CA+Program&component=CA+Certificate+Compliance&short_desc_type=allwords&short_desc=GlobalSign&order=changeddate+DESC ## FAQ **What CAA record allows GlobalSign to issue certificates?** Publish example.com. CAA 0 issue "globalsign.com". The CCADB lists 1 recognized domain(s) for GlobalSign: globalsign.com. **Who audits GlobalSign?** KPMG, according to the CCADB. The latest TLS Baseline Requirements audit (WebTrust) covers 2025-04-01 to 2026-03-31; the statement is dated 2026-06-29. **How do I report a problem certificate to GlobalSign?** Use the channel(s) listed in the CCADB: report-abuse[at]globalsign[dot]com. **How many root certificates does GlobalSign have?** 6 in the CCADB TLS report. Trusted for TLS: Chrome 5, Mozilla 5, Apple 6, Microsoft 6. They have signed 568 intermediates, 237 of them still valid. Sources: CCADB All Certificate Information (V5), List of CAA Identifiers, List of CA problem reporting mechanisms and TLS Server Authentication report (ccadb.org/resources).