help secure Express/Connect apps with various HTTP headers


Helmet helps you secure your Express apps by setting various HTTP headers. It's not a silver bullet, but it can help!

Looking for a version of Helmet that supports the Koa framework?

First, run npm install helmet --save for your app. Then, in an Express (or Connect) app:

var express = require('express')
var helmet = require('helmet')
var app = express()
// ... 

You can also use its pieces individually:


If you're using Express 3, make sure these middlewares are listed before app.router.

Helmet is really just a collection of 10 smaller middleware functions that set HTTP headers:

Running app.use(helmet()) will include 6 of the 10, leaving out contentSecurityPolicy, dnsPrefetchControl, hpkp, and noCache. You can also use each module individually, as documented below.

dnsPrefetchControl is in "beta" right now and will soon become part of the default Helmet middleware.

For each of the middlewares, we'll talk about three things:

  1. What's the attack we're trying to prevent?
  2. How do we use Helmet to help mitigate those issues?
  3. What are the non-obvious limitations of this middleware?

Let's get started.

Trying to prevent: Injecting anything unintended into our page. That could cause XSS vulnerabilities, unintended tracking, malicious frames, and more.

How to use Helmet to mitigate this: Set an appropriate Content Security Policy. If you want to learn how CSP works, check out the fantastic HTML5 Rocks guide and the Content Security Policy Reference.


  // Specify directives as normal. 
  directives: {
    defaultSrc: ["'self'", 'default.com'],
    scriptSrc: ["'self'", "'unsafe-inline'"],
    styleSrc: ['style.com'],
    imgSrc: ['img.com', 'data:'],
    sandbox: ['allow-forms', 'allow-scripts'],
    reportUri: '/report-violation'
    objectSrc: [], // An empty array allows nothing through 
  // Set to true if you only want browsers to report errors, not block them 
  reportOnly: false,
  // Set to true if you want to blindly set all headers: Content-Security-Policy, 
  // X-WebKit-CSP, and X-Content-Security-Policy. 
  setAllHeaders: false,
  // Set to true if you want to disable CSP on Android where it can be buggy. 
  disableAndroid: false

You can specify keys in a camel-cased fashion (imgSrc) or dashed (img-src); they are equivalent.

There are a lot of inconsistencies in how browsers implement CSP. Helmet sniffs the user-agent of the browser and sets the appropriate header and value for that browser. If no user-agent is matched, it will set all the headers with the latest spec.

Note: If you're using the reportUri feature and you're using csurf, you might have errors. Check this out for a workaround.

Limitations: CSP is often difficult to tune properly, as it's a whitelist and not a blacklist. It isn't supported on old browsers but is pretty well-supported on newer browsers.

Trying to prevent: Cross-site scripting attacks (XSS), a subset of the attacks mentioned above.

How to use Helmet to mitigate this: The X-XSS-Protection HTTP header is a basic protection against XSS. It was originally by Microsoft but Chrome has since adopted it as well. Helmet lets you use it easily:


This sets the X-XSS-Protection header. On modern browsers, it will set the value to 1; mode=block. On old versions of Internet Explorer, this creates a vulnerability (see here and here), and so the header is set to 0 to disable it. To force the header on all versions of IE, add the option:

app.use(helmet.xssFilter({ setOnOldIE: true }))
// This has some security problems for old IE! 

Limitations: This isn't anywhere near as thorough as CSP. It's only properly supported on IE9+ and Chrome; no other major browsers support it at this time. Old versions of IE support it in a buggy way, which we disable by default.

Trying to prevent: Your page being put in a <frame> or <iframe> without your consent. This can result in clickjacking attacks, among other things.

How to use Helmet to mitigate this: The X-Frame HTTP header restricts who can put your site in a frame. It has three modes: DENY, SAMEORIGIN, and ALLOW-FROM. If your app does not need to be framed (and most don't) you can use the default DENY. If your site can be in frames from the same origin, you can set it to SAMEORIGIN. If you want to allow it from a specific URL, you can allow that with ALLOW-FROM and a URL.


// Only let me be framed by people of the same origin: 
app.use(helmet.frameguard())  // Same-origin by default. 
// Don't allow anyone to put me in a frame. 
// Allow from a specific host: 
app.use(helmet.frameguard('allow-from', 'http://example.com'))

Limitations: This has pretty good (but not 100%) browser support: IE8+, Opera 10.50+, Safari 4+, Chrome 4.1+, and Firefox 3.6.9+. It only prevents against a certain class of attack, but does so pretty well. It also prevents your site from being framed, which you might want for legitimate reasons.

Trying to prevent: Users viewing your site on HTTP instead of HTTPS. HTTP is pretty insecure!

How to use Helmet to mitigate this: This middleware adds the Strict-Transport-Security header to the response. This tells browsers, "hey, only use HTTPS for the next period of time". (See the spec for more.)

This will set the Strict Transport Security header, telling browsers to visit by HTTPS for the next ninety days:

var ninetyDaysInMilliseconds = 7776000000;
app.use(helmet.hsts({ maxAge: ninetyDaysInMilliseconds }))

You can also include subdomains. If this is set on example.com, supported browsers will also use HTTPS on my-subdomain.example.com. Here's how you do that:

  maxAge: 123000,
  includeSubdomains: true

Chrome lets you submit your site for baked-into-Chrome HSTS by adding preload to the header. You can add that with the following code, and then submit your site to the Chrome team at hstspreload.appspot.com.

  maxAge: 10886400000,     // Must be at least 18 weeks to be approved by Google 
  includeSubdomains: true, // Must be enabled to be approved by Google 
  preload: true

This'll be set if req.secure is true, a boolean auto-populated by Express. If you're not using Express, that value won't necessarily be set, so you have two options:

// Set the header based on silly conditions 
  maxAge: 1234000,
  setIffunction(reqres) {
    return Math.random() < 0.5;
// ALWAYS set the header 
  maxAge: 1234000,
  force: true

Note that the max age is in milliseconds, even though the spec uses seconds. This middleware will round to the nearest full second.

Limitations: This only works if your site actually has HTTPS. It won't tell users on HTTP to switch to HTTPS, it will just tell HTTPS users to stick around. You can enforce this with the express-enforces-ssl module. It's somewhat well-supported by browsers.

Trying to prevent: Hackers can exploit known vulnerabilities in Express/Node if they see that your site is powered by Express (or whichever framework you use). X-Powered-By: Express is sent in every HTTP request coming from Express by default. Disabling this won't provide much security benefit (as discussed here), but might help a tiny bit. It will also improve performance by reducing the number of bytes sent.

How to use Helmet to mitigate this: The hidePoweredBy middleware will remove the X-Powered-By header if it is set (which it will be by default in Express).


You can also explicitly set the header to something else, if you want. This could throw people off:

app.use(helmet.hidePoweredBy({ setTo: 'PHP 4.2.0' }))

Note: if you're using Express, you can skip Helmet's middleware if you want:


Limitations: There might be other telltale signs that your site is Express-based (a blog post about your tech stack, for example). And if a hacker wants to hack your site, they could try Express (even if they're not sure that's what your site is built on).

Trying to prevent: Some web applications will serve untrusted HTML for download. By default, some versions of Internet Explorer will allow you to open those HTML files in the context of your site, which means that an untrusted HTML page could start doing bad things in the context of your pages. For more, see this MSDN blog post.

How to use Helmet to mitigate this: Set the X-Download-Options header to noopen to prevent IE users from executing downloads in your site's context.


Limitations: This is pretty obscure, fixing a small bug on IE only. No real drawbacks other than performance/bandwidth of setting the headers, though.

Trying to prevent: Some browsers will try to "sniff" mimetypes. For example, if my server serves file.txt with a text/plain content-type, some browsers can still run that file with <script src="file.txt"></script>. Many browsers will allow file.js to be run even if the content-type isn't for JavaScript. There are some other vulnerabilities, too.

How to use Helmet to mitigate this: Use Helmet's noSniff middleware to keep Chrome, Opera, and IE from doing this sniffing (and Firefox soon). The following example sets the X-Content-Type-Options header to its only option, nosniff:


MSDN has a good description of how browsers behave when this header is sent.

Limitations: This only prevents against a certain kind of attack.

Trying to prevent: Users caching your old, buggy resources. It's possible that you've got bugs in an old HTML or JavaScript file, and with a cache, some users will be stuck with those old versions.

How to use Helmet to mitigate this: Use Helmet to disable this kind of caching. This sets a number of HTTP headers that stop caching.


This sets four headers, disabling a lot of browser caching:

  • Cache-Control: no-store, no-cache, must-revalidate, proxy-revalidate
  • Pragma: no-cache
  • Expires: 0
  • Surrogate-Control: no-store

If you want to crush the ETag header as well, you can:

app.use(helmet.noCache({ noEtag: true }))

Limitations: Caching has some real benefits, and you lose them here (which is why it's disabled in the default configuration). Browsers won't cache resources with this enabled, although some performance is retained if you keep ETag support. It's also possible that you'll introduce new bugs and you'll wish people had old resources cached, but that's less likely.

Trying to prevent: HTTPS certificates can be forged, allowing man-in-the middle attacks. HTTP Public Key Pinning aims to help that.

How to use Helmet to mitigate this: Pass the "Public-Key-Pins" header to better assert your SSL certificates. See the spec for more.

var ninetyDaysInMilliseconds = 7776000000;
  maxAge: ninetyDaysInMilliseconds,
  sha256s: ['AbCdEf123=', 'ZyXwVu456='],
  includeSubdomains: true,         // optional 
  reportUri: 'http://example.com'  // optional 
  reportOnly: false                // optional 

Setting reportOnly to true will change the header from Public-Key-Pins to Public-Key-Pins-Report-Only.

Limitations: Don't let these get out of sync with your certs!

Trying to prevent: Some browsers can start doing DNS lookups of other domains before visiting those domains. This can improve performance but can worsen security. Mozilla Developer Network describes how browsers do this prefetching. Chromium's documentation describes some ways that DNS lookups can be abused.

How to use Helmet to mitigate this: Browsers will listen for the X-DNS-Prefetch-Control header and will disable DNS prefetching if the header is set to off.

// Disable DNS prefetching (these two lines are equivalent): 
app.use(helmet.dnsPrefetchControl({ allow: false }))
// Enable DNS prefetching (less secure but faster): 
app.use(helmet.dnsPrefetchControl({ allow: true }))

Limitations: This hurts performance—browsers will no longer prefetch resources from your site.

Helmet only deals with HTTP headers, but there are a number of other helpful security modules for Express. We haven't heavily audited these—that's what the Node Security Project is for—but take a look at some of these modules!