atx/registry

www.zelume.io

https://www.zelume.io/mcp

89
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+12
mcp_requires_authentication+10
reachable+6
headers.missing_hsts-3

Findings (1)

lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0

Evidence (6)

TypeObservedSHA-256
dns_resolution_observation2d ago0889a5f18ebd51b8…
http_response_observation2d agoadfb061363ba976a…
availability_observation2d ago04bc41b7aef2044b…
tls_certificate_observation2d ago5e08100d543db027…
oauth_metadata_observation2d ago16134a5f10573df9…
mcp_protocol_observation2d ago5f4c66c82509bed4…

Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.

Operate this service?

Prove control of www.zelume.io to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →