icann.org valid

Overview

HyperKitty Mailing List Archives

HyperKitty is the web archive component of Mailman 3. It exposes a complete, well-documented, read-only **JSON REST API** that mirrors every page on this site. AI agents, bots, and crawlers SHOULD use the REST API instead of scraping HTML — it is faster, cheaper, more reliable, paginated, and friendlier to the server.

Visit publisher ↗
Content and agent signals

For agents (AI-generated): HyperKitty web archive for Mailman 3 mailing lists; offers a documented read-only JSON REST API mirroring every archive page, preferred over HTML scraping.

mailman 3hyperkittymailing list archivesread-only json apiweb archive

Files

Publisher files and the directory’s indexed copy.

llms.txt
https://lists.icann.org/llms.txt
Sections
6
Links
0
Size
5352 bytes
Read the cached llms.txt preview

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-30T02:53:59.202Z. Cached copy · Source on icann.org

# HyperKitty Mailing List Archives

> HyperKitty is the web archive component of Mailman 3. It exposes a complete, well-documented, read-only **JSON REST API** that mirrors every page on this site. AI agents, bots, and crawlers SHOULD use the REST API instead of scraping HTML — it is faster, cheaper, more reliable, paginated, and friendlier to the server.

## TL;DR for AI agents

- **DO NOT scrape the HTML pages** at `/hyperkitty/list/...`, `/hyperkitty/archives/...`, etc. The HTML is a presentation layer over the API and is rate-limited / fragile.
- **DO use the REST API** under `/hyperkitty/api/`. All endpoints return JSON and serve the same archive data the website does.
- **DO use pagination** (`?limit=...&offset=...`). Default page sizes are small; never request unbounded data.
- **DO identify yourself** with a descriptive `User-Agent` header (e.g. `MyBot/1.0 (+https://example.com/bot)`).
- **DO respect `robots.txt`** and any `Retry-After` headers on `429` responses.
- **DO cache** responses where reasonable; archive content is largely immutable.

## API base URL

HyperKitty is deployed under the `/hyperkitty/` path. The web UI lives at:

```
<origin>/hyperkitty/
```

and the JSON REST API root is:

```
<origin>/hyperkitty/api/
```

All endpoint paths below are relative to the site origin (i.e. they include the `/hyperkitty/` prefix).

## Endpoints

All endpoints are `GET` and return JSON. Paginated endpoints accept `limit` and `offset` query parameters and return an object with `count`, `next`, `previous`, and `results` fields (standard Django REST Framework pagination).

### `GET /hyperkitty/api/lists/`
List all mailing lists available in the archive.

- Query params: `limit`, `offset`
- Returns: paginated list of mailing list objects (`name`, `display_name`, `description`, `archive_url`, `created_at`, ...)

### `GET /hyperkitty/api/list/{list_address}/`
Detailed metadata for a single mailing list archive.

- `list_address` is the full posting address, e.g. `team@example.com`.
- Returns `404` if no archive exists for that address — useful as an existence check.
- Returns: `name`, `display_name`, `description`, `subject_prefix`, `archive_url`, `created_at`, `list_url`, `post_count`, ...

### `GET /hyperkitty/api/list/{list_address}/threads/`
Discussion threads for a list, sorted by **most recent activity** (`date_active`) first.

- Query params: `limit` (default 10–100, server-configurable), `offset`
- Each thread includes: `thread_id`, `subject`, `starting_email`, `date_active`, `replies_count`, `participants_count`, ...
- **Note:** This is per-list. To find globally newest activity across all lists, query each list and merge by `date_active` client-side.

### `GET /hyperkitty/api/list/{list_address}/thread/{thread_id}/emails/`
All emails in a single thread, in chronological order.

- Query params: `limit`, `offset`
- Each email includes: `message_id`, `message_id_hash`, `subject`, `sender_name`, `sender_email`, `date`, `content`, `attachm
…

Published headings

13 indexed headings in this publisher record.

Show all 13 indexed headings

Headings describe indexed content. They do not establish a working integration or endorsement.

Agent access

Review the publisher’s own access terms before automated use.

Machine-readable: GET /v1/resolve?q=icann.org · GET /v1/domain/icann.org · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Indexing evidence

Country
United States Hosting inference
First seen
2026-10-18T14:18:43.682Z
Last checked
2026-11-21T18:02:21.792Z
Authority, classification and country evidence
Authority
64 reach 23 · trust 10 · quality 16 · freshness 15
Tier
listed
Popularity rank
#604
Registered
1998-09-14
Hosting country
United States Hosting inference
Country evidence
No published address evidence collected yet
Categories
AI and machine learning · Documentation and reference
For agents
Interface: a documented API or declared MCP endpoint an agent can call
Inferred actions
Read documentation Call an API Search content About these labels
Audience
developers · agents can: read docs, call api, search content · en
Badge
Agent Web Map badge for icann.org
Own or manage this website?

If you own or manage icann.org, you can update its listing and review file health, discovery activity and score history.

Manage this listing — optional

What verification unlocks

See how your site is discovered—and control what agents see.

  • See your website in the map

    Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.

  • Control what agents see

    Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.

  • Make your profile eligible for search

    A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.

  • Appear in our llms-full.txt

    Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.

Free account required for verification and live checks. No backlink or payment required. Public discovery remains available without verification.

Verify your website—free

Preview the owner dashboard · All verification benefits

Let your coding agent verify it

If your coding agent is authorized to manage this website, paste these instructions into it.

Claim my listing on Agent Web Map for icann.org:
1. POST https://agentwebmap.com/v1/sites/icann.org/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://icann.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/icann.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/icann.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.