Skip to main content

Security report for gist.build

Peaberry Software Inc. · Technology · United States

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

Security score

75/100

Risk levelMedium

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

Customer.io, operated by Peaberry Software Inc., is a mature SaaS company specializing in customer engagement through in-app messaging and omnichannel marketing automation. The platform enables businesses to create personalized campaigns combining in-app messages with email, push notifications, SMS, and webhooks. Positioned as a trusted solution with over 7,800 brands worldwide, Customer.io targets product-led companies and marketing teams seeking to enhance user engagement and retention. Technically, the website is built on modern frameworks such as Next.js and React, hosted on AWS infrastructure, and integrates multiple analytics and advertising technologies including Google Analytics, Microsoft Clarity, and various ad network pixels. The site demonstrates excellent performance, mobile optimization, and SEO practices, supported by a comprehensive developer resource section with open-source SDKs. From a security perspective, the site enforces HTTPS with good SSL configuration and employs cookie consent mechanisms. However, explicit security headers and detailed security policies are not prominently published. The WHOIS data confirms a consistent and legitimate domain registration dating back to 2011, reinforcing the company's credibility. Overall, Customer.io presents a professional and trustworthy online presence with strong technical and business foundations. The main areas for improvement include publishing clear privacy policies, terms of service, and contact information to enhance privacy compliance and user trust.

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 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 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 gist.build

This scan found 21 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
72
Security headers
30
Email security
80
DNS health
80
Network security
100
GDPR outside view
85
Average
75

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

Customer.io operates in the competitive marketing automation sector, leveraging a SaaS business model focused on delivering personalized customer communication tools. Its competitive advantages include a no-code builder, intelligent segmentation, and integration of multiple communication channels. The company targets medium to large enterprises and product-led companies, emphasizing developer-friendly SDKs and comprehensive documentation to facilitate adoption. The presence of certifications like AICPA, HIPAA, and GDPR compliance signals a focus on regulated industries and data privacy. The extensive use of analytics and advertising tools indicates a mature marketing strategy aimed at growth and customer acquisition.

Security posture

The website exhibits a solid security posture with mandatory HTTPS and good SSL configuration. Cookie consent is implemented, reflecting awareness of privacy regulations. However, the absence of explicit security headers such as Content-Security-Policy and X-Frame-Options, and lack of published security or incident response policies, represent gaps in transparency and defense-in-depth. No vulnerabilities or exposed sensitive data were detected in the analyzed content. The WHOIS data is transparent and consistent, supporting domain legitimacy. To enhance security maturity, the company should publish detailed security policies, incident response contacts, and consider adding a vulnerability disclosure program.

Recommendations

  1. Publish a comprehensive privacy policy and terms of service accessible from all pages.
  2. Implement and publish explicit security headers including Content-Security-Policy and X-Frame-Options.
  3. Provide clear contact information including security incident response channels.
  4. Enable DNSSEC on the domain to improve DNS security.
  5. Establish a vulnerability disclosure program or security.txt file to encourage responsible reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Peaberry Software Inc.
Description
Create high-performing multi-channel campaigns by combining in-app messages with email, push, SMS, and webhooks.
Key services
In-app messaging, Email campaigns, Push notifications, SMS messaging, Webhooks, Omnichannel marketing automation
Content quality
excellent
Branding
consistent

Technology

Stack
Next.js, React, AWS DNS, Google Analytics, Microsoft Clarity, Bing Ads, Reddit Pixel, Twitter Ads, LinkedIn Insight Tag, Salesloft, Cookiebot, FingerprintJS
Frameworks
Next.js, React
Platforms
Web
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of cookie consent mechanism
  • Use of fingerprinting and analytics scripts with consent

Analytics and tracking

Services
Google Analytics, Microsoft Clarity, Salesloft Analytics, G2 Crowd Attribution
Tracking level
extensive
Privacy practices
basic

Advertising

Ad networks
Bing Ads, Reddit Ads, Twitter Ads, LinkedIn Ads
Tracking pixels
Microsoft Clarity, G2 Crowd Attribution, Salesloft Analytics
Marketing tools
Cookiebot
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with rich content and professional design.
  2. Strong focus on in-app messaging and omnichannel marketing automation.
  3. Use of multiple analytics and advertising tracking scripts with cookie consent.
  4. No explicit privacy policy or terms of service links found on the analyzed page.
  5. WHOIS data confirms long-standing domain ownership by a US-based company.
  6. Certifications such as AICPA, HIPAA, and GDPR are indicated, enhancing trust.
  7. No contact emails or phone numbers explicitly found on this page.
  8. Developer resources and SDKs are prominently featured, targeting engineering teams.
Technical notes

Notes

The website is built using modern web technologies including Next.js and React, ensuring a responsive and performant user experience. Hosting on AWS with multiple DNS servers provides reliable infrastructure. Integration of numerous analytics and marketing scripts indicates a sophisticated digital marketing approach. The site is well-optimized for SEO and mobile devices. However, some technical improvements could include enhanced security headers and more explicit privacy compliance features. The developer resources and open-source SDKs demonstrate a commitment to developer engagement and product extensibility.
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 gist.build. 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 gist.build.

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.