Unverified50% confidenceCautionExact time
An HTTP request's User-Agent must be identifiable and include contact information; masquerading as Chrome may bypass a WAF but violates crawling etiquette.
1
Sources
50%
Confidence
Long-term
Relevance
10/18/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe User-Agent field in HTTP requests is declared by the client itself; the HTTP protocol has not introduced any authentication mechanism for this field, and anyone can freely forge it.77% similarUnverifiedUser-Agent identification is when a server reads the client identifier in the HTTP request header to determine the type of visitor, but this field can be forged, so it is often combined with behavioral fingerprints (such as mouse trajectories, request timing, and TLS fingerprints).69% similarUnverified企业系统鉴权中，Token 通常以 Authorization: Bearer <token> 的形式携带在 HTTP 请求头中68% similarUnverifiedUser-agent is a string field in the HTTP request header filled in by the client itself, with virtually zero cost to forge, so blocking based on user agent alone is unreliable and needs to be combined with IP verification68% similarUnverifiedAny contact that proactively reaches out to you and asks for passwords, verification codes, or identity documents should be regarded as suspicious, and verification should always be done through the official app or by manually typing the official website address.65% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1062902API
curl https://kongchang.com/api/v1/knowledge/claims/1062902MCP
get_claim(id=1062902)