Digital exposure report
keepersecurity.com
Low exposure. The domain is well protected in most areas checked.
Scanned: 2026-11-19 02:59 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
Limit what your site shares when visitors click links
This reduces how much page address detail is passed to other websites.
Who can fix it: Your website developer or web host
How to verify after the fix
curl -sIL https://keepersecurity.com/ | grep -i "Referrer-Policy"
- 2.
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://keepersecurity.com/ | grep -i "Content-Security-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- keepersecurity.com
- Website request
- GET https://keepersecurity.com/ → https://www.keepersecurity.com/
- Scan time
- 2026-11-19 02:59:39 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 | 30/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 | 22/30 | Some browser protections are missing. |
| DNS infrastructure | 15/15 | The domain's infrastructure is well hardened. |
Fix priorities
- 1.LowReferrer-Policy · Hardening gap+3
- 2.LowPermissions-Policy · Hardening gap+2
- 3.LowCSP — protection from script injection · Hardening gap+3
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 10/10An authorized sender list is defined and mail from other servers is rejected.
Valid SPF record with -all. 1 of the 10 allowed DNS lookups.
v=spf1 redirect=keepersecurity.com.hosted.spf-report.com
$ dig +short TXT keepersecurity.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;pct=100;rua=mailto:544eede5@mxtoolbox.dmarc-report.com;ruf=mailto:544eede5@forensics.dmarc-report.com;fo=1
$ dig +short TXT _dmarc.keepersecurity.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, selector1, selector2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
google._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCxd3ynBbJsk+eZzYkQjKttpP6jy1PPFmET… selector1._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCzcIV2bgmfXUs/giTAHrZ4j5kupKO6waTW… selector2._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCytVEKcANVSBS/obMlYxltJZn9qytlyiNU…
$ dig +short TXT google._domainkey.keepersecurity.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 20 alt2.aspmx.l.google.com 30 aspmx2.googlemail.com 30 aspmx3.googlemail.com
$ dig +short MX keepersecurity.com
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://keepersecurity.com/ returned HTTP 200 (final URL: https://www.keepersecurity.com/). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.keepersecurity.com/
$ curl -sIL https://keepersecurity.com/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://keepersecurity.com:443/
HTTP 301 Location: https://keepersecurity.com:443/
$ curl -sI http://keepersecurity.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. Latest issuance in CT logs: Amazon Trust Services, expiring 2027-04-11 (143 days). CT shows issued certificates, not necessarily the one served — confirm dates with the verify command.
Live TLS handshake: certificate accepted CT logs (context only, not scored): Issuer: Amazon Trust Services Valid from: 2026-09-26 Valid until: 2027-04-11 Names: keepersecurity.com, www.keepersecurity.com Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect keepersecurity.com:443 -servername keepersecurity.com 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Passed · Severity: OK · 8/8Browsers are told to always use an encrypted connection to the site.
max-age=31536000 (365 days), includeSubDomains, preload. ≥ 180 days recommended.
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
$ curl -sIL https://keepersecurity.com/ | grep -i "Strict-Transport-Security"
CSP — protection from script injection
Needs attention · Severity: Low · Hardening gap · 5/8A script policy exists, but it's permissive and offers only partial protection.
script-src includes: no script-src/default-src — weakens XSS protection.
Content-Security-Policy: frame-ancestors 'self' https://keepersecurity.com https://keepersecurity.eu https://keepersecurity.com.au https://keepersecurity.jp https://keepersecurity.ca;
$ curl -sIL https://keepersecurity.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
Passed · Severity: OK · 5/5The site can't be embedded by foreign sites.
X-Frame-Options: DENY frame-ancestors 'self' https://keepersecurity.com https://keepersecurity.eu https://keepersecurity.com.au https://keepersecurity.jp https://keepersecurity.ca
X-Frame-Options: DENY CSP frame-ancestors: 'self' https://keepersecurity.com https://keepersecurity.eu https://keepersecurity.com.au https://keepersecurity.jp https://keepersecurity.ca
$ curl -sIL https://keepersecurity.com/ | grep -i "X-Frame-Options"
X-Content-Type-Options
Passed · Severity: OK · 4/4The browser won't guess file types in a way that could execute code.
nosniff is set.
X-Content-Type-Options: nosniff
$ curl -sIL https://keepersecurity.com/ | grep -i "X-Content-Type-Options"
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://keepersecurity.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://keepersecurity.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://keepersecurity.com/ | grep -iE "^(server|x-powered-by)"
DNSSEC — signed DNS records
Passed · Severity: OK · 7/7The domain's records are digitally signed and hard to forge.
An AD (Authenticated Data) flag was returned by a validating resolver.
AD = true
$ dig +dnssec keepersecurity.com | grep -E "flags:.* ad"
CAA — who may issue certificates
Passed · Severity: OK · 5/5Only authorized certificate authorities can issue certificates for the domain.
CAA records: 0 issue "amazonaws.com" | 0 issue "digicert.com" | 0 issue "starfieldtech.com"
0 issue "amazonaws.com" 0 issue "digicert.com" 0 issue "starfieldtech.com"
$ dig +short CAA keepersecurity.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-194.awsdns-24.com ns-596.awsdns-10.net ns-1433.awsdns-51.org ns-1835.awsdns-37.co.uk
$ dig +short NS keepersecurity.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.01 observed gaps
- NIS2 / vendor due diligenceNo gaps observed
- SOC 2 / ISO 27001 baseline1 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 | keepersecurity.com | 100.25.27.45 | 34.194.152.47 |
| AAAA | keepersecurity.com | — |
| MX | keepersecurity.com | 10 aspmx.l.google.com | 20 alt1.aspmx.l.google.com | 20 alt2.aspmx.l.google.com | 30 aspmx2.googlemail.com | 30 aspmx3.googlemail.com |
| NS | keepersecurity.com | ns-194.awsdns-24.com | ns-596.awsdns-10.net | ns-1433.awsdns-51.org | ns-1835.awsdns-37.co.uk |
| TXT | keepersecurity.com | OSSRH-71116 | MS=ms17866620 | yDsmBfO5_kQK-d4XyNnDuQ | uaicfulqr146uo3h0pv4i4iqcr | ZOOM_verify_e2x3TvgYhiYsjH7Bs8kVo4 | apple-domain-verification=W3Y24YCrOJqMf8pN | status-page-domain-verification=8g5t6987qvvx | docusign=2d8314b4-8fe8-440a-8137-60c4f086f94b | jamf-site-verification=ahpHAtPKUqBdo3CFH75-iA | _github-challenge-Keeper-Security-org=778c035663 | openai-domain-verification=dv-AostJGhbSHvYG1FKSTBRFhbc | docker-verification=5465ae54-7f62-4a0d-b2f9-6f5cd27dd4e9 | v=spf1 redirect=keepersecurity.com.hosted.spf-report.com | cursor-domain-verification-px0w7b=mNXhudVEUIW7eFAKQiKPVAooG | facebook-domain-verification=noze28nwtzxeej2r4c9nh407bhuwvj | anthropic-domain-verification-8c2qbt=FRtP1ZA8rqrbECXTUn0cIoEd9 | slack-domain-verification=ugIdU70Xkn9EA7PwACS2M9iOFfBAB2pHjijPibBC | monday-com-verification=IOtGp5L_-3MvLTSF-m9nnrzhtoJYZVnYvQ_Tlq93Crw | google-site-verification=81jzOASWSu6b5upDW2CYd_KPjvy3BXaKp0bkw0dBSTM | google-site-verification=EYhZmCYzZOYJQtJyHSedaICv8_ZVbj-c3kd-NRL5Vvo | google-site-verification=KSyZZpFylLNpzFOr0UUki4JXas3k0VED56trvCGQB2U | google-site-verification=O0SkyQe1zVNovlAm9PGnktWaFhVlgWsUA9tyHT3QnIQ | google-site-verification=WIfAuDB3ruMmt2dv-7X999CpE30j22jwUiKbQVkIMSk | google-site-verification=__zlDNSYxlA2pNFI59ABhdvzzJiZlOV6K2S1cqPAnes | google-site-verification=fsWQXEw9Qg8xrsBH5NfmDEC6uDtr-At5KHL6cihCXG8 | google-site-verification=nhoQxQYTHGSmyD20CWExeMm8pW4AxwaH6EtPsA0aBUQ | sentinelone-domain-verification=72JlYeZC7YuWMD2vVAcEWCZEar3JigWi6HdNz8nJTIh | wiz-domain-verification=24295edc3c6f54a9e69b70a11f85b8184df878a0d373d0981cf86a22832540d0 | parallels-domain-verification=bed9f261502d4ebe840a9c0cd2179b90219d8712639d458f9da21c9785a607be |
| TXT | _dmarc.keepersecurity.com | v=DMARC1;p=reject;pct=100;rua=mailto:544eede5@mxtoolbox.dmarc-report.com;ruf=mailto:544eede5@forensics.dmarc-report.com;fo=1 |
| CAA | keepersecurity.com | 0 issue "amazonaws.com" | 0 issue "digicert.com" | 0 issue "starfieldtech.com" |
| DS | keepersecurity.com | 11755 13 2 73da736eec2d09f2264521d9ee980ac61c7b927df86ba2cdfbe86dfc1e7d4540 |