DNS/CDN/frontend hash drift
Falcon Finance's assessment for RD-F-105 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
DNS / frontend hash drift | Applicable: Yes (falcon.finance, app.falcon.finance active) | Official domain stable at assessment date. No DNS drift or cert-change alerts. Impersonation domains (event-falconsfinance[.]com, claim-falcon[.]app) are separate domains — not drift on official domain. Signal not firing on official domain.
Detail #
Official falcon.finance domain appears stable as of 2026-05-12 based on public monitoring. No DNS record changes, TLS cert changes, or JS bundle hash drift alerts from public CT logs or monitoring services. The active impersonation domains (event-falconsfinance[.]com, claim-falcon[.]app) documented by PCRisk are entirely separate domain registrations — they do not constitute drift on the official falcon.finance domain. Those feed into Cat 11 RD-F-161. T-09 phase-2 signal (requires external hash monitoring stack). Signal on official domain not firing.
Sources #
- URL
- Falcon Finance Transparency Dashboard (JS-rendered, data not accessible via WebFetch)https://app.falcon.finance/transparencyretrieved 2026-05-12
Methodology #
Detect whether the hash of production frontend JS changes versus the prior published hash, or a DNS config change is detected.
See the full factor methodology and distribution across all protocols →