# Change Password Well-Known URL Auditor (`phoenix2810/change-password-well-known-auditor`) Actor

Audit a domain's /.well-known/change-password redirect against the W3C spec. Verify the target loads and get a readiness score.

- **URL**: https://apify.com/phoenix2810/change-password-well-known-auditor.md
- **Developed by:** [Sanskar Jaiswal](https://apify.com/phoenix2810) (community)
- **Categories:** Developer tools, SEO tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Change Password Well-Known URL Auditor

Audits whether a public domain implements the W3C/WHATWG specification for a well-known URL for changing passwords (`/.well-known/change-password`) and returns a readiness score, letter grade, issues, and recommendations as structured JSON.

### Use cases

- Security and identity engineering teams verifying that `/.well-known/change-password` correctly redirects to the real password-change page
- Password manager vendors and browser teams sampling adoption of the convention across customer or partner domains
- Site migration QA confirming the well-known redirect survives an identity-provider or account-settings URL change
- Agency consultants running recurring account-security audits across client domains
- CI pipelines gating releases on regressions to the well-known redirect

### Input

| Field | Type | Default | Description |
| --- | --- | --- | --- |
| startUrl | string | (required) | Public domain or URL to audit. Only the scheme and host are used; the actor always requests `/.well-known/change-password` on that host. |
| timeoutSeconds | integer | 10 | Request timeout per request, from 3 to 30 seconds. |
| followRedirectTarget | boolean | true | When the well-known URL redirects, also fetch the redirect target once to confirm it returns a successful response. |

### Output

One dataset item per run:

| Field | Type | Description |
| --- | --- | --- |
| inputUrl | string | URL as provided in the input. |
| wellKnownUrl | string or null | The resolved `/.well-known/change-password` URL that was requested. |
| https | boolean or null | Whether the well-known URL was requested over HTTPS. |
| ok | boolean | Whether the audit completed without a fetch or validation error. |
| checkedAt | string | ISO 8601 timestamp of the check. |
| httpStatus | integer or null | HTTP status of the well-known response. |
| classification | string | One of: redirect, redirect-missing-location, direct-serve, not-found, unexpected-status, unreachable. |
| isRedirect | boolean | Whether the well-known URL returned a 3xx status. |
| isDirectServe | boolean | Whether the well-known URL served a 200 response directly instead of redirecting. |
| redirectLocation | string or null | Raw `Location` header value from the well-known response. |
| redirectTargetUrl | string or null | The redirect Location resolved to an absolute URL. |
| redirectIsHttps | boolean or null | Whether the redirect target is an HTTPS URL. |
| sameOriginRedirect | boolean or null | Whether the redirect target is on the same host as the audited domain. |
| redirectTargetChecked | boolean | Whether the actor fetched the redirect target to confirm it loads. |
| redirectTargetReachable | boolean or null | Whether the redirect target returned a successful response. |
| redirectTargetStatus | integer or null | HTTP status of the redirect target fetch. |
| redirectTargetError | string or null | Error message if the redirect target fetch failed. |
| contentType | string or null | Content-Type of the well-known response. |
| score | integer | Readiness score from 0 to 100. |
| grade | string | Letter grade from A+ to F. |
| issues | array | Concrete problems found. |
| recommendations | array | Actionable fixes. |
| error | string or null | Error message when the audit could not complete. |

### Example input

```json
{
    "startUrl": "https://github.com/",
    "timeoutSeconds": 10,
    "followRedirectTarget": true
}
```

### Example output

```json
{
    "inputUrl": "https://github.com/",
    "wellKnownUrl": "https://github.com/.well-known/change-password",
    "https": true,
    "ok": true,
    "httpStatus": 301,
    "classification": "redirect",
    "isRedirect": true,
    "isDirectServe": false,
    "redirectLocation": "https://github.com/settings/security",
    "redirectTargetUrl": "https://github.com/settings/security",
    "redirectIsHttps": true,
    "sameOriginRedirect": true,
    "redirectTargetChecked": true,
    "redirectTargetReachable": true,
    "redirectTargetStatus": 200,
    "score": 85,
    "grade": "A",
    "issues": [],
    "recommendations": [
        "The /.well-known/change-password convention is correctly implemented. Periodically re-check after deploys or identity-provider migrations."
    ],
    "error": null
}
```

### Security

- Fetches public HTTP/HTTPS URLs only; URLs with credentials are rejected.
- Private IPv4, private IPv6, and loopback targets are blocked, hostnames are DNS-resolved, and resolutions to private ranges are rejected (SSRF defense).
- Redirects are never followed automatically. The redirect Location is revalidated through the same SSRF checks before the actor optionally performs one additional fetch to confirm the target page loads.
- Only `/.well-known/change-password` on the audited host, and its declared redirect target, are ever fetched. No other links on the site are followed.
- No login, no cookies are stored, no JavaScript is executed, and no page content is retained beyond a small Content-Type check.

### Pricing

| Event | Price |
| --- | --- |
| Actor start | $0.005 per run |
| Domain audited | $0.01 per result |

A typical single-domain audit costs $0.015.

### FAQ

**What is the well-known change-password URL?**
It is a convention defined by the W3C/WHATWG specification "A Well-Known URL for Changing Passwords" (https://w3c.github.io/webappsec-change-password-url/). Sites that support it serve `/.well-known/change-password`, which redirects password managers and browsers directly to the account's password-change form, so users and tools do not need to search for it manually.

**Why does a 200 response still lose points?**
The specification's model is a redirect. Some sites serve the password-change form directly at the well-known path instead of redirecting to it. This still works for most password managers, so it is scored as a partial pass rather than a hard failure, but it is flagged so the site owner can align with the published convention.

**Does this actor change or submit anything?**
No. It only performs read-only GET requests to the well-known path and, optionally, its redirect target, and reports what it finds.

**What if the domain does not implement the convention at all?**
A 404 or 410 response is reported as `not-found` with a low score and a recommendation to implement the redirect.

# Actor input Schema

## `startUrl` (type: `string`):

Public domain or URL to audit. Only the scheme and host are used; the actor always requests /.well-known/change-password on that host.

## `timeoutSeconds` (type: `integer`):

Request timeout from 3 to 30 seconds per request.

## `followRedirectTarget` (type: `boolean`):

When the well-known URL redirects, also fetch the redirect target once to confirm it returns a successful response.

## Actor input object example

```json
{
  "startUrl": "https://example.com/",
  "timeoutSeconds": 10,
  "followRedirectTarget": true
}
```

# Actor output Schema

## `results` (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 = {
    "startUrl": "https://example.com/"
};

// Run the Actor and wait for it to finish
const run = await client.actor("phoenix2810/change-password-well-known-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 = { "startUrl": "https://example.com/" }

# Run the Actor and wait for it to finish
run = client.actor("phoenix2810/change-password-well-known-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 '{
  "startUrl": "https://example.com/"
}' |
apify call phoenix2810/change-password-well-known-auditor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,phoenix2810/change-password-well-known-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/zmpUeryZBvpIEYnNz/builds/A36YBQJ62nxg1GdiU/openapi.json