Skip to main content

Security report for integrationeye.com

Integsoft, Inc. · Technology · Czech Republic

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

Security score

68/100

Risk levelMedium

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

Integration Eye is a modular software product developed by Integsoft, Inc., focused on API monitoring, logging, and security. The product targets businesses and developers requiring robust API management and security solutions. The website presents detailed product features, modular architecture, and transparent pricing, positioning itself as a niche provider in the technology sector. The company emphasizes on-premise and private cloud deployment options, catering to customers with strict data privacy requirements. Technically, the website leverages a modern technology stack including Java, Mule Runtime, XML configurations, and popular web libraries such as jQuery and FontAwesome. It integrates analytics and marketing tools like Google Analytics and Hotjar, indicating a mature digital presence. The site is well-structured, mobile-optimized, and provides comprehensive documentation and demos, reflecting good digital maturity. From a security perspective, the site uses HTTPS and implements CSRF tokens and cookie consent mechanisms, demonstrating basic security hygiene. However, the absence of explicit security headers and a published security policy or incident response contact reduces its security posture. The missing WHOIS domain registration data is a significant concern, potentially impacting trust and legitimacy. Overall, the website is professional and content-rich but requires improvements in domain registration transparency and enhanced security practices to strengthen trust and compliance.

Scanned

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 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 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 Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

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

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

Keep watching integrationeye.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. 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
62
Security headers
55
Email security
95
DNS health
85
Network security
40
GDPR outside view
68
Average
68

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

Integration Eye operates in the technology sector, offering modular API monitoring and security solutions. Its business model revolves around software licensing with transparent pricing tiers, including demo, start-up, and production licenses. The company targets enterprises and developers needing API management tools with on-premise deployment options. The presence of detailed documentation and online demos suggests a customer-centric approach. Partnerships with Integsoft entities indicate a broader ecosystem. The lack of public contact emails and phone numbers on the about page suggests controlled communication channels, likely via contact forms. The missing WHOIS data raises questions about domain ownership, which could affect customer confidence and market positioning.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enabled, CSRF protection, and cookie consent mechanisms. However, it lacks critical security headers such as Content-Security-Policy and HSTS, which are industry best practices. No published security policy or incident response contacts are found, limiting transparency and readiness for security incidents. The absence of vulnerability disclosure or security.txt files further reduces security openness. The missing WHOIS registration data is a red flag that could indicate domain registration issues or privacy concerns. Overall, while basic security measures are in place, significant improvements are needed to enhance trust and compliance.

Recommendations

  1. Implement and enforce security headers including Content-Security-Policy, X-Frame-Options, and HSTS to improve protection against common web attacks.
  2. Publish a clear security policy and provide incident response contact information to enhance transparency and readiness.
  3. Establish a vulnerability disclosure program or publish a security.txt file to encourage responsible reporting of security issues.
  4. Investigate and resolve the missing WHOIS domain registration data to improve domain legitimacy and customer trust.
  5. Enhance accessibility features and conduct regular security audits to maintain compliance with GDPR and other regulations.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Integsoft, Inc.
Description
Integration Eye is a modular product by Integsoft which allows monitoring of APIs and services, creating statistics and analysis, tracking response times, securing APIs with roles, and more.
Key services
API monitoring, Logging, API security, Proxy services, Data transformation, Integration with dashboards
Content quality
good
Branding
consistent

Technology

Stack
Java, Mule Runtime, XML Configuration, jQuery, FontAwesome, Google Analytics, Hotjar, Vimeo Player
Platforms
Web
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • CSRF tokens present in forms
  • Cookie consent banner implemented

Analytics and tracking

Services
Google Analytics, Hotjar
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Google Ads
Tracking pixels
Hotjar
Marketing tools
Hotjar
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with rich content and professional design
  2. No WAF or blocking mechanisms detected
  3. WHOIS data missing, indicating possible domain registration issues
  4. Comprehensive product information and documentation available
  5. Privacy and cookie policies are present and GDPR compliant
  6. No direct company contact emails or phone numbers found on the about page
  7. Contact is via a form on a separate contact page
  8. Use of modern analytics and marketing tools
  9. No explicit security policy or incident response information published
Technical notes

Notes

The website is built on a solid technical foundation using Java-based Mule Runtime and XML configurations for backend processes. Frontend technologies include jQuery, FontAwesome, and modern CSS frameworks ensuring responsive design and good user experience. Integration with Google Analytics and Hotjar provides insights into user behavior and site performance. The site loads quickly and is mobile-optimized, though accessibility could be improved. No CMS is detected, indicating a custom or static site architecture. The absence of explicit hosting provider information limits infrastructure assessment. Overall, the technical implementation is modern and efficient but could benefit from enhanced security configurations and accessibility improvements.
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 integrationeye.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 integrationeye.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.