Certificate authority
GlobalSign: Belgian-Japanese CA, roots R3–R46 and ACME
Details
- CCADB CA owner
- GlobalSign nv-sa
- Country
- BE
- Country (CCADB)
- Belgium
- ACME
- Yes
- Free certificates
- No
- Products
- DV OV EV wildcard multi-domain S/MIME code-signing document-signing VMC private-PKI
- Roots
- 6
- Roots trusted for TLS
- Chrome 5 · Mozilla 5 · Apple 6 · Microsoft 6
- Intermediates under its roots
- 568 (237 valid)
- Auditor
- KPMG
- CAA
globalsign.com
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 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.
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.
Copy-ready record(s) for the first 1 domain(s):
example.com. CAA 0 issue "globalsign.com"| Domain | Valid intermediates |
|---|---|
globalsign.com | 286 |
For issuewild, iodef or DNS-provider formats, use the CAA record generator: CAA Generator
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.
Roots this CA owner has in the CCADB TLS Server Authentication report, with current status in each root store.
- trusted for TLS
- included with limits (NotBefore / no TLS bit)
- removed or blocked
- not included
| Root certificate | Key | Expires | Ch | Mo | Ap | MS | Intermediates |
|---|---|---|---|---|---|---|---|
| GlobalSign | RSA 2048 | 2029-03-18 | Included | Included | Included | Included | 216 (86) |
| GlobalSign | ECDSA P-384 | 2038-01-19 | Included | Included | Included | Included | 93 (23) |
| GlobalSign | RSA 4096 | 2034-12-10 | Included | Included | Included | Included | 60 (35) |
| GlobalSign Root CA | RSA 2048 | 2028-01-28 | Removed | Included | Included | Included | 73 (12) |
| GlobalSign Root E46 | ECDSA P-384 | 2046-03-20 | Included | Included | Included | Included | 52 (27) |
| GlobalSign Root R46 | RSA 4096 | 2046-03-20 | Included | Included | Included | Included | 74 (54) |
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.
| Audit | Scheme | Period | Statement | Report |
|---|---|---|---|---|
| Standard audit | WebTrust | 2025-04-01 – 2026-03-31 | 2026-06-29 | cpacanada.ca |
| Network security | WebTrust | 2025-04-01 – 2026-03-31 | 2026-06-29 | cpacanada.ca |
| TLS Baseline Requirements | WebTrust | 2025-04-01 – 2026-03-31 | 2026-06-29 | cpacanada.ca |
| TLS EV Guidelines | WebTrust | 2025-04-01 – 2026-03-31 | 2026-06-29 | cpacanada.ca |
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 (effective 2026-06-15)
- CP/CPS: https://www.globalsign.com/en/repository/GlobalSign-eIDAS-CPCPS-v1.1.pdf (effective 2026-06-15)
- Document repository: https://www.globalsign.com/en/repository
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”:
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.