Unverified50% confidenceFactExact time
The SVCB parser covers all standard SvcParamKey values defined in RFC 9460 §6, including alpn, port, ipv4hint, ipv6hint, ech, dohpath, ohttp, mandatory and others.
1
Sources
50%
Confidence
Long-term
Relevance
10/18/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe SVCB resolution endpoint complements the existing TLS-layer ECH probing endpoint: the latter reads ECHConfig from the TLS extension, while the new endpoint resolves SVCB records from the DNS layer.62% similarUnverifiedIn the MP_REACH_NLRI attribute, the AFI identifies the address family (1=IPv4, 2=IPv6), and the SAFI identifies the sub-address family (1=unicast, 128=VPN, etc.).57% similarUnverifiedQuarkDash supports deterministic key derivation, deriving keys from a master key, salt, and version number, so the database only needs to store metadata such as the salt, version, and KDF parameters.55% similarUnverifiedvLLM's --api-key only takes effect for endpoints under the path prefixes /v1, /v2, /inference and /cohere; other endpoints have no authentication enforcement.55% similarUnverifiedPostgreSQL's authentication method is determined by pg_hba.conf, with common ones including trust, md5, scram-sha-256, peer, etc.54% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1061951API
curl https://kongchang.com/api/v1/knowledge/claims/1061951MCP
get_claim(id=1061951)