Security & Trust

security.txt API

Check whether a domain publishes a valid security.txt with one request. Get the parsed fields, days until expiry, signature presence and machine-coded errors and warnings.

View documentation Try the free tool Explore all APIs

Endpoints Active

GET /v1/security-txt

Example request

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

Example response 200 OK

{
  "domain": "example.com",
  "status": "valid",
  "location": "well_known",
  "fields": {
    "contact": ["mailto:[email protected]"],
    "expires": "2027-01-01T00:00:00.000Z",
    "expires_in_days": 83,
    "policy": ["https://example.com/security-policy"]
  },
  "signed": false,
  "issues": []
}

Example request GET /v1/security-txt

Key Features 4

Frequently asked questions 4

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

Category Security & Trust

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

domainurl

Response fields

Example response

domainstatuslocationfieldsfields.contactfields.expiresfields.expires_in_daysfields.policysignedissues

Status coverage

HTTP status codes

200400401402429502

Endpoints

GET /v1/security-txt

Credits: 1Authentication: 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

RFC 9116 validation

Required Contact and Expires fields, URI formats, HTTPS links, Preferred-Languages and Canonical are checked, with errors and warnings kept apart.

Location handling

Reads /.well-known/security.txt first and the legacy /security.txt only after a 404 or 410.

Expiry monitoring

Returns the expiry date and the days remaining, so you can alert before a disclosure policy lapses.

Four clear statuses

valid, invalid, not_found and unknown. Blocked or failed fetches are never reported as a missing file.

Example request

GET /v1/security-txt?domain=example.com bash

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

Example response

200 OK json

{
  "domain": "example.com",
  "status": "valid",
  "location": "well_known",
  "fields": {
    "contact": ["mailto:[email protected]"],
    "expires": "2027-01-01T00:00:00.000Z",
    "expires_in_days": 83,
    "policy": ["https://example.com/security-policy"]
  },
  "signed": false,
  "issues": []
}

Frequently asked questions

What makes a file invalid?

A missing Contact or Expires field, several Expires fields, an expired date, invalid contact URIs, plain http links or an HTML page served instead of text.

Are signatures verified?

Signed files are detected and parsed, but the OpenPGP signature is not verified.

How many requests does a check make?

One, or two when the well-known location returns 404 or 410 and the legacy location is tried.

How many credits does it cost?

One credit per request. 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

Check a security.txt

Start free View documentation Try the free tool