Skip to main content

Security report for sorryapp.com

SorryApp LTD · Technology · N/a

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

Security score

74/100

Risk levelMedium

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

SorryApp LTD operates the website www.sorryapp.com, offering hosted status page solutions designed to integrate seamlessly into incident management workflows. Their services include public and private status pages, incident and maintenance notices, changelogs, and integrations with popular communication platforms such as Slack, Teams, and Google Chat. The company targets businesses and teams that require reliable and timely communication tools to maintain customer trust during incidents and maintenance periods. The business model is SaaS-based with a free trial and enterprise options, positioning SorryApp as a niche player focused on ease of use and integration. Technically, the website is built using modern web technologies including Gatsby, React, and Tailwind CSS, ensuring fast performance, mobile optimization, and good SEO practices. The site employs REST APIs and supports SAML-based SSO for team members, indicating a mature technical infrastructure. Analytics and marketing tools such as ProfitWell, HelpScout Beacon, and Google Tag Manager are used to monitor user engagement and support. From a security perspective, the site enforces HTTPS and offers a dedicated security and performance page. However, explicit security headers like CSP and HSTS are not detected, and there is no public security.txt or incident response contact information. Privacy policies and data processing agreements are comprehensive and GDPR compliant, though a cookie consent mechanism is absent. No vulnerabilities or exposed sensitive data were found in the HTML content. Overall, the website presents a professional, trustworthy, and technically sound platform with minor areas for improvement in security headers and public incident response transparency. The lack of WHOIS data limits full domain legitimacy verification, but the business presence and content quality support a positive trust assessment.

Scanned

This is an earlier scan of sorryapp.com. View the latest report

NIS2 and GDPR posture

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

4 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 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 Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

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

This scan found 17 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
75
Security headers
30
Email security
85
DNS health
85
Network security
100
GDPR outside view
68
Average
74

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

SorryApp LTD occupies a specialized market niche providing status page communication tools that help businesses maintain customer trust during incidents and maintenance. Their competitive advantage lies in seamless integration with existing workflows and communication platforms, a straightforward SaaS subscription model, and enterprise support options. Revenue streams likely include subscription fees from small to medium businesses and enterprise clients. The company demonstrates growth potential through partnerships and customer testimonials from recognized clients. The marketing ecosystem includes analytics and customer support tools, indicating a data-driven approach to customer engagement and retention.

Security posture

The security posture of SorryApp LTD's website is solid with HTTPS enforced and no visible exposure of sensitive data. The use of SAML SSO for team members enhances internal security. However, the absence of explicit security headers such as Content Security Policy and HSTS reduces defense-in-depth. The lack of a public security.txt file and incident response contact information may hinder vulnerability reporting and incident handling transparency. Privacy policies are comprehensive and GDPR compliant, but cookie consent mechanisms are missing. Overall, the security maturity is good but could be improved with additional headers and public security disclosures.

Recommendations

  1. Implement and enforce security headers including Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options to enhance protection against common web attacks.
  2. Publish a security.txt file to facilitate responsible vulnerability disclosure and improve transparency with security researchers.
  3. Add explicit incident response contact information on the website to improve trust and readiness for security incidents.
  4. Introduce a cookie consent mechanism to comply fully with privacy regulations and enhance user privacy control.
  5. Regularly audit third-party scripts and tracking tools to ensure minimal privacy impact and maintain compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
SorryApp LTD
Description
Sorry™ provides hosted status pages that integrate into incident workflows, offering tools for incidents, maintenance, and general announcements to build trust with customers.
Key services
Public Status Pages, Private Status Pages, Incident Notices, Maintenance Notices, General Notices (Changelog), Integrations with Slack, Teams, Google Chat, REST and Status APIs, SSO with any SAML provider
Content quality
excellent
Branding
consistent

Technology

Stack
Gatsby, React, Tailwind CSS, JavaScript, REST API, SAML SSO
Frameworks
Gatsby
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of SSO with SAML
  • Security and performance page available

Analytics and tracking

Services
ProfitWell, Google Tag Manager, Fathom Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
helpscout.net, profitwell.com, googletagmanager.com, usefathom.com
Marketing tools
ProfitWell, Factors.ai, HelpScout Beacon
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with rich content and professional design
  2. No WHOIS data available, which is unusual and may indicate privacy protection or domain registration issues
  3. Strong focus on status page services with clear product offerings and customer testimonials
  4. Use of modern web technologies and integrations with popular tools
  5. No direct contact emails or phone numbers publicly listed, contact primarily via web forms and support beacon
  6. Security and privacy policies are present and comprehensive
  7. No signs of adult or questionable content
  8. No WAF or blocking mechanisms detected
Technical notes

Notes

The website is built on a modern static site generator (Gatsby) using React and styled with Tailwind CSS, resulting in fast load times and excellent mobile responsiveness. The integration of REST APIs and SAML SSO indicates a well-architected backend supporting secure team collaboration. Analytics and marketing tools are integrated thoughtfully, balancing user insights with privacy considerations. The site structure and meta tags support good SEO and accessibility standards. There is no indication of technical debt or outdated technologies, positioning the platform well for scalability and maintainability.
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. 74/100Medium21 findingsView report
Reviews of this site

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