com.frontsentinel/domain-security · v1.0.0 · security
Front Sentinel is healthy: it completed an MCP handshake in 644 ms and exposes 4 tools.
Read-only security checks for dApp domains: registry lock, DNSSEC, CAA, SRI, SEAL DNS controls
Endpoint: https://frontsentinel.com/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 4 |
| Latency | 644 ms |
| Last checked (UTC) | 2026-10-23T11:05:16.943Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-23T11:05:16.943Z | Healthy | 644 |
scan_domain | Scores how well a dApp or website domain is protected against hijacking: registrar transfer/update locks, registry lock, DNSSEC, CAA, expiry, nameserver consistency across resolvers, SRI on third-party scripts and the Content-Security-Policy header. Returns a 0-100 score, each check with pass/fail/u |
check_registry_lock | Reads the domain's EPP status codes from RDAP and tells whether registry lock (serverUpdateProhibited + serverTransferProhibited) is on, partly on or off, and which registrar-level locks are set. |
check_sri | Loads a public page and lists every script, stylesheet and preload it pulls in. For third-party files, checks whether an integrity= hash is present and matches, and returns a ready sha384 hash for files that have none. |
check_seal_dns_registrar | Goes through the 16 controls of the SEAL Security Frameworks certification for DNS & Registrar and marks what public data shows for each: ok, partial, gap, not visible from outside, or a process control the team has to document itself. Includes DNSSEC, CAA, SPF/DMARC/MTA-STS, locks, expiry and secur |