domain_check_v1
Measures how resilient a public web domain is from the outside and returns a weighted score out of 100, a per-category breakdown, and prioritised findings explaining what to fix first. Use it to audit a domain you do not control, to verify a fix after deployment, or to compare several domains on ...
This record as markdown: /tools/com-feranor-resilience/domain-check-v1.md
What domain_check_v1 does on Feranor Resilience
AI agents call domain_check_v1 to retrieve information from Feranor Resilience without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | Bare domain name, apex or subdomain, for example 'example.com' or 'www.example.com'. Scheme, path, port and query string are ignored if present. IP addresses an |
Parameters from the server's own tool schema.
Why domain_check_v1 is rated Low
domain_check_v1 performs passive external assessment of a domain's security posture via public DNS/HTTP/TLS queries. It retrieves and analyzes publicly available information with no side effects on the target domain or any system. The tool cannot modify, execute code on, delete from, or charge money to any system.
From the tool's definition Tool measures and returns a weighted score, per-category breakdown, and findings. Verbs in description are 'Measures', 'returns', 'audit', 'verify', 'compare' — all read-only operations. No mutation, deletion, execution, or financial operations are performed.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs domain_check_v1 safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Feranor Resilience, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For domain_check_v1, this is the rule to start with:
domain_check_v1 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Feranor Resilience, apply this rule, and every domain_check_v1 call is checked against it from then on.
Questions about domain_check_v1
Measures how resilient a public web domain is from the outside and returns a weighted score out of 100, a per-category breakdown, and prioritised findings explaining what to fix first. Use it to audit a domain you do not control, to verify a fix after deployment, or to compare several domains on the same scale. Covers TLS certificate validity and protocol version, HTTP to HTTPS redirection, HSTS, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, cache directives, response time, DNS redundancy, IPv6 availability, CDN detection and software version disclosure. Everything is read from the public internet: nothing is authenticated, no ports are scanned, and no credentials are needed. Do not use it for private, internal, or localhost hostnames, for IP addresses, or to test a service you need logged-in access to. For a free score without the detailed findings, use domain_check_score_v1 instead. Price: $0.01 per call (x402, USDC on Base). No signup, no API key. It is categorised as a Read tool in the Feranor Resilience MCP Server, which means it retrieves data without modifying state.
domain_check_v1 accepts 1 parameter: domain. Required: domain. The full parameter table on this page comes from the server's own tool schema.
Register the Feranor Resilience MCP server in PolicyLayer and add a rule for domain_check_v1: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Feranor Resilience. Nothing to install.
domain_check_v1 is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the domain_check_v1 rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for domain_check_v1. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
domain_check_v1 is provided by the Feranor Resilience MCP server (https://www.feranor.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Feranor Resilience, and thousands of servers like it.
This server
Across the catalogue