mostexpensivewatches.net
https://mostexpensivewatches.net/mcp
57
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d 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 | 1d ago | 80dbd6ef4bb5e2d6… |
| http_response_observation | 1d ago | d203cba9d80be017… |
| availability_observation | 1d ago | 1c58f411bf2b84bd… |
| hosting_provider_observation | 1d ago | 958411567b2d9bdc… |
| tls_certificate_observation | 1d ago | a873d238e295d5c4… |
| oauth_metadata_observation | 1d ago | 444be551d5bd62a5… |
| mcp_protocol_observation | 1d ago | 990dd5d89cf9c73d… |
| mcp_capability_observation | 1d ago | e2cc264adee6e831… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mostexpensivewatches.net to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.