Skip to main content

Security report for clerk.co

Clerk · Finance · United States

High risk. 10 critical or high findings in GDPR outside view, SSL/TLS and 2 other checks.

Security score

44/100

Risk levelHigh

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

Clerk is a small financial services provider specializing in corporate financial management for profitable, owner-led businesses in the United States and Canada. The website is minimalistic, serving primarily as an informational landing page with a clear description of services and a referral to a sister company for further contact. The technical infrastructure is basic, relying on vanilla JavaScript and Google Fonts, with no detected CMS or advanced frameworks. Mobile optimization is adequate, but accessibility and SEO features are minimal. Security posture is weak due to lack of HTTPS confirmation, absence of security headers, and no visible privacy or cookie policies. No contact information or forms are provided, limiting user engagement and trust signals. Overall, the site presents a professional but sparse digital presence.

Scanned

NIS2 and GDPR posture

GDPR outside view
10/ 100 · Critical
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

10 findings rated critical or high. Fix these first.

  1. GDPR outside view

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

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

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

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

Keep watching clerk.co

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
0
Security headers
15
Email security
75
DNS health
65
Network security
100
GDPR outside view
10
Average
44

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 company targets a niche market of profitable, owner-led businesses in North America, positioning itself as a specialized financial management service provider. The business model appears service-oriented with a focus on corporate financial management. The external link to a sister company suggests a partnership ecosystem that may handle client interactions or complementary services. The lack of detailed business information, such as founding year or company size, limits deeper analysis. The minimal web presence may reflect a boutique or emerging firm with limited digital marketing efforts.

Security posture

The website lacks fundamental security features such as HTTPS enforcement and security headers, which are critical for protecting user data and establishing trust. No privacy or cookie policies are published, indicating potential compliance gaps with GDPR and other privacy regulations. The absence of contact information for security incidents or vulnerability disclosure mechanisms further reduces the security maturity level. No signs of vulnerable libraries or exposed sensitive data were detected, but the overall security posture is weak and requires significant improvements to meet industry standards.

Recommendations

  1. Implement HTTPS with a valid SSL/TLS certificate to secure all communications.
  2. Publish comprehensive privacy and cookie policies to enhance compliance and user trust.
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Provide clear contact information including emails and phone numbers for general and security inquiries.
  5. Establish a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Clerk
Description
Clerk provides corporate financial management services to profitable, owner-led businesses in the United States and Canada.
Key services
corporate financial management services
Content quality
basic
Branding
consistent

Technology

Stack
Vanilla JavaScript, Google Fonts (Arvo)
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
30/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a simple single-page site with minimal content.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact emails or phone numbers explicitly provided on the site.
  4. External link to sister company origami.ca is present.
  5. No forms or data collection mechanisms detected.
  6. No social media links or phone numbers found.
  7. No security headers or HTTPS status available from provided data.
  8. No structured data (JSON-LD) found.
  9. Site uses Google Fonts and vanilla JavaScript for UI.
  10. No analytics or tracking scripts detected.
Technical notes

Notes

The website is built with simple HTML, CSS, and vanilla JavaScript, using Google Fonts for typography. There is no evidence of a CMS or advanced frameworks. The site is responsive and adapts to various screen sizes, but accessibility features are basic. Performance is moderate, with no heavy scripts or external dependencies detected. SEO optimization is minimal, relying mainly on meta tags and Open Graph data. The lack of analytics or tracking scripts suggests limited data collection and user behavior analysis. Hosting provider and server details are not available from the provided data.
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 clerk.co. 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 clerk.co.

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.