Skip to main content

Security report for instana.io

Instana · Technology · N/a

Low risk. 3 critical or high findings in Security headers and GDPR outside view.

Security score

76/100

Risk levelLow

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

Instana is a technology company specializing in application performance monitoring and observability solutions tailored for cloud-native and microservices environments. Positioned as an enterprise-grade SaaS provider, it operates under the IBM corporate umbrella, leveraging IBM's infrastructure and compliance frameworks. The website analyzed is primarily a login portal for users to access Instana's monitoring services, featuring integration with Google Single Sign-On for streamlined authentication. From a technical perspective, the site employs modern TLS protocols (TLS 1.3 and 1.2) with valid SSL certificates covering the domain and subdomains. Hosting is managed via Amazon AWS, ensuring reliable DNS and infrastructure performance. However, some security best practices such as HSTS, OCSP stapling, and security headers are not implemented, which could be improved to enhance the security posture. Security-wise, the domain has a valid SPF record and a DMARC policy set to quarantine a small percentage of emails, indicating attention to email security. No critical vulnerabilities or exposed sensitive data were detected. Privacy compliance is supported by comprehensive privacy and terms documents hosted on IBM domains, though no cookie consent mechanism was found on the login page. Overall, the site demonstrates a solid but improvable security and privacy posture. The overall risk assessment suggests a well-maintained enterprise SaaS platform with moderate technical and security maturity. Strategic recommendations include enhancing HTTPS security headers, enabling HSTS and OCSP stapling, publishing a formal security policy, and implementing cookie consent mechanisms to improve privacy compliance and user trust.

Scanned

This is an earlier scan of instana.io. View the latest report

NIS2 and GDPR posture

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

3 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

  2. GDPR outside view

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

    • 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

    • 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

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

Keep watching instana.io

This scan found 18 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
92
Security headers
65
Email security
65
DNS health
90
Network security
100
GDPR outside view
43
Average
76

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

Instana operates in the competitive application performance monitoring and observability market, targeting enterprise customers deploying cloud-native and microservices architectures. Its integration into IBM's portfolio provides a strong market position and access to a broad customer base. The business model is SaaS-based, generating revenue through subscriptions to its monitoring platform. The company leverages partnerships and IBM's infrastructure for hosting and compliance, which strengthens its operational capabilities. Growth indicators include adoption of modern authentication methods like Google SSO and continuous investment in cloud infrastructure. The lack of direct contact information on the login page suggests a focus on existing customers and enterprise sales channels rather than direct consumer engagement.

Security posture

The security posture of the Instana website is solid but has room for improvement. HTTPS is properly implemented with modern TLS versions and valid certificates. Email security is addressed with SPF and DMARC policies. However, the absence of HSTS, OCSP stapling, and security headers reduces the overall security hardening. No known vulnerabilities or exposed sensitive data were found. The site lacks a published security policy or incident response contact, which are important for transparency and trust. Privacy compliance is supported by IBM-hosted policies, but cookie consent mechanisms are missing. Overall, the site reflects an enterprise-level security baseline but should enhance security controls and transparency to meet best practices and regulatory expectations.

Recommendations

  1. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload flags to enforce HTTPS.
  2. Implement OCSP stapling to improve SSL certificate revocation checking and reduce latency.
  3. Add essential security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Publish a clear security policy and incident response contact information on the website.
  5. Introduce a cookie consent banner and cookie policy to comply with privacy regulations and enhance user trust.
Technical notes

Notes

The website is hosted on Amazon AWS infrastructure with DNS managed by AWS Route 53. It supports modern TLS protocols (1.3 and 1.2) with a valid SSL certificate covering the domain and subdomains. The site uses standard web technologies including HTML5, CSS, and JavaScript. Performance is moderate with a page load time of approximately 3.3 seconds and a small page size (~9 KB). No CMS or advanced frameworks were detected from the HTML content. The site lacks advanced SEO and accessibility features but maintains a clean and professional login interface. Technical debt appears low, but improvements in security headers and performance optimizations could enhance the overall technical maturity.
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/100 +1Medium27 findingsView report
  2. 73/100Medium29 findingsView report
Reviews of this site

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