Digital exposure report
kenshoo.com
Moderate exposure. There are gaps an attacker could exploit — fix them soon.
Scanned: 2026-11-21 09:50 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
Tell receiving mail servers how to treat fake email from your domain
Without this policy, inboxes have less guidance for spotting messages that impersonate you.
Who can fix it: Your email provider, together with whoever manages your DNS
How to verify after the fix
dig +short TXT _dmarc.kenshoo.com
- 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 kenshoo.com
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- kenshoo.com
- Website request
- GET https://kenshoo.com/ → https://skai.io/
- Scan time
- 2026-11-21 09:50:09 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 | 19/30 | Spoofing email in the company's name is possible in some cases. |
| Encryption & certificate | 25/25 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | 23/30 | Some browser protections are missing. |
| DNS infrastructure | 8/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.MediumDMARC — anti-spoofing policy · Hardening gap+10
- 2.MediumDNSSEC — signed DNS records · Hardening gap+7
- 3.LowPermissions-Policy · Hardening gap+2
- 4.LowReferrer-Policy · Hardening gap+2
- 5.LowCSP — protection from script injection · Hardening gap+3
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. 5 of 10 DNS lookups.
v=spf1 a mx include:stspg-customer.com include:aspmx.pardot.com include:mail.zendesk.com ip4:95.142.18.0/23 ip4:5.104.244.0/23 ip4:217.65.35.0/24 ip4:217.65.38.0/24 ip4:170.76.228.0/23 ip4:198.2.132.0/22 ip4:198.2.136.0/23 ip4:198.2.186.0/23 ip4:205.201.131.128/25 ip4:205.201.134.128/25 ip4:205.201.136.0/23 ip4:205.201.139.0/24 ip4:198.2.180.0/24 ip4:198.2.179.0/24 ip4:198.2.178.0/24 ip4:198.2.177.0/24 ip4:91.228.126.200 ip4:91.228.126.201 ip4:91.228.126.202 ip4:80.179.219.132 ip4:109.201.141.70 ip4:109.201.141.71 ip4:198.245.81.0/24 ip4:136.147.176.0/24 ip4:13.111.0.0/24 ip4:13.111.1.0/24 ip4:13.111.2.0/24 ip4:13.111.3.0/24 ip4:13.111.53.0/24 ip4:13.111.54.0/24 ip4:13.111.63.0/24 ip4:13.111.92.0/24 ip4:136.147.182.0/24 ip4:136.147.135.0/24 ip4:199.122.123.188/30 ip4:199.122.123.192 ip4:109.201.141.72 ip4:62.219.212.59 ip4:87.253.232.0/21 ip4:185.189.236.0/22 ip4:185.211.120.0/22 ip4:185.250.236.0/22 ip4:216.71.96.0/22 ip4:205.201.128.0/20 ip4:198.2.128.0/18 ip4:148.105.8.0/21 ip4:207.126.144.0/20 ip4:199.255.192.0/22 ip4:199.127.232.0/22 ip4:54.240.0.0/18 ip4:69.169.224.0/20 ip4:76.223.180.0/23 ip4:76.223.188.0/24 ip4:76.223.189.0/24 ip4:76.223.190.0/24 ip4:167.89.101.239 ip4:192.161.144.0/20 ip4:185.12.80.0/22 ip4:96.46.150.192/27 ip4:174.137.46.0/24 ip4:188.172.128.0/20 ip4:198.245.81.0/24 ip4:136.147.176.0/24 ip4:13.111.0.0/24 ip4:13.111.1.0/24 ip4:13.111.2.0/24 ip4:13.111.3.0/24 ip4:13.111.53.0/24 ip4:13.111.54.0/24 ip4:13.111.63.0/24 ip4:13.111.92.0/24 ip4:13.111.111.0/24 ip4:136.147.182.0/24 ip4:136.147.135.0/24 ip4:199.122.123.188/30 ip4:199.122.123.192 ip4:147.160.167.0/26 ip4:23.21.109.197 ip4:23.21.109.212 ip4:52.49.201.246 ip4:52.49.235.189 ip4:216.198.0.0/18 ip4:54.240.63.0/25 ip4:54.240.40.0/25 ip4:54.240.56.128/26 ip4:167.89.0.0/17 ip4:168.245.0.0/17 ip4:95.183.4.66 ip4:23.90.105.106 ip4:23.90.102.178 ip4:207.54.76.249 ip4:207.54.77.81 ip4:209.85.218.71 ~all
$ dig +short TXT kenshoo.com
DMARC — anti-spoofing policy
Needs attention · Severity: Medium · Hardening gap · 5/15DMARC is in monitoring mode only — forged email still reaches recipients.
Policy p=none. p=none collects reports but does not protect.
v=DMARC1; p=none; rua=mailto:security-mail-dmarc@skai.io;
$ dig +short TXT _dmarc.kenshoo.com
- Step 1 (monitoring, no effect on mail): publish p=none with an rua address to receive reports.
- Step 2: analyze reports for 2–4 weeks and make sure every legitimate sender passes SPF/DKIM.
- Step 3: move to p=quarantine, and finally to p=reject.
_dmarc.kenshoo.com. TXT "v=DMARC1; p=none; rua=mailto:dmarc@kenshoo.com; fo=1"
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. Jumping straight to reject without a monitoring phase can block legitimate mail.
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, s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
google._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCB6yh1Y8qMXFxIIBxJHonuFIQvmY3syKpH… s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA1Yal/tntoqAjDSOHQT9UMoCAgDOyYZa4… s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC8hiDf8Ux0EHINmzowLekJAuI2iO9h8NP8UgEz…
$ dig +short TXT google._domainkey.kenshoo.com
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
2 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
1 mx1.hc677-17.eu.iphmx.com 10 mx2.hc677-17.eu.iphmx.com
$ dig +short MX kenshoo.com
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://kenshoo.com/ returned HTTP 200 (final URL: https://skai.io/). Client-side certificate validation passed.
HTTP 200 Final URL: https://skai.io/
$ curl -sIL https://kenshoo.com/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://skai.io:443/
HTTP 301 Location: https://skai.io:443/
$ curl -sI http://kenshoo.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: GoDaddy, expiring 2027-05-23 (183 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: GoDaddy Valid from: 2026-11-06 Valid until: 2027-05-23 Names: *.kenshoo.com, kenshoo.com Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect kenshoo.com:443 -servername kenshoo.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=63072000 (730 days), includeSubDomains, preload. ≥ 180 days recommended.
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
$ curl -sIL https://kenshoo.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://mcp-guides.skai.io;
$ curl -sIL https://kenshoo.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: SAMEORIGIN frame-ancestors 'self' https://mcp-guides.skai.io
X-Frame-Options: SAMEORIGIN CSP frame-ancestors: 'self' https://mcp-guides.skai.io
$ curl -sIL https://kenshoo.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://kenshoo.com/ | grep -i "X-Content-Type-Options"
Referrer-Policy
Needs attention · Severity: Low · Hardening gap · 1/3The policy sends full URLs to external sites.
Referrer-Policy: no-referrer-when-downgrade — sends the full URL including path and query.
Referrer-Policy: no-referrer-when-downgrade
$ curl -sIL https://kenshoo.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://kenshoo.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://kenshoo.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 kenshoo.com: NODATA
$ dig +short DS kenshoo.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 kenshoo.com SOA delv kenshoo.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 "awstrust.com" | 0 issue "godaddy.com" | 0 issue "letsencrypt.org"
0 issue "awstrust.com" 0 issue "godaddy.com" 0 issue "letsencrypt.org"
$ dig +short CAA kenshoo.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-1454.awsdns-53.org ns-1937.awsdns-50.co.uk ns-493.awsdns-61.com ns-543.awsdns-03.net
$ dig +short NS kenshoo.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 rules1 observed gaps
- PCI DSS v4.01 observed gaps
- NIS2 / vendor due diligence2 observed gaps
- SOC 2 / ISO 27001 baseline2 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 | kenshoo.com | 184.197.225.75 | 52.86.132.249 |
| AAAA | kenshoo.com | — |
| MX | kenshoo.com | 1 mx1.hc677-17.eu.iphmx.com | 10 mx2.hc677-17.eu.iphmx.com |
| NS | kenshoo.com | ns-1454.awsdns-53.org | ns-1937.awsdns-50.co.uk | ns-493.awsdns-61.com | ns-543.awsdns-03.net |
| TXT | kenshoo.com | 00DQ10000009mzbt=1TBQ1000000001wz | MS=ms24302744 | NVpUZeajVNTSbop7E1Wir507g/QZkv36Iykwu0Xxvf0= | anthropic-domain-verification-16q6bz=xRJlCoyddF3LGN7f2UPJHECtz | apple-domain-verification=RMaQ5TtSYtPcIhOY | apple-domain-verification=lpKze76INVkHKpvL | atlassian-domain-verification=owAuDUwrlsJNieK8p/aEjdGX/sG06ZHjZkzHAw956NN9wULHgcDNC6noVOutFiUy | docusign=1ad76b38-b4cc-46e2-8ea9-5c0c434916fa | google-site-verification=3_QCZmmZ2TgX2eIL7u1R-V0YbnEdeXUJ5BVlam1ALTA | google-site-verification=5N9sqcTE-dS5rT-edyroe7boDtl49-0wEJL-wKZvlJY | google-site-verification=6l7ZZL1x3oUaY4A1827oiYUHR8_BQADzRwqjUBvlgZY | google-site-verification=EfTAsIu_SiGmMgt4E0tpv5FO_JEjBW5niK0YVmMRE_I | google-site-verification=asxOLBVfkaaQl92HOfzL-kj1SgwYr4l1R-L5kUp3f5s | google-site-verification=hREpJiAIXAmrA-Zmzu3cIb1wXGCIC8s2qlp9P3ivxm4 | google-site-verification=l95Yj8HkHr9ulmFoZzKwKEyuPXJT6geNbAfekEIN4Tc | google-site-verification=uz2mgRZ12yZfa3fhykLQzXXkOT73TajfBXkMvbbjhP4 | mixpanel-domain-verify=3681159f-bf1f-445a-9f5e-738dce1f750c | ms58769343.msv1.invalid | onetrust-domain-verification=26adec8e338343dcbeebc5e9e8fe69a4 | pardot_67532_*=973724b0f35868f0acf9466fe700affa62a49100 4a8673883938969cd75a23c4 | status-page-domain-verification=jw6nmwxjxjzb | v=spf1 a mx include:stspg-customer.com include:aspmx.pardot.com include:mail.zendesk.com ip4:95.142.18.0/23 ip4:5.104.244.0/23 ip4:217.65.35.0/24 ip4:217.65.38.0/24 ip4:170.76.228.0/23 ip4:198.2.132.0/22 ip4:198.2.136.0/23 ip4:198.2.186.0/23 ip4:205.201.131.128/25 ip4:205.201.134.128/25 ip4:205.201.136.0/23 ip4:205.201.139.0/24 ip4:198.2.180.0/24 ip4:198.2.179.0/24 ip4:198.2.178.0/24 ip4:198.2.177.0/24 ip4:91.228.126.200 ip4:91.228.126.201 ip4:91.228.126.202 ip4:80.179.219.132 ip4:109.201.141.70 ip4:109.201.141.71 ip4:198.245.81.0/24 ip4:136.147.176.0/24 ip4:13.111.0.0/24 ip4:13.111.1.0/24 ip4:13.111.2.0/24 ip4:13.111.3.0/24 ip4:13.111.53.0/24 ip4:13.111.54.0/24 ip4:13.111.63.0/24 ip4:13.111.92.0/24 ip4:136.147.182.0/24 ip4:136.147.135.0/24 ip4:199.122.123.188/30 ip4:199.122.123.192 ip4:109.201.141.72 ip4:62.219.212.59 ip4:87.253.232.0/21 ip4:185.189.236.0/22 ip4:185.211.120.0/22 ip4:185.250.236.0/22 ip4:216.71.96.0/22 ip4:205.201.128.0/20 ip4:198.2.128.0/18 ip4:148.105.8.0/21 ip4:207.126.144.0/20 ip4:199.255.192.0/22 ip4:199.127.232.0/22 ip4:54.240.0.0/18 ip4:69.169.224.0/20 ip4:76.223.180.0/23 ip4:76.223.188.0/24 ip4:76.223.189.0/24 ip4:76.223.190.0/24 ip4:167.89.101.239 ip4:192.161.144.0/20 ip4:185.12.80.0/22 ip4:96.46.150.192/27 ip4:174.137.46.0/24 ip4:188.172.128.0/20 ip4:198.245.81.0/24 ip4:136.147.176.0/24 ip4:13.111.0.0/24 ip4:13.111.1.0/24 ip4:13.111.2.0/24 ip4:13.111.3.0/24 ip4:13.111.53.0/24 ip4:13.111.54.0/24 ip4:13.111.63.0/24 ip4:13.111.92.0/24 ip4:13.111.111.0/24 ip4:136.147.182.0/24 ip4:136.147.135.0/24 ip4:199.122.123.188/30 ip4:199.122.123.192 ip4:147.160.167.0/26 ip4:23.21.109.197 ip4:23.21.109.212 ip4:52.49.201.246 ip4:52.49.235.189 ip4:216.198.0.0/18 ip4:54.240.63.0/25 ip4:54.240.40.0/25 ip4:54.240.56.128/26 ip4:167.89.0.0/17 ip4:168.245.0.0/17 ip4:95.183.4.66 ip4:23.90.105.106 ip4:23.90.102.178 ip4:207.54.76.249 ip4:207.54.77.81 ip4:209.85.218.71 ~all |
| TXT | _dmarc.kenshoo.com | v=DMARC1; p=none; rua=mailto:security-mail-dmarc@skai.io; |
| CAA | kenshoo.com | 0 issue "awstrust.com" | 0 issue "godaddy.com" | 0 issue "letsencrypt.org" |
| DS | kenshoo.com | — |