tls-devicer
    Preparing search index...

    Interface TlsProfile

    Passively collected TLS / network signals for a single request. All fields optional — gracefully scored when partially available.

    interface TlsProfile {
        cipherSuites?: number[];
        ellipticCurves?: number[];
        extensions?: number[];
        headerOrder?: string[];
        headerValues?: Record<string, string>;
        http2Settings?: Http2SettingsMap;
        ja3?: string;
        ja3s?: string;
        ja4?: string;
        pointFormats?: number[];
    }
    Index

    Properties

    cipherSuites? ellipticCurves? extensions? headerOrder? headerValues? http2Settings? ja3? ja3s? ja4? pointFormats?

    Properties

    cipherSuites?: number[]

    TLS cipher suite codes in the order sent by the client. GREASE values (0xXAXA patterns) should be stripped before passing.

    ellipticCurves?: number[]

    Supported elliptic curves (named groups)

    extensions?: number[]

    TLS extension type codes in the order encountered in the ClientHello.

    headerOrder?: string[]

    HTTP header names in the order they were received

    headerValues?: Record<string, string>

    Selected stable header values used to detect spoofing. Suggested keys: Accept, Accept-Encoding, Accept-Language, Connection.

    http2Settings?: Http2SettingsMap

    HTTP/2 SETTINGS frame values observed in the connection preface

    ja3?: string

    JA3 fingerprint MD5 string

    ja3s?: string

    JA3S (server-side) fingerprint MD5 string

    ja4?: string

    JA4 fingerprint string (e.g. "t13d1516h2_...")

    pointFormats?: number[]

    Elliptic curve point formats

    Settings

    Member Visibility

    On This Page

    Properties