URL Threat Scan: Understand and Use the Results
Combine host threat blocking with URL-pattern heuristics
URL threat triage: separating host reputation from suspicious link patterns
A Uniform Resource Locator (URL) identifies a resource using a scheme, host, path, and sometimes a query string. A link review can examine the host's reputation and the structure of the complete address. These are different observations: a host-level finding does not identify which page is harmful, and an unusual path does not prove that its content is malicious.
This distinction helps teams investigate reported messages and suspicious links without treating every detector as a verdict. Host reputation can change, newly created threats may have no feed coverage, and a legitimate service can contain a harmful page among otherwise ordinary content.
A useful review distinguishes:
Host-level evidence: whether a supported reputation source flags the destination host.
Address heuristics: suspicious syntax or patterns in the submitted URL.
Detection scope: whether an observation concerns the host, the full address, or neither.
Unavailable evidence: lookups that failed or could not establish a result.
The result helps answer why a link was flagged and what an analyst should inspect next. An address-pattern check is not a downloaded-file sandbox, a complete malware scan, or a guarantee that visiting the link is safe. An empty detection list means no supported signal was found during that check.
Preserve the submitted address and the reported reasons for investigation. Corroborate findings with appropriate security tools and incident context before making consequential decisions. Treat query strings carefully because a reported link can contain personal information or access tokens.
The URL Threat Scan endpoint, in plain language
Combine host threat blocking with URL-pattern pattern-matching rules
Add a bounded triage step for reported links, then investigate signals in context before blocking a shared host or trusting an unflagged URL (web address).
What is actually happening when you call it
Parses an HTTP (HyperText Transfer Protocol)(S) URL (web address) and evaluates patterns including embedded credentials, raw-IP hosts, suspicious paths, deep subdomains, URL shorteners and punycode. Combines these observations with a Quad9 host-level check and returns detections, pattern-matching rules and a threat level. match_scope is currently host for a Quad9 hit and none otherwise; the declared URL value is reserved. URL pattern-matching rules influence threat_level but do not set is_malicious. DNS (Domain Name System) failures can reduce available evidence.
Why this specific tool matters
Choose a task: Reported Link Triage. Inspect a reported link before investigating the destination.
Run the URL Threat Scan request below and retain the input and observed result. Before changing configuration, compare the relevant fields with the value or policy you expected. Use the URL Threat Scan reference to check the field definitions and supported options.
Available on the developer plan. The technical details: `GET /v1/url/scan`.
When would I actually use this?
Reported Link Triage
Inspect a reported link before investigating the destination.
Use the finding: Distinguish host blocking from URL-pattern observations.
Call this endpoint through REST
This is a REST-only GET endpoint and is not registered as a tool on the dedicated MCP server. Use its documented query parameters and the request example below. See the authentication guide for API-key setup.
The dedicated MCP server is available on every plan. Individual tool access and request limits depend on your plan. Management categories and endpoints disabled for the tool catalog are not exposed through MCP.
The technical way: call it from code
This URL Threat Scan request uses the example inputs from its API contract. Replace YOUR_API_KEY with a key on the developer plan or higher; adapt the target to your task.
curl --request GET 'https://api.edgedns.dev/v1/url/scan?url=https%3A%2F%2Fexample.com%2Fpath' \
--header "Authorization: Bearer YOUR_API_KEY"Prepare inputs for URL Threat Scan
Start with the inputs below. Keep the same hostname, path, and options when comparing URL Threat Scan observations. The API reference contains the complete parameter contract, optional settings, and access requirements.
| Field | Type | Required? | What it means | Example |
|---|---|---|---|---|
url | string | Yes | HTTP (HyperText Transfer Protocol)(S) URL (web address), up to 4096 characters; URL-encode it as a query value. | https://example.com/path |
Interpret URL Threat Scan findings
Read these fields alongside the full response from your URL Threat Scan check. A missing value or failed lookup is different from a passing result. Keep returned errors and confidence or cache metadata when available; do not replace missing evidence with a successful default. See the complete response reference for additional fields.
| Field | Type | What you'll see in it |
|---|---|---|
url | string | Queried URL (web address). |
host | string | Parsed hostname. |
is_malicious | boolean | True only when a Quad9 host detection is present; URL (web address) pattern-matching rules alone do not set this flag. False does not prove safety. |
Words you might be wondering about
DNS (Domain Name System) — The internet's address book. When you type a website name, DNS turns it into the actual numeric address computers use to find each other.
IP (Internet Protocol address) — A unique number that identifies a computer on the internet, like a phone number for a server.
URL (web address) — The full address of a page, like https://example.com/about.
HTTP (HyperText Transfer Protocol) — The language web browsers and websites use to talk to each other.
Need Programmatic Access?
Automate domain intelligence with 100+ API endpoints and a free MCP server for AI integration.