Skip to main content

Security report for titanapps.io

Railsware Products Studio LLC · Technology · United States

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

Security score

66/100

Risk levelMedium

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

TitanApps is a technology company specializing in productivity tools designed for professional teams using Jira and monday.com platforms. Positioned as a trusted Atlassian Platinum Marketplace Partner, TitanApps offers a suite of smart tools including checklists, templates, hierarchy visualization, productivity dashboards, and AI-powered release notes. Their market presence is supported by a client base of over 4000 organizations, including major enterprises such as Cisco, Microsoft, and Amazon. The company operates under the parent organization Railsware Products Studio LLC, based in the US, and was founded in 2022. Technically, the website is built using modern web technologies such as Astro, Google Tag Manager, Microsoft Clarity, and Cookiebot for consent management. Hosting is provided via Amazon AWS infrastructure. While the site demonstrates good mobile optimization, accessibility, and SEO practices, performance is currently slow, likely due to a large page size and resource count. The site integrates multiple analytics and marketing tools, reflecting a mature digital marketing strategy. From a security perspective, the site lacks a valid SSL certificate and does not support modern TLS protocols, which is a critical vulnerability impacting user trust and data security. Other security best practices such as HSTS, OCSP stapling, and security headers are missing or minimal. Email authentication is partially configured with SPF and DMARC (policy none). Privacy compliance is strong, with clear privacy and cookie policies and an active consent mechanism. Business credibility is high, supported by professional content, clear contact information, and trust signals. Overall, TitanApps presents a professional and trustworthy business with a strong market position and comprehensive privacy compliance. However, the lack of HTTPS and weak SSL/TLS configuration represent significant security risks that should be addressed immediately to protect users and maintain reputation.

Scanned

NIS2 and GDPR posture

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

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. 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. DNS health

    DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.

    • High

      Unregistered MX Record

      MX record points to unregistered domain: pnrjecrurgx4c2z7sdc5qfq4b4zkcstcmwlel3z542alqucdy45a.mx-verification.google.com

      What to do: Remove or fix MX record pointing to unregistered domain

      • RFC 5321 §5.1
      • NIS2 21(2)(i)
      • IR 2024/2690 12.4: Implementing Regulation (EU) 2024/2690, Annex point 12.4: Asset inventory
      • NIST CM-8: NIST SP 800-53 Rev. 5 CM-8: System Component Inventory

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

Keep watching titanapps.io

This scan found 22 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. See sample alerts.

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
85
Security headers
15
Email security
75
DNS health
65
Network security
100
GDPR outside view
58
Average
66

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

TitanApps operates in the technology sector, focusing on SaaS productivity tools integrated with popular project management platforms Jira and monday.com. Their business model revolves around providing specialized add-ons and smart tools that enhance workflow management and team productivity. The company targets professional teams and enterprises seeking to optimize project execution and process automation. Their competitive advantage lies in deep integration with Atlassian products, a strong partner ecosystem, and a growing portfolio of innovative tools including AI-powered features. Revenue streams likely include app marketplace sales, subscriptions, and partner program benefits. The presence of a partner program and extensive documentation indicates a strategic approach to community building and customer support. Growth indicators include recent recognition as an Atlassian Partner of the Year finalist and a client base exceeding 4000 organizations. The company maintains a close relationship with its parent Railsware Product Studio, leveraging its resources and reputation.

Security posture

The current security posture of TitanApps' website is moderate to low due to the absence of a valid SSL certificate and lack of HTTPS enforcement. This exposes users to risks such as data interception and undermines trust. While DNS records show SPF and DMARC configurations, the DMARC policy is set to 'none', which limits email spoofing protection. No advanced security headers or mechanisms like HSTS, OCSP stapling, or session resumption are implemented. The site uses secure cookie consent management via Cookiebot, indicating awareness of privacy regulations. No incident response or vulnerability disclosure policies are publicly available, which could be improved to enhance security transparency. Overall, the security maturity is basic, with critical improvements needed in SSL/TLS deployment and security header implementation to align with industry best practices and compliance requirements.

Recommendations

  1. Immediately install and maintain a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and disable deprecated versions to improve security and performance.
  3. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives to enforce HTTPS usage.
  4. Configure OCSP stapling and session resumption to enhance SSL performance and reliability.
  5. Review and enforce a stricter DMARC policy (e.g., quarantine or reject) to improve email security and reduce spoofing risks.
  6. Add comprehensive security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web vulnerabilities.
  7. Publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting and improve security posture.
  8. Consider adding incident response contact channels (e.g., security@ or abuse@ emails) to facilitate security communications.
  9. Optimize website performance by reducing page size and resource count to improve load times and user experience.
  10. Maintain and update privacy and cookie policies regularly to ensure ongoing GDPR and privacy compliance.
Technical notes

Notes

The website is built using Astro, a modern static site generator, combined with client-side libraries such as Swiper.js for sliders and Google Fonts for typography. Analytics and tracking are implemented via Google Tag Manager and Microsoft Clarity, with Cookiebot managing cookie consent. Hosting is on Amazon AWS infrastructure, as indicated by DNS nameservers. The site has a large page size (~847 KB) and high resource count (242), contributing to slow load times (~17.7 seconds). Mobile optimization and accessibility are good, with responsive design and ARIA roles used appropriately. SEO is supported by meta tags, Open Graph images, and canonical URLs. However, the lack of valid SSL and disabled TLS protocols are significant technical risks. The site uses privacy proxy registration for the domain, which is justified given the business type. Overall, the technical infrastructure is modern but requires security and performance improvements to enhance reliability and user trust.
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 titanapps.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 titanapps.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.