404.directory
https://404.directory/mcp
57
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 4h ago
Why this score
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| headers.missing_hsts | -3 |
| reachable | +2 |
Findings (1)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 4h ago | 88053e58db7aa738… |
| http_response_observation | 4h ago | a94e8c4eb444c70f… |
| availability_observation | 4h ago | b63dd46b73092b86… |
| hosting_provider_observation | 4h ago | 958411567b2d9bdc… |
| tls_certificate_observation | 4h ago | 30ea77682b4f22a6… |
| oauth_metadata_observation | 4h ago | 84690b28966c3e3c… |
| mcp_protocol_observation | 4h ago | 16ca4765a2424525… |
| mcp_capability_observation | 4h ago | ed4e25a4f09c1575… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of 404.directory to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.