# Security.txt Checker — Security Contact Finder (`q_services/security-txt-checker`) Actor

Check websites for security.txt, extract security contacts, expiry, policy, hiring and compliance fields.

- **URL**: https://apify.com/q\_services/security-txt-checker.md
- **Developed by:** [Q Services](https://apify.com/q_services) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.50 / 1,000 checked domains

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Security.txt Checker — Security Contact Finder

Check any list of websites for `security.txt` and extract structured security contact data.

Use it for vendor security reviews, bug bounty intake audits, compliance monitoring, agency reports, and scheduled checks that alert you when a site's security contact file disappears or expires.

**Example result:**

```json
{
    "domain": "securitytxt.org",
    "checkedUrl": "https://securitytxt.org/.well-known/security.txt",
    "status": "found",
    "hasSecurityTxt": true,
    "contacts": ["mailto:security@example.com"],
    "expiresAt": "2027-01-01T00:00:00.000Z",
    "isExpired": false,
    "policy": ["https://example.com/security-policy"],
    "scrapedAt": "2026-07-09T10:30:00.000Z"
}
```

### How to use it

1. Paste one or more domains or URLs.
2. Keep the root fallback enabled if you also want to check `/security.txt`.
3. Start the Actor and export the Dataset as JSON, CSV or Excel.

### Pricing

Pay per result, no subscription:

| Event | Price |
|---|---|
| Run start | $0.005 |
| Per checked domain | $0.0005 |

1,000 checked domains cost about $0.505 before Apify platform usage.

### Output fields

| Field | Type | Always present |
|---|---|---|
| `domain` | string | Yes |
| `checkedUrl` | URL | Yes |
| `status` | string: `found`, `expired`, `missing` | Yes |
| `hasSecurityTxt` | boolean | Yes |
| `statusCode` | number or null | No |
| `contacts` | array | Yes |
| `expiresAt` | ISO date or null | No |
| `isExpired` | boolean or null | No |
| `encryption` | array | Yes |
| `acknowledgments` | array | Yes |
| `preferredLanguages` | array | Yes |
| `canonical` | array | Yes |
| `policy` | array | Yes |
| `hiring` | array | Yes |
| `csaf` | array | Yes |
| `unknownFields` | array | Yes |
| `attempts` | array | Yes |
| `scrapedAt` | ISO date | Yes |

### Limitations

- It reads public `security.txt` files only.
- It does not validate cryptographic signatures.
- Missing files are returned as normal results because the absence is useful audit data.

### FAQ

**Why do missing files appear in the dataset?**
For compliance and monitoring workflows, "missing" is an actionable status.

**Can I schedule it?**
Yes. Schedule it weekly or monthly to monitor a portfolio of domains.

**Does it call private APIs?**
No. It only requests public website URLs.

### Verified automation package

The following reproducible example comes from successful Apify run `fAG15T4UybKDbNRpS`. See the [full Q Services technical guide](https://q-services.fr/blog/security-txt-checker-2026-07-26-growth-guide/) and the [tested n8n automation example](https://github.com/Gasppacho/q-services-automations/tree/main/n8n/security-txt-checker).

Audit public domains for security.txt availability and expiry, then reuse the structured results in scheduled vendor-risk, compliance, or security-operations monitoring.

#### High-value use cases

- Weekly security.txt monitoring across a vendor portfolio
- Security contact discovery for incident-response preparation
- Expiry and missing-file alerts after website releases
- Evidence collection for recurring vendor-risk reviews
- Managed security reporting across customer domains

**Target audience:** Security operations, vendor-risk, compliance, and managed-service teams monitoring portfolios of public domains

**Growth hypothesis:** A portfolio-monitoring position and reusable n8n loop will increase repeat runs by teams that need continuous security-contact coverage rather than a one-time lookup.

#### Tested input

```json
{
  "startUrls": [
    "https://securitytxt.org"
  ],
  "includeRootFallback": true,
  "maxResults": 1,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

#### Clean output sample

```json
[
  {
    "domain": "\u003cstring\u003e",
    "checkedUrl": "\u003cstring\u003e",
    "finalUrl": "\u003cstring\u003e",
    "status": "\u003cstring\u003e",
    "hasSecurityTxt": "\u003cstring\u003e"
  }
]
```

#### API example

```bash
curl --request POST   'https://api.apify.com/v2/acts/5jcFA2uhR3HJLAMTK/runs?waitForFinish=120&maxTotalChargeUsd=0.05'   --header "Authorization: Bearer $APIFY_TOKEN"   --header 'Content-Type: application/json'   --data @input.json
```

#### Measured cost and limits

The proof run took 6.33 seconds and reported $0.001438 in platform usage. Actual cost depends on input size and source behavior. Set an Apify maximum charge per run and conservative result limits.

Known limits:

- Public sources can change or become unavailable.
- Output completeness depends on the supplied input.
- The measured proof cost is evidence for one run, not a universal quote.

[Run Security.txt Checker — Security Contact Finder on the Apify Store](https://apify.com/q_services/security-txt-checker).

# Actor input Schema

## `startUrls` (type: `array`):

Domains or website URLs to check for /.well-known/security.txt.

## `includeRootFallback` (type: `boolean`):

If /.well-known/security.txt is missing, also check the older /security.txt location.

## `maxResults` (type: `integer`):

The Actor stops and stops charging after this many domains.

## `proxyConfiguration` (type: `object`):

Proxy configuration. The default Apify Proxy works for most websites.

## Actor input object example

```json
{
  "startUrls": [
    "https://securitytxt.org"
  ],
  "includeRootFallback": true,
  "maxResults": 100,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "startUrls": [
        "https://securitytxt.org"
    ],
    "includeRootFallback": true,
    "maxResults": 100,
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("q_services/security-txt-checker").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "startUrls": ["https://securitytxt.org"],
    "includeRootFallback": True,
    "maxResults": 100,
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("q_services/security-txt-checker").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "startUrls": [
    "https://securitytxt.org"
  ],
  "includeRootFallback": true,
  "maxResults": 100,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call q_services/security-txt-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=q_services/security-txt-checker",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/5jcFA2uhR3HJLAMTK/builds/k3xIINkLiy6ZcWuqV/openapi.json