Modern applications aren’t limited to servers and IP ranges anymore.
Customer-facing services, SaaS applications, APIs, and web endpoints often sit outside traditional infrastructure boundaries — making them harder to discover, monitor, and map. For many teams, these URLs remain blind spots in the CMDB, even though they are business-critical.
That’s where ITOM URL Discovery comes in.
ITOM URL Discovery helps organisations discover, track, and gain insights into web-based endpoints so they can extend visibility beyond traditional infrastructure and improve service awareness.
Why URL Discovery is needed
Traditional discovery methods focus on IP-based infrastructure — servers, network devices, and applications reachable via credentials. However, many real-world scenarios don’t fit that model.
Common challenges include:
-
Customer-facing URLs with unknown ownership
-
SaaS or third-party endpoints not backed by internal servers
-
Missing visibility into externally exposed services
-
URLs that change over time without governance
Without URL-level visibility, teams struggle to:
-
Understand service dependencies
-
Maintain CMDB completeness
-
Monitor business-critical endpoints
-
Assess operational and security risk
ITOM URL Discovery addresses this gap.
What is ITOM URL Discovery?
ITOM URL Discovery allows you to discover and model URLs as first-class entities within ServiceNow ITOM. Instead of relying only on IP-based scans, you can explicitly discover web endpoints and capture key insights about them.
This enables organizations to:
-
Track important URLs in the CMDB
-
Understand what technologies power them
-
Identify availability, security, and ownership gaps
-
Improve downstream ITOM use cases
Key use cases addressed
1. Discover business-critical web endpoints
Identify customer-facing portals, APIs, and application URLs that were previously unmanaged or undocumented.
2. Improve CMDB completeness
Model URLs as configuration items so they are visible, governed, and linked to services.
3. Understand technology exposure
Gain insights into the underlying technologies and configurations used by discovered URLs.
4. Reduce blind spots in monitoring and operations
Ensure critical web services are known and can be monitored, mapped, or assessed for risk.
5. Support modern, distributed architectures
Extend visibility to cloud-native, SaaS, and internet-facing services that don’t fit traditional discovery models.
Insights delivered by URL Discovery
URL Discovery doesn’t just identify endpoints — it brings meaningful insights that help teams take action.
Some of the insights include:
-
Technology fingerprints powering the endpoint
-
Domain and hosting-related metadata
- Certificate-related details (Future Roadmap)
These insights help teams answer key questions like:
-
Is this URL still active?
-
What category does it belong to eg: Dev productivity vs finance?
-
Is it externally exposed?
-
Who should own and govern it?
Prerequisites and availability
Before enabling ITOM URL Discovery, ensure the following prerequisites are met:
- ACC agents are deployed on endpoint devices
URL Discovery relies on endpoint-level visibility provided by the Agent Client Collector (ACC). - DEX Browser Extension is installed (DEX license not needed)
The browser extension enables collection of URL activity and insights from user interactions. - ITOM Advanced SKU
ITOM URL Discovery is available as part of the ITOM Advanced SKU.
How URL Discovery works
At a high level, ITOM URL Discovery follows a simple flow:
- Define URLs to discover
Admins specify URLs that should be discovered and tracked.
- Execute URL discovery probes
The system evaluates the URL and collects metadata and response details.
- Create or update URL configuration items
Discovered data is stored and normalized within the CMDB.
- Surface insights for visibility and action
Insights are made available for operations, analysis, and downstream ITOM use cases.
This approach allows teams to extend discovery beyond infrastructure and into the application experience layer.
Setting up ITOM URL Discovery
Setting up URL Discovery is designed to be straightforward and lightweight.
High-level setup typically includes:
-
Enabling the required ITOM capabilities
-
Defining the URLs to be discovered
-
Scheduling or triggering discovery runs
-
Reviewing discovered insights and CMDB entries
The setup is intentionally simple so teams can quickly start gaining visibility without complex prerequisites.
Why this matters for ITOM?
URL Discovery strengthens the ITOM data foundation by:
-
Expanding discovery coverage
-
Improving CMDB accuracy
-
Supporting modern application architectures
-
Reducing operational blind spots
When combined with other ITOM capabilities, URL Discovery helps teams build a more complete and accurate picture of how services are delivered and consumed.
Final thoughts
ITOM URL Discovery brings visibility where it was previously missing.
By discovering, modelling, and enriching URLs with meaningful insights, teams can better understand their digital footprint, govern web-facing services, and support modern operations.
If your environment includes customer-facing portals, SaaS services, or externally exposed endpoints, URL Discovery is a powerful step toward closing the visibility gap.
Have you started using ITOM URL Discovery yet?
Share how you’re using it — or what insights surprised you the most — in the comments below.
Links and Documentation:-
ITOM URL Discovery Store App link: https://store.servicenow.com/store/app/cfbfef8347c0cf10f43984f8736d4316
Product Documentation:
https://www.servicenow.com/docs/r/it-operations-management/agent-client-collector/collect-web-data-u...
https://www.servicenow.com/docs/r/it-operations-management/discovery/url-disco-insights.html