domainrating.org

Developers

API documentation

The domainrating.org API returns a domain’s Open Authority Rating, a free 0 to 100 authority score computed from the public Common Crawl web graph, as plain JSON. The score endpoint is free; score history needs any API key, and enrichment and top lists need a key on the paid tier. Machine-readable spec: /openapi.json.

Authentication and tiers

Create API keys on your account page (up to 2 active keys) and send them as Authorization: Bearer drk_…. New keys start on the free tier: 1,000 requests/hour, with score history for the latest 3 crawl releases (?include=history). The paid tier (10,000 requests/hour) extends history to 12 releases and unlocks ?include=enrichment and /api/v1/top. There is no self-serve checkout yet: an admin grants the paid tier by hand after payment is arranged out of band — contact us to upgrade. Self-serve billing will follow once payments are wired.

GET /api/v1/domains/<domain>

Free, no key needed. The domain’s current rating:

curl https://domainrating.org/api/v1/domains/wikipedia.org

{
  "domain": "wikipedia.org",
  "oar": 93,
  "dataSufficient": true,
  "hcRank": 47,
  "prRank": 128,
  "crawlRelease": "cc-main-2026-apr-may-jun",
  "lastComputedAt": "2026-07-07T04:12:00.000Z",
  "verified": false
}

With a paid key, ?include=enrichment embeds registration (RDAP), DNS, hosting (IP→ASN), TLS-certificate, and homepage facts. Each source carries its provenance, fetch date, and an honest status — ok, unavailable, error, or opted-out (the site’s robots.txt declined the homepage fetch). Facts we can’t prove are null, never estimated.

curl -H "Authorization: Bearer drk_…" \
  "https://domainrating.org/api/v1/domains/wikipedia.org?include=enrichment"

With any key, ?include=history adds the domain’s score in its latest crawl releases, oldest first: 3 releases on the free tier, 12 on the paid tier. A release where the domain had too little link data has "oar": null, never an estimate, and historyComplete is false when older releases exist beyond your tier’s limit. Combine both with ?include=enrichment,history.

curl -H "Authorization: Bearer drk_…" "https://domainrating.org/api/v1/domains/wikipedia.org?include=history"

{
  "domain": "wikipedia.org",
  "oar": 93,
  …
  "history": [
    { "crawlRelease": "cc-main-2025-oct-nov-dec", "oar": 92, "computedAt": "2026-01-14T05:20:00.000Z" },
    { "crawlRelease": "cc-main-2026-jan-feb-mar", "oar": 93, "computedAt": "2026-04-06T04:55:00.000Z" },
    { "crawlRelease": "cc-main-2026-apr-may-jun", "oar": 93, "computedAt": "2026-07-07T04:12:00.000Z" }
  ],
  "historyComplete": false
}

GET /api/v1/top

Paid tier. Prebuilt top lists per crawl release, ordered by harmonic-centrality rank (OAR’s primary input). list is global (top 10,000) or tld:<suffix> (top 1,000 per listed TLD, e.g. tld:com, tld:co.uk); page selects a prebuilt page of 100 rows.

curl -H "Authorization: Bearer drk_…" \
  "https://domainrating.org/api/v1/top?list=tld:nl&page=1"

Honesty, caching, and limits

  • Score responses are CDN-cached up to a day and refreshed with each crawl release; enrichment refreshes roughly monthly per domain.
  • The score endpoint never triggers a first-time scoring — an unknown domain is a 404. Visit its page on the site to score it.
  • Anonymous requests are limited per IP (120/hour on cache misses); keyed requests per key (1,000/hour free, 10,000/hour paid).