Skip to main content

Security report for h2.finance

Other · N/a

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

Security score

62/100

Risk levelMedium

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

H2 Finance presents a minimalistic website with very limited content, primarily consisting of a loading animation and basic metadata. The site title and description simply state "H2 Finance" without further elaboration on business activities, services, or market positioning. The technical infrastructure includes modern JavaScript modules and integration with Google Analytics and Segment for user tracking, indicating some level of digital maturity. However, the absence of visible business information, contact details, or compliance policies suggests a low level of transparency and professionalism. Security posture is basic with HTTPS enabled but lacking critical security headers and no visible forms or inputs to assess further security controls. The WHOIS data is unavailable or unsupported for this domain's TLD, limiting trust and making it difficult to verify ownership or legitimacy. Overall, the website appears to be in an early or placeholder state, with significant gaps in content, security, and compliance that should be addressed to improve trust and user confidence.

Scanned

NIS2 and GDPR posture

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

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

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

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

Keep watching h2.finance

This scan found 25 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
15
Email security
75
DNS health
70
Network security
100
GDPR outside view
35
Average
62

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

Due to the minimal content and lack of business details, it is not possible to determine H2 Finance's market positioning, competitive advantages, or revenue streams. The absence of contact information and policies suggests the site may not yet be fully operational or is under development. The use of Google Analytics and Segment indicates an intent to collect user data for marketing or product improvement. No partnerships or subsidiaries are identified. The business model and target audience remain unclear, and no growth indicators or strategic insights can be derived from the current data.

Security posture

The website employs HTTPS, which is a fundamental security requirement. However, it lacks essential security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security, which are critical for protecting against common web vulnerabilities. No forms or user inputs are present to evaluate input validation or secure data handling. The absence of privacy and cookie policies indicates non-compliance with GDPR and other data protection regulations. No incident response or vulnerability disclosure information is available, reducing transparency and preparedness. Overall, the security posture is weak and requires significant improvements to meet industry best practices and regulatory requirements.

Recommendations

  1. Implement comprehensive privacy and cookie policies to ensure compliance with GDPR and other regulations.
  2. Add standard security headers to enhance protection against common web attacks.
  3. Provide clear contact information and business details to improve credibility and user trust.
  4. Establish a vulnerability disclosure policy or security.txt file to promote transparency and security responsiveness.
  5. Enhance website content with detailed business descriptions, services, and user engagement features.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
H2 Finance
Content quality
basic
Branding
moderate

Technology

Stack
Google Tag Manager, Google Analytics, Segment Analytics, JavaScript ES Modules
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
55/100
Good practices seen
  • HTTPS enabled

Analytics and tracking

Services
Google Analytics, Segment Analytics
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
Segment Analytics
Marketing tools
Segment Analytics
Transparency
poor

Site quality

Design
basic
User experience
basic
Content relevance
poor
Navigation
poor
Professionalism
basic
Trustworthiness
low

Key observations

  1. Website content is minimal and mostly placeholder/loading animation
  2. No visible contact information or business details
  3. No privacy, cookie, or terms of service policies found
  4. Uses Google Analytics and Segment for tracking
  5. No security headers detected
  6. WHOIS data is unavailable or unsupported for this TLD
  7. No forms or user input fields present
  8. No social media or external business links found
  9. No visible branding beyond generic site title and logo image path
Technical notes

Notes

The website uses modern JavaScript ES modules and integrates Google Tag Manager, Google Analytics, and Segment for analytics and tracking. The HTML structure is valid but minimal, with limited content and no visible forms or interactive elements. Performance is moderate given the lightweight content, but mobile optimization and accessibility are basic and could be improved. SEO optimization is minimal with only basic meta tags and Open Graph data present. Hosting provider and CMS are not identifiable from the available data. Overall, the technical implementation is functional but lacks depth and sophistication.
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 h2.finance. 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 h2.finance.

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.