Skip to main content

Security report for iocto.com

iocto GmbH · Manufacturing · Germany

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

Security score

80/100

Risk levelLow

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

iocto GmbH is a German company specializing in industrial measurement technology and automation, established since 1984. The company positions itself as an expert in its field, targeting industrial clients requiring precise measurement and automation solutions. The website reflects a mature digital presence built on WordPress with modern SEO and analytics integrations, indicating a moderate to high level of digital maturity. Security posture is solid with HTTPS enforced and cookie consent mechanisms in place, though some improvements such as enabling DNSSEC and publishing a security.txt file could enhance trust and compliance. Overall, the website is professional, compliant with GDPR, and trustworthy, supporting iocto's market position as a reliable industrial technology provider.

Scanned

NIS2 and GDPR posture

GDPR outside view
85/ 100 · Low
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 Policy found

      GDPR requires clear information about cookie usage

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

  3. DNS health

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

    • High

      Domain Expires Soon

      Domain expires in 25 days

      What to do: Renew domain registration before expiration

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

Keep watching iocto.com

This scan found 16 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
95
Security headers
55
Email security
80
DNS health
65
Network security
100
GDPR outside view
85
Average
80

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention iocto.com, from OffSeq Breach.

No leaked records found

Breach holds no records for iocto.com right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

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 in the manufacturing sector, focusing on B2B services related to industrial measurement and automation. Its market position is that of an established expert with a long history. The business model revolves around providing specialized technical solutions to industrial clients. The website's content and structured data reinforce the company's credibility and branding consistency. The presence of LinkedIn social media links suggests engagement with professional networks. No parent or subsidiary companies were identified, indicating an independent medium-sized enterprise. The company leverages modern web technologies and analytics to support marketing and customer engagement.

Security posture

The website employs HTTPS with a valid SSL configuration and uses clientTransferProhibited status on the domain to prevent unauthorized transfers. Cookie consent is managed via a professional cookie banner plugin, supporting GDPR compliance. However, DNSSEC is not enabled, which is a recommended security enhancement. No explicit security policy or incident response information is published, and no vulnerability disclosure mechanism is found. Security headers beyond HTTPS are not explicitly detected, suggesting room for improvement. Overall, the security posture is good but could be strengthened by adopting additional best practices and transparency measures.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and integrity.
  2. Publish a security.txt file to provide a clear vulnerability disclosure channel.
  3. Implement and verify security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Consider publishing a formal security policy and incident response information to enhance transparency and trust.
  5. Regularly audit third-party scripts and plugins to ensure no vulnerable libraries are in use.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
iocto GmbH
Description
Das Unternehmen iocto aus Hofheim am Taunus ist der Experte für industrielle Messtechnik und Automation – seit 1984.
Key services
industrielle Messtechnik, Automation
Content quality
good
Branding
consistent

Technology

Stack
WordPress, Yoast SEO, Google Analytics, Google Maps, YouTube embeds, Real Cookie Banner Pro, jQuery
Frameworks
Bootstrap 5
Platforms
WordPress CMS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • ClientTransferProhibited domain status
  • Cookie consent mechanism implemented

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Google DoubleClick
Tracking pixels
Google Consent Mode
Transparency
good

Site quality

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

Key observations

  1. Website is professionally designed and content-rich.
  2. Strong compliance with GDPR and cookie consent requirements.
  3. Use of modern web technologies and SEO best practices.
  4. No signs of malicious or suspicious activity.
  5. No explicit security policy or incident response information publicly available.
  6. No vulnerability disclosure or security.txt found.
Technical notes

Notes

The website is built on WordPress CMS with Bootstrap 5 for responsive design and uses Yoast SEO for search engine optimization. It integrates Google Analytics and Google Maps for analytics and functional enhancements, and embeds YouTube videos for content enrichment. The cookie consent is managed by Real Cookie Banner Pro, indicating a mature approach to privacy compliance. Performance is moderate with preloading of scripts and styles. Accessibility is basic but present. The hosting provider is not explicitly identified beyond the domain registrar INWX GmbH. Overall, the technical infrastructure is modern and well-maintained, supporting the business's digital presence effectively.
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 iocto.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 iocto.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.