Just the evidence, as a file.
Not every question needs an analyst write-up. These are the underlying records as a spreadsheet you can work with, with a short summary of what they show. Each one is checked before you are charged, because an evidence file with nothing in it is worth nothing.
PTR Evidence Pack — Operator
Subject: An operator domain
You are checking whether an operator really runs the infrastructure they claim, and you want the underlying observations rather than someone's summary of them.
What is in it
- Observed hostnames, as recorded by our own reverse-DNS scan
- Parent domain for each hostname, and the concentration across parents
- Address grouping: which parts of their space the observations fall in
- Naming clusters and how densely the space is named
- PTR coverage as a share of their announced space
- Observation dates
You receive: XLSX and CSV evidence file, plus a short branded PDF summary.
When it is available
Offered only where we hold at least 1,000 observed PTRs for the operator. Around 10,400 operators qualify. Where we do not have enough, the order is refused before any charge.
Limitations
Observations are partial. Reverse DNS is evidence of naming, not of traffic, occupancy or legal ownership, and coverage of any operator's space is never complete.
See the deliverable first: Download sample · sample PDF summary · CSV (fictional company, for demonstration only)
PTR Evidence Pack — Network Range
Subject: A CIDR range you supply
You have a specific range in front of you and want to know what our scan observed inside it.
What is in it
- Every PTR record we observed inside the range you supplied
- Hostname and its parent domain
- Where in the range each observation falls
- Naming concentration across the range
- Observation dates
You receive: XLSX and CSV evidence file, plus a short branded PDF summary.
When it is available
The range is only the query boundary. Offered where we actually observed PTR records inside it; where we observed none, the order is refused before any charge.
Limitations
This is our own observation set for the addresses you asked about. It carries no third-party prefix attribution and no CAIDA-derived data. Partial by nature, and it establishes nothing about ownership or availability.
See the deliverable first: Download sample · sample PDF summary · CSV (fictional company, for demonstration only)
Corporate Ownership Map
Subject: An operator domain
You need to know who actually owns the company you are about to contract with, and who owns them.
What is in it
- Registered legal entity name and its identifier
- Jurisdiction of incorporation
- Entity status: active, lapsed or retired
- Direct parent company
- Ultimate parent at the top of the ownership chain
- Related entities in the same group, where a group exists
You receive: Short branded PDF.
When it is available
Offered on any operator we hold. Corporate records are checked before assembly; where there is genuinely no registered entity to map, you are told and refunded rather than sent an empty document.
Limitations
Built from published corporate registry data. Registry records lag real changes in control, and a consolidation relationship is an accounting fact rather than proof of operational control. Where no group relationship is found, the document says so plainly.
See the deliverable first: Download sample (fictional company, for demonstration only)
Need something different?
If you need evidence for a list of operators, a comparison across several, a different cut of the data, or a question none of these answer, ask. We will tell you what we can actually produce, and what we cannot, before anyone commits to anything.
Custom research or data requestLooking for analysis rather than data?
The exports above hand you the records. If you want them researched and interpreted, that is what the Operator Brief, Operator Deep Dossier and Network Evidence Report are for.