api.refero.design
https://api.refero.design/mcp
75
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| tls_present_and_valid | +12 |
| mcp_requires_authentication | +10 |
| reachable | +6 |
| headers.missing_hsts | -3 |
Findings (1)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (6)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 8dae724d48a67cf6… |
| http_response_observation | 2d ago | 51615125cde5cf31… |
| availability_observation | 2d ago | 4d113dba2911524f… |
| tls_certificate_observation | 2d ago | 932d315c3e06669b… |
| oauth_metadata_observation | 2d ago | 0a05ad0e1f1f18f8… |
| mcp_protocol_observation | 2d ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of api.refero.design to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.