Skip to main content

Security report for desktime.com

DeskTime · Technology · N/a

Low risk. 2 critical or high findings in Security headers and SSL/TLS.

Security score

78/100

Risk levelLow

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

DeskTime is a well-established SaaS company specializing in time tracking and productivity analysis software for both remote and on-site teams. The website presents a comprehensive suite of features including automatic time tracking, project tracking, productivity insights, integrations, analytics, and workforce management. The business targets managers and employees seeking to optimize work efficiency and transparency. The domain age and WHOIS data confirm a long-standing presence in the market, supporting the company's credibility. Technically, the website leverages modern web technologies such as Alpine.js for interactivity, Cloudflare for DNS and CDN services, and integrates multiple third-party marketing and analytics tools including Google Tag Manager, Cookiebot for consent management, and Survicate for surveys. The site is well-optimized for performance, mobile responsiveness, and accessibility, reflecting a mature digital infrastructure. From a security perspective, DeskTime enforces HTTPS, employs standard security headers, and provides clear privacy and cookie policies with consent mechanisms, indicating a strong commitment to user data protection and compliance. However, DNSSEC is not enabled, and no explicit vulnerability disclosure or incident response contacts are published, which could be improved. Overall, the website is professional, trustworthy, and secure, with no indications of malicious activity or content safety concerns. The business demonstrates a solid market position with consistent branding and high-quality content. Strategic recommendations include enabling DNSSEC, publishing a security.txt file, and enhancing incident response transparency to further strengthen security posture and trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
88/ 100 · Low
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

2 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 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. 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 desktime.com

This scan found 16 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
60
Security headers
45
Email security
87
DNS health
85
Network security
100
GDPR outside view
88
Average
78

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

DeskTime operates in the technology sector, providing essential productivity and time tracking tools primarily to medium-sized businesses and teams. Their SaaS subscription model with a free trial lowers entry barriers and supports customer acquisition. The company’s market positioning is reinforced by a long domain history and positive user reviews. Their integration ecosystem with popular platforms like Jira, Asana, Outlook, and Google Calendar enhances their competitive advantage. The website content and resources indicate a focus on transparency, accountability, and hybrid work support, aligning with current workforce trends. The absence of explicit parent or subsidiary companies suggests an independent operation with a focused product offering.

Security posture

The security maturity of DeskTime’s website is high, with HTTPS enforced and multiple security headers likely in place. The presence of cookie consent and privacy policy pages demonstrates compliance with GDPR and other privacy regulations. The use of reputable third-party services for analytics and customer support is balanced with privacy considerations. No exposed sensitive data or vulnerable libraries were detected in the HTML content. However, the lack of DNSSEC and absence of a published vulnerability disclosure policy or security.txt file represent areas for improvement. Incident response contact information is not publicly available, which could hinder rapid communication in case of security events. Overall, the security posture is strong but could benefit from enhanced transparency and DNS security.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Publish a security.txt file to provide clear vulnerability disclosure guidelines and contact information.
  3. Add explicit incident response contact channels such as security@ or abuse@ email addresses.
  4. Regularly audit and update third-party scripts and libraries to mitigate potential vulnerabilities.
  5. Enhance trust signals by obtaining and displaying recognized security certifications or compliance badges.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
DeskTime
Description
DeskTime time tracker lets you track work time and analyze productivity to see how your team's time is spent. Try time tracking with our free 14-day trial!
Key services
Automatic time tracking, Project time tracking, Productivity insights, Integrations & API, Analytics & reports, Workforce management
Content quality
excellent
Branding
consistent

Technology

Stack
Cloudflare DNS, Google Tag Manager, Cookiebot, Survicate, Zendesk Web Widget, Quora Qevents, Lottie animations, Alpine.js (x-data directives), Web fonts (Source Sans Pro, Lucide)
Frameworks
Alpine.js
Platforms
Web
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Cookie consent mechanism
  • No exposed sensitive data in HTML
  • Service worker unregister script to avoid stale caches

Analytics and tracking

Services
Google Analytics, Google Ads conversion tracking, Quora Events, Survicate
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Google Analytics (via gtag), Quora Qevents, Survicate surveys
Marketing tools
Cookiebot, Survicate
Transparency
good

Site quality

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

Key observations

  1. Professional SaaS website for time tracking and productivity software.
  2. Comprehensive feature set with clear navigation and multilingual support.
  3. Strong privacy and cookie consent mechanisms implemented.
  4. Use of modern web technologies and third-party analytics and marketing tools.
  5. No signs of malicious or suspicious content.
  6. WHOIS data supports legitimacy and long-term operation.
Technical notes

Notes

DeskTime’s website is built on a modern technology stack including Alpine.js for frontend interactivity and Cloudflare for DNS and CDN services, ensuring fast and reliable content delivery. The site uses web fonts and Lottie animations for a polished user experience. Google Tag Manager and Cookiebot are integrated for analytics and privacy compliance. The website is mobile-optimized and accessible, with clear navigation and multilingual support. Performance is fast, and SEO best practices are followed with proper meta tags and Open Graph data. The technical infrastructure is robust with minimal technical debt, though enabling DNSSEC and publishing security-related metadata would further enhance the technical security posture.
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

Reviews of this site

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