Acceptable Internal domain names
Posted by Leonard Grove on 05 March 2013 06:48 PM
In all cases, a domain name, whether intended for internal or external use, containing a gTLD or ccTLD listed on IANA which is unregistered, or otherwise not controlled by the applicant will be rejected. This includes, but is not limited to the use of .INT as an internal domain name.|
The following are NOT acceptable for trusted SSL certificates.
1) The following IP blocks are defined as private and non-routable over the internet:
10.0.0.0 – 10.255.255.255
172.16.0.0 – 172.31.255.255
192.168.0.0 – 192.168.255.255
2) Any single server name containing no dots. For example:
3) The following internal use TLD's referenced in RFC2606 , and comments to the same:
Any other unreserved TLD domain names included on a certificate request will be reviewed on a case by case basis, but in all likelihood will be rejected.
(a) As of July 1, 2012 (Effective Date), the use of Certificates containing Reserved IP Address or Internal Server Name has been deprecated by the CA / Browser Forum and the practice will be eliminated by October 2016. Also as of the Effective Date, SSL.com WILL NOT issue a certificate with an Expiry Date later than 31 October 2015 with a subjectAlternativeName (SAN) extension or Subject commonName (CN) field containing a Reserved IP Address or Internal Server Name. Effective 1 October 2016, SSL.com WILL REVOKE all unexpired Certificates whose subjectAlternativeName extension or Subject commonName field contains a Reserved IP Address or Internal Server Name.
(b) If you are using an internal top level domain (TLD) which is not currently a valid TLD), such as those above, or others which we may allow at our discretion for your internal use in this certificate request, please be advised that should such TLD become recognized by IANA/ICANN as a valid TLD this certificate will be revoked without further notice. Prior to the certificate being reinstated you will need to demonstrate domain ownership/control.