Unverified50% confidenceFactExact time
GET /api/quic-0rtt-replay-risk?host=<HOST> sends a hand-crafted QUIC Initial packet conforming to RFC 9000 §17.2 to the target's UDP/443 port, detects the stateless Retry mechanism, infers whether an anti-replay token exists, and heuristically judges 0-RTT support via TLS 1.3 ALPN=h3 and Alt-Svc=quic.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/17/2026
First Seen
Valid until: 1/15/2027
Sources
Related Entities
Related Claims
UnverifiedFCC has a built-in automatic failover mechanism: when a provider returns a 429, 503, or timeout error, the proxy immediately reroutes the request to the next available node in the backup provider list, transparently to the upper-layer Coding Agent.62% similarUnverifiedVite listens on port 5173 by default, and when multiple agents run simultaneously without port isolation, EADDRINUSE port conflict errors will occur.60% similarUnverifiedWhen a port scan detects that the target has port 3306 (MySQL's default port) open, it is flagged as a risk; however, the port may actually be unreachable from the external network due to access control whitelists, WAF, or cloud security group rules, resulting in a false positive.59% similarUnverified0.65.4 is a security backport for the stable branch.59% similarUnverifiedPorts published by Docker bypass ufw firewall rules by default, directly exposing ports by writing DNAT and FORWARD rules into iptables' nat table and filter table.59% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1053693API
curl https://kongchang.com/api/v1/knowledge/claims/1053693MCP
get_claim(id=1053693)