emailens.dev/api
https://emailens.dev/api/mcp
63
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 4h ago
Why this score
| mcp_requires_authentication | +10 |
| 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 (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 4h ago | 801c0b15b83c4cb1… |
| http_response_observation | 4h ago | efcf446201283e8c… |
| availability_observation | 4h ago | e42100ce4fa89fa7… |
| hosting_provider_observation | 4h ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 4h ago | d8050e2dd1683f15… |
| oauth_metadata_observation | 4h ago | b9c7ce83eca6a082… |
| mcp_protocol_observation | 4h ago | dbba9866ec116847… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of emailens.dev/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.