Skip to main content

Security report for trailhub.io

Call-tracking aps · Information technology and services

Medium risk. 5 critical or high findings in Security headers, SSL/TLS and 1 other check.

Security score

53/100

Risk levelMedium

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

Scanned

NIS2 and GDPR posture

GDPR outside view
83/ 100 · Low
Checks completed
5of 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 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';…

  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 Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

  3. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • 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

      • 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

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

Keep watching trailhub.io

This scan found 14 issues across 4 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
77
Security headers
30
Network security
20
GDPR outside view
83
Average
53

Not counted

  • Email security: did not complete in this scan.
  • DNS health: did not complete in this scan.
  • 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

Trailhub holds a strong market position in Denmark's call tracking sector, leveraging SaaS delivery and digital marketing integrations such as Hubspot and Google Analytics. The company targets small to medium-sized enterprises requiring detailed call analytics to improve marketing spend efficiency. Their business model relies on subscription revenue with a free trial to lower entry barriers. Social media presence on Facebook and LinkedIn supports brand visibility and customer engagement. The absence of explicit contact details on the homepage suggests a focus on digital lead capture rather than direct sales. No parent or subsidiary companies were identified, indicating an independent operation. The company demonstrates compliance with privacy regulations through comprehensive cookie consent and a detailed privacy policy.

Security posture

The website enforces HTTPS with a valid SSL certificate and includes several security headers enhancing protection against common web threats. Cookie consent is implemented with granular user controls, reflecting GDPR compliance. No critical vulnerabilities or exposed sensitive data were detected in the HTML content. However, the lack of DNSSEC and absence of a security.txt file or published incident response policy represent areas for improvement. The site does not appear to use a Web Application Firewall or other advanced security mechanisms. Overall, the security posture is good for a small SaaS provider but could be enhanced by adopting additional domain security measures and formalizing security policies.

Recommendations

  1. Enable DNSSEC on the domain to protect against DNS spoofing and improve domain security.
  2. Publish a security.txt file to facilitate responsible vulnerability disclosure and improve transparency.
  3. Develop and publish explicit security and incident response policies to demonstrate security maturity.
  4. Implement a comprehensive Content Security Policy to mitigate cross-site scripting and related attacks.
  5. Enhance website accessibility features to meet higher compliance standards and improve user experience.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Trailhub ApS
Description
Danmarks førende Call Tracking-platform, offering software to track phone calls and analyze marketing effectiveness.
Key services
Call Tracking software, Marketing analytics, Call attribution
Content quality
good
Branding
consistent

Technology

Stack
WordPress, Yoast SEO plugin, Google Tag Manager, Google Analytics, Cookiebot
Frameworks
WPBakery Page Builder
Platforms
AWS (based on DNS nameservers)
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Cookie consent with opt-in/out
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics, Hubspot Analytics
Tracking level
extensive
Privacy practices
good

Advertising

Ad networks
Google Ads, Meta Platforms (Facebook)
Tracking pixels
Facebook Pixel, Hubspot tracking
Marketing tools
Hubspot, Cookiebot
Transparency
good

Site quality

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

Key observations

  1. Website uses HTTPS with valid SSL certificate.
  2. Cookie consent implemented with detailed cookie categories and opt-in/out toggles.
  3. No explicit contact emails or phone numbers found on homepage or metadata.
  4. Social media presence on Facebook and LinkedIn confirmed via JSON-LD and links.
  5. No visible security.txt or vulnerability disclosure page.
  6. No terms of service page detected.
  7. Website built on WordPress with common SEO and analytics plugins.
  8. DNSSEC not enabled, which is a minor security gap.
  9. No signs of WAF or blocking mechanisms.
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 trailhub.io. 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 trailhub.io.

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.