GlobalSign: IP in dnsName

GlobalSign was reported for issuing certificates with invalid dnsNames that contained IP addresses. The issue was initially reported on January 29, 2019, but GlobalSign did not revoke the certificates or respond to the report. Following the public disclosure of the issue, GlobalSign confirmed that all identified certificates have since been revoked. They acknowledged a failure to meet the Baseline Requirements for timely revocation and committed to improving their incident response processes. The case has been resolved with the necessary actions taken.

1. 2019-01-29 Report of invalid dnsNames containing IP addresses was submitted to GlobalSign.
2. 2019-02-08 GlobalSign confirmed all identified certificates have been revoked.

1. 2019-01-29 Titanous representative — Reported that GlobalSign issued certificates with invalid dnsNames containing IP addresses and did not revoke them.
2. 2019-02-04 Community commenter — Requested an update and incident report regarding GlobalSign's failure to meet revocation timelines.
3. 2019-02-08 Community commenter — Confirmed that all identified certificates have been revoked.
4. 2019-02-11 Fastly representative — Expressed concern over GlobalSign's lack of response to the problem report within the required timeframe.
5. 2019-02-19 Community commenter — Outlined updates to the incident response process to ensure timely acknowledgments.
6. 2019-02-21 Fastly representative — Noted that remediation is complete.