---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/it-operations-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Run Certificate Discovery via individual URL scans

# Run Certificate Discovery via individual URL scans {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

To initiate certificate discovery through URL scans, you must manually include individual URLs and configure a new certificate Discovery schedule.

## Vorbereitungen

Role required: discovery_admin or admin

## Warum und wann dieser Vorgang ausgeführt wird

Only the certificates that are available on the server during URL scans can be discovered. To confirm the available certificates, use the following command:
`openssl s_client -showcerts
-connect <URL>:<PORT> </dev/null`

## Prozedur

1. Navigate to AllCertificate ManagementCertificate Discovery Source URLS.
2. To add individual URLs to the table, select New.  
   Ensure accurate results by entering URLs in the following format: scheme://host:port. The port is optional, and defaults are used if not provided. For example: https://www.servicenow.com or https://servicenow.com:443, ldaps://myldap.com or ldaps://myldap.com:636.
3. Create a Discovery schedule with the following fields.  
   For more information on setting up your Discovery schedules, see [Schedule a horizontal discovery](https://servicenow-prod.fluidtopics.net/2aizkyr5X8Yrzi2WXW~chQ#t_CreateADiscoverySchedule "A discovery schedule determines what horizontal discovery searches for, when it runs, and which MID Servers are used. Create a discovery schedule for your local environment or a schedule for discovering the resources in your cloud service account.").
   1. Select Discovery: Certificates.
   2. Select Certificate Discovery Type: URL Certificate Discovery.  
      Keep the batch size as is, unless there is a specific recommendation to change it.
   {#run-cert-inventory-mgmt-urls__substeps_f4w_gtt_kjb}
4. To add or delete other URLs, from the Certificate URLs tab, select Edit.
5. Select Submit.
6. Select the checkbox to include URLs from the HTTP(s) Endpoint \[cmdb_ci_endpoint_http\] table in the discovery process.

## Ergebnisse

When your Discovery schedule runs, it automatically scans for any
certificates on the specified URLs and fetches all URLs from the
cmdb_ci_endpoint_http table. It then creates a mapping between the URL and the
schedule in the sn_disco_certmgmt_cert_url_sched_m2m.

With Service Mapping enabled, by default, it creates a relationship
between the HTTP endpoint and application when it creates an entry in
cmdb_ci_endpoint_http. For example, the Amazon application is automatically
connected to amazon.com.

The relationship is: cmdb_ci_endpoint_http\[parent\] --\> \[Implement End Point
To::Implement End Point From\] --\> cmdb_ci_appl\[child\].

If the above relationship exists, the URL certificate discovery creates an additional
relationship between the certificate and application. This relationship is:
cmdb_ci_appl\[parent\] --\> \[Uses::Used by\] --\> cmdb_ci_certificate\[child\].  
Hinweis:  
URL discovery schedules do not generate server configuration items (CIs).