TLS ClientHello
E893545
TLS ClientHello is the initial message a client sends in a TLS handshake to propose security parameters and capabilities to the server.
All labels observed (1)
| Label | Occurrences |
|---|---|
| TLS ClientHello canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10926898 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TLS ClientHello Context triple: [Max Fragment Length extension, usedIn, TLS ClientHello]
-
A.
ServerHello with extensions
ServerHello with extensions is a TLS handshake message variant that allows a server to include additional extension data to negotiate optional protocol features and capabilities with a client.
-
B.
TLS heartbeat extension (later deprecated)
The TLS heartbeat extension was a Transport Layer Security protocol feature designed to keep secure connections alive and test reachability, later becoming widely known for the critical Heartbleed vulnerability that led to its deprecation.
-
C.
TLS 1.2 Finished message
The TLS 1.2 Finished message is the protocol’s final handshake message that proves both parties share the same session keys and that the preceding handshake messages have not been tampered with.
-
D.
TLS-over-TCP
TLS-over-TCP is a secure communication method that encrypts data using the Transport Layer Security (TLS) protocol on top of the reliable Transmission Control Protocol (TCP).
-
E.
TLS 1.2
TLS 1.2 is a widely deployed version of the Transport Layer Security protocol that provides encrypted and authenticated communication over computer networks.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: TLS ClientHello Target entity description: TLS ClientHello is the initial message a client sends in a TLS handshake to propose security parameters and capabilities to the server.
-
A.
ServerHello with extensions
ServerHello with extensions is a TLS handshake message variant that allows a server to include additional extension data to negotiate optional protocol features and capabilities with a client.
-
B.
TLS heartbeat extension (later deprecated)
The TLS heartbeat extension was a Transport Layer Security protocol feature designed to keep secure connections alive and test reachability, later becoming widely known for the critical Heartbleed vulnerability that led to its deprecation.
-
C.
TLS 1.2 Finished message
The TLS 1.2 Finished message is the protocol’s final handshake message that proves both parties share the same session keys and that the preceding handshake messages have not been tampered with.
-
D.
TLS-over-TCP
TLS-over-TCP is a secure communication method that encrypts data using the Transport Layer Security (TLS) protocol on top of the reliable Transmission Control Protocol (TCP).
-
E.
TLS 1.2
TLS 1.2 is a widely deployed version of the Transport Layer Security protocol that provides encrypted and authenticated communication over computer networks.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
TLS protocol message
ⓘ
handshake message ⓘ |
| definedIn |
RFC 5246
ⓘ
RFC 8446 ⓘ |
| followedBy |
TLS ServerHello
ⓘ
linked to:
ServerHello with extensions
|
| hasField |
cipher_suites
ⓘ
client_version ⓘ compression_methods ⓘ extensions ⓘ random ⓘ session_id ⓘ |
| hasRole | initiates TLS handshake from client side ⓘ |
| includes |
ALPN extension (Application-Layer Protocol Negotiation) when supported
ⓘ
SNI extension (Server Name Indication) when virtual hosting is used ⓘ client random value ⓘ key_share extension in TLS 1.3 ⓘ list of supported TLS versions ⓘ list of supported cipher suites ⓘ list of supported compression methods ⓘ signature_algorithms extension in modern TLS ⓘ supported_groups extension in modern TLS ⓘ supported_versions extension in TLS 1.3 ⓘ |
| layer | transport layer security ⓘ |
| mayInclude |
session resumption identifiers
ⓘ
session tickets ⓘ |
| occursBefore |
Finished messages in TLS handshake
ⓘ
certificate exchange in TLS handshake ⓘ |
| partOf | TLS handshake ⓘ |
| proposes |
TLS extensions
ⓘ
TLS protocol version ⓘ cipher suites ⓘ compression methods ⓘ |
| securityProperty |
does not itself provide confidentiality
ⓘ
is sent in cleartext over the underlying transport ⓘ |
| sentBy | TLS client ⓘ |
| sentTo | TLS server ⓘ |
| transportedOver |
QUIC (in TLS 1.3-based QUIC)
ⓘ
linked to:
QUIC
TCP ⓘ
linked to:
Transmission Control Protocol
|
| usedFor |
advertising client capabilities
ⓘ
negotiating security parameters ⓘ starting key exchange ⓘ |
| usedInProtocol |
SSL 3.0
ⓘ
TLS 1.0 ⓘ TLS 1.1 ⓘ TLS 1.2 ⓘ TLS 1.3 ⓘ
linked to:
RFC 8446
Transport Layer Security ⓘ
linked to:
TLS
|
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: TLS ClientHello Description of subject: TLS ClientHello is the initial message a client sends in a TLS handshake to propose security parameters and capabilities to the server.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.