# Well-Known Extractor (`vojtam/well-known-extractor`) Actor Probes the domain's .well-known endpoints and returns the body and parsed structure for each. - **URL**: https://apify.com/vojtam/well-known-extractor.md - **Developed by:** [Vojtěch Mašláň](https://apify.com/vojtam) (community) - **Categories:** Automation, Developer tools - **Stats:** 1 total users, 0 monthly users, 85.7% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $10.00 / 1,000 domain scans 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/actors/running/actors-in-store.md#pay-per-event ## 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 ## Well-Known Extractor Probes a domain's [`/.well-known/`](https://www.rfc-editor.org/rfc/rfc8615) endpoints and returns each file's raw body plus a parsed representation. Runs as a batch over many domains, or as a Standby HTTP API for one domain per request. ### Input | Field | Type | Default | Description | | ----------------- | ------- | ------------ | ------------------------------------------------------------------------------ | | `domains` | array | — (required) | Domains to probe, e.g. `google.com`. Each is normalized to its `https` origin. | | `profiles` | array | `["core"]` | Endpoint groups to probe. Use `["all"]` for all 35. | | `endpoints` | array | — | Individual endpoint ids, added on top of `profiles`. | | `includeNotFound` | boolean | `false` | Also write dataset rows for endpoints that were absent. | `profiles` and `endpoints` are combined and deduplicated by path. If both are empty, `core` is used. At most 50 endpoints are probed per domain; extras are skipped with a warning. ### Endpoint profiles | Profile | Endpoints | | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `core` (11) | `security.txt`, `gpc.json`, `openid-configuration`, `oauth-authorization-server`, `oauth-protected-resource`, `assetlinks.json`, `apple-app-site-association`, `nodeinfo`, `host-meta`, `agent-card.json`, `llms.txt` | | `security` (4) | `security.txt`, `gpc.json`, `dnt-policy.txt`, `openpgpkey-policy` | | `identity` (7) | `openid-configuration`, `oauth-authorization-server`, `oauth-protected-resource`, `openid-federation`, `jwks.json`, `did.json`, `microsoft-identity-association.json` | | `mobile` (4) | `assetlinks.json`, `apple-app-site-association`, `apple-developer-merchantid-domain-association`, `microsoft-identity-association.json` | | `email` (2) | `mta-sts.txt`, `openpgpkey-policy` | | `social` (9) | `did.json`, `nodeinfo`, `host-meta`, `host-meta.json`, `matrix-server`, `matrix-client`, `matrix-support`, `atproto-did`, `discord` | | `ai` (6) | `oauth-protected-resource`, `agent-card.json`, `agent.json`, `mcp.json`, `ai.txt`, `llms.txt` | | `adtech` (3) | `ads.txt`, `app-ads.txt`, `sellers.json` | | `web` (5) | `traffic-advice`, `related-website-set.json`, `privacy-sandbox-attestations.json`, `web-app-origin-association`, `discord` | | `all` (35) | All of the above. | Profiles overlap; an endpoint in two selected profiles is probed once. 34 of the 35 endpoints have a parser; `openpgpkey-policy` returns raw only. `llms.txt`, `ads.txt`, `app-ads.txt`, and `sellers.json` live at the site root, not under `/.well-known/`. ### Output A batch run writes one dataset row per endpoint found: ```json { "domain": "www.google.com", "origin": "https://www.google.com", "scannedAt": "2026-08-04T12:00:00.000Z", "id": "security.txt", "path": "/.well-known/security.txt", "title": "Security contact policy", "spec": "https://www.rfc-editor.org/rfc/rfc9116", "url": "https://www.google.com/.well-known/security.txt", "finalUrl": "https://www.google.com/.well-known/security.txt", "found": true, "httpStatus": 200, "contentType": "text/plain", "raw": "Contact: https://g.co/vulnz\nExpires: 2027-01-01T00:00:00Z\n", "parsed": { "contact": ["https://g.co/vulnz"], "expires": "2027-01-01T00:00:00Z" }, "error": null } ``` | Field | Description | | -------------------------------- | --------------------------------------------------------------------------- | | `domain` / `origin` | Scanned host and its normalized origin. | | `id` / `path` / `title` / `spec` | Which endpoint this row is, and the spec that defines it. | | `url` / `finalUrl` | Requested URL and the URL after redirects. | | `found` | Whether the response counted as a real hit. | | `httpStatus` / `contentType` | Response status and content type. `null` status means a transport error. | | `raw` | Response body, capped at 256 KB. `null` when not found. | | `parsed` | Structured form of `raw`, or `null` if no parser applies or parsing failed. | | `error` | Transport error message, otherwise `null`. | `found` is `false` for a 4xx, and also for a `200` that returns HTML or an unexpected body shape, since sites commonly answer unknown paths with a catch-all page. You can download the dataset as JSON, CSV, Excel, or HTML. ### Standby API ``` GET /?domain=google.com GET /?domain=google.com&profiles=ai,security GET /?domain=google.com&endpoints=security.txt,openid-configuration POST / { "domain": "google.com", "profiles": ["core"] } ``` One domain per request. The response wraps the same probes in `wellKnown[]` and adds a summary: ```json { "domain": "www.google.com", "url": "https://www.google.com", "scannedAt": "2026-08-04T12:00:00.000Z", "wellKnown": [{ "id": "security.txt", "found": true, "httpStatus": 200, "parsed": {} }], "summary": { "probed": 11, "found": ["security.txt"], "notFound": ["assetlinks.json"], "errored": [], "security": { "contacts": ["https://g.co/vulnz"], "expires": "2027-01-01T00:00:00Z" }, "openidIssuer": "https://accounts.google.com" } } ``` ### Pricing One `domain-scanned` event per domain, charged whether or not anything is found. Cost is the number of domains times the per-domain price. # Actor input Schema ## `domains` (type: `array`): Domains whose well-known endpoints should be probed (e.g. google.com). ## `profiles` (type: `array`): Preset groups of endpoints to probe. ## `endpoints` (type: `array`): Specific endpoints to probe, added on top of the selected profiles. Leave empty to use profiles only. ## `includeNotFound` (type: `boolean`): Push a row for endpoints that were absent too. Useful for auditing coverage; off by default to keep the dataset small. ## Actor input object example ```json { "domains": [ "google.com" ], "profiles": [ "core" ], "includeNotFound": false } ``` # Actor output Schema ## `dataset` (type: `string`): No description ## `standbyUrl` (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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "domains": [ "google.com" ] }; // Run the Actor and wait for it to finish const run = await client.actor("vojtam/well-known-extractor").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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "domains": ["google.com"] } # Run the Actor and wait for it to finish run = client.actor("vojtam/well-known-extractor").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 '{ "domains": [ "google.com" ] }' | apify call vojtam/well-known-extractor --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,vojtam/well-known-extractor" } } } ``` 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 ` 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/3JznCsfTxov0eBqGJ/builds/DnhsZn0uGreLcbPUl/openapi.json