Skip to content
Last updated

Our Incidents feature within urlscan Observe allows you to continuously monitor specific observables and receive updates when changes occur. Incidents can be customized with options such as perpetual monitoring, custom scan intervals, stop conditions, scanner locations, and user-agents. This page provides a reference for the available fields and parameters used to create and manage Incidents via the API.

Searchable Fields

The following fields can only be searched on the Professional, Enterprise, and Ultimate plans.

Field NameTypeField semantics, features, & notes
allTagskeywordTags from all observation periods
asnkeywordThe ASN number of the last observed IP
asnnametextThe ASN description of the last observed IP
asnname.keywordkeywordThe ASN description of the last observed IP (analyzed as keyword)
cnamedomainLast observed CNAME records
countrieskeywordScan location list
countriesPerIntervalintegerNumer of countries incident scan was observed from per interval
createdAtdateDatetime of when the incident was created
domaindomainContains the registered (apex) domain, indexed as individual levels of subdomains. Wildcard / Regular Expression supported
expireAtdateDatetime for when the incident is due to expire
hostnamedomainThe full hostname. Wildcard / Regular Expression supported
incidentProfilekeywordThe ID of the incident profile used to create the incident
ipipLast observed IPv4/IPv6 values for A/AAAA records
mxdomainLast observed MX records
nameserverdomainLast observed NS records
observablekeywordThe observable of the incident
scanIntervalintegerInterval between triggering full website scan (in seconds)
scanIntervalAfterMaliciousintegerThe scan interval of the incident after the hostname/domain/URL was detected as malicious (in seconds)
scanIntervalAfterSuspendedintegerThe scan interval of the incident after the site was suspended or taken down (in seconds)
scanIntervalModekeywordThe scan mode type
sourceIdkeywordID of the trigger source
sourceTypekeywordIncident source type
statekeywordCurrent incident state, can be active or closed
stateCountintegerHow many intervals we have stored for the incident
stateSizeintegerThe size of the state internally
stopDelayInactiveintegerControl for when the incident is automatically closed
stopDelayMaliciousintegerControl for when the incident is automatically closed
stopDelaySuspendedintegerControl for when the incident is automatically closed
tagskeywordTags from the latest observation period
tlddomainThe top level domain of the observable
typekeywordThe type of observable: hostname, ip, or url
uniqueIdkeywordUnique ID for the incident
uniqueIPsintegerCount of unique IPs observed in the incident
updatedAtdateDatetime of when the incident was updated
userAgentsPerIntervalintegerCount of user agents per scan interval
verdictkeywordIncident malicious or benign verdict
visibilitykeywordIncident visibility private or unlisted