Warning: get_class() expects parameter 1 to be object, null given in /home/hanslie0/public_html/hali.no/wp-content/plugins/real-media-library/inc/comp/WPML.class.php on line 32

Warning: Cannot modify header information - headers already sent by (output started at /home/hanslie0/public_html/hali.no/wp-content/plugins/real-media-library/inc/comp/WPML.class.php:32) in /home/hanslie0/public_html/hali.no/wp-content/plugins/sg-cachepress/core/Supercacher/Supercacher_Helper.php on line 77
SSL Certificates for Internal Server Names | Hans' Place

After November 1, 2015 Certificates for Internal Names Will No Longer Be Trusted

In November 2011, the CA/Browser Forum (CA/B) adopted Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates that took effect on July 1, 2012. These requirements state:

“As of the Effective Date of these Requirements, prior to the issuance of a Certificate with a Subject Alternative Name (SAN) extension or Subject Common Name field containing a Reserved IP Address or Internal Server Name, the CA shall notify the Applicant that the use of such Certificates has been deprecated by the CA / Browser Forum and that the practice will be eliminated by October 2016. Also as of the Effective Date, the CA shall not issue a certificate with an Expiry Date later than 1 November 2015 with a SAN or Subject Common Name field containing a Reserved IP Address or Internal Server Name. As from 1 October 2016, CAs shall revoke all unexpired Certificates.”

https://www.digicert.com/internal-names.htm