A long-standing commercial authority, selling under GlobalSign and AlphaSSL, and one of the authorities Fastly offers. One CAA value, globalsign.com, covers both brands.
| Run by | GlobalSign nv-sa, Belgium |
| CAA value | globalsign.com |
| CAA parameters | Not documented |
| ACME | https://emea.acme.atlas.globalsign.com/directory — with an External Account Binding key from your account |
| Cost | Paid |
| Certificates | DV (and AlphaSSL), OV and EV; wildcards for DV and OV |
| Longest certificate | 200 days |
| Issuer names on its certificates | GlobalSign Atlas R46 DV TLS CA 2026 Q4, GlobalSign GCC R6 AlphaSSL CA 2025, GlobalSign GCC R46 OV TLS CA 2026 |
| Also sold as | AlphaSSL |
| Issues for | One of the authorities Fastly uses |
May GlobalSign issue for your domain?
Enter a domain or hostname: we read its CAA records as GlobalSign must — its own, or the nearest parent’s — and say whether they let it issue, for wildcards too, and which authority issued the certificate it serves now.
The CAA record for GlobalSign
Published on your domain, this lets GlobalSign issue for it and for every name under it that has no CAA records of its own. Every authority not named must refuse. Keep the records for any other authority you use — your host’s or CDN’s included.
example.com. CAA 0 issue "globalsign.com"
An issue record covers wildcard certificates too. To let GlobalSign issue wildcards and no one else, add an issuewild record — once there is one, issue records stop counting for wildcards — and an iodef address for authorities to report refused requests to:
example.com. CAA 0 issuewild "globalsign.com"
example.com. CAA 0 iodef "mailto:security@example.com"
How it reads CAA
It processes issue, issuewild, issuemail and issuevmc, and reads but does not act on iodef. It caches CAA answers for up to an hour and follows up to 10 CNAMEs.
It issues after a lookup timeout or SERVFAIL only for zones that are not signed with DNSSEC.
Getting a certificate
Through its Atlas platform, or ACME with an external account key made from the Atlas API and MAC keys.
When a CAA record stops it
Its error names the blocking record, in the form “example.com.”: “issue”=”another-ca.com” — the records on example.com allow another-ca.com and not globalsign.com. Other CAA errors read SERVFAIL, “i/o timeout”, or “The quorum requirements were not met” when the check from several places disagrees.
What changed
- July 2025 — New TLS-only issuing CAs under its R46 and E46 roots.
- 27 July 2026 — Moved every product to its TLS-dedicated roots.
- 13 September 2026 — Chrome stopped accepting new certificates from its multi-purpose roots R3, R5 and R6.
Worth knowing
- Its issuing CAs change every quarter, and the name says which: GlobalSign Atlas R46 DV TLS CA 2026 Q4.
- It cross-signs Google Trust Services’ older roots for older devices.
Questions
Which CAA value does AlphaSSL need?
globalsign.com — AlphaSSL is GlobalSign’s, and has no value of its own.
Sources
Checked on 27 September 2026 against these official sources:
- GlobalSign Generic CPCPS v1.1 — globalsign.com
- CAA Checking for SSL Certificates — support.globalsign.com
- Upcoming Changes to TLS Roots and Certificate Profiles :: GlobalSign Atlas Documentation — docs.globalsign.com