package google.security.safebrowsing.v5
Get desktop application:
View/edit binary Protocol Buffers messages
The Safe Browsing APIs enable clients to check web resources (most commonly URLs) against Google's constantly updated lists of unsafe web resources.
Get multiple hash lists at once. It is very common for a client to need to get multiple hash lists. Using this method is preferred over using the regular Get method multiple times. This is a standard batch Get method as defined by https://google.aip.dev/231 and the HTTP method is also GET.
message
safebrowsing.proto:528The request to get multiple hash lists at the same time.
repeated string names = 1
Required. The names of the particular hash lists. The list MAY be a threat list, or it may be the Global Cache. The names MUST NOT contain duplicates; if they did, the client will get an error.
repeated bytes version = 2
The versions of the hash list that the client already has. If this is the first time the client is fetching the hash lists, the field should be left empty. Otherwise, the client should supply the versions previously received from the server. The client MUST NOT manipulate those bytes. The client need not send the versions in the same order as the corresponding list names. The client may send fewer or more versions in a request than there are names. However the client MUST NOT send multiple versions that correspond to the same name; if it did, the client will get an error. Historical note: in V4 of the API, this was called `states`; it is now renamed to `version` for clarity.
optional size_constraints = 4
The size constraints on each list. If omitted, there are no constraints. Note that the sizes here are per-list, not aggregated across all lists.
message
safebrowsing.proto:561The response containing multiple hash lists.
repeated hash_lists = 1
The hash lists in the same order given in the request.
rpc GetHashList (, )
safebrowsing.proto:52Get the latest contents of a hash list. A hash list may either by a threat list or a non-threat list such as the Global Cache. This is a standard Get method as defined by https://google.aip.dev/131 and the HTTP method is also GET.
message
safebrowsing.proto:265A request to obtain a hash list, which may be a threat list or a non-threat list such as the Global Cache. **What's new in V5**: What was previously called `states` in V4 is renamed to `version` for clarity. Lists are now named, platform types and threat entry types are removed. It is now possible for multiple lists to have the same threat type, or a single list concerned with multiple threat types. In contrast to V4's variable-length hash prefixes which has caused trouble in many client implementations: all hashes in a list now have a single length, permitting much more efficient client implementations. Constraints have been simplified, and compression type is removed (compression is always applied).
string name = 1
Required. The name of this particular hash list. It may be a threat list, or it may be the Global Cache.
bytes version = 2
The version of the hash list that the client already has. If this is the first time the client is fetching the hash list, this field MUST be left empty. Otherwise, the client SHOULD supply the version previously received from the server. The client MUST NOT manipulate those bytes. **What's new in V5**: in V4 of the API, this was called `states`; it is now renamed to `version` for clarity.
optional size_constraints = 4
The size constraints on the list. If omitted, there are no constraints. Constraints are recommended on all devices with limited processing power, bandwidth, or storage.
rpc ListHashLists (, )
safebrowsing.proto:67List hash lists. In the V5 API, Google will never remove a hash list that has ever been returned by this method. This enables clients to skip using this method and simply hard-code all hash lists they need. This is a standard List method as defined by https://google.aip.dev/132 and the HTTP method is GET.
message
safebrowsing.proto:567The request to list the available hash lists.
int32 page_size = 1
The maximum number of hash lists to return. The service may return fewer than this value. If unspecified, the server will choose a page size, which may be larger than the number of hash lists so that pagination is not necessary.
string page_token = 2
A page token, received from a previous `ListHashLists` call. Provide this to retrieve the subsequent page.
message
safebrowsing.proto:580The response containing metadata about hash lists.
repeated hash_lists = 1
The hash lists in an arbitrary order. Only metadata about the hash lists will be included, not the contents.
string next_page_token = 2
A token, which can be sent as `page_token` to retrieve the next page. If this field is omitted, there are no subsequent pages.
rpc SearchHashes (, )
safebrowsing.proto:41Search for full hashes matching the specified prefixes. This is a custom method as defined by https://google.aip.dev/136 (the custom method refers to this method having a custom name within Google's general API development nomenclature; it does not refer to using a custom HTTP method).
message
safebrowsing.proto:175A request that the client issues to search for specific hash prefixes. This is designed to only searches threat lists, and does not search non-threat lists such as the Global Cache. **What's new in V5**: Clients don't need to specify a `ClientInfo` or the states of the hash lists in their local database. This is for improved privacy. Furthermore, clients don't need to send which threat types they are interested in.
repeated bytes hash_prefixes = 1
Required. The hash prefixes to be looked up. Clients MUST NOT send more than 1000 hash prefixes. However, following the URL processing procedure, clients SHOULD NOT need to send more than 30 hash prefixes. Currently each hash prefix is required to be exactly 4 bytes long. This MAY be relaxed in the future.
message
safebrowsing.proto:196The response returned after searching threat hashes. If nothing is found, the server will return an OK status (HTTP status code 200) with the `full_hashes` field empty, rather than returning a NOT_FOUND status (HTTP status code 404). **What's new in V5**: There is a separation between `FullHash` and `FullHashDetail`. In the case when a hash represents a site having multiple threats (e.g. both MALWARE and SOCIAL_ENGINEERING), the full hash does not need to be sent twice as in V4. Furthermore, the cache duration has been simplified into a single `cache_duration` field.
repeated full_hashes = 1
Unordered list. The unordered list of full hashes found.
optional cache_duration = 2
The client-side cache duration. The client MUST add this duration to the current time to determine the expiration time. The expiration time then applies to every hash prefix queried by the client in the request, regardless of how many full hashes are returned in the response. Even if the server returns no full hashes for a particular hash prefix, this fact MUST also be cached by the client. If and only if the field `full_hashes` is empty, the client MAY increase the `cache_duration` to determine a new expiration that is later than that specified by the server. In any case, the increased cache duration must not be longer than 24 hours. Important: the client MUST NOT assume that the server will return the same cache duration for all responses. The server MAY choose different cache durations for different responses depending on the situation.
message
safebrowsing.proto:220The full hash identified with one or more matches.
Used in:
bytes full_hash = 1
The matching full hash. This is the SHA256 hash. The length will be exactly 32 bytes.
repeated full_hash_details = 2
Unordered list. A repeated field identifying the details relevant to this full hash.
message
safebrowsing.proto:234Details about a matching full hash. An important note about forward compatibility: new threat types and threat attributes may be added by the server at any time; those additions are considered minor version changes. It is Google's policy not to expose minor version numbers in APIs (see https://cloud.google.com/apis/design/versioning for the versioning policy), so clients MUST be prepared to receive `FullHashDetail` messages containing `ThreatType` enum values or `ThreatAttribute` enum values that are considered invalid by the client. Therefore, it is the client's responsibility to check for the validity of all `ThreatType` and `ThreatAttribute` enum values; if any value is considered invalid, the client MUST disregard the entire `FullHashDetail` message.
Used in:
ThreatType threat_type = 1
The type of threat. This field will never be empty.
repeated ThreatAttribute attributes = 2
Unordered list. Additional attributes about those full hashes. This may be empty.
message
safebrowsing.proto:461A list of hashes identified by its name.
Used as response type in: SafeBrowsing.GetHashList
Used as field type in: ,
oneof compressed_additions
The Rice-delta encoded version of additions. The hash prefix lengths of additions are uniform across all additions in the list.
additions_four_bytes = 4
The 4-byte additions.
additions_eight_bytes = 9
The 8-byte additions.
additions_sixteen_bytes = 10
The 16-byte additions.
additions_thirty_two_bytes = 11
The 32-byte additions.
string name = 1
The name of the hash list. Note that the Global Cache is also just a hash list and can be referred to here.
bytes version = 2
The version of the hash list. The client MUST NOT manipulate those bytes.
bool partial_update = 3
When true, this is a partial diff containing additions and removals based on what the client already has. When false, this is the complete hash list. When false, the client MUST delete any locally stored version for this hash list. This means that either the version possessed by the client is seriously out-of-date or the client data is believed to be corrupt. The `compressed_removals` field will be empty. When true, the client MUST apply an incremental update by applying removals and then additions.
optional compressed_removals = 5
The Rice-delta encoded version of removal indices. Since each hash list definitely has less than 2^32 entries, the indices are treated as 32-bit integers and encoded.
optional minimum_wait_duration = 6
Clients should wait at least this long to get the hash list again. If omitted or zero, clients SHOULD fetch immediately because it indicates that the server has an additional update to be sent to the client, but could not due to the client-specified constraints.
bytes sha256_checksum = 7
The sorted list of all hashes, hashed again with SHA256. This is the checksum for the sorted list of all hashes present in the database after applying the provided update. In the case that no updates were provided, the server will omit this field to indicate that the client should use the existing checksum.
optional metadata = 8
Metadata about the hash list. This is not populated by the `GetHashList` method, but this is populated by the `ListHashLists` method.
message
safebrowsing.proto:416Metadata about a particular hash list.
Used in:
repeated ThreatType threat_types = 1
Unordered list. If not empty, this specifies that the hash list is a kind of threat list, and this enumerates the kind of threats associated with hashes or hash prefixes in this hash list. May be empty if the entry does not represent a threat, i.e. in the case that it represents a likely safe type.
repeated LikelySafeType likely_safe_types = 2
Unordered list. If not empty, this specifies that the hash list represents a list of likely safe hashes, and this enumerates the ways they are considered likely safe. This field is mutually exclusive with the threat_types field.
string description = 4
A human-readable description about this list. Written in English.
HashListMetadata.HashLength hash_length = 6
The supported hash length for this hash list. Each hash list will support exactly one length. If a different hash length is introduced for the same set of threat types or safe types, it will be introduced as a separate list with a distinct name and respective hash length set.
The length of hashes in a hash list.
Used in:
HASH_LENGTH_UNSPECIFIED = 0
Unspecified length.
FOUR_BYTES = 2
Each hash is a four-byte prefix.
EIGHT_BYTES = 3
Each hash is an eight-byte prefix.
SIXTEEN_BYTES = 4
Each hash is a sixteen-byte prefix.
THIRTY_TWO_BYTES = 5
Each hash is a thirty-two-byte full hash.
Types of likely-safe sites. Note that the `SearchHashesResponse` intentionally does not contain `LikelySafeType`.
Used in:
LIKELY_SAFE_TYPE_UNSPECIFIED = 0
Unknown.
GENERAL_BROWSING = 1
This site is likely safe enough for general browsing. This is also known as the global cache.
CSD = 2
This site is likely safe enough that there is no need to run Client-Side Detection models or password protection checks.
DOWNLOAD = 3
This site is likely safe enough that downloads from the site need not be checked.
message
safebrowsing.proto:362Same as `RiceDeltaEncoded32Bit` except this encodes 128-bit numbers.
Used in:
uint64 first_value_hi = 1
The upper 64 bits of the first entry in the encoded data (hashes). If the field is empty, the upper 64 bits are all zero.
fixed64 first_value_lo = 2
The lower 64 bits of the first entry in the encoded data (hashes). If the field is empty, the lower 64 bits are all zero.
int32 rice_parameter = 3
The Golomb-Rice parameter. This parameter is guaranteed to be between 99 and 126, inclusive.
int32 entries_count = 4
The number of entries that are delta encoded in the encoded data. If only a single integer was encoded, this will be zero and the single value will be stored in `first_value`.
bytes encoded_data = 5
The encoded deltas that are encoded using the Golomb-Rice coder.
message
safebrowsing.proto:385Same as `RiceDeltaEncoded32Bit` except this encodes 256-bit numbers.
Used in:
uint64 first_value_first_part = 1
The first 64 bits of the first entry in the encoded data (hashes). If the field is empty, the first 64 bits are all zero.
fixed64 first_value_second_part = 2
The 65 through 128th bits of the first entry in the encoded data (hashes). If the field is empty, the 65 through 128th bits are all zero.
fixed64 first_value_third_part = 3
The 129 through 192th bits of the first entry in the encoded data (hashes). If the field is empty, the 129 through 192th bits are all zero.
fixed64 first_value_fourth_part = 4
The last 64 bits of the first entry in the encoded data (hashes). If the field is empty, the last 64 bits are all zero.
int32 rice_parameter = 5
The Golomb-Rice parameter. This parameter is guaranteed to be between 227 and 254, inclusive.
int32 entries_count = 6
The number of entries that are delta encoded in the encoded data. If only a single integer was encoded, this will be zero and the single value will be stored in `first_value`.
bytes encoded_data = 7
The encoded deltas that are encoded using the Golomb-Rice coder.
message
safebrowsing.proto:322The Rice-Golomb encoded data. Used for either hashes or removal indices. It is guaranteed that every hash or index here has the same length, and this length is exactly 32 bits. Generally speaking, if we sort all the entries lexicographically, we will find that the higher order bits tend not to change as frequently as lower order bits. This means that if we also take the adjacent difference between entries, the higher order bits have a high probability of being zero. This exploits this high probability of zero by essentially choosing a certain number of bits; all bits more significant than this are likely to be zero so we use unary encoding. See the `rice_parameter` field. Historical note: the Rice-delta encoding was first used in V4 of this API. In V5, two significant improvements were made: firstly, the Rice-delta encoding is now available with hash prefixes longer than 4 bytes; secondly, the encoded data are now treated as big-endian so as to avoid a costly sorting step.
Used in:
uint32 first_value = 1
The first entry in the encoded data (hashes or indices), or, if only a single hash prefix or index was encoded, that entry's value. If the field is empty, the entry is zero.
int32 rice_parameter = 2
The Golomb-Rice parameter. This parameter is guaranteed to be between 3 and 30, inclusive.
int32 entries_count = 3
The number of entries that are delta encoded in the encoded data. If only a single integer was encoded, this will be zero and the single value will be stored in `first_value`.
bytes encoded_data = 4
The encoded deltas that are encoded using the Golomb-Rice coder.
message
safebrowsing.proto:342Same as `RiceDeltaEncoded32Bit` except this encodes 64-bit numbers.
Used in:
uint64 first_value = 1
The first entry in the encoded data (hashes), or, if only a single hash prefix was encoded, that entry's value. If the field is empty, the entry is zero.
int32 rice_parameter = 2
The Golomb-Rice parameter. This parameter is guaranteed to be between 35 and 62, inclusive.
int32 entries_count = 3
The number of entries that are delta encoded in the encoded data. If only a single integer was encoded, this will be zero and the single value will be stored in `first_value`.
bytes encoded_data = 4
The encoded deltas that are encoded using the Golomb-Rice coder.
message
safebrowsing.proto:291The constraints on the sizes of the hash lists.
Used in: ,
int32 max_update_entries = 1
The maximum size in number of entries. The update will not contain more entries than this value, but it is possible that the update will contain fewer entries than this value. This MUST be at least 1024. If omitted or zero, no update size limit is set.
int32 max_database_entries = 2
Sets the maximum number of entries that the client is willing to have in the local database for the list. (The server MAY cause the client to store less than this number of entries.) If omitted or zero, no database size limit is set.
Attributes of threats. These attributes may confer additional meaning to a particular threat but will not affect the threat type. For example, an attribute may specify a lower confidence while a different attribute may specify higher confidence. More attributes may be added in the future.
Used in:
THREAT_ATTRIBUTE_UNSPECIFIED = 0
Unknown attribute. If this is returned by the server, the client shall disregard the enclosing `FullHashDetail` altogether.
CANARY = 1
Indicates that the threat_type should not be used for enforcement.
FRAME_ONLY = 2
Indicates that the threat_type should only be used for enforcement on frames.
Types of threats.
Used in: ,
THREAT_TYPE_UNSPECIFIED = 0
Unknown threat type. If this is returned by the server, the client shall disregard the enclosing `FullHashDetail` altogether.
MALWARE = 1
Malware threat type. Malware is any software or mobile application specifically designed to harm a computer, a mobile device, the software it's running, or its users. Malware exhibits malicious behavior that can include installing software without user consent and installing harmful software such as viruses. More information can be found [here](https://developers.google.com/search/docs/monitor-debug/security/malware).
SOCIAL_ENGINEERING = 2
Social engineering threat type. Social engineering pages falsely purport to act on behalf of a third party with the intention of confusing viewers into performing an action with which the viewer would only trust a true agent of that third party. Phishing is a type of social engineering that tricks the viewer into performing the specific action of providing information, such as login credentials. More information can be found [here](https://developers.google.com/search/docs/monitor-debug/security/social-engineering).
UNWANTED_SOFTWARE = 3
Unwanted software threat type. Unwanted software is any software that does not adhere to [Google's Software Principles](https://www.google.com/about/software-principles.html) but isn't malware.
POTENTIALLY_HARMFUL_APPLICATION = 4
Potentially harmful application threat type [as used by Google Play Protect for the Play Store](https://developers.google.com/android/play-protect/potentially-harmful-applications).