ClientHello
E893550
ClientHello is the initial message sent by a client in the TLS handshake to propose security parameters and initiate a secure connection with a server.
All labels observed (1)
| Label | Occurrences |
|---|---|
| ClientHello canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10927063 — 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: ClientHello Context triple: [ServerHello with extensions, followsMessage, 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.
ALPN (Application-Layer Protocol Negotiation)
ALPN (Application-Layer Protocol Negotiation) is a TLS extension that allows clients and servers to agree on which application-layer protocol (such as HTTP/2 or SPDY) to use over a secure connection during the TLS handshake.
-
C.
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.
-
D.
Server Name Indication extension
The Server Name Indication (SNI) extension is a TLS protocol feature that allows a client to indicate the hostname it is trying to connect to at the start of the handshake so that the server can present the correct certificate for virtual hosting.
-
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: ClientHello Target entity description: ClientHello is the initial message sent by a client in the TLS handshake to propose security parameters and initiate a secure connection with a 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.
ALPN (Application-Layer Protocol Negotiation)
ALPN (Application-Layer Protocol Negotiation) is a TLS extension that allows clients and servers to agree on which application-layer protocol (such as HTTP/2 or SPDY) to use over a secure connection during the TLS handshake.
-
C.
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.
-
D.
Server Name Indication extension
The Server Name Indication (SNI) extension is a TLS protocol feature that allows a client to indicate the hostname it is trying to connect to at the start of the handshake so that the server can present the correct certificate for virtual hosting.
-
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 (55)
| Predicate | Object |
|---|---|
| instanceOf |
TLS handshake message
ⓘ
protocol data unit ⓘ |
| canInclude |
ALPN protocol list
ⓘ
OCSP stapling request ⓘ SNI hostname ⓘ heartbeat extension ⓘ max_fragment_length extension ⓘ record_size_limit extension ⓘ session resumption parameters ⓘ |
| containsField |
application_layer_protocol_negotiation extension
ⓘ
cipher_suites ⓘ compression_methods ⓘ extensions ⓘ key_share extension ⓘ legacy_compression_methods (TLS 1.3) ⓘ legacy_session_id (TLS 1.3) ⓘ legacy_version (TLS 1.3) ⓘ pre_shared_key extension ⓘ protocol version ⓘ psk_key_exchange_modes extension ⓘ random ⓘ renegotiation_info extension ⓘ server_name extension ⓘ session_id ⓘ session_ticket extension ⓘ signature_algorithms extension ⓘ supported_groups extension ⓘ supported_versions extension ⓘ |
| definedInStandard |
SSL 3.0
ⓘ
TLS 1.0 ⓘ TLS 1.1 ⓘ TLS 1.2 ⓘ TLS 1.3 ⓘ
linked to:
RFC 8446
|
| followedBy |
ServerHello
ⓘ
linked to:
ServerHello with extensions
|
| followsMessageType |
handshake message type 1 in TLS 1.2
ⓘ
handshake message type 1 in TLS 1.3 ⓘ |
| includesValue |
client_random
ⓘ
list of supported TLS versions ⓘ list of supported cipher suites ⓘ list of supported compression methods ⓘ list of supported extensions ⓘ |
| purpose |
initiate secure connection
ⓘ
propose security parameters ⓘ |
| roleInProtocol | initiates TLS handshake ⓘ |
| securityProperty |
contributes to downgrade protection in TLS 1.3 via supported_versions
ⓘ
contributes to key establishment ⓘ does not provide confidentiality by itself ⓘ |
| sentBy | TLS client ⓘ |
| sentTo | TLS server ⓘ |
| specifiedIn |
RFC 5246
ⓘ
RFC 8446 ⓘ |
| usedIn |
HTTPS
ⓘ
IMAP over TLS ⓘ SMTP over TLS ⓘ any TLS-based protocol ⓘ |
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: ClientHello Description of subject: ClientHello is the initial message sent by a client in the TLS handshake to propose security parameters and initiate a secure connection with a server.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.