telegram.regiq.in/api
https://telegram.regiq.in/api/mcp
53
trust
0.35
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Insufficient evidence.Too little independent observation to support a confident judgment. Absence of negative evidence is not safety — this score should not gate a high-impact action.
Why this score
| tls_present_and_valid | +4 |
| headers.missing_hsts | -3 |
| reachable | +2 |
Findings (1)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (6)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | c99926f9e73d0eea… |
| http_response_observation | 2d ago | ab02dc101d15f2b0… |
| availability_observation | 2d ago | 15bb2bef7b90a8d4… |
| hosting_provider_observation | 2d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 2d ago | 76aca781a4e8421e… |
| oauth_metadata_observation | 2d ago | def438e8370b60d5… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of telegram.regiq.in/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.