Skip to main content

Security report for inspectlet.io

Inspectlet · Technology · United States

Medium risk. 7 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

61/100

Risk levelMedium

0–100, higher is better. How it is calculated

Inspectlet is a technology company founded in 2014, specializing in website visitor session recording and analytics services. Their platform enables website owners and marketers to understand user behavior deeply by recording mouse movements, clicks, scrolls, and keypresses, providing insights beyond traditional analytics. The company serves a broad audience including e-commerce, SaaS, and digital marketing professionals, boasting over 90,000 customers including major brands like Shopify, eBay, and Salesforce. The website is professionally designed, mobile-optimized, and presents a clear value proposition with strong trust signals such as testimonials and client logos. Technically, Inspectlet's website uses modern web technologies including AngularJS, Google Analytics, Segment, and Cloudflare DNS services. The site loads scripts asynchronously and defers non-critical JavaScript to optimize performance. While the site is well-structured and SEO-friendly, it lacks visible privacy and cookie policies, which are critical for compliance and user trust. No security.txt or incident response information is published, and security headers are not detected, indicating room for improvement in security posture. From a security perspective, the site uses HTTPS with a good SSL configuration and no exposed sensitive data in the HTML. However, the absence of DNSSEC and security headers reduces the overall security score. The domain registration data is consistent and trustworthy, with a domain age appropriate for the business maturity. No suspicious WHOIS patterns were found. Overall, Inspectlet presents a credible and professional online presence with strong business credibility and technical implementation. The main risks relate to privacy compliance and security best practices, which should be addressed to enhance user trust and regulatory adherence.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

7 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

Need hands-on remediation? Email guard@offseq.com

Keep watching inspectlet.io

This scan found 24 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. The full timeline opens with your unlock code.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
65
Security headers
35
Email security
70
DNS health
60
Network security
100
GDPR outside view
35
Average
61

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Inspectlet operates in the competitive website analytics and user behavior tracking market, leveraging session recording as a differentiator. Their SaaS business model targets digital marketers, UX designers, and product managers seeking to optimize conversion rates and user experience. The company has established itself with a medium-sized customer base and notable enterprise clients, indicating solid market positioning. The use of trusted third-party analytics and integration with platforms like Segment suggests a mature data ecosystem. However, the lack of explicit privacy and security disclosures may impact customer confidence in privacy-sensitive markets. Strategic partnerships or integrations are not explicitly listed but could be inferred from technology stack and client logos. Growth potential exists through enhanced compliance and expanded service offerings.

Security posture

Inspectlet demonstrates a moderate security maturity level with HTTPS enforced and no visible sensitive data leaks. The absence of DNSSEC and security headers such as Content-Security-Policy and X-Frame-Options indicates gaps in defense-in-depth strategies. No vulnerability disclosures or incident response contacts are published, which limits transparency and preparedness perception. The use of reputable registrars and consistent WHOIS data supports domain legitimacy. Privacy compliance is weak due to missing privacy and cookie policies, which could expose the company to regulatory risks, especially under GDPR. The extensive user tracking via session recordings and third-party analytics necessitates robust data protection measures, which are not clearly communicated. Overall, the security posture is functional but requires enhancements in policy transparency and technical controls.

Recommendations

  1. Publish a comprehensive privacy policy and make it easily accessible on the website.
  2. Implement and display a cookie consent mechanism to comply with GDPR and other privacy regulations.
  3. Enable DNSSEC for the domain to improve DNS security and prevent spoofing.
  4. Add essential security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  5. Provide clear security policy and incident response contact information to enhance transparency and trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Inspectlet
Description
Inspectlet records videos of your visitors as they use your site, allowing you to see everything they do. See every mouse movement, scroll, click, and keypress on your site. Forget traditional analytics. You never need to wonder how exactly people are using your site again.
Key services
Session Recording, Website Heatmaps, Javascript A/B Testing, Feedback Surveys, Error Logging, Form Analytics
Content quality
good
Branding
consistent

Technology

Stack
Google Analytics, Segment Analytics, jQuery, Font Awesome, Cloudflare DNS
Frameworks
AngularJS (ng-controller detected), Pure CSS, Webflow Icons
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • No exposed sensitive data in HTML
  • Use of async and defer on scripts to improve loading

Analytics and tracking

Services
Google Analytics, Segment
Tracking level
extensive
Privacy practices
poor

Advertising

Tracking pixels
Segment
Marketing tools
Segment
Transparency
basic

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website provides detailed information about session recording and analytics services.
  2. Strong customer trust signals with logos and testimonials.
  3. No visible privacy or cookie policies on homepage HTML content.
  4. Use of modern analytics and tracking technologies.
  5. No contact emails or phone numbers explicitly found in HTML content.
  6. No security.txt or vulnerability disclosure information found.
  7. No visible security policy or incident response information.
  8. Website is well designed and mobile optimized.
  9. Domain registration is stable and consistent with business profile.
Technical notes

Notes

The website is built using a combination of AngularJS, Pure CSS, and standard web technologies with integration of Google Analytics and Segment for analytics. It uses Cloudflare for DNS and likely CDN services, contributing to performance and availability. The site loads scripts asynchronously and defers non-critical JavaScript, improving load times. Mobile optimization is good, and the site is responsive. However, no CMS is detected, indicating a custom or static site approach. Accessibility features are basic but present. SEO is supported by proper meta tags and Open Graph data. Technical risks include lack of DNSSEC and missing security headers, which could be addressed to reduce attack surface. Overall, the technical infrastructure is solid but could benefit from modernization and enhanced security configurations.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Earlier scans of this domain

  1. 61/100Medium32 findingsView report
Reviews of this site

Share your experience with inspectlet.io. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review inspectlet.io.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.