Skip to main content

Security report for slaask.com

Slaask, Inc. · Technology · N/a

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

Security score

67/100

Risk levelMedium

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

Slaask, Inc. operates a SaaS platform that integrates customer service communication directly into Slack, targeting businesses that use Slack as their primary collaboration tool. The company positions itself as a niche leader specializing exclusively in Slack-based customer messaging, offering services such as chatbot creation, lead and customer communication unification, and integrations with popular CRM and marketing tools. The website is professionally designed, mobile-optimized, and provides clear navigation and relevant content for its target audience of SMBs and larger enterprises. Technically, the website is built on WordPress with modern JavaScript libraries and integrates multiple analytics and marketing tools including Google Analytics, Facebook Pixel, and Albacross. The site uses HTTPS with good SSL configuration but lacks some security headers and cookie consent mechanisms, which are areas for improvement. The site is accessible with no WAF or blocking detected, and SEO is enhanced by Yoast plugin and structured data. From a security perspective, the site demonstrates good practices such as HTTPS enforcement and no visible sensitive data exposure. However, it lacks explicit security policies, incident response contacts, and vulnerability disclosure mechanisms. Privacy compliance is basic with a privacy policy present but no cookie consent banner or GDPR-specific indicators. WHOIS data for the subdomain is unavailable as expected, but the main domain is presumed legitimate based on website content and branding. Overall, the website presents a moderate to good security posture and business credibility with room for enhancements in privacy compliance and security transparency. The risk level is low, but strategic improvements in security headers, cookie consent, and incident response documentation are recommended to strengthen trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 100 · Medium
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

5 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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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 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

  3. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching slaask.com

This scan found 23 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
75
Security headers
30
Email security
75
DNS health
70
Network security
100
GDPR outside view
53
Average
67

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

Slaask operates in the technology sector with a focused SaaS business model targeting Slack users for customer service solutions. Its competitive advantage lies in its hyperspecialization on Slack, being the first fully funded Slack-based company. The company leverages integrations with numerous CRM and marketing platforms to enhance its offering. The target customers range from SMBs to large enterprises seeking unified customer communication. The presence of testimonials, social media engagement, and integration partnerships indicate a growing and credible market presence. Revenue streams are likely subscription-based with tiered pricing. The company maintains a consistent brand and professional online presence, supporting its market positioning as a niche leader.

Security posture

The security maturity level is moderate with HTTPS enforced and no visible sensitive data leaks. However, the absence of security headers such as Content-Security-Policy and lack of explicit incident response or vulnerability disclosure policies indicate gaps. Privacy compliance is basic with a privacy policy but no cookie consent or GDPR-specific mechanisms. The site uses multiple tracking and marketing tools, which may raise privacy concerns without explicit user consent. Incident response readiness and security culture indicators are not publicly documented. Overall, the security posture is adequate for a SaaS provider but requires enhancements to meet higher compliance and trust standards.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web attacks.
  2. Add a cookie consent banner and explicit GDPR compliance statements to improve privacy compliance and user trust.
  3. Publish a detailed security policy and incident response plan accessible to users and partners.
  4. Create and maintain a vulnerability disclosure program or security.txt file to encourage responsible reporting of security issues.
  5. Enhance accessibility features and conduct regular security audits to maintain and improve overall security posture.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Slaask, Inc.
Description
Slaask is a customer service application that integrates customer and team communication into Slack, enabling businesses to interact with leads and customers from multiple channels in one place.
Key services
Customer messaging integration with Slack, Chatbot creation aligned with company branding, Lead and customer communication unification, Integration with multiple CRM and marketing tools
Content quality
good
Branding
consistent

Technology

Stack
WordPress 4.7.29, jQuery 3.2.1, Google Analytics, Facebook Pixel, Yoast SEO plugin, Slack API integration, Albacross tracking, Rewardful, Twitter widgets
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of asynchronous script loading

Analytics and tracking

Services
Google Analytics, Facebook Pixel, Albacross
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Facebook Pixel, Albacross, Rewardful
Marketing tools
Facebook Pixel, Albacross, Rewardful
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is business-focused, targeting Slack users for customer service solutions.
  3. No direct contact emails or phone numbers found on the landing page.
  4. Privacy and legal pages are present but cookie consent is missing.
  5. Multiple social media profiles linked, indicating active engagement.
  6. Use of modern marketing and analytics tools.
  7. No security.txt or explicit vulnerability disclosure found.
  8. WHOIS query failure is due to subdomain query, not domain registration issues.
Technical notes

Notes

The website is built on WordPress 4.7.29 with jQuery and uses several third-party scripts for analytics and marketing, including Google Analytics, Facebook Pixel, and Albacross. The site is mobile-optimized and uses Yoast SEO for search engine optimization. Performance is moderate with asynchronous loading of scripts. The technical stack is modern but could benefit from updates to WordPress and libraries to reduce technical debt. Hosting provider details are not explicit. There is no evidence of advanced frameworks beyond WordPress. The site lacks some security best practices such as security headers and cookie consent mechanisms, which are important for compliance and security. Overall, the technical infrastructure supports the business needs but has room for modernization and security improvements.
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. 64/100Medium30 findingsView report
Reviews of this site

Share your experience with slaask.com. 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 slaask.com.

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.