# scan_domain_trust

Audit a domain's DNS, TLS, certificates, and email authentication (SPF/DKIM/DMARC/DNSSEC).

Agent View of the PolicyLayer registry record for `scan_domain_trust`. HTML page: https://policylayer.com/tools/com-fedlin-fedlin-mcp-server/scan-domain-trust

## Facts

- Tool: `scan_domain_trust`
- Server: FEDLIN Scanners (`https://mcp.fedlin.com/mcp`) — https://policylayer.com/tools/com-fedlin-fedlin-mcp-server.md
- Homepage: https://github.com/fedlinllc/fedlin-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `domain` | string | yes | A bare public hostname to scan, for example example.com. No scheme, path, or port; IP literals and internal hostnames are rejected. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "scan_domain_trust",
    "arguments": {
      "domain": "<domain>"
    }
  }
}
```

## Why scan_domain_trust is rated Low

Even though scan_domain_trust only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call scan_domain_trust to retrieve information from FEDLIN Scanners without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches FEDLIN Scanners:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "scan_domain_trust": {}
  }
}
```

## Other tools on FEDLIN Scanners (2)

- `scan_post_quantum` — Read — https://policylayer.com/tools/com-fedlin-fedlin-mcp-server/scan-post-quantum.md
- `scan_security_headers` — Read — https://policylayer.com/tools/com-fedlin-fedlin-mcp-server/scan-security-headers.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-fedlin-fedlin-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-fedlin-fedlin-mcp-server