Essential Japan Tech
Japan edge node — infrastructure notes TLS 1.3 · h1 / h2 · no h3
Scope
This node is an edge relay. It serves this page and terminates TLS for one private application endpoint used by managed client software. There is no public API, no directory listing and no search-engine indexing.
Endpoints
| Path | Purpose | Behaviour |
|---|---|---|
/ | This document | Static, Cache-Control: no-store |
<undocumented> | Client sync stream | Not enumerable; requires a provisioned credential; unbuffered end to end |
| anything else | Falls through to the static handler | 200 for /, 404 for unknown files |
Path names and credentials for the private endpoint are distributed out of band and are deliberately absent from this page.
Transport
- ALPN offers
h2thenhttp/1.1. HTTP/3/QUIC is not served. - Certificate is issued by Let's Encrypt and renewed automatically by the web server.
- Cleartext requests on TCP/80 are redirected to HTTPS and also carry ACME challenge traffic.
- UDP/443 is closed by perimeter policy — do not attempt QUIC.
- Reverse-proxy forwarding headers are stripped on the private handler.
- HSTS is published with
includeSubDomains; expect it on subsequent visits.
Operational notes
- Health check:
GET /over HTTPS, expect HTTP 200 and a Let's Encrypt chain. - Long-lived streams are expected; idle connections are reaped by the client, not the relay.
- MTU/fragmentation issues show up as stalled streams, not as refused connections.