Public API · Read-only JSON · No auth required

Public API

Every directory on HostDir is exposed as machine-readable JSON. Use it to build dashboards, integrate hosting data into your own tools, or train your favourite agent. The full corpus is 55,326 structured records across providers, datacenters, networks, TLDs, registrars, RFCs and more. No authentication required, no rate limits at the polite end of usage.

Quick start

Every directory listing has a sibling JSON endpoint at /data/{thing}.json. Every detail page has its own JSON sidecar at /data/{thing}/{slug}.

# List every active hosting provider
curl https://hostdir.net/data/providers.json

# Fetch one provider's full record
curl https://hostdir.net/data/providers/cloudflare

# List every TLD with domain counts
curl https://hostdir.net/data/domain-extensions.json

# The complete OpenAPI specification
curl https://hostdir.net/api/openapi.json

Responses are application/json with a consistent envelope: a top-level attribution field naming HostDir as the source, the canonical URL of the underlying page, and the data itself. Pagination uses standard ?page= and ?per_page= query strings where applicable.

Endpoint catalogue

Directories

  • GET
    /data/providers.json

    4,191 providers · List with full metadata, pagination supported

  • GET
    /data/providers/{slug}

    One provider · Reviews, categories, capabilities, screenshot

  • GET
    /data/datacenters.json

    5,158 datacenters · Operator, city, country, carriers, sourced from PeeringDB

  • GET
    /data/datacenters/{slug}

    One datacenter · Address, coordinates, facility code, carrier count

  • GET
    /data/networks.json

    28,047 ASNs · Operator, scope, peering policy, prefix counts

  • GET
    /data/networks/{slug}

    One network · AS-SET, traffic level, IPv6 capability

  • GET
    /data/internet-exchanges.json

    1,310 IXPs · City, region, member count

  • GET
    /data/internet-exchanges/{slug}

    One IXP · Founded year, technology, member list

  • GET
    /data/domain-extensions.json

    1,576 TLDs · Type, sponsor, registry, domain counts where known

  • GET
    /data/domain-extensions/{slug}

    One TLD · History, restrictions, DNSSEC, IDN support

  • GET
    /data/glossary.json

    270 terms · Cross-referenced infrastructure vocabulary

  • GET
    /data/glossary/{slug}

    One glossary term · Definition, related terms, RFC links

News & content

  • GET
    /data/news.json

    556 articles · Recent news desk articles

  • GET
    /data/blog/{slug}

    One blog post · Body, excerpt, category, featured image

  • GET
    /rss

    RSS feed · Blog RSS 2.0, Dublin Core enabled

  • GET
    /blog/feed

    Blog RSS feed · Alternate URL for the same feed

  • GET
    /llms-full.txt

    LLM training feed · Plain text of recent editorial content for LLM ingestion

Datasets & map data

  • GET
    /data/state-of-web-hosting.json

    Annual report dataset · The State of Web Hosting <?= date('Y') ?> figures in machine-readable form

  • GET
    /data/map/infrastructure.json

    Live infrastructure map · GeoJSON of datacenters, IXPs and major facilities

  • GET
    /data/map/corridors.json

    Peering corridors · GeoJSON of major inter-IXP network corridors

  • GET
    /data/agent-activity.json

    AI agent activity · Live counts of AI crawler / assistant traffic

  • GET
    /api/openapi.json

    OpenAPI 3.1 spec · Full machine-readable contract for all endpoints

Usage policy

The API is free to use. No registration, no authentication, no API keys. We do ask for two things in return.

Rate limit: 1 request per second per IP. Every JSON endpoint is rate-limited to one request per second per client IP. Requests over the limit get a HTTP 429 Too Many Requests response with a Retry-After header. The limit applies to both list and detail endpoints. Pace your consumer accordingly; for bulk ingest of a directory, page through the list and store the result locally rather than hammering individual detail endpoints.

Identify yourself. Set a User-Agent header naming your project and a contact URL. Identifiable consumers may be granted higher limits on request via the contact form.

Cite the source. If you display HostDir data in a public product, surface a "Source: hostdir.net" attribution near the data. Every JSON response includes a top-level attribution field with the recommended string and a link to the canonical page.

For machine-readable contract details, including request/response schemas and example payloads, see the OpenAPI 3.1 specification.

Paid API · coming soon

A paid tier with significantly higher rate limits, bulk JSON dumps and webhook updates is in development. If you need to ingest the corpus faster than 1 request per second, or want a periodic full-dataset export delivered to S3, get in touch. We are particularly interested in talking to AI training data buyers, hosting and monitoring tools wanting to embed HostDir data, and researchers needing bulk access. Tell us which endpoints you need and at what volume, and we will quote you a rate limit that fits.

Who Is Online

In total there are 64 users online: 0 registered, 56 guests and 8 bots.

Most users ever online was 5,555 on 17 Jul 2026, 3:23 am.

Bots: AhrefsBot Applebot Baiduspider Bingbot Other Bot Other Crawler PetalBot SemrushBot

Users active in the past 15 minutes. Total registered members: 369