Skip to content
Osint Daily
Osint Daily cover for RIPEstat, under Domain & infrastructure, published 16 Oct 2026. The right side is a monogram because no capture is filed. RIPE NCC's free IP and ASN lookup. Widgets did not.

01 · Product name

RIPEstat

RIPE NCC's free IP and ASN lookup. Widgets did not paint.

Published by RIPE NCC.

In short

RIPEstat is the RIPE NCC lookup at stat.ripe.net. On 22 Oct 2026 the homepage said it visualises IP address space and ASNs from over 35 datasets, and that the Data API is for non-commercial purposes. Article 3.3 of the terms says commercial use needs written permission from the RIPE NCC. No dollar price and no SPDX field were printed. Pages for owasp.org and 1.1.1.1 did not paint. Domain and infrastructure is the nearest category. RIPEstat is not a port scanner.

Product pricing strategy

02

Free

RIPEstat printed no dollar price on 22 Oct 2026. No SPDX field was printed on the homepage, the Data API article, or the terms. The homepage says the Data API may be used for non-commercial purposes. Article 3.3 says commercial use is not allowed unless the RIPE NCC grants written permission, requested via stat@ripe.net. Those are the price-related sentences. They are not a fee schedule. The 1000-requests-a-day line is a registration request, not a charge. The 8-concurrent-request line is a technical limit, not a charge. Over 35 datasets is the homepage's count of datasets. It is not a price. A written-permission commercial arrangement would be a later document. This review did not open one, and it does not invent a rate.

Utility and features

03

The homepage says RIPEstat is an information service for Internet-related data, with insights and visualisations on IP address space and Autonomous System Numbers from over 35 datasets. It says a developer may use the Data API for non-commercial purposes to create alerts, configurations, visualisations, or applications, and that the API is the public data interface for RIPEstat and the data source for the UI. The Data API article repeats that the API is the only data source for the widgets and the UI. The request URL pattern it prints is https://stat.ripe.net/data/<endpoint>/data.json. It says there is no limit on the amount of requests, and it asks you to register if you plan to do more than 1000 requests a day. It limits one IP address to 8 concurrent requests. It documents a sourceapp parameter and the mailbox stat@ripe.net.

  • Over 35 datasets. The homepage says RIPEstat visualises IP address space and ASNs from over 35 datasets.
  • 1000 requests and 8 concurrent. The API article asks regular users above 1000 requests a day to register, and it limits one IP to 8 concurrent requests.
  • Article 3.3 needs written permission. Commercial reuse of the service or the data is not allowed unless the RIPE NCC agrees in writing.

Article 3.3 of the RIPEstat service terms says a user may not re-package, compile, or re-distribute the service or the data. It says commercial use, including paid products based on the service or combining the data into a commercial product, is not allowed unless the RIPE NCC grants written permission. The contact for that request is stat@ripe.net. No dollar price was printed. The new UI's resource pages for owasp.org and 1.1.1.1 painted the navigation and a blank main area, about 179 characters of text, and are not described as lookup results. This listing did not confirm a GitHub repository for the service.

  1. 1

    Quote the homepage for non-commercial API use and article 3.3 for the written-permission rule.

  2. 2

    Register with stat@ripe.net when you expect more than 1000 requests a day. That line is the API article's.

  3. 3

    Do not describe a resource widget for owasp.org or 1.1.1.1 from this review. Those pages did not paint.

Caveats

04

The homepage's non-commercial sentence and article 3.3 are the same policy told twice, with the terms adding the written-permission path. Do not drop the permission sentence and call the homepage a blanket ban, and do not drop the homepage and call the terms a paid plan.

The resource UI did not paint for owasp.org or for 1.1.1.1. A blank main area is not a routing result, and this listing does not invent a prefix or an ASN from it. Domain and infrastructure is the nearest category. RIPEstat looks up address space and ASNs from the datasets it names. It is not a port scanner and it is not a geolocation product. The whois repository under RIPE-NCC is a different project and is not cited as RIPEstat. No license field was printed.

Potential use cases

06

  • Commercial use is about to be described as a plan with a price. On 22 Oct 2026 the homepage said the Data API may be used for non-commercial purposes. Article 3.3 says a user may not re-package or redistribute the service or the data, and that commercial use needs written permission from the RIPE NCC via stat@ripe.net. No dollar price and no SPDX field were printed.
  • A blank resource page is about to be briefed as a lookup. The pages for owasp.org and 1.1.1.1 painted the navigation and a blank main area. They are not prefix results. The homepage says the service visualises IP address space and ASNs from over 35 datasets. The API article says the API is the only data source for the widgets and the UI.
  • The request rule is about to be called a fee. The API article says there is no limit on the amount of requests, asks you to register above 1000 requests a day, and limits one IP address to 8 concurrent requests. Those are usage rules. Domain and infrastructure is the nearest category. RIPEstat is not a port scanner.

Hard cases

The case where the first result is easy to over-read.

A blank pane is given a prefix

The resource UI did not paint for owasp.org or 1.1.1.1. Inventing an announced prefix or an ASN from that blank area describes a page this review did not see. Cite the homepage and the API article, and say the resource widgets did not load.

Questions

Is RIPEstat free?

No dollar price and no SPDX field were printed on 22 Oct 2026. The homepage limits the Data API to non-commercial purposes. Article 3.3 says commercial use needs written permission from the RIPE NCC.

Did a resource lookup open in this review?

No. The pages for owasp.org and 1.1.1.1 showed the navigation and a blank main area. The homepage, the Data API article, and the terms did open.

Citations

07

Titled sources. These public pages are what the quotes on this listing come from.

When this listing changes, the letter says so.

Developments in OSINT. Confirm from your inbox before the first issue.

Only for this letter. Privacy

Related tools