Skip to main content

Security report for inbanx.com

inbanx, Inc. · Finance · N/a

Medium risk. 4 critical or high findings in GDPR outside view and SSL/TLS.

Security score

70/100

Risk levelMedium

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

inbanx, Inc. is a financial technology company offering an integrated solution for budgeting, card management, expense reporting, and accounts payable automation targeted at banks, businesses, and non-profit organizations. The company positions itself as a niche fintech provider aiming to boost payment efficiency through a unified platform. The website is professionally designed using modern Webflow CMS and includes clear calls to action such as scheduling demos and contact forms. The presence of Visa licensed card issuance via Cottonwood Payments LLC adds credibility to their financial services offering. Technically, the site employs standard web technologies including Google Fonts, jQuery, and a ZoomInfo tracking pixel, hosted on AWS Cloudfront CDN, providing moderate performance and good mobile optimization. Security posture is adequate with HTTPS implied but lacks explicit security headers and cookie consent mechanisms, which are recommended for compliance and enhanced protection. The absence of WHOIS registration data is a notable concern, suggesting either privacy protection or a domain registration anomaly, which impacts trustworthiness. Overall, the site is functional and professional but would benefit from improved security and privacy compliance measures.

Scanned

NIS2 and GDPR posture

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

  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 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
    • 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 inbanx.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. 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
49
Security headers
60
Email security
85
DNS health
75
Network security
100
GDPR outside view
53
Average
70

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 inbanx.com, from OffSeq Breach.

No leaked records found

Breach holds no records for inbanx.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 targets financial institutions, businesses, and non-profits with a SaaS fintech model focused on payment and budgeting efficiency. Their key competitive advantage lies in offering a comprehensive solution that integrates budgeting, card management, expense reporting, and AP automation. The partnership with Cottonwood Payments LLC for card issuance strengthens their market position. The business appears small-sized with no public data on founding year or parent company. The website content and social media presence indicate active engagement but lack detailed business disclosures. Growth potential exists in the fintech sector, especially with automation and real-time spend control features. Strategic partnerships and clear branding support market credibility, though domain registration inconsistencies warrant further due diligence.

Security posture

The website demonstrates a basic security maturity level with HTTPS usage and no visible sensitive data exposure. However, the lack of security headers such as Content Security Policy, HSTS, and X-Frame-Options reduces defense-in-depth. No incident response or security policy information is published, limiting transparency. The contact form collects personal and business data but lacks visible anti-bot or CAPTCHA protections. GDPR compliance is partial, with a privacy policy present but no cookie consent mechanism. The ZoomInfo tracking pixel indicates some user data collection, which should be disclosed more explicitly. Overall, the security posture is functional but requires enhancements in headers, privacy compliance, and incident response readiness to meet higher standards.

Recommendations

  1. Implement comprehensive security headers including CSP, HSTS, and X-Frame-Options to enhance protection against common web attacks.
  2. Add a cookie consent banner and detailed cookie policy to improve GDPR compliance and user transparency.
  3. Publish a dedicated security policy and incident response contact information to build trust and preparedness.
  4. Enhance accessibility features to improve usability for all users and meet compliance standards.
  5. Verify and update WHOIS domain registration information to ensure legitimacy and reduce suspicion.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
inbanx, Inc.
Description
Whether you are a bank, a business, or a non-profit organization, let our team boost your payment efficiency. In one complete solution.
Key services
Budgeting, Card Management, Expense Reporting, Automating Accounts Payable
Content quality
good
Branding
consistent

Technology

Stack
Webflow, Google Fonts, jQuery, ZoomInfo Pixel
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enforced (implied by CDN and modern site)
  • No exposed sensitive data in HTML

Analytics and tracking

Services
ZoomInfo pixel
Tracking level
minimal
Privacy practices
basic

Advertising

Tracking pixels
ZoomInfo
Marketing tools
ZoomInfo
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. WHOIS data is missing or domain is unregistered, which is unusual for an active business site.
  3. Site uses modern Webflow CMS and standard web technologies.
  4. Contact form collects personal and business information with clear labeling.
  5. No cookie consent or terms of service pages detected.
  6. Privacy policy is present but basic and lacks explicit GDPR compliance statements.
  7. No explicit security policies or incident response information found.
  8. Social media presence on Twitter and LinkedIn is linked.
  9. Site branding is consistent and professional.
  10. No signs of adult or questionable content.
Technical notes

Notes

The website is built on Webflow CMS, leveraging modern web standards and Google Fonts for typography. It uses jQuery and includes a ZoomInfo tracking pixel for marketing analytics. Hosting is via AWS Cloudfront CDN, supporting good content delivery performance. The site is mobile optimized with responsive design and clear navigation. However, no advanced frameworks or backend technologies are detectable from the front-end content. The absence of security headers and cookie consent mechanisms indicates technical debt in security and privacy implementation. Performance is moderate with room for optimization in loading speed and accessibility compliance. Overall, the technical infrastructure is solid for a small fintech company but requires improvements to meet enterprise-grade security and privacy expectations.
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 inbanx.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 inbanx.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.