# HTTP Security Headers Auditor (`junipr/http-security-headers-auditor`) Actor

Audit public URLs or supplied header snapshots for security-relevant HTTP response headers and weak values.

- **URL**: https://apify.com/junipr/http-security-headers-auditor.md
- **Developed by:** [junipr](https://apify.com/junipr) (community)
- **Categories:** SEO tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.90 / 1,000 http security headers auditor url auditeds

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

## HTTP Security Headers Auditor

### Store Positioning

**Store title:** HTTP Security Headers Auditor

**Short description:** Audit public URLs or supplied header snapshots for security-relevant HTTP response headers and weak values.

**SEO title:** HTTP Security Headers Auditor — technical SEO, web, and domain audit

**SEO description:** Audit public URLs or supplied header snapshots for security-relevant HTTP response headers and weak values. Use it to find crawlability, indexability, security, metadata, and page-quality issues with evidence-backed rows and audit reports.

**Categories:** SEO\_TOOLS

**Keywords:** http, security, headers, auditor, public data, security headers, web/domain audit

### Fixed-Inclusive PPE Pricing

This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.

- Tier: W1 — Web/domain audit
- Primary event: `url-audited` at $0.00490 base
- Default max charge: $10.00
- Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount

Event set:

- `actor-start`: base $0.00500, GOLD $0.00400. HTTP Security Headers Auditor: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `url-audited`: base $0.00490, GOLD $0.00392. HTTP Security Headers Auditor: charged when url audited is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `rule-parsed`: base $0.00372, GOLD $0.00298. HTTP Security Headers Auditor: charged when rule parsed is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `finding-emitted`: base $0.00372, GOLD $0.00298. HTTP Security Headers Auditor: charged when finding emitted is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `audit-report-generated`: base $0.05000, GOLD $0.04000. HTTP Security Headers Auditor: charged when audit report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

### Public Task Concepts

- Audit HTTP Security Headers controls on a capped public sample
- Find high-priority HTTP Security Headers issues before release
- Validate HTTP Security Headers evidence from supplied pages
- Prioritize HTTP Security Headers fixes with severity and proof
- Export HTTP Security Headers QA rows for client review

Audit public URLs or supplied header snapshots for security-relevant HTTP response headers and weak values.

### Inputs

- `urls`
- `sitemapUrls`
- `headerInputs`
- `allowedDomains`
- `maxUrls`
- `useHeadRequests`
- `getFallback`
- `securityProfile`
- `includeRedirectSummary`
- `includeHeaderEvidence`
- `requestDelayMs`
- `timeoutMs`

### Output

Dataset rows include: `resourceUrl`, `finalUrl`, `statusCode`, `https`, `strictTransportSecurity`, `contentSecurityPolicy`, `contentSecurityPolicyReportOnly`, `xFrameOptions`, `referrerPolicy`, `permissionsPolicy`, `xContentTypeOptions`, `crossOriginOpenerPolicy`, `crossOriginEmbedderPolicy`, `crossOriginResourcePolicy`, `headerName`, `headerValue`, `issueCode`, `severity`, `recommendation`.

The checked-in output example is produced by the deterministic supplied-header input and is verified against the dataset schema in automated tests.

# Actor input Schema

## `urls` (type: `array`):

urls used by HTTP Security Headers Auditor.

## `sitemapUrls` (type: `array`):

sitemapUrls used by HTTP Security Headers Auditor.

## `headerInputs` (type: `array`):

Offline header captures to audit without fetching live URLs.

## `allowedDomains` (type: `array`):

allowedDomains used by HTTP Security Headers Auditor.

## `maxUrls` (type: `number`):

Numeric limit for HTTP Security Headers Auditor.

## `useHeadRequests` (type: `boolean`):

Enable useHeadRequests behavior.

## `getFallback` (type: `boolean`):

Enable getFallback behavior.

## `securityProfile` (type: `object`):

Optional profile settings for HTTP Security Headers Auditor.

## `includeRedirectSummary` (type: `boolean`):

Enable includeRedirectSummary behavior.

## `includeHeaderEvidence` (type: `boolean`):

Enable includeHeaderEvidence behavior.

## `requestDelayMs` (type: `number`):

Numeric limit for HTTP Security Headers Auditor.

## `timeoutMs` (type: `number`):

Numeric limit for HTTP Security Headers Auditor.

## Actor input object example

```json
{
  "urls": [
    "https://www.wikipedia.org"
  ],
  "sitemapUrls": [],
  "headerInputs": [],
  "allowedDomains": [],
  "maxUrls": 25,
  "useHeadRequests": true,
  "getFallback": true,
  "securityProfile": {},
  "includeRedirectSummary": true,
  "includeHeaderEvidence": true,
  "requestDelayMs": 0,
  "timeoutMs": 10000
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `report` (type: `string`):

No description

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("junipr/http-security-headers-auditor").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("junipr/http-security-headers-auditor").call(run_input=run_input)

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

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

```

## CLI example

```bash
echo '{}' |
apify call junipr/http-security-headers-auditor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,junipr/http-security-headers-auditor"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/UzmoO1J1fFQaG6bBg/builds/2lqVCc1mhjlIoOjFd/openapi.json