Security.txt + Well-Known Inspector avatar

Security.txt + Well-Known Inspector

Pricing

$20.00 / 1,000 domain inspecteds

Go to Apify Store
Security.txt + Well-Known Inspector

Security.txt + Well-Known Inspector

Bulk domain inspector for security.txt and useful .well-known trust/security endpoints: change-password, OpenID config, assetlinks, Apple app-site association, MTA-STS, host-meta, and more.

Pricing

$20.00 / 1,000 domain inspecteds

Rating

0.0

(0)

Developer

Mack

Mack

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 days ago

Last modified

Share

Bulk-check domains for security.txt and useful .well-known trust/security endpoints.

This actor is for security consultants, OSINT researchers, sysadmins, agencies, and SaaS teams that need a quick map of public disclosure/contact and platform-discovery files across many domains.

Checks

For each domain, the actor checks:

  • /.well-known/security.txt
  • /security.txt fallback
  • /.well-known/change-password
  • /.well-known/openid-configuration
  • /.well-known/assetlinks.json
  • /.well-known/apple-app-site-association
  • /.well-known/webfinger
  • /.well-known/host-meta
  • /.well-known/nodeinfo
  • https://mta-sts.<domain>/.well-known/mta-sts.txt

For security.txt, it parses common RFC 9116 fields such as Contact, Expires, Policy, Encryption, Acknowledgments, and Canonical.

Example input

{
"domains": ["github.com", "google.com"],
"maxDomains": 50
}

Example output fields

{
"domain": "example.com",
"score": 62,
"verdict": "partial well-known posture",
"present_keys": ["security_txt_well_known", "change_password"],
"security_contacts": ["mailto:security@example.com"],
"risk_flags": [],
"checks": [{"key": "security_txt_well_known", "status": 200, "parsed": {}}]
}

Pricing

Charged per valid domain inspected: $0.02 / domain.

Limitations

  • Surface-level HTTP discovery only; not a full compliance audit.
  • Missing files are not proof the organization lacks the underlying capability.
  • Some .well-known endpoints intentionally redirect, require query parameters, or behave differently by user agent.
  • Use the output as triage evidence and manually inspect high-impact findings.