Appropriate geofeed URLs

At IPinfo, we spend a lot of time with IP WHOIS data and are used to seeing many weird and wonderful entries and strange edge cases for which we need to support. We recently came across something odd from the WHOIS records of of AS58172, which just points to a Google Map URL for their geofeed data.

The map points to a very specific geographic coordinate.

However, since we cannot extract the data from Google Maps automatically, we ended up doing a manual override for the geofeed record.

We find malformed geofeed URLs all the time; however, there are specific guidelines on the correct format to include the geofeed URLs in WHOIS records. According to RFC 9092, the recommended format for mentioning geofeed in the WHOIS record is as follows:

inetnum: # example

The geofeed URL points to a CSV file, which should have data in the following format (RFC 8805):,RU,RU-SPE,Saint Petersburg,,,CA,CA-ON,Toronto,,,AT,AT-9,Vienna,1060,,AT,AT-9,Vienna,1060,

With the columns representing:

  • IP address prefix
  • ISO 3166-1 alpha-2 country code
  • ISO 3166-2 region code
  • Name of the city
  • Postal Code or zip code

In this article, we have more details on setting up geofeed: Geofeed: what is it and how to set up a right one?

Sometimes, internet organizations submit Google Sheets, which is acceptable as long as the underlying data is valid CSV. For example: IP range details -

Links such as Pastebin, GitHub raw text, or GitHub gist files are also good:

As geofeed data can change, internet organizations should find convenient ways to keep their locations updated according to the guidelines. We will take care of the rest. Going beyond WHOIS records, internet organizations can also directly submit their geofeed directly to us through our corrections page.

However, directly pasting your geofeed CSV data as a geofeed value in the WHOIS records with a comment field is not something we can automatically ingest. We have to fix that manually. IP range details -

WHOIS records provide a standard, and machine-readable document, so unusual entries can be difficult to parse automatically. If you find any incorrect geofeed URLs, please feel free to share them with us! If you would like, you can fix these issues yourself by submitting corrections to us: Incorrect IP Geolocation data update -

1 Like

New standard? No, substandard. LMFAO

The RFCs still don’t feel really ready and the adaptations are even worse.

1 Like

Geofeed data is usually a fallback source when it comes to our geolocation data. We don’t mind fixing a few of these geofeeds manually.

1 Like

Yeah that’s also true, better rely on owner’s data than random third parties; it’s just that the standard has the chance to be ALOT better.

1 Like