Skip to main content

Security report for givingpage.org

FinDock · Technology · N/a

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

Security score

74/100

Risk levelMedium

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

FinDock is a technology company specializing in providing payment page and form solutions integrated within Salesforce, enabling businesses to create seamless payment experiences and unify payment data within their CRM systems. The company operates primarily in the B2B SaaS space, targeting Salesforce users and organizations seeking efficient payment processing solutions. The website demonstrates a professional design with good content relevance and clear navigation, reflecting a mature digital presence consistent with a company founded in 2017. Technically, the website is built on WordPress using the Divi theme and several plugins including Yoast SEO and GDPR Cookie Compliance, indicating a modern and extensible infrastructure. The site is mobile optimized and performs moderately well, though accessibility features are basic. The domain is registered with a reputable registrar without privacy protection, and SSL is properly configured, enhancing trustworthiness. From a security perspective, the site uses HTTPS and implements cookie consent mechanisms, but lacks visible security headers and publicly available security policies or incident response contacts. No vulnerabilities or exposed sensitive data were detected in the analyzed content. The absence of privacy and terms of service documents is a compliance gap that should be addressed. Overall, FinDock's website presents a solid business and technical foundation with room for improvement in privacy compliance and security best practices. Strategic enhancements in these areas will strengthen trust and regulatory adherence, supporting the company's market position and growth.

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 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 givingpage.org

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
77
Security headers
45
Email security
70
DNS health
65
Network security
100
GDPR outside view
85
Average
74

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 givingpage.org, from OffSeq Breach.

No leaked records found

Breach holds no records for givingpage.org 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

FinDock positions itself as a niche payment integration provider within the Salesforce ecosystem, offering configurable payment pages and forms that unify payment data into CRM workflows. This specialization provides a competitive advantage by addressing a specific market need for seamless payment processing integrated with Salesforce. The business model is subscription-based SaaS targeting medium to large enterprises using Salesforce. The company appears to maintain consistent branding and professional content, supporting credibility. The lack of explicit contact information on the analyzed page suggests contact details may be located elsewhere or require further discovery. The presence of GDPR cookie compliance indicates awareness of privacy regulations, though full policy disclosures are missing. The company likely generates revenue through software licenses and possibly transaction fees, focusing on technology and financial sectors. No direct partnerships or subsidiaries were identified from the content provided.

Security posture

The website demonstrates a baseline security posture with HTTPS enabled and no visible exposure of sensitive data. The use of a GDPR cookie compliance plugin indicates attention to privacy regulations. However, the absence of key security headers such as Content-Security-Policy, X-Frame-Options, and others reduces the overall security hardening. No public security policies, incident response contacts, or vulnerability disclosure mechanisms were found, which limits transparency and preparedness for security incidents. The WHOIS data shows no privacy protection, which is appropriate for this business type and supports legitimacy. No WAF or blocking mechanisms were detected, indicating open accessibility. Recommendations include implementing security headers, publishing security and incident response policies, and adding a security.txt file to improve security posture and compliance.

Recommendations

  1. Publish a comprehensive privacy policy and terms of service accessible from the website footer or main navigation.
  2. Implement and configure security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Add a publicly accessible security.txt file and vulnerability disclosure policy to facilitate responsible reporting.
  4. Enhance accessibility features to improve compliance and user experience for all users.
  5. Consider enabling DNSSEC for the domain to improve DNS security.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
FinDock
Description
Design and configure landing pages and payment forms in Salesforce. Create a seamless payment experience and unify payment data in your CRM.
Key services
Payment pages, Payment forms, CRM payment data unification
Content quality
good
Branding
consistent

Technology

Stack
WordPress, Divi Theme, jQuery, Yoast SEO, GDPR Cookie Compliance plugin, Divi Pixel plugin
Frameworks
WordPress
Platforms
WordPress CMS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Tracking pixels
leadsy.ai
Marketing tools
Yoast SEO
Transparency
basic

Site quality

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

Key observations

  1. Website is a WordPress site using Divi theme and plugins
  2. Content is focused on payment page features integrated with Salesforce
  3. No explicit privacy policy or terms of service found on the analyzed page
  4. Cookie consent is implemented via GDPR Cookie Compliance plugin
  5. No contact emails or phone numbers explicitly found on this page
  6. No security.txt or vulnerability disclosure information found
  7. SSL is enabled and domain is valid and active
  8. No WAF or blocking mechanisms detected
Technical notes

Notes

The website is built on a WordPress CMS platform using the Divi theme and several plugins including Yoast SEO and GDPR Cookie Compliance. The technology stack is modern and widely supported, facilitating ease of content management and SEO optimization. Performance is moderate with good mobile responsiveness. The site uses jQuery and custom JavaScript for UI enhancements. Hosting details are not explicit but domain registration is stable and consistent. There is no evidence of technical debt or deprecated technologies. Opportunities exist to improve security configurations and accessibility compliance. Overall, the technical infrastructure supports the business needs effectively with room for incremental 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 givingpage.org. 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 givingpage.org.

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.