HTTP Strict Transport Security (HSTS)
Open accessThe DOI matches its Crossref record; 29 of the 32 references it cites were found in a registry or an index.
Abstract
This specification defines a mechanism enabling web sites to declare themselves accessible only via secure connections and/or for users to be able to direct their user agent(s) to interact with given sites only over secure connections.This overall policy is referred to as HTTP Strict Transport Security (HSTS).The policy is declared by web sites via the Strict-Transport-Security HTTP response header field and/or by other means, such as user agent configuration, for example.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Key words for use in RFCs to Indicate Requirement Levels
Bradner, S. (1997) · doi:10.17487/rfc2119 · Cited by 2,997
The Transport Layer Security (TLS) Protocol Version 1.3
Rescorla, E. (2018) · doi:10.17487/rfc8446 · Cited by 1,897
Domain names - implementation and specification
Mockapetris, P. V. (1987) · doi:10.17487/rfc1035 · Cited by 1,698
Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
Cooper, D., Santesson, S., Farrell, S., Boeyen, S., Housley, R., & Polk, W. (2008) · doi:10.17487/rfc5280 · Cited by 1,075
Uniform Resource Identifier (URI): Generic Syntax
Berners-Lee, T., Fielding, R., & Masinter, L. (2005) · doi:10.17487/rfc3986 · Cited by 815
DNS Security Introduction and Requirements
Arends, R., Austein, R., Larson, M., Massey, D., & Rose, S. (2005) · doi:10.17487/rfc4033 · Cited by 685
Network Time Protocol Version 4: Protocol and Algorithms Specification
Mills, D., Burbank, J., & Kasch, W. (2010) · doi:10.17487/rfc5905 · Cited by 577
Guidelines for Writing an IANA Considerations Section in RFCs
Narten, T., & Alvestrand, H. (2008) · doi:10.17487/rfc5226 · Cited by 469
X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP
Myers, M., Ankney, R., Malpani, A., Galperin, S., & Adams, C. (1999) · doi:10.17487/rfc2560 · Cited by 448
Hypertext Transfer Protocol -- HTTP/1.1
Fielding, R., Gettys, J., Mogul, J., Frystyk, H., & Berners-Lee, T. (1997) · doi:10.17487/rfc2068 · Cited by 370
Research works printed but not linked: 3
- [ForceHTTPS] Jackson, C. and A. Barth, "ForceHTTPS: Protecting High- Security Web Sites from Network Attacks", In Proceedings of the 17th International World Wide Web Conference (WWW2008) , 2008, <https://crypto.stanford.edu/forcehttps/>.
- [GoodDhamijaEtAl05] Good, N., Dhamija, R., Grossklags, J., Thaw, D., Aronowitz, S., Mulligan, D., and J. Konstan, "Stopping Spyware at the Gate: A User Study of Privacy, Notice and Spyware", In Proceedings of Symposium On Usable Privacy and Security (SOUPS) Pittsburgh, PA, USA, July 2005, <http://www.law.berkeley.edu/files/ Spyware_at_the_Gate.pdf>.
- [JacksonBarth2008] Jackson, C. and A. Barth, "Beware of Finer-Grained Origins", Web 2.0 Security and Privacy Workshop, Oakland, CA, USA, 2008, <http://seclab.stanford.edu/websec/origins/fgo.pdf>.
Cited by
A Survey of Man in the Middle Attacks
Conti, M., Dragoni, N., & Lesyk, V. (2016) · IEEE Communications Surveys & Tutorials · doi:10.1109/comst.2016.2548426 · Cited by 724
“Similar solution is HTTP Strict Transport Security (HSTS) [155], a proposal which allows websites to instruct browsers to make SSL/TLS connections mandatory on their sites.”
MethodSecurity issues in cloud environments: a survey
Fernandes, D. A. B., Soares, L. F. B., Gomes, J. V., Freire, M. M., & Inácio, P. R. M. (2014) · International Journal of Information Security · doi:10.1007/s10207-013-0208-7 · Cited by 494
“More recently, the HyperText Transport Protocol Strict Transport Security (HSTS) is currently under proposed standard on the Request for Comments (RFC) 6797 [111], which consists of a mechanism to declare websites accessible only under secure connections or to instruct user agents only to interact with websites under…”
Third-Party Web Tracking: Policy and Technology
Mayer, J. R., & Mitchell, J. C. (2012) · 2012 IEEE Symposium on Security and Privacy · doi:10.1109/sp.2012.47 · Cited by 492
“name property∗ (session only) HTTP strict transport security [90] plug-in storage∗ (e.”
BackgroundTriple Handshakes and Cookie Cutters: Breaking and Fixing Authentication over TLS
Bhargavan, K., Lavaud, A. D., Fournet, C., Pironti, A., & Strub, P. Y. (2014) · 2014 IEEE Symposium on Security and Privacy · doi:10.1109/sp.2014.14 · Cited by 173
“To protect against SSL stripping, several browsers support HTTP Strict Transport Security [30] (HSTS), which introduces a Strict-Transport-Security header for websites to indicate that the browser should always connect to its domain over TLS, regardless of the port.”
MethodA Survey on Web Tracking: Mechanisms, Implications, and Defenses
Bujlow, T., Carela-Español, V., Lee, B.-R., & Barlet‐Ros, P. (2017) · Proceedings of the IEEE · doi:10.1109/jproc.2016.2637878 · Cited by 157
“When a user visits websites in the HSTS mode, for each of the subdomains, a single entry is made in the HSTS database on the user’s computer.”
MethodInfluential
Metadata
- Authors
- Hodges, J., Jackson, C., & Barth, A.
- Affiliations
- Carnegie Mellon University (US)
- Publisher
- RFC Editor
- Published
- 2012-11
- OpenAlex
- W2300554752
- Cited by
- 198
- References
- 32
- Citations by year
- 2026: 5 · 2025: 6 · 2024: 8 · 2023: 10 · 2022: 11 · 2021: 9 · 2020: 18 · 2019: 8 · 2018: 21 · 2017: 12 · 2016: 16 · 2015: 27 · 2014: 19 · 2013: 15 · 2012: 7
- Type
- report
- Language
- en
- Open access
- gold
- doi.org
- Topics
- Physical Sciences › Computer Science › Information Systems › Web Application Security Vulnerabilities
- Physical Sciences › Computer Science › Information Systems › Mobile and Web Applications
- Social Sciences › Sociology and Political Science › Privacy, Security, and Data Protection
- Keywords
- highstand systems tract, HTTPS, secure connections
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: HTTP Strict Transport Security (HSTS). https://app.cochat.ai/papers/10.17487/rfc6797
- The paper
- Hodges, J., Jackson, C., & Barth, A. (2012). HTTP Strict Transport Security (HSTS). https://doi.org/10.17487/rfc6797
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.