What this checks
The headers that tell browsers how to protect your visitors: HTTPS only, no framing by other sites, no guessing file types, a content security policy, a private referrer, and the redirect from HTTP to HTTPS.
Free tool
Your grade, and the lines that fix it.
Type your site’s address. You get its grade, every test behind it, and the exact lines that fix each failing one for the server your site runs on.
Graded by Mozilla’s HTTP Observatory, asked from your browser. The grade is worked out again here from its tests, so you can see which one moved it.
HTTPS, the certificate, DNS, mail and registration – the whole address in one run.
Runs in your browser – nothing is saved to an account.
What each part of the answer means, and what to do when one is not right.
Your grade, every test behind it, and copy-ready lines for your own server – not just a list of what is missing.
The headers that tell browsers how to protect your visitors: HTTPS only, no framing by other sites, no guessing file types, a content security policy, a private referrer, and the redirect from HTTP to HTTPS.
A missing header leaves a door open: a site that can be framed can be used for clickjacking, and one without HTTPS-only can be downgraded on public Wi-Fi. Insurers and security questionnaires increasingly ask for these.
Choose your server and copy the lines shown. Add a content security policy in report-only mode first, watch what it reports for a week, then switch it on.
Grade your live site after every deploy and fail the build when a header goes missing, with the lines that put it back. Any Xovris API token is the key – a Free workspace’s too – for 100 checks a day, 2,000 on any paid plan.
The API in full, and moving from the securityheaders.com APIname: Security headers
on:
deployment_status:
schedule:
- cron: '0 6 * * *'
jobs:
grade:
if: ${{ github.event_name == 'schedule' || github.event.deployment_status.state == 'success' }}
runs-on: ubuntu-latest
steps:
- name: Grade the live site's headers
env:
XOVRIS_TOKEN: ${{ secrets.XOVRIS_TOKEN }}
SITE: yourdomain.com
MIN_SCORE: '70'
run: |
r=$(curl -sf "https://api.xovris.ai/v1/tools/security-headers?host=$SITE" -H "authorization: Bearer $XOVRIS_TOKEN")
echo "$r" | jq -r '"Grade \(.grade) (\(.score)) for \(.host)"'
if [ "$(echo "$r" | jq '.score')" -lt "$MIN_SCORE" ]; then
echo "$r" | jq -r '"Add these lines for \(.fix.server):\n\(.fix.lines)"'
exit 1
fiStraight answers, from what the check itself does.
Xovris re-checks your headers every day and tells you if a deploy drops one.
The answer on this page is xovris.ai’s own, recorded by this check 18 November at 23:06 UTC. Nothing here is a sample: name your own address and Xovris runs it for you.
Each technical word this page uses, said simply.