URLScan
URLScan is a comprehensive website scanning and analysis platform that provides detailed security intelligence, threat detection, and web infrastructure reconnaissance capabilities. It functions as an automated website scanner and threat intelligence service that captures, analyzes, and archives web pages to identify malicious content, phishing attempts, suspicious behavior, and security threats.
| Category | Threat intelligence |
| Direction | Query source |
| Sign-in | API Key |
| Query languages | SQLite |
| Tables | 16 |
| Query templates | 29 |
| Website | urlscan.io |
Before you start
Huntbase signs in to URLScan with API Key. Create the credential in URLScan first, then keep it to hand for the Connect step.
- Create a user account on urlscan.io through the sign-up page, then log in.
- Go to Settings & API and click New API key.
- Copy the new API key.
- Without an API key, requests are subject to the quotas for unauthenticated users.
For the vendor's own instructions, see urlscan.io quickstart guide.
Use a dedicated, read-only credential for Huntbase where the product allows it. Huntbase only needs to read.
Connect URLScan
- Go to Connections and click New connection, or click New connection on the URLScan product page.
- On Product, pick URLScan and choose the Owner.
- On Details, give the connection a Name and, optionally, a Description.
- On Connect, fill in the settings and credentials described below.
- On Verify, review the summary and click Create & check.
For everything else on the setup page — saving a draft, I'll do this later, and what each check result means — see Connections.
Credentials
The only Method is API Key. Enter a Credential label (for example Production), then fill in:
| Field | Required | Notes |
|---|---|---|
| API Key | Yes | Secret — not shown again after you save it. |
Query it
Once connected, URLScan can serve these languages in a query tab, and Scout can use it when you ask in Auto:
| Language | Use it for |
|---|---|
| SQLite | SQL over the 16 tables listed below, alongside every other connected source. |
Example: SQLite
List detected apps — Explore which applications have been detected by analyzing the results of a specific scan.
select
*
from
urlscan_app
where
scan = {{scan_id}};
URLScan ships with 29 query templates. Find them in Library › Queries — see Query templates.
Tables
URLScan adds 16 tables. Browse their columns from Schema in the query bar's ⋯ menu.
All 16 tables
| Table | Contains |
|---|---|
urlscan_app | Apps used by the page. |
urlscan_asn | Autonomous System Numbers (ASNs) used by requests during the scan. |
urlscan_certificate | Certificates returned by requests for the page. |
urlscan_console | Console messages returned while executing the page. |
urlscan_cookie | Cookies set by the page for the scan. |
urlscan_document_type | Document types returned for the page. |
urlscan_domain | Domains used by requests during the scan. |
urlscan_global | Global variables set in Javascript for the page. |
urlscan_ip | IPs used by requests during the scan. |
urlscan_link | Links in the HTML of the page. |
urlscan_protocol | Protocols used by requests during the scan. |
urlscan_request | Requests configured for the account. |
urlscan_search | |
urlscan_server | Servers used by requests during the scan. |
urlscan_task | Details of the task that ran the scan. |
urlscan_tls | Transport Layer Security (TLS) status for requests during the scan. |
Next steps
- Connections — health, credentials and settings after you connect
- Query languages — syntax, parameters and time ranges
- Chatting with Scout — ask questions without writing a query
- All integrations — the rest of the catalog