Does NextDNS Publish an Authoritative SPKI Pinset?

I’m using NextDNS with DNS-over-TLS/QUIC and am evaluating whether to enforce an SPKI/public-key pin in addition to normal PKIX certificate and hostname validation.

Does NextDNS publish an authoritative SPKI/public-key pinset, certificate hash set, or other signed/authenticated metadata intended for client-side pinning of dns.nextdns.io or profile-specific endpoints such as 537ca5.dns.nextdns.io?

I noticed that the generated Stubby configuration uses tls_auth_name without tls_pubkey_pinset, and the generated DNSCrypt stamp appears to leave the optional certificate-hash field empty. Is that intentional because PKIX + hostname validation is the recommended authentication model?

If NextDNS does support pinning, where is the authoritative pinset published, how are rotations announced, and does the same pinset apply across DoT, DoQ, DoH2, and DoH3?