The Transmission Control Protocol (TCP) header includes optional parameter fields designed to extend performance and reliability across high-bandwidth networks. Defined in RFC 1323 (later updated by RFC 7323), the TCP Timestamps option embeds a 10-to-12-byte timestamp field into each transmitted packet header. This enables two critical transport capabilities: accurate Round-Trip Time Measurement (RTTM) and Protection Against Wrapped Sequence Numbers (PAWS). However, on modern broadband connections and enterprise networks, administrators often face trade-offs between protocol reliability, security fingerprinting risks, and packet overhead. This article explains how to inspect, configure, and validate TCP Timestamps across network profiles in Windows 11 using PowerShell.
Understanding TCP Timestamps (RFC 1323) Architecture
The TCP Timestamps option operates by adding two 32-bit values to the TCP header options field:
- Timestamp Value (TSval): Set by the sending host to a monotonic clock value reflecting when the packet was dispatched.
- Timestamp Echo Reply (TSecr): Echoed back by the receiving host in its acknowledgement (ACK) frame, reflecting the timestamp of the last received data packet.
This timestamp exchange provides significant performance and diagnostic benefits:
- Accurate RTT Measurement (RTTM): Rather than sampling RTT once per transmission window, TCP Timestamps allow the sender to calculate precise round-trip times for every acknowledged packet, improving congestion window responsiveness and timeout accuracy.
- Protection Against Wrapped Sequence Numbers (PAWS): On multi-gigabit connections (such as 10GbE or 25GbE links), TCP’s 32-bit sequence numbers can wrap around (exceeding 4.29 billion bytes) within seconds. PAWS uses timestamps to distinguish between old duplicate packets lingering in network queues and newly transmitted packets sharing identical sequence numbers, preventing data corruption.
- Security and Fingerprinting Considerations: Because the timestamp value increments at a constant frequency linked to system uptime, remote network scanners (such as Nmap) can analyze timestamp progression to deduce the exact uptime and reboot schedule of an unpatched Windows machine. Consequently, security compliance standards frequently mandate disabling timestamps on internet-facing workstations.
Inspecting Current TCP Timestamp Configuration in Windows 11
To inspect whether TCP Timestamps are enabled on your system, launch an elevated Windows PowerShell console (Run as Administrator) and execute Get-NetTCPSetting:
Get-NetTCPSetting | Select-Object SettingName, Timestamps, AutoTuningLevelLocal, CongestionProvider
To view detailed properties specifically for the standard Internet transport profile, run:
Get-NetTCPSetting -SettingName "Internet" | Format-List SettingName, Timestamps, MinRtoMs, InitialCongestionWindowMss
Review the Timestamps property. In Windows 11, timestamps are typically set to Disabled on client editions to conserve header bandwidth (12 bytes per packet) and mitigate remote uptime reconnaissance, while server environments often maintain them enabled for high-speed throughput.
Enabling TCP Timestamps for High-Throughput Networks
On local enterprise networks, datacenter fabrics, and high-bandwidth fiber links where maximum throughput and PAWS protection are required, enable TCP Timestamps using Set-NetTCPSetting:
Set-NetTCPSetting -SettingName "Internet" -Timestamps Enabled
To enable timestamps across all defined network profiles (including Datacenter, Compat, and Custom), pipe the query directly into the setting cmdlet:
Get-NetTCPSetting | Set-NetTCPSetting -Timestamps Enabled
The configuration change is applied dynamically to the Windows kernel TCP/IP stack without requiring a system restart. Newly negotiated TCP connections will include timestamp options during the initial SYN handshake.
Disabling TCP Timestamps for Security Hardening
If your organization enforces strict perimeter defense guidelines to prevent external network mapping and uptime fingerprinting, disable TCP Timestamps across all client profiles:
Get-NetTCPSetting | Set-NetTCPSetting -Timestamps Disabled
Disabling timestamps removes the 12-byte option overhead from every outbound packet header, slightly maximizing payload space within standard 1500-byte MTU frames while ensuring remote scanners cannot calculate host uptime.
Verifying Registry Persistence and Active Transport State
Confirm that the driver has successfully updated the active profile configuration:
Get-NetTCPSetting -SettingName "Internet" | Select-Object SettingName, Timestamps
To verify the low-level TCP parameters stored within the Windows Registry, inspect the TCP/IP parameters hive:
Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters" -Name "Tcp1323Opts" -ErrorAction SilentlyContinue
In the legacy registry model, Tcp1323Opts values correspond to: 0 (Disabled), 1 (Window Scaling only), 2 (Timestamps only), or 3 (Both Window Scaling and Timestamps enabled).
Validating Timestamp Headers in Active Packets
To verify that outbound connections negotiate RFC 1323 timestamps in practice:
- Initiate a connection to a remote web server or run a network file transfer.
- Capture live traffic using a network protocol analyzer (such as Wireshark) or PowerShell packet capture (
New-NetEventSession). - Inspect the TCP header options of an outbound SYN packet. You will observe
Kind: 8 (Timestamp)containing theTSvalandTSecrfields.
By tailoring TCP Timestamps via PowerShell, Windows 11 administrators can effectively balance high-speed data integrity against security hardening requirements across their environments.