kifly.io/api
https://kifly.io/api/mcp
71
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| oauth_metadata_present | +14 |
| tls_present_and_valid | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (0)
No findings from the current evidence set.
Evidence (6)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 626e6611ed161b8a… |
| http_response_observation | 2d ago | 0d85c8c558ceb64b… |
| availability_observation | 2d ago | b95146b289de269c… |
| hosting_provider_observation | 2d ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 2d ago | ed0f5223fb4283cb… |
| oauth_metadata_observation | 2d ago | 3c9498b0fda8b1a5… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of kifly.io/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.