Skip to content
TheChatArchiveThe Chat Archive
DeepSeekdeepseek-r1-0528· DeepSeekHugging Face LMArena Human Preference 140K

Is it possible to issue a CA cert for an IP address?

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Metallama-4-maverick-03-26-experimental’s answer.
  1. User

    Is it possible to issue a CA cert for an IP address?

  2. DeepSeek Assistant

    Yes, it is technically possible to issue a TLS/SSL certificate (including CA certificates) for an IP address, but significant restrictions and caveats apply:


    1. Where IP Addresses Are Allowed

    • Subject Alternative Name (SAN) Extension:
      IP addresses must be specified in the subjectAltName extension (RFC 5280), not in the Common Name (CN) field.
      Example:
      subjectAltName = IP:192.0.2.1
      

    2. Public Certificate Authorities (CAs) - Strict Limitations

    • Public IP Addresses:
      Most public CAs (e.g., Let's Encrypt, DigiCert, Sectigo) prohibit issuing certificates for public IP addresses due to:

      • Security Risks: IPs can be reassigned, leading to impersonation.
      • Compliance: Violates CA/Browser Forum Baseline Requirements (BRs §7.1.4.2.1).
      • Ownership Validation: Hard to prove control of an IP (vs. a domain via DNS/HTTP challenges).
    • Private IP Addresses:
      Public CAs will not issue certificates for private IPs (e.g., 192.168.*, 10.*, 172.16-31.*).
      Why? They are non-routable and cannot be publicly validated.

    • Exceptions:
      Some enterprise CAs (e.g., internal Microsoft AD CS) or specialized providers might issue IP-based certs for controlled environments, but not for public trust.


    3. Private/Internal Certificate Authorities (CAs) - The Solution

    • For internal infrastructure (e.g., servers accessed via IP in a VPN/data center):
      • Deploy a Private CA (e.g., OpenSSL, HashiCorp Vault, Active Directory Certificate Services).
      • Issue certificates with IP SANs (e.g., IP:10.0.0.5).
      • Clients must trust your private CA root certificate.

    4. Use Cases for IP-Based Certificates

    • Legacy systems without DNS.
    • IoT devices in isolated networks.
    • Internal APIs/services accessed via static IP.
    • Testing environments (using self-signed certs with IP SANs).

    5. Key Technical Notes

    • Browsers: Modern browsers (Chrome, Firefox) enforce SAN-based validation. Certificates with IPs in the CN field will be rejected.
    • RFC Compliance: Supported by TLS standards (RFC 2818, RFC 6066).
    • Self-Signed Certificates:
      Easily created for IPs (e.g., OpenSSL):
      openssl req -x509 -newkey rsa:4096 -sha256 -days 365 \
        -subj "/CN=myapp" -addext "subjectAltName=IP:192.168.1.1" \
        -keyout key.pem -out cert.pem
      

    Summary

    • Public CAs: ❌ Almost never issue certificates for IP addresses (public or private).
    • Private CAs: ✅ Use to issue IP-based certificates for internal networks.
    • Self-Signed: ✅ For testing/internal use (clients must manually trust the cert).

    Recommendation: For public services, always use a domain name. For private IPs, deploy a private CA. Avoid public IPs in certificates unless strictly necessary in a controlled environment.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.