Google’s HTTPS infrastructure
E878875
Google’s HTTPS infrastructure is the large-scale, secure web transport system that encrypts and protects users’ connections to Google services across the internet.
All labels observed (1)
| Label | Occurrences |
|---|---|
| Google’s HTTPS infrastructure canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10682104 — 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: Google’s HTTPS infrastructure Context triple: [Adam Langley, contributedTo, Google’s HTTPS infrastructure]
-
A.
Google’s global edge network
Google’s global edge network is a worldwide infrastructure of distributed data centers and points of presence that delivers low-latency, high-performance connectivity and security services for Google and Google Cloud customers.
-
B.
Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access
"Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access" (RFC 8314) is an IETF standards-track document that recommends and defines best practices for using TLS to secure email submission and retrieval protocols instead of unencrypted connections.
-
C.
Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS)
"Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS)" is an IETF standard (RFC 7919) that defines secure, standardized finite-field Diffie-Hellman parameter sets for use in TLS to improve cryptographic security and interoperability.
-
D.
AT-TLS (Application Transparent TLS)
AT-TLS (Application Transparent TLS) is an IBM z/OS networking function that transparently provides TLS encryption and decryption for application traffic without requiring changes to the applications themselves.
-
E.
DNS over DTLS
DNS over DTLS is a protocol that secures DNS queries using Datagram Transport Layer Security over UDP, providing encryption and integrity while preserving DNS’s low-latency, connectionless nature.
- 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: Google’s HTTPS infrastructure Target entity description: Google’s HTTPS infrastructure is the large-scale, secure web transport system that encrypts and protects users’ connections to Google services across the internet.
-
A.
Google’s global edge network
Google’s global edge network is a worldwide infrastructure of distributed data centers and points of presence that delivers low-latency, high-performance connectivity and security services for Google and Google Cloud customers.
-
B.
Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access
"Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access" (RFC 8314) is an IETF standards-track document that recommends and defines best practices for using TLS to secure email submission and retrieval protocols instead of unencrypted connections.
-
C.
Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS)
"Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS)" is an IETF standard (RFC 7919) that defines secure, standardized finite-field Diffie-Hellman parameter sets for use in TLS to improve cryptographic security and interoperability.
-
D.
AT-TLS (Application Transparent TLS)
AT-TLS (Application Transparent TLS) is an IBM z/OS networking function that transparently provides TLS encryption and decryption for application traffic without requiring changes to the applications themselves.
-
E.
DNS over DTLS
DNS over DTLS is a protocol that secures DNS queries using Datagram Transport Layer Security over UDP, providing encryption and integrity while preserving DNS’s low-latency, connectionless nature.
- F. None of above. chosen
Statements (54)
| Predicate | Object |
|---|---|
| instanceOf |
transport layer security deployment
ⓘ
web security infrastructure ⓘ |
| compliesWith | industry TLS best practices (at time of deployment) ⓘ |
| designedFor |
high availability
ⓘ
low latency ⓘ resilience to failures ⓘ |
| evolvedFrom | earlier Google SSL deployments ⓘ |
| integratesWith |
Google DDoS protection systems
NERFINISHED
ⓘ
Google identity and access management systems NERFINISHED ⓘ Google load balancing systems NERFINISHED ⓘ |
| maintainedBy | Google LLC NERFINISHED ⓘ |
| monitoredBy | Google Site Reliability Engineering NERFINISHED ⓘ |
| protects | connections to Google services ⓘ |
| purpose |
encrypt web traffic between users and Google
ⓘ
provide authentication ⓘ provide confidentiality ⓘ provide integrity ⓘ |
| runsOn |
Google Front End
NERFINISHED
ⓘ
Google data centers NERFINISHED ⓘ Google edge points of presence NERFINISHED ⓘ |
| scale |
global
ⓘ
handles millions of requests per second ⓘ serves billions of users ⓘ |
| supportsClient |
API clients
ⓘ
mobile apps ⓘ web browsers ⓘ |
| supportsFeature |
HSTS
NERFINISHED
ⓘ
OCSP stapling ⓘ TLS session resumption ⓘ certificate pinning on some clients ⓘ forward secrecy ⓘ |
| supportsService |
Android device services
ⓘ
Gmail NERFINISHED ⓘ Google Cloud Platform NERFINISHED ⓘ Google Drive NERFINISHED ⓘ Google Maps NERFINISHED ⓘ Google Photos NERFINISHED ⓘ Google Play NERFINISHED ⓘ Google Search NERFINISHED ⓘ Google Workspace NERFINISHED ⓘ YouTube NERFINISHED ⓘ |
| usesCertificateAuthority |
Google Trust Services
NERFINISHED
ⓘ
external public certificate authorities ⓘ |
| usesCryptography |
message authentication codes
ⓘ
public key cryptography ⓘ symmetric encryption ⓘ |
| usesKeyManagement |
automated certificate rotation
ⓘ
ephemeral session keys ⓘ hardware security modules ⓘ |
| usesProtocol |
HTTP/2
ⓘ
HTTP/3 ⓘ HTTPS ⓘ QUIC NERFINISHED ⓘ TLS NERFINISHED ⓘ |
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: Google’s HTTPS infrastructure Description of subject: Google’s HTTPS infrastructure is the large-scale, secure web transport system that encrypts and protects users’ connections to Google services across the internet.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.