Skip to main content

Security report for crontab.guru

Cronitor.io · Technology · N/a

Medium risk. 9 critical or high findings in Email security, Security headers and 2 other checks.

Security score

60/100

Risk levelMedium

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

Crontab.guru is a specialized web tool providing an easy-to-use editor for cron schedule expressions, primarily targeting developers and system administrators managing cron jobs. The site is closely linked to Cronitor.io, a cron job monitoring service, which it promotes prominently. The business model revolves around offering a free scheduling tool while driving users towards Cronitor's paid monitoring services. The website is professionally designed with consistent branding and clear navigation, reflecting a small but focused technology business.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 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

9 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. 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 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';…

  3. 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

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

Keep watching crontab.guru

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
82
Security headers
15
Email security
40
DNS health
75
Network security
100
GDPR outside view
50
Average
60

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

The website occupies a niche in the cron scheduling and monitoring market, leveraging the Cronitor brand to provide complementary services. Its open source self-hosted dashboard offering indicates a community-oriented approach and technical transparency. The target audience is technical professionals requiring reliable cron job management and monitoring. The site’s partnership with Cronitor.io strengthens its market position, although direct business details such as founding year or company size are not disclosed. The lack of explicit contact information and privacy policies suggests areas for business maturity improvement.

Security posture

The site enforces HTTPS and uses modern web technologies, with no visible security vulnerabilities or exposed sensitive data. However, it lacks several security headers and does not provide explicit privacy or cookie policies, which are important for compliance and user trust. The absence of a security.txt or incident response contact limits transparency in vulnerability handling. Overall, the security posture is good but could be enhanced by adopting best practices in security headers, privacy compliance, and incident response readiness.

Recommendations

  1. Implement and publish comprehensive privacy and cookie policies with user consent mechanisms to improve compliance and trust.
  2. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to harden security posture.
  3. Provide clear contact information for security incidents and consider publishing a security.txt file to facilitate vulnerability disclosures.
  4. Enhance accessibility features to meet compliance standards and improve user experience for all users.
  5. Maintain transparency in WHOIS data or provide alternative trust signals to compensate for privacy-protected domain registration.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Cronitor.io
Description
An easy to use editor for crontab schedules. The site offers a quick and simple editor for cron schedule expressions and promotes Cronitor, a cron job monitoring service.
Key services
Cron schedule expression editor, Cron job monitoring service via Cronitor, Open source self-hosted dashboard for cron jobs
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, SVG, Cronitor RUM script
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No visible sensitive data exposure
  • No vulnerable libraries detected

Analytics and tracking

Services
Cronitor RUM
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Cronitor RUM
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenge.
  2. No explicit privacy, cookie, or terms of service pages found in the main HTML content.
  3. No contact emails or phone numbers explicitly provided on the main page.
  4. Strong branding linkage to Cronitor.io, a known cron monitoring service.
  5. Use of modern web technologies and good SEO practices.
  6. No signs of adult or questionable content.
  7. WHOIS data is unavailable due to TLD not supported and privacy protection.
  8. Site includes a self-hosted open source dashboard promoted via GitHub link.
  9. Minimal tracking via Cronitor RUM script only.
Technical notes

Notes

The website uses a clean, modern tech stack with HTML5, CSS3, JavaScript, and SVG graphics. It integrates a proprietary Cronitor RUM script for performance monitoring and tracking. The site is mobile optimized and loads quickly, with good SEO metadata including Open Graph tags. There is no detected CMS or third-party hosting provider explicitly identified. The site promotes an open source self-hosted dashboard via GitHub, indicating a commitment to open development. Technical risks are minimal, but the absence of some security headers and privacy compliance features represent areas for improvement.
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. 60/100Medium34 findingsView report
Reviews of this site

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

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.