Digital exposure report
hotjar.com
High exposure. Significant weaknesses put the brand, customers and email at risk.
Scanned: 2026-11-19 02:59 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
Limit what scripts your pages are allowed to run
This adds one layer of protection against injected scripts.
Who can fix it: Your website developer or web host
How to verify after the fix
curl -sIL https://hotjar.com/ | grep -i "Content-Security-Policy"
- 2.
Turn on DNS signing for your domain
Signing helps resolvers detect forged answers about your domain.
Who can fix it: Your domain registrar or DNS provider
How to verify after the fix
dig +short DS hotjar.com
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- hotjar.com
- Website request
- GET https://hotjar.com/ → https://contentsquare.com/hotjar/?utm_campaign=exp__hj_hp_redirection
- Scan time
- 2026-11-19 02:59:56 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- None. Every applicable check was assessed.
This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.
Score by category
| Email security | 29/30 | Spoofing email from this domain is hard. |
| Encryption & certificate | 25/25 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | 7/30 | Several browser hardening headers are missing, which removes layers of protection against script injection and framing. |
| DNS infrastructure | 8/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.MediumClickjacking protection · Hardening gap+5
- 2.MediumDNSSEC — signed DNS records · Hardening gap+7
- 3.MediumCSP — protection from script injection · Hardening gap+8
- 4.LowX-Content-Type-Options · Hardening gap+4
- 5.LowReferrer-Policy · Hardening gap+3
- 6.LowPermissions-Policy · Hardening gap+2
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 9/10An authorized sender list is defined; mail from other servers is flagged as suspicious.
~all (softfail) — acceptable when combined with enforced DMARC. 7 of 10 DNS lookups.
v=spf1 include:amazonses.com include:spf.braintreegateway.com include:stspg-customer.com include:mail.zendesk.com a:zgateway.zuora.com include:spf.tipalti.com include:_spf1.hotjar.com ~all
$ dig +short TXT hotjar.com
DMARC — anti-spoofing policy
Passed · Severity: OK · 15/15Forged email in the company's name is blocked by mail servers.
Policy p=reject.
v=DMARC1; p=reject; rua=mailto:re+sc9orosaozu@dmarc.postmarkapp.com; sp=reject; aspf=r;
$ dig +short TXT _dmarc.hotjar.com
DKIM — digital signature on email
Passed · Severity: OK · 5/5A DKIM public key is published. On its own this doesn't prove outgoing mail is signed or aligned with your From domain.
DKIM public key found for selector: google, k1, s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
google._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCB5koEin+VRSlk69XevJfsFZQyykTKN8oz… k1._domainkey: k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDONVFRBQH3QcGHXxjBTX1UHX5sQzJ22LeoR8j606avv… s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnoCMuQP1aiBBdytJl2DUkaC0DbY1TLwT… s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDezqBb2VjEllhUCPwOqOXCxiFxC8/K4YkqEXxz…
$ dig +short TXT google._domainkey.hotjar.com
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
5 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
10 aspmx.l.google.com 20 alt1.aspmx.l.google.com 30 alt2.aspmx.l.google.com 40 aspmx2.googlemail.com 50 aspmx3.googlemail.com
$ dig +short MX hotjar.com
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://hotjar.com/ returned HTTP 200 (final URL: https://contentsquare.com/hotjar/?utm_campaign=exp__hj_hp_redirection). Client-side certificate validation passed.
HTTP 200 Final URL: https://contentsquare.com/hotjar/?utm_campaign=exp__hj_hp_redirection
$ curl -sIL https://hotjar.com/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://contentsquare.com/hotjar/?utm_campaign=exp__hj_hp_redirection
HTTP 301 Location: https://contentsquare.com/hotjar/?utm_campaign=exp__hj_hp_redirection
$ curl -sI http://hotjar.com/ | grep -iE "^(HTTP|location)"
SSL/TLS certificate validity
Passed · Severity: OK · 8/8The certificate was accepted by a validating TLS client at scan time.
Live TLS handshake succeeded. No matching certificate details were available from CT logs; run the verify command to see the served certificate's dates.
Live TLS handshake: certificate accepted The CT log service was unavailable at the time of the check Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect hotjar.com:443 -servername hotjar.com 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Passed · Severity: OK · 7/8Browsers are told to always use an encrypted connection to the site.
max-age=63072000 (730 days), no includeSubDomains. ≥ 180 days recommended.
Strict-Transport-Security: max-age=63072000
$ curl -sIL https://hotjar.com/ | grep -i "Strict-Transport-Security"
CSP — protection from script injection
Failed · Severity: Medium · Hardening gap · 0/8Missing Content-Security-Policy header: this removes one layer of protection against script injection.
No Content-Security-Policy header found.
Content-Security-Policy: (missing)
$ curl -sIL https://hotjar.com/ | grep -i "Content-Security-Policy"
- First publish Content-Security-Policy-Report-Only — it blocks nothing, it only reports.
- Collect violations for a week or two and tune the policy to your legitimate sources.
- Switch to the Content-Security-Policy header and replace 'unsafe-inline' with a nonce or hash.
/* Content-Security-Policy-Report-Only: default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'
Safety: This change is made in your server/CDN settings. Test on staging before production. An overly strict CSP will break scripts — that's why you start in Report-Only mode.
Clickjacking protection
Failed · Severity: Medium · Hardening gap · 0/5Missing X-Frame-Options / frame-ancestors: this removes one layer of protection against clickjacking.
No valid X-Frame-Options and no frame-ancestors in the CSP.
X-Frame-Options: (missing)
$ curl -sIL https://hotjar.com/ | grep -i "X-Frame-Options"
- Add X-Frame-Options: SAMEORIGIN (or DENY if the site is never embedded anywhere).
- Also set frame-ancestors in the CSP — the modern alternative.
/* X-Frame-Options: SAMEORIGIN
Safety: This change is made in your server/CDN settings. Test on staging before production. If partners embed the site in an iframe, add them to frame-ancestors instead of using DENY.
X-Content-Type-Options
Failed · Severity: Low · Hardening gap · 0/4The browser may interpret files as code unintentionally.
Missing X-Content-Type-Options: nosniff header (MIME sniffing).
X-Content-Type-Options: (missing)
$ curl -sIL https://hotjar.com/ | grep -i "X-Content-Type-Options"
- Add X-Content-Type-Options: nosniff to every response.
/* X-Content-Type-Options: nosniff
Safety: This change is made in your server/CDN settings. Test on staging before production.
Referrer-Policy
Failed · Severity: Low · Hardening gap · 0/3Internal URLs (including parameters) may leak to external sites.
Referrer-Policy is missing; the browser will use its default.
Referrer-Policy: (missing)
$ curl -sIL https://hotjar.com/ | grep -i "Referrer-Policy"
- Set Referrer-Policy: strict-origin-when-cross-origin.
/* Referrer-Policy: strict-origin-when-cross-origin
Safety: This change is made in your server/CDN settings. Test on staging before production.
Permissions-Policy
Needs attention · Severity: Low · Hardening gap · 0/2Access to sensitive features like the camera and location isn't restricted.
Missing Permissions-Policy header.
Permissions-Policy: (missing)
$ curl -sIL https://hotjar.com/ | grep -i "Permissions-Policy"
- Disable browser features the site doesn't need (camera, microphone, geolocation).
/* Permissions-Policy: camera=(), microphone=(), geolocation=()
Safety: This change is made in your server/CDN settings. Test on staging before production. Don't disable a feature the site actually uses.
Software version disclosure
Passed · Severity: OK · unscoredThe server doesn't disclose software versions.
No version numbers found in the Server / X-Powered-By headers.
server: cloudflare x-powered-by: (missing)
$ curl -sIL https://hotjar.com/ | grep -iE "^(server|x-powered-by)"
DNSSEC — signed DNS records
Needs attention · Severity: Medium · Hardening gap · 0/7The domain's records aren't signed, so in some scenarios users could be redirected to a forged server.
No DS record is published at the parent zone, so there's no DNSSEC chain of trust for this zone.
AD = false DS hotjar.com: NODATA
$ dig +short DS hotjar.com
- Enable DNSSEC at your DNS provider (one click at most providers).
- Copy the DS record your provider generates to your domain registrar.
- Wait for propagation and verify with DNSViz.
dig +dnssec hotjar.com SOA delv hotjar.com
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. A wrong DS record at the registrar will make the domain stop resolving — copy it exactly from the provider.
CAA — who may issue certificates
Passed · Severity: OK · 5/5Only authorized certificate authorities can issue certificates for the domain.
CAA records: 0 issue "amazon.com" | 0 issue "comodoca.com" | 0 issue "digicert.com" | 0 issue "globalsign.com" | 0 issue "letsencrypt.org"
0 issue "amazon.com" 0 issue "comodoca.com" 0 issue "digicert.com" 0 issue "globalsign.com" 0 issue "letsencrypt.org"
$ dig +short CAA hotjar.com
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
4 NS servers.
ns-1049.awsdns-03.org ns-1740.awsdns-25.co.uk ns-474.awsdns-59.com ns-873.awsdns-45.net
$ dig +short NS hotjar.com
Indicative alignment
Best-practice mapping of public findings to common frameworks. Passive scanning tests public configuration only; it doesn't prove compliance or a violation.
- Google & Yahoo sender rulesNo gaps observed
- PCI DSS v4.02 observed gaps
- NIS2 / vendor due diligence1 observed gaps
- SOC 2 / ISO 27001 baseline3 observed gaps
Indicative alignment only, based on public configuration. It doesn't establish whether a framework applies to you, and it isn't legal advice, an audit or a certification.
Public DNS records
| A | hotjar.com | 3.170.131.67 | 3.170.131.57 | 3.170.131.64 | 3.170.131.26 |
| AAAA | hotjar.com | — |
| MX | hotjar.com | 10 aspmx.l.google.com | 20 alt1.aspmx.l.google.com | 30 alt2.aspmx.l.google.com | 40 aspmx2.googlemail.com | 50 aspmx3.googlemail.com |
| NS | hotjar.com | ns-1049.awsdns-03.org | ns-1740.awsdns-25.co.uk | ns-474.awsdns-59.com | ns-873.awsdns-45.net |
| TXT | hotjar.com | 1password-site-verification=KASYZA5P7BFPNLAJF7OJXB4AGA | MS=ms71662109 | ZOOM_verify_ZoL82GLHAPUadNpWa746HC | adobe-idp-site-verification=f89818cce2a5552dea41256864bf659e1a500d4113f56e9a8cc2551fbda79d1c | anthropic-domain-verification-t0ajxj=KTdWrJtg4DuIMmSpvrzaRaTEd | apple-domain-verification=DOoDtgFrUzwhsBts | atlassian-domain-verification=PhFr7m+NL66maSfKMnRb1Rp8vhGVbDLPyYPLSDZHPjabIXsfpOtGHQLoNBKzRoZ6 | atlassian-domain-verification=ZrRRCzAEXu6Rt8csFbFro8mLbHdFFIV8PObjew3mhis4ZeUIGPE9olB4qjIg/fpX | bitrise-verification=ce42699e4be25393-mqOu-pxkhZws | cursor-domain-verification-xnxx1x=8pvRo0VResT5gVi84qkYAuqsY | docker-verification=c32d8e66-64c7-4003-b4da-6959a17dd16b | docusign=61e9409b-5f82-4c2b-9191-a2f9f67b3143 | dust-domain-verification-wss3ry=jk8VfpaWnAPSi9sTg1DApn3fR | google-site-verification=-SK6ManVKmMJ0Y3E5nRTU0qvE5geYbC-3o0FHCRFfAE | google-site-verification=65LnEfnj9-Oooat6efnDWBk8b0jVIoWvsnh5MgtaOMM | google-site-verification=94WbRw173SJmzoUFmL65oZDQ_k6NzK7V_vTwmjTyojw | google-site-verification=QCnIv31NwV_43DuVKrjEd02s-hmcXBJFfhjZZ7WLcGc | google-site-verification=Z2UrBbrNmI__zUHWISAYmqP1pHAQ_3IgpraHtZ5lVWQ | google-site-verification=jEitMJefiuuFO_LwQXMtQSn1wchSn0Dv27_NtzmMs3Q | google-site-verification=nASytrG_N4t5HifFE2qbZ9EkPq66gSJhBB63LkWSHxE | hubspot-developer-verification=MjI0ZTViMWUtZmMxNi00NjBjLWFmMDctOWMyZjBlOWMxOTg2 | loom-site-verification=062e481d3e82470f948acde3f490ed7f | loom-verification=4794730025 | lovable_verification=NkMjoDBkXP64uRuGEbIf | mixpanel-domain-verify=51115d25-d779-4633-a01d-07cc295f622e | monday-com-verification=Q3fM-zJax7wSaDSYPq1ikOEEfBXD0OfofGZ4BNub-uM | mongodb-site-verification=MRoHfxXNY8U4kk3t1RBF7f4tPlTv9i9S | protonmail-verification=9e4d0310f3bcbad8a9695663425fa06eb3ca8806 | status-page-domain-verification=ggq0xfsy0530 | stripe-verification=8BD243B2431EF42C3F860FD6D9BFDE93F974909AEA7D56D7049782DDF22B7E41 | unbounce571164 | v=spf1 include:amazonses.com include:spf.braintreegateway.com include:stspg-customer.com include:mail.zendesk.com a:zgateway.zuora.com include:spf.tipalti.com include:_spf1.hotjar.com ~all | zapier-domain-verification-challenge=a2db56ae-8416-457c-806e-d13a70cce131 | zapier-domain-verification-challenge=b3f25e2f-55b5-431e-a2b2-ac9d02c20ff1 |
| TXT | _dmarc.hotjar.com | v=DMARC1; p=reject; rua=mailto:re+sc9orosaozu@dmarc.postmarkapp.com; sp=reject; aspf=r; |
| CAA | hotjar.com | 0 issue "amazon.com" | 0 issue "comodoca.com" | 0 issue "digicert.com" | 0 issue "globalsign.com" | 0 issue "letsencrypt.org" |
| DS | hotjar.com | — |