Skip to main content

Security report for okredo.com

Okredo · Technology · N/a

Medium risk. 4 critical or high findings in Security headers and SSL/TLS.

Security score

69/100

Risk levelMedium

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

Okredo is a technology-driven business data platform founded in 2020, offering comprehensive company information including ratings, credit limits, and corporate values to support business growth. The company operates in multiple European countries and targets businesses seeking reliable data for decision-making. The website is built on a modern React/Next.js stack, hosted behind Cloudflare, and integrates secure payment processing via Stripe. It demonstrates good digital maturity with fast performance, mobile optimization, and accessibility features. Security posture is solid with HTTPS enforced, clientTransferProhibited domain status, and cookie consent managed by Cookiebot, although DNSSEC is not enabled and some security headers are missing. Privacy compliance is good, with a comprehensive privacy policy linked via Cookiebot and a clear cookie consent mechanism. However, no direct contact information, terms of service, or vulnerability disclosure policies are present on the site, which could be improved to enhance trust and compliance. Overall, the website is professional, trustworthy, and well-positioned in its market segment.

Scanned

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

NIS2 and GDPR posture

GDPR outside view
83/ 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 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. 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 okredo.com

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. 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
20
Email security
60
DNS health
75
Network security
100
GDPR outside view
83
Average
69

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

Okredo's market positioning focuses on providing essential business data services to companies in Lithuania, Latvia, Estonia, Poland, and the United Kingdom. Its competitive advantage lies in offering free ratings and credit limits combined with corporate values, enabling clients to make informed decisions. The business model revolves around data aggregation and analytics, likely monetized through subscriptions or pay-per-use services, supported by secure payment processing via Stripe. The company maintains an active social media presence on Facebook and LinkedIn, indicating engagement with its audience. Growth indicators include expansion into multiple countries and continuous service development. The partnership ecosystem includes Stripe for payments and Cookiebot for consent management, reflecting a reliance on trusted third-party services.

Security posture

The security maturity level of Okredo's website is good, with HTTPS enforced and domain status set to clientTransferProhibited, reducing risks of unauthorized domain transfers. Cookie consent is managed via Cookiebot, providing transparency and control over data collection. Payment processing is securely handled by Stripe, minimizing exposure to sensitive payment data. However, the absence of DNSSEC and missing explicit security headers such as Content Security Policy (CSP), HSTS, and X-Frame-Options represent areas for improvement. No exposed sensitive data or vulnerable libraries were detected. The site lacks published security policies or incident response contacts, which are important for compliance and trust. Overall, the security posture is solid but could be enhanced by implementing additional security headers and publishing formal security documentation.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement and configure security headers including CSP, HSTS, and X-Frame-Options to mitigate common web vulnerabilities.
  3. Publish clear terms of service and a vulnerability disclosure policy to improve transparency and compliance.
  4. Add explicit contact information including security and incident response contacts to facilitate communication and trust.
  5. Regularly review and update privacy and security policies to maintain GDPR and other regulatory compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Okredo
Description
New design and even more information about companies: free ratings, credit limits, corporate values and other indicators.
Key services
Company ratings, Credit limits, Corporate values, Business indicators
Content quality
good
Branding
consistent

Technology

Stack
React, Next.js, Cookiebot, Google Tag Manager, Stripe
Frameworks
Next.js
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • ClientTransferProhibited domain status
  • Cookie consent with opt-in/out
  • Use of Stripe for secure payments

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Meta Platforms, Inc., Google
Tracking pixels
Facebook Pixel
Marketing tools
Cookiebot
Transparency
good

Site quality

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

Key observations

  1. Website uses modern React/Next.js framework with good performance
  2. Cookie consent implemented via Cookiebot with detailed cookie categories
  3. Payment processing handled securely via Stripe
  4. No direct contact emails or phone numbers found on main page
  5. No explicit privacy or security policies hosted on own domain, but privacy policy linked via Cookiebot
  6. No terms of service or vulnerability disclosure policy found
  7. Social media presence on Facebook and LinkedIn
  8. No security.txt or incident response contacts found
  9. DNSSEC not enabled, which is a recommended security improvement
Technical notes

Notes

The website is built using Next.js, a modern React framework, ensuring server-side rendering and good SEO capabilities. It uses Cookiebot for cookie consent management and Google Tag Manager for analytics integration. Payment processing is integrated via Stripe, a secure and widely trusted platform. Hosting and DNS services are provided by Cloudflare, offering CDN and DDoS protection. The site demonstrates fast loading times and good mobile responsiveness. Accessibility features are present, and SEO meta tags are properly configured. There is no evidence of technical debt or legacy technologies. Opportunities exist to enhance security by enabling DNSSEC and adding security headers. Overall, the technical infrastructure is modern, scalable, and well-implemented.
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. 71/100Medium29 findingsView report
Reviews of this site

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