Incorrect blocks causing potential issues with public portal and embeds on version 6

Update timeline

1. identified Jan 14, 2026, 06:13 PM UTC

   Last weekend, automated systems from Netcraft, an online threat assessment company working on behalf of Facebook, incorrectly reported app.onechurchsoftware.com to internet security providers that manage phishing and scam blocklists. As a result, those providers quickly blocked our domain without evidence. After we contacted Netcraft, they acknowledged the error and formally retracted the report. However, despite being notified by Netcraft, some providers are still blocking the domain. We are actively working with Netcraft to resolve this as quickly as possible and have requested a full list of all providers they contacted so we can help expedite the process however we can. This issue only potentially affects customers using version 6 of the platform. Version 7 is not impacted. Even within version 6, only a subset of users may be affected. Whether someone experiences an issue depends on the security checks performed by their device when accessing the public portal or pages using web embeds, as well as how current their blocklists are. The browser used may also contribute. As a result, the same page may load successfully for one user but not for another. We understand this is frustrating. We are upset as well. We will continue to provide updates as the situation develops.

2. monitoring Jan 20, 2026, 05:28 PM UTC

   Most providers at this point have updated their block lists to no longer include app.onechurchsoftware.com. Users on version 6 of One Church should see improvement though there may still be pockets of blocked access here and there. This would most commonly be observed in corporate / managed networks or tools that elevate security. In addition to what Netcraft did on their end, we have actively worked with major security and browser providers (including Apple, Google, Microsoft, Cisco, Fortinet, Webroot, and Norton) to ensure the corrected status propagates as quickly as possible. As well, we submitted formal reclassification requests where applicable. We will continue to monitor the situation. If there are any blocking instances, please let us know along with who is blocking access and the network used so we can reach out to those providers as appropriate.

3. resolved Jan 28, 2026, 04:53 PM UTC

   This incident has been resolved.