search.shaq-logistics.com/sse
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-009 | OK | — | 215 | 9 | a0bb5ae911adac54… | |
| REL-SNAP-010 | OK | — | 340 | 9 | a0bb5ae911adac54… | |
| REL-SNAP-011 | OK | — | 147 | 9 | a0bb5ae911adac54… | |
| REL-SNAP-012 | OK | — | 230 | 9 | a0bb5ae911adac54… | |
| REL-SNAP-013 | OK | — | 146 | 9 | a0bb5ae911adac54… | |
| REL-SNAP-014 | OK | — | 363 | 9 | a0bb5ae911adac54… | |
| REL-SNAP-015 | OK | — | 611 | 9 | a0bb5ae911adac54… | |
| REL-SNAP-016 | OK | — | 600 | 9 | a0bb5ae911adac54… | |
| REL-SNAP-017 | OK | — | 606 | 9 | a0bb5ae911adac54… | |
| REL-SNAP-018 | TLS_FAIL | tls_certificate_name_mismatch | — | — | — | |
| REL-SNAP-019 | OK | — | 2038 | 9 | a0bb5ae911adac54… | |
| REL-SNAP-020 | OK | — | 1860 | 9 | a0bb5ae911adac54… | |
| REL-SNAP-021 | OK | — | 1844 | 9 | a0bb5ae911adac54… | |
| REL-SNAP-022 | OK | — | 1802 | 9 | a0bb5ae911adac54… | |
| REL-SNAP-023 | HTTP_5XX | http_525 | — | — | — | |
| REL-SNAP-024 | OK | — | 1795 | 9 | a0bb5ae911adac54… | |
| REL-SNAP-025 | OK | — | 2559 | — | — | |
| REL-SNAP-026 | OK | — | 1887 | 9 | a0bb5ae911adac54… |
Identity
- Record key
search.shaq-logistics.com/sse— the normalised endpoint observed. See the methodology for the rule.- Transport
- sse
- Registry names (not anchored)
- com.shaq-log/freight-mcp What the registry said when we swept it, as observed by us — not evidence that the registry was correct, that the name belongs to whoever registered it, or that it still resolves. Not covered by the chain: no inclusion proof reaches this field.
- Name reported by the server
- shaq-logistics Self-reported and unverified — never used as identity.
Verifying this record
Each observation above carries a merkle leaf in the published snapshot it belongs to. Verify the chain explains how to walk a leaf to a published root without taking our word for any of it.