Security / file snapshot 2026-09-21
Imperva IP ranges
The Imperva file fetched on 2026-09-21 contained 11 distinct IPv4 prefix strings and 1 IPv6 prefix strings. Inspect the source URL, recorded fields and content hash below.
File measurement
11
IPv4 prefix strings
1
IPv6 prefix strings
298
bytes
JSON
file format
- Fetched at (UTC)
- SHA-256 of downloaded bytes
- ae399325cb61229dba4f65e86afbec50aaac9847aa9d90fb8a3796c6bf8671ad
Fields recorded from the file
These are literal field names and values. A timestamp or counter is shown without assigning an update schedule to it.
The parser recorded no publisher version or timestamp field for this file.
No selected facet values were collected by this measurement.
Reproduce the count
Save the linked source as provider-file, download the Python measurement script, then run:
python3 ip-ranges-measure.py provider-fileThe result includes counts, fields and a hash. A different hash means you measured different bytes. Counts retain overlapping prefixes and repeated address space under different prefix lengths. Full counting method.
ASN reference records
Holder names were read from RIPEstat on the dates below. These are separately selected reference records, not a mapping of every prefix to its origin ASN. A listed holder may differ from the provider named on this page.
| ASN | RIPEstat holder | Checked |
|---|---|---|
| AS19551 | INCAPSULA - Incapsula Inc | 2026-09-21 |
Interpreting this snapshot
Where is the Imperva IP range file?
The selected snapshot was downloaded from https://my.imperva.com/api/integration/v1/ips. The source and documentation links above let you inspect the publisher's current data and scope.
What does a matching prefix establish?
A match means an address falls inside a prefix in this selected file. The measurement does not establish the identity of a requester, a device location or ownership of every address. Check the publisher’s documentation before applying access rules.
How often is this file updated?
This record measures the file fetched at 2026-09-21T19:35:33.349726+00:00. Publisher fields are reproduced as recorded, without inferring a future update schedule. Download the current source and compare hashes to check for a change.