api.filetopdf.dev
https://api.filetopdf.dev/mcp
57
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 29m ago
Why this score
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| headers.missing_hsts | -3 |
| reachable | +2 |
Findings (2)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 29m ago | 8c2d9510001ab320… |
| http_response_observation | 29m ago | b9b4964245e6b757… |
| availability_observation | 29m ago | b39cd8a07d9c7e04… |
| hosting_provider_observation | 29m ago | 958411567b2d9bdc… |
| tls_certificate_observation | 29m ago | 5d05f94410e9d44f… |
| oauth_metadata_observation | 29m ago | 9210ccc54d6b05a6… |
| mcp_protocol_observation | 29m ago | 303438f2b4b53de8… |
| mcp_capability_observation | 29m ago | 2ca3440ff19daf67… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of api.filetopdf.dev to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.