I think it would be possible to make a clock that does not rely on judgments as inputs (although has judgements as rules)
You mention a couple
- Status of root DNSServers
But we could come up with more (I suspect around 50 metrics would be comprehensive)
- Ratio of servers reachable by http vs https
- Ratio of servers hosted in countries with mature legal frameworks (needs work)
- Ratio of devices able to reach "representative servers" (ie can your device in beijing reach bbc news and WeChat and Russian newspaper)
- Ratio of devices in areas with "24 hour" electricity supply
- ratio of servers that do not have basic security holes plugged
- ratio of devices that have uptodate security patches
- current volume of DDOS attacks
- Number of successful ransomware attacks per day
- number of networks only reachable through N pipes (ie resilience to network failure)
I would be interested in any thoughts / extras / improvements
You mention a couple
- Status of root DNSServers
But we could come up with more (I suspect around 50 metrics would be comprehensive)
- Ratio of servers reachable by http vs https - Ratio of servers hosted in countries with mature legal frameworks (needs work) - Ratio of devices able to reach "representative servers" (ie can your device in beijing reach bbc news and WeChat and Russian newspaper)
- Ratio of devices in areas with "24 hour" electricity supply
- ratio of servers that do not have basic security holes plugged
- ratio of devices that have uptodate security patches
- current volume of DDOS attacks
- Number of successful ransomware attacks per day
- number of networks only reachable through N pipes (ie resilience to network failure)
I would be interested in any thoughts / extras / improvements