From the source
Meta has added authenticated time to its public time service by supporting Network Time Security (NTS, RFC 8915) at nts.meta.com, letting devices verify that time packets came from Meta and were not tampered with.
- The company says unauthenticated NTP has been a security weak point since 1985, because every certificate, token and signature check depends on the local clock being correct.
- Meta's NTS servers hold no per-client state: cookie keys are derived from a shared master secret and the current day, not stored or replicated.
- Meta has open-sourced the protocol, server and client through its Time library on
GitHub and is encouraging NTP client maintainers on Android and iOS to enable NTS support.






