Security report for puzzel.com

Name: Dark-web exposure summary for puzzel.com
Creator: OffSeq Breach

Puzzel · Technology · Norway

High risk. 16 critical or high findings in Network security, Security headers and 2 other checks.

Security score

49/100

Risk levelHigh

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

Puzzel is a Norway-based AI-native customer experience (CX) ecosystem provider offering a modular SaaS platform designed to empower contact centers with AI-powered tools such as conversational intelligence, workforce management, and virtual agents. The company targets CX leaders and enterprises seeking to improve customer service efficiency and personalization. The website demonstrates a mature digital presence with modern technologies including HubSpot CMS, Google Analytics 4, and multiple marketing and tracking integrations. Security posture is strong with HTTPS, security headers, and cookie consent mechanisms, though explicit security policies and incident response details are not publicly available. The absence of public WHOIS data reduces transparency but the overall business credibility is supported by consistent branding, detailed product offerings, and customer trust signals. Strategic recommendations include publishing security and incident response policies, adding vulnerability disclosure mechanisms, and enhancing direct contact information for security and compliance inquiries.

Scanned

NIS2 and GDPR posture

GDPR outside view: 68/ 100 · Medium
Checks completed: 7of 7

NIS2 Art. 21(2)

(a) Risk analysis and security policies: Not visible from outside
(b) Incident handling: One indicator
(c) Business continuity, backups and crisis management: Not visible from outside
(d) Supply chain security: Not visible from outside
(e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
(f) Assessing the effectiveness of security measures: Not visible from outside
(g) Cyber hygiene and security training: Not visible from outside
(h) Cryptography and encryption: Partly checked
(i) HR security, access control and asset management: One indicator
(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

16 findings rated critical or high. Fix these first.

Network security
Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.
- Critical
  Critical Service Exposed: Telnet
  Port 23 (Telnet) is publicly accessible - Telnet - Unencrypted remote access
  What to do: Immediately restrict access to Telnet using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: SMB
  Port 445 (SMB) is publicly accessible - SMB - Windows file sharing, high risk
  What to do: Immediately restrict access to SMB using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: MSSQL
  Port 1433 (MSSQL) is publicly accessible - MSSQL - Database server
  What to do: Immediately restrict access to MSSQL using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: Oracle
  Port 1521 (Oracle) is publicly accessible - Oracle - Database server
  What to do: Immediately restrict access to Oracle using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: MySQL
  Port 3306 (MySQL) is publicly accessible - MySQL - Database server
  What to do: Immediately restrict access to MySQL using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: RDP
  Port 3389 (RDP) is publicly accessible - RDP - Remote Desktop, prime ransomware target
  What to do: Immediately restrict access to RDP using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: PostgreSQL
  Port 5432 (PostgreSQL) is publicly accessible - PostgreSQL - Database server
  What to do: Immediately restrict access to PostgreSQL using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: Redis
  Port 6379 (Redis) is publicly accessible - Redis - In-memory database
  What to do: Immediately restrict access to Redis using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: MongoDB
  Port 27017 (MongoDB) is publicly accessible - MongoDB - NoSQL database
  What to do: Immediately restrict access to MongoDB using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- High
  High-Risk Service Exposed: FTP
  Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer
  What to do: Consider restricting access to FTP or implementing strong authentication
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- High
  High-Risk Service Exposed: RPC
  Port 135 (RPC) is publicly accessible - RPC - Windows RPC endpoint
  What to do: Consider restricting access to RPC or implementing strong authentication
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- High
  High-Risk Service Exposed: NetBIOS
  Port 139 (NetBIOS) is publicly accessible - NetBIOS - Windows file sharing
  What to do: Consider restricting access to NetBIOS or implementing strong authentication
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- High
  High-Risk Service Exposed: Elasticsearch
  Port 9200 (Elasticsearch) is publicly accessible - Elasticsearch - Search engine
  What to do: Consider restricting access to Elasticsearch or implementing strong authentication
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
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"
  References
  - CWE-1021
  - OWASP A06:2025
  - CAPEC-103
  - ASVS V3.4.6
  - OWASP Secure Headers: OWASP Secure Headers Project recommends X-Frame-Options: deny
  - RFC 7034
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
  References
  - ePrivacy Art. 5(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
  References
  - CWE-326
  - OWASP A04:2025
  - Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048
  - NIS2 21(2)(h)
  - IR 2024/2690 9.2(b): Implementing Regulation (EU) 2024/2690, Annex point 9.2(b): Cryptography
  - NIST SC-13: NIST SP 800-53 Rev. 5 SC-13: Cryptographic Protection

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

Keep watching puzzel.com

This scan found 32 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: 55
Email security: 80
DNS health: 80
Network security: 0
GDPR outside view: 68
Average: 60
After the cap: 49

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 · found on this site
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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention puzzel.com, from OffSeq Breach.

Total records: 425
Employees: 4
Customers: 383
Third parties: 38
Weak passwords: 12%

Latest record dated 2026-01-13 · 16 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for puzzel.com.

Select it in the checkout above.

Masked preview

–hub.puzzel.com2026-01-13
–presencehub.puzzel.com2025-07-30
–presencehub.puzzel.com2025-07-19
–presencehub.puzzel.com2025-04-14

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach Monitor on Breach

Technical appendix

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

Business context

Business profile

Puzzel occupies a strong position in the European CX technology market with over 25 years of experience. Its AI-native approach and modular product suite provide competitive advantages in delivering scalable, human-first customer service solutions. The business model is SaaS-based with a focus on flexibility and integration across industries including retail, banking, energy, and government. The company leverages partnerships and a comprehensive marketing ecosystem to drive growth. The website content and customer logos indicate a medium-sized enterprise with a focus on innovation and customer-centric values. No parent or subsidiary companies were identified from the data provided.

Security posture

The website enforces HTTPS with strong SSL configuration and implements key security headers, indicating good baseline security hygiene. Cookie consent and privacy policies demonstrate GDPR compliance. However, the lack of a published security policy, incident response plan, or vulnerability disclosure program limits transparency and may impact trust for security-conscious customers. No vulnerabilities or exposed sensitive data were detected in the HTML content. The use of multiple third-party tracking scripts requires ongoing monitoring to mitigate supply chain risks. Overall, the security posture is good but could be improved with enhanced transparency and dedicated security communications.

Recommendations

Publish a detailed security policy and incident response plan on the website.
Implement and publicize a vulnerability disclosure program or security.txt file.
Provide direct security contact emails (e.g., security@puzzel.com) for incident reporting.
Regularly audit third-party scripts and tracking tools for security and privacy compliance.
Enhance transparency on data retention and processing policies to strengthen GDPR compliance.

Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company: Puzzel
Description: Puzzel is the AI-native CX ecosystem designed to help agents deliver faster and more human service at scale with less effort and more impact. It offers a modular, AI-powered contact center platform with solutions for conversational intelligence, workforce management, case management, and virtual agents.
Key services: Contact Centre Suite, Conversational Intelligence, Workforce Management, Case Management, Virtual Agent Suite, Quality Management, Knowledge Management
Content quality: excellent
Branding: consistent

Technology

Stack: HubSpot CMS, Google Fonts, Google Tag Manager, Google Analytics 4, Lottie animations, JavaScript libraries for analytics and tracking
Frameworks: HubSpot CMS framework
Platforms: HubSpot
Performance: moderate
Mobile: excellent
Accessibility: good
SEO: good

Security

Observed score

85/100

Good practices seen

HTTPS enforced
Cookie consent banner with opt-in/out
No exposed sensitive data in HTML
Use of security headers

Analytics and tracking

Services: Google Analytics 4, Dreamdata, HubSpot Analytics
Tracking level: extensive
Privacy practices: good

Advertising

Ad networks: Google Ads, Facebook Ads, Bing Ads, LinkedIn Ads, Reddit Ads
Tracking pixels: Google Analytics 4, Facebook Pixel, LinkedIn Insight Tag, Bing UET
Marketing tools: HubSpot Marketing, Dreamdata Analytics, Factors AI
Transparency: good

Site quality

Design: excellent
User experience: excellent
Content relevance: excellent
Navigation: excellent
Professionalism: excellent
Trustworthiness: high

Key observations

Website is fully accessible with rich content and navigation
Strong branding and consistent design
Comprehensive product and industry coverage
Use of modern web technologies and analytics
Cookie consent and privacy policy present and GDPR compliant
No direct contact emails or phone numbers publicly listed, only contact forms
No explicit security policy or incident response info found
WHOIS data unavailable or domain not found in public WHOIS
No signs of adult or questionable content
Multiple third-party tracking and advertising scripts present

Technical notes

Notes

The website is built on the HubSpot CMS platform, utilizing modern web technologies including Google Fonts, Lottie animations, and multiple analytics and marketing integrations. The site is mobile-optimized with responsive design and good accessibility features. Performance is moderate, with potential improvements possible by optimizing third-party scripts and image loading. SEO is well addressed with proper meta tags and Open Graph data. The technical infrastructure supports a professional and scalable digital presence aligned with the company's AI-native CX ecosystem branding.

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.

OWASP Top 10:2025 (opens in a new tab)2025 (membership per CWE 4.20) · CC BY-SA 4.0
OWASP ASVS (opens in a new tab)5.0.0 · CC BY-SA 4.0
OWASP Web Security Testing Guide (opens in a new tab)latest (checklist.json, master) · CC BY-SA 4.0
OWASP Secure Headers Project (opens in a new tab)2026-10-18 · Apache-2.0
Mozilla Server Side TLS (intermediate) (opens in a new tab)6.0 · MPL-2.0
NIST SP 800-53 Rev. 5 (OSCAL catalog) (opens in a new tab)5.2.0 · Public domain (US Government work)
Directive (EU) 2022/2555 (NIS2) (opens in a new tab)OJ L 333, 27.12.2022 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Commission Implementing Regulation (EU) 2024/2690 (opens in a new tab)OJ L, 18.10.2024 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Regulation (EU) 2016/679 (GDPR) (opens in a new tab)OJ L 119, 4.5.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Directive 2002/58/EC (ePrivacy), consolidated (opens in a new tab)19.12.2009 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
RFC Editor metadata (opens in a new tab)per-RFC (obsolete RFCs rejected) · IETF Trust Legal Provisions (metadata only)
NIST CSRC, W3C TR, IETF Datatracker, EDPB, EUR-Lex CELLAR and gesetze-bayern.de (opens in a new tab)per document · Titles and links only
W3C WCAG 2.2 (opens in a new tab)W3C Recommendation (wcag.json) · W3C Software and Document License
Directive (EU) 2019/882 (European Accessibility Act) (opens in a new tab)OJ L 151, 7.6.2019 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Directive (EU) 2016/2102 (Web Accessibility Directive) (opens in a new tab)OJ L 327, 2.12.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)

Retrieved 2026-10-25

Earlier scans of this domain

7 Sept 202549/100 −23High41 findingsView report
14 Jun 202572/100Medium28 findingsView report

Feedback on this report

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

Priority findings

Network security

Critical Service Exposed: Telnet

Critical Service Exposed: SMB

Critical Service Exposed: MSSQL

Critical Service Exposed: Oracle

Critical Service Exposed: MySQL

Critical Service Exposed: RDP

Critical Service Exposed: PostgreSQL

Critical Service Exposed: Redis

Critical Service Exposed: MongoDB

High-Risk Service Exposed: FTP

High-Risk Service Exposed: RPC

High-Risk Service Exposed: NetBIOS

High-Risk Service Exposed: Elasticsearch

Security headers

Missing X-Frame-Options header

GDPR outside view

No Cookie Policy found

SSL/TLS

Weak SSL Key Length

Keep watching puzzel.com

Daily monitoring

Full report

Results by check

Security headers, 5 findings, score 55/100

SSL/TLS, 3 findings, score 75/100

Email security, 4 findings, score 80/100

DNS health, 3 findings, score 80/100

Network security, 14 findings, score 0/100

GDPR outside view, 3 findings, score 68/100

NIS2 outside view, Earlier method, rescan for details · not counted in the security score–