api.oreilly.com/api/content-discovery/v1
https://api.oreilly.com/api/content-discovery/v1/mcp/
75
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 50m 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 | 50m ago | a20feb1c8fa4cfcb… |
| http_response_observation | 50m ago | 070feb0b777f7cf7… |
| availability_observation | 50m ago | 967666d83251be3f… |
| tls_certificate_observation | 50m ago | 88927ce5ae719f70… |
| oauth_metadata_observation | 50m ago | 8857b00edb3002a7… |
| mcp_protocol_observation | 50m ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of api.oreilly.com/api/content-discovery/v1 to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.