security.txt (RFC 9116) in Mass notification and critical events
It tells a researcher where to report a vulnerability instead of guessing.
4 of 39 companies we measured here publish it, that is 10%. Last checked 2026-10-17.
10% here against 11% across every category we measure. Mass notification and critical events sits below the overall share for this criterion.
This page counts companies, not product entries: a company with two products in this category is one company here and two rows below.
Back to security.txt (RFC 9116) across all categories, or to Mass notification and critical events.
- Found4
- Not found at checked addresses35
- Not measured2
41 companies in total. Unmeasured companies are excluded from the published share.
Published
Served at /.well-known/security.txt.
| Vendor | What we found |
|---|---|
| Divera 247 | https://divera247.com/.well-known/security.txtChecked |
| F24 | https://f24.com/.well-known/security.txtChecked |
| Raptor Technologies | https://raptortech.com/.well-known/security.txtChecked |
| Zello | https://zello.com/.well-known/security.txtChecked |
No security.txt found.
We reached at least one address for each of these vendors and none of them carried it. That is what we found at the addresses we checked, on the date we checked them, and not a statement about what the vendor has.
| Vendor | What we found |
|---|---|
| 911Cellular | 1 address checkedChecked |
| Active911 | 1 address checkedChecked |
| Agility Recovery | 1 address checkedChecked |
| AlertMedia | 1 address checkedChecked |
| Alertus | 1 address checkedChecked |
| ATI Systems | 1 address checkedChecked |
| Bryx | 1 address checkedChecked |
| CallingPost | 1 address checkedChecked |
| Connect Rocket | 1 address checkedChecked |
| CrisisGo | 1 address checkedChecked |
| D4H | 1 address checkedChecked |
| DialMyCalls | 1 address checkedChecked |
| Educational Message Services | 1 address checkedChecked |
| Fireboard | 1 address checkedChecked |
| Genasys | 1 address checkedChecked |
| GroupAlarm | 1 address checkedChecked |
| Hyper-Reach | 1 address checkedChecked |
| IamResponding | 1 address checkedChecked |
| Intersec | 1 address checkedChecked |
| Intrado | 1 address checkedChecked |
| Juvare | 1 address checkedChecked |
| Klaxon | 1 address checkedChecked |
| Mobile Text Alerts | 1 address checkedChecked |
| Navigate360 | 1 address checkedChecked |
| Noggin | 1 address checkedChecked |
| Omnilert | 1 address checkedChecked |
| Perimeter | 1 address checkedChecked |
| Rapid Recall | 1 address checkedChecked |
| Regroup | 1 address checkedChecked |
| Singlewire | 1 address checkedChecked |
| Status Solutions | 1 address checkedChecked |
| Text-Em-All | 1 address checkedChecked |
| Titan HST | 1 address checkedChecked |
| Veoci | 1 address checkedChecked |
| Visiplex | 1 address checkedChecked |
Not measured
We could not look at these, or their robots.txt asks us not to. That says something about our measurement, not about them, and they are left out of the percentage above.
| Vendor | What we found |
|---|---|
| DeskAlerts | The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked |
| SnapComms | The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured.Checked |
Other criteria in Mass notification and critical events
- Data processing agreement
- Subprocessor list
- Data location stated
- Status page with history
- Public pricing
- Certifications named
- Uptime SLA with a figure
- HTTPS enforced with HSTS
- No third-party tracking before consent
- Notice before subprocessors change
- Named privacy contact
security.txt (RFC 9116) in related categories
Found something we missed? Tell us. A correction moves that vendor into our next nightly run. That run reads the same fixed addresses we check for every vendor, not the address you send.