# Getting ready to issue IP address certificates

**URL:** <https://community.letsencrypt.org/t/getting-ready-to-issue-ip-address-certificates/238777>\
**Category:** Issuance Tech\
**Created:** [June 24, 2025, 10:47pm UTC](https://community.letsencrypt.org/t/getting-ready-to-issue-ip-address-certificates/238777 "2025-06-24T22:47:10Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\
**Post date:** [June 24, 2025, 11:31pm UTC](https://community.letsencrypt.org/t/getting-ready-to-issue-ip-address-certificates/238777/3 "2025-06-24T23:31:42Z")

</div>

It should be an IP SAN type. This would be `IP.#` in OpenSSL, not `DNS.#`.

A related post:

> **[SSL certificate with IP in the SAN](https://forum.checkmk.com/t/ssl-certificate-with-ip-in-the-san/38175)**
>
> Hi, I issued an SSL certificate with and FQN, hostname and IP in the Subject Alternative Name extension. It’s working okay if I either use the FQDN or the hostname in the browser to connect to the console, but I get this meesage: Your...

---

_[View the full topic](https://community.letsencrypt.org/t/getting-ready-to-issue-ip-address-certificates/238777)._