Web Data

XML sitemap audit API

Discover a website sitemaps and audit up to 10 files per request. Get URL counts, sitemap index structure, lastmod freshness, image, video, news and hreflang extensions, and protocol issues.

View documentation Try the free tool Explore all APIs

Endpoints Active

GET /v1/sitemaps

Example request

curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/sitemaps?url=example.com"

Example response 200 OK

{
  "status": "found",
  "robots_txt": { "status": "found", "declared_sitemaps": ["https://example.com/sitemap.xml"] },
  "sitemaps": [
    {
      "url": "https://example.com/sitemap.xml",
      "source": "robots",
      "status": "ok",
      "type": "urlset",
      "url_count": 1240,
      "lastmod": {
        "newest": "2026-10-01T00:00:00.000Z",
...

Example request GET /v1/sitemaps

Key Features 4

Frequently asked questions 4

HTTP status codes 200 / 400 / 401 / 402 / 429 / 502

Category Web Data

Endpoints 1

Key Features 4

Frequently asked questions 4

Used by people at these companies

Trust signals before you integrate

Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.

Live Service status

Check live service health and documented failure responses before you integrate.

OpenAPI API artifacts

OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.

API keys Protected access

Authenticated endpoints use API keys with clear credit costs before you call them.

10,000 Free allowance

Start with 10,000 monthly credits and upgrade only when usage grows.

What this API helps you ship

Use this page as a production brief: endpoints, examples, response shape, and the workflow pieces needed to plug DomScan into your own product.

Product workflows

Embed domain checks, DNS intelligence, risk signals, or enrichment into onboarding, search, and internal tools.

Analyst automation

Replace repeated manual lookups with scheduled jobs, alerting, and reproducible investigation steps.

Clean JSON data

Use predictable fields, documented status codes, and credit costs instead of scraping provider pages.

AI and ops tooling

Feed agents, dashboards, SOAR playbooks, and CRMs through OpenAPI, SDK, Postman, or MCP.

Integration workflow

A simple path from first request to repeatable production usage.

Authenticate once

Send your API key with the documented header and keep requests consistent across services.

Query with examples

Start from the curl and HTTP samples, then map the parameters into your application code.

Operate and monitor

Use status codes, credit costs, and response fields to build retries, logs, and alerts.

Developer kit

Jump from this page into machine-readable docs, request collections, SDKs, or agent tooling.

OpenAPI schema

Generate clients or inspect every request and response shape.

Postman collection

Import ready-made requests for manual testing and team handoff.

SDKs and CLI

Use maintained packages and command-line workflows instead of writing boilerplate.

MCP integration

Expose domain intelligence to AI agents and internal assistant workflows.

Parameters and response map

Scan the inputs, output fields, and status codes before wiring the endpoint into your client.

Request parameters

Parameter

urldomainsitemapmax_sitemaps

Response fields

Example response

statusrobots_txtrobots_txt.statusrobots_txt.declared_sitemapssitemapstotalstotals.sitemaps_checkedtotals.urls_countedtotals.budget_exhausted

Status coverage

HTTP status codes

200400401402429502

Endpoints

GET /v1/sitemaps

Credits: 2Authentication: Authentication required

Trust signals before you integrate

Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.

Service status API artifacts

OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.

API keys Protected access

Authenticated endpoints use API keys with clear credit costs before you call them.

Free allowance Sign up for free

Start with 10,000 monthly credits and upgrade only when usage grows.

Active Example request

Start from the curl and HTTP samples, then map the parameters into your application code.

Key Features

Discovery from robots.txt

Same-site Sitemap lines are followed first. Cross-site declarations are listed but not fetched, and standard paths are tried when none are declared.

Bounded crawling

Sitemap indexes are followed breadth-first within a fixed file budget, and every file left out is listed as skipped.

Freshness signals

Newest and oldest lastmod per file, the share of entries with a lastmod, and days since the newest update across the site.

Protocol issues

Entry and size limits, invalid or overlong locations, cross-host and duplicate URLs, invalid or future dates and HTML served instead of XML.

Example request

GET /v1/sitemaps?url=example.com bash

curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/sitemaps?url=example.com"

Example response

200 OK json

{
  "status": "found",
  "robots_txt": { "status": "found", "declared_sitemaps": ["https://example.com/sitemap.xml"] },
  "sitemaps": [
    {
      "url": "https://example.com/sitemap.xml",
      "source": "robots",
      "status": "ok",
      "type": "urlset",
      "url_count": 1240,
      "lastmod": {
        "newest": "2026-10-01T00:00:00.000Z",
        "oldest": "2025-03-12T00:00:00.000Z",
        "with_lastmod_ratio": 0.98
      },
      "issues": []
    }
  ],
  "totals": { "sitemaps_checked": 1, "urls_counted": 1240, "budget_exhausted": false }
}

Frequently asked questions

Can I audit one specific sitemap?

Yes. Pass sitemap with a URL on the same site to audit that file and its index children without reading robots.txt.

Are the URL counts complete?

They cover the files fetched within the budget. The response says when the budget ran out, so you can raise max_sitemaps up to 10.

What does not_found mean?

Every candidate location returned an exact 404 or 410 and robots.txt declared no sitemap. Blocked or failed fetches return unknown instead.

How many credits does it cost?

Two credits per request, because one audit can read several files. Requests that end in an unknown state are refunded.

Related tools and resources

HTTP status codes

These are the HTTP status codes to handle, so you can tell apart successful responses, auth issues, credits, rate limits, missing data, and upstream failures.

OK 200

Request successful

Bad Request 400

Invalid parameters

Unauthorized 401

Missing or invalid API key/session.

Payment Required 402

Not enough credits to run this request.

Too Many Requests 429

Rate limit exceeded

Bad Gateway 502

Upstream RDAP error

Audit a sitemap

Start free View documentation Try the free tool