pro.makeup/api
https://pro.makeup/api/mcp
75
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 11h ago
Why this score
| oauth_metadata_present | +14 |
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (1)
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 11h ago | 6182c7a503ed289c… |
| http_response_observation | 11h ago | 1131e024e5bacd29… |
| availability_observation | 11h ago | ebc9a2de88f3eafc… |
| hosting_provider_observation | 11h ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 11h ago | 32be4e8d2c64524a… |
| oauth_metadata_observation | 11h ago | dab9d0b0be27869e… |
| mcp_protocol_observation | 11h ago | 6dfce47954e09cd7… |
| mcp_capability_observation | 11h ago | 6505b27c8a9ce28b… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of pro.makeup/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.