Package types (1.18.0)

Stay organized with collections Save and categorize content based on your preferences.

The ways in which threat entry sets can be compressed.

Describes an API diff request.

Request to send a potentially phishy URI to WebRisk.

The uncompressed threat entries in hash format. Hashes can be anywhere from 4 to 32 bytes in size. A large majority are 4 bytes, but some hashes are lengthened if they collide with the hash of a popular URI.

Used for sending ThreatEntryAdditons to clients that do not support compression, or when sending non-4-byte hashes to clients that do support compression.

A set of raw indices to remove from a local list.

The Rice-Golomb encoded data. Used for sending compressed 4-byte hashes or compressed removal indices.

Request to return full hashes matched by the provided hash prefixes.

Request to check URI entries against threatLists.

Wraps a URI that might be displaying malicious content.

Metadata for the Submit URI long-running operation.

Request to send a potentially malicious URI to WebRisk.

Details about how the threat was discovered.

Contains the set of entries to add to a local database. May contain a combination of compressed and raw data in a single response.

Contains the set of entries to remove from a local database.

Context about the submission including the type of abuse found on the URI and supporting details.

The type of threat. This maps directly to the threat list a threat may belong to.