Perf regression: antiforgery-validation, kestrel-header-symbols, tls-handshakes-kestrel

| Scenario | Environment | Date | Old RPS | New RPS | Change | Deviation | StDev | Dependencies |
| -------- | ----------- | ---- | ------- | ------- | ------ | --------- | ----- | ------------ |
| antiforgery-validation [Fixed] | Antiforgery Token Validation 11- Trends idna-intel-lin | 07/22/2026 10:30:08 | 41,244 | 39,108 | -5.18 % (-2,137) :thumbsdown: | -5.35 σ | 399.29 | Changes NameVersionDiff |
| kestrel-header-symbols | Kestrel Linux: Invalid Header 10- Trends idna-amd-lin | 07/21/2026 10:06:45 | 1,278 | 1,244 | -100.00 % (-34) :thumbsdown: | -2.26 σ | 15.07 | Changes NameVersionDiff |
| tls-handshakes-kestrel | Kestrel Linux: TLS Handshakes 10- Trends idna-amd-lin | 07/21/2026 10:01:25 | 1,415 | 1,382 | -100.00 % (-33) :thumbsdown: | -2.64 σ | 12.51 | Changes NameVersionDiff |

[PowerBI Dashboard](https://aka.ms/aspnet/benchmarks)

@sebastienros

Start with the three benchmark scenarios listed in the issue and compare their old and new runs through the linked PowerBI Dashboard. Trace the dependency and environment differences first; done means the reported performance regression is explained and the affected benchmark results are corrected or confirmed.

Written by the indexing model from the issue text.