Geofeed Observatory
Public geofeed diagnostics

Find the gaps in your geofeeds.

Explore reference errors, download failures, and WHOIS inconsistencies.
Search your IP space or geofeed URL to see the reported findings.

Observation date: Not supplied  ·  Static snapshot · IPv4 & IPv6
Geofeed URLs with findings—Distinct URLs across both datasets
Reference / retrieval records—WHOIS resources with reported issues
Coverage records—Geofeed entries with WHOIS inconsistencies
Distinct reported prefixes—Across both datasets · may overlap

Understand the scope. These are findings from supplied bulk WHOIS and geofeed analyses, not live checks. Missing references and mismatched references describe the analyzed snapshot; they do not establish unauthorized use or incorrect geolocation.

Geofeed details

Reported findings

About this snapshot

What you are looking at

The dashboard combines two error-only CSV exports: WHOIS geofeed reference / retrieval findings, and comparisons between entries in downloaded geofeeds and their covering inetnum objects in bulk WHOIS. There are no live WHOIS, DNS, or geofeed requests.

The reported prefix in the first dataset identifies the WHOIS resource. In the second dataset it identifies the entry inside a downloaded geofeed. A URL is matched exactly between datasets: HTTP and HTTPS URLs, trailing slashes, and malformed URLs remain distinct.

No finding is not a clean bill of health. These files do not provide the full set of tested resources, successful checks, or a denominator for success rates. The observation date is not inferred from upload time.

Error definitions

Search behavior

IP searches compare the reported prefix in each row. Overlapping finds any intersection; covering finds rows that contain the query; within finds rows contained by the query. An address is treated as /32 or /128. Queries with host bits are normalized to their network. The covering inetnum prefix displayed for a mismatch is context, not an additional search target.

URL and hostname searches are case-insensitive substring matches. Summary cards always describe the entire snapshot; results and exports follow the active filters. Geofeed counts in the results describe matching records. Detail pages show all records for the selected URL.

Updating and hosting

Host this HTML file on any static web server. No build system, external libraries, API, or database is needed. To publish new data, choose Update snapshot, select both replacement CSVs, optionally enter their observation date, then download the updated HTML and replace the hosted file. Loading files changes only your local browser view.

CSV files must have three fields per row, with no header or the header prefix,url,errors (or prefix,geofeed url,error). In the feed-error CSV, multiple errors are comma-separated inside a quoted third field. Coverage errors use no_whois or other_owner: prefix. Unknown error codes are preserved.

Filtered CSV exports include a header and separate fields for source, reported prefix, URL, error codes, and covering inetnum prefix. Spreadsheet formula-like cells are prefixed with an apostrophe for safer viewing.

Update the snapshot

Select the two CSV exports from the same analysis run. Files are processed entirely in this browser. Your published page is only updated when you upload the downloaded HTML to your server.