api.brick.directory/connect
https://api.brick.directory/connect
71
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 3h 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 | 3h ago | 07896aec42b9be1f… |
| http_response_observation | 3h ago | b457514aaf995556… |
| availability_observation | 3h ago | e6a78f118615fe27… |
| hosting_provider_observation | 3h ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 3h ago | fc6800440b9feb7b… |
| oauth_metadata_observation | 3h ago | 56cc7c212cbc2906… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of api.brick.directory/connect to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.