Skip to main content

Security report for tgbwidget.com

The Giving Block · Non-profit · N/a

Medium risk. 7 critical or high findings in Email security, Security headers and 1 other check.

Security score

66/100

Risk levelMedium

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

The Giving Block website serves as a platform enabling charitable donations via cryptocurrency and card payments. The business operates in the non-profit sector, targeting donors interested in leveraging modern payment methods for philanthropy. The platform is powered by The Giving Block brand and integrates third-party services such as Shift4 for card payments and Plaid for financial data connectivity. The website's content is minimal but consistent with its purpose, focusing on donation facilitation with clear branding and loading indicators. Technically, the site employs modern web technologies including React and Material-UI, with integrations for Google Tag Manager and Google reCAPTCHA enhancing analytics and security. Hosting is supported by Amazon AWS infrastructure as indicated by DNS records. Performance and mobile optimization are moderate to good, though accessibility and SEO optimizations are basic. The absence of explicit privacy, cookie, and terms of service policies is a notable gap. From a security perspective, the site uses HTTPS and includes anti-bot measures via reCAPTCHA. However, no explicit security headers such as CSP or HSTS were detected, and no vulnerability disclosure or security policy information is present. The WHOIS data is transparent and consistent with the business, showing no privacy protection or suspicious registration patterns. Overall, the security posture is moderate but could be improved with enhanced headers and policy disclosures. The overall risk assessment indicates a functional and legitimate platform with moderate security and compliance maturity. Strategic recommendations include implementing comprehensive privacy and cookie policies, adding security headers, publishing vulnerability disclosure information, and improving accessibility and SEO. These steps will enhance trust, compliance, and security posture, supporting the platform's mission in the charitable donation space.

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

7 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. 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';…
  3. 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 tgbwidget.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
100
Security headers
40
Email security
60
DNS health
60
Network security
100
GDPR outside view
35
Average
66

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

Total records
1
Employees
0
Customers
1
Third parties
0
Weak passwords
0%

1 subdomain affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for tgbwidget.com.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The Giving Block occupies a niche market position as a facilitator of cryptocurrency and card donations for charities, leveraging the growing interest in digital assets for philanthropy. Its business model centers on providing a seamless donation experience integrating crypto and traditional payment methods. Revenue streams likely include transaction fees or service charges associated with payment processing. The target customer segment includes crypto holders and donors seeking modern, secure ways to contribute to non-profits. Partnerships with Shift4 and Plaid indicate a robust payment ecosystem. Growth indicators include domain age since 2019 and integration of advanced payment APIs. The platform's strategic focus on crypto donations positions it well in the evolving charitable giving landscape.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and use of Google reCAPTCHA to mitigate automated abuse. However, the absence of key security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options reduces defense-in-depth. No explicit privacy or security policies are published, limiting transparency and compliance with GDPR or similar regulations. There is no evidence of a vulnerability disclosure program or security.txt file, which could hinder incident response and responsible vulnerability reporting. The WHOIS data is clear and consistent, supporting legitimacy. Overall, while basic security controls are in place, enhancements are needed to meet higher compliance and security standards.

Recommendations

  1. Implement comprehensive privacy and cookie policies with clear GDPR compliance statements.
  2. Add critical security headers including CSP, HSTS, and X-Frame-Options to improve security posture.
  3. Publish a vulnerability disclosure policy and security.txt file to facilitate responsible reporting.
  4. Enhance accessibility features and SEO metadata to improve user experience and discoverability.
  5. Provide clear contact information including support and security contacts to increase trust and compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
The Giving Block
Description
The website facilitates donations to charity using cryptocurrency and card payments.
Key services
Crypto donation processing, Card donation processing
Content quality
basic
Branding
consistent

Technology

Stack
Google Tag Manager, Shift4 payment integration, Plaid API, Google reCAPTCHA
Frameworks
Material-UI (MuiPaper, MuiTypography classes)
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
65/100
Good practices seen
  • Use of HTTPS (implied by external scripts loaded over HTTPS)
  • Integration of Google reCAPTCHA
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is a donation platform focused on cryptocurrency and card donations for charities.
  2. No privacy, cookie, or terms of service policies found on the main page.
  3. No contact emails, phone numbers, or physical addresses explicitly provided.
  4. Uses modern JavaScript frameworks and third-party payment and financial APIs.
  5. No security.txt or vulnerability disclosure information present.
  6. No explicit security headers detected in the provided data.
  7. Content is minimal and mostly a loading interface with branding and logos.
  8. No adult or questionable content detected.
  9. WHOIS data is transparent and consistent with business claims.
Technical notes

Notes

The website is built using modern JavaScript frameworks, likely React, with Material-UI components for UI consistency. It integrates third-party services such as Google Tag Manager for analytics, Shift4 for card payments, and Plaid for financial data connectivity. Hosting is supported by Amazon AWS infrastructure, as indicated by DNS servers. Performance is moderate with deferred script loading and asynchronous tag management. Mobile optimization is good, but accessibility and SEO optimizations are basic and could be improved. The absence of CMS-specific markers suggests a custom or SPA architecture rather than a traditional CMS. Technical risks include missing security headers and lack of explicit privacy and cookie management mechanisms.
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 tgbwidget.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 tgbwidget.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.