Skip to main content

Security report for apphero.co

Technology · United States

Medium risk. 8 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

64/100

Risk levelMedium

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

The website apphero.co/en/timeout/ serves as a session timeout page for a campaign management SaaS platform, requiring users to log in again to continue their work. The business appears to be a small technology company founded around 2018, operating in the marketing technology sector. The page content is minimal, providing only a session expiration notice without additional business or policy information. Technically, the site uses common JavaScript libraries including jQuery and integrates with Google Analytics, Google Tag Manager, and Helpscout Beacon for analytics and customer support. The hosting infrastructure is likely AWS based on DNS records. Security posture is basic with HTTPS enabled but lacks DNSSEC and security headers. No privacy or cookie policies are present, indicating poor privacy compliance. The domain uses WHOIS privacy protection, which is typical for small SaaS businesses but reduces transparency. Overall, the site is accessible and not blocked by any WAF or security challenge.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
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

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

    • 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

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

Keep watching apphero.co

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
77
Security headers
15
Email security
75
DNS health
80
Network security
100
GDPR outside view
35
Average
64

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 operates a SaaS platform focused on campaign management targeting marketers or campaign managers. The business model is subscription or usage-based software delivery. Market positioning is unclear due to lack of visible branding or business details on this page. The platform integrates standard marketing and analytics tools but lacks visible trust indicators such as certifications or customer testimonials. The domain age is consistent with a small startup or growing business. No partnerships or subsidiaries are evident from the data provided.

Security posture

Security maturity is low to moderate. HTTPS is enabled, but no DNSSEC or security headers are implemented. The absence of privacy and cookie policies indicates compliance gaps with GDPR and other privacy regulations. No incident response or vulnerability disclosure information is available. The use of WHOIS privacy protection is common but reduces transparency. Tracking scripts are present, but no consent mechanism is detected. Overall, the security posture requires improvement to meet industry best practices and regulatory requirements.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Publish comprehensive privacy and cookie policies with GDPR compliance details.
  3. Implement security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Add visible contact information and business details to improve trust and credibility.
  5. Establish a vulnerability disclosure policy and incident response contact channels.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
The page indicates a session timeout message for an app related to campaign management, requiring users to log in again to continue working on campaigns.
Key services
Campaign management platform
Content quality
poor
Branding
moderate

Technology

Stack
JavaScript, jQuery, Google Analytics, Google Tag Manager, Helpscout Beacon, AWS DNS
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
40/100
Good practices seen
  • Use of HTTPS (implied by URL https://)
  • Domain status includes clientDeleteProhibited and other EPP protections

Analytics and tracking

Services
Google Analytics, Google Tag Manager, Helpscout Beacon
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
Helpscout Beacon
Marketing tools
Helpscout Beacon
Transparency
poor

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is minimal and only shows a session timeout message.
  2. No privacy, cookie, or terms of service policies found on this page.
  3. No contact information or business details visible on this page.
  4. Uses multiple external tracking and analytics services.
  5. No security headers or DNSSEC enabled.
  6. Domain uses privacy protection for WHOIS.
  7. Page is accessible and not blocked by WAF or security challenge.
Technical notes

Notes

The website uses a standard JavaScript stack with jQuery and integrates third-party analytics and support tools. Hosting appears to be on AWS infrastructure. The page is minimal and likely part of a larger web application. Performance is moderate with basic mobile optimization. SEO and accessibility are minimal due to lack of meta tags and structured content. No CMS or frameworks are explicitly detected. Technical debt is low but modernization opportunities exist in security and privacy compliance.
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 apphero.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 apphero.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.