Skip to main content

Security report for butteryum.org

ButterYum · Other · United States

Medium risk. 7 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

65/100

Risk levelMedium

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

ButterYum is a small personal recipe blog focused on sharing cooking and baking recipes with high-quality food photography. The site targets home cooks and food enthusiasts, offering a variety of recipes including Italian, American, dinner, and dessert dishes. The business model includes affiliate marketing through the Amazon Associates program, as disclosed on the site. Technically, the website is built on the Squarespace platform, leveraging modern web technologies and Google Analytics for visitor tracking. The site is well-structured, mobile-optimized, and uses HTTPS with HSTS for secure communications. However, it lacks explicit privacy and cookie policies, which impacts its privacy compliance score. Security posture is strong with no visible vulnerabilities or exposed sensitive data. Overall, the website presents a professional and trustworthy front for a personal food blog but should improve privacy compliance and formalize security policies to enhance trust and regulatory adherence.

Scanned

NIS2 and GDPR posture

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

7 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 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 Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

    • High

      Third-party services without privacy policy

      Detected services: Google Analytics, Facebook, YouTube, Google APIs

      What to do: Document all third-party data sharing in your privacy policy

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

Keep watching butteryum.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. 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
62
Security headers
35
Email security
65
DNS health
80
Network security
100
GDPR outside view
50
Average
65

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

ButterYum operates in the niche food blogging sector with a focus on recipe development and food photography. Its competitive advantage lies in quality content and visual appeal. Revenue streams likely include affiliate commissions from Amazon links. The target audience is primarily home cooks and food lovers seeking recipe inspiration. The site maintains an active social media presence across Pinterest, Instagram, YouTube, Facebook, and X (formerly Twitter), supporting community engagement and content distribution. The business appears to be a sole proprietorship or small entity without parent or subsidiary companies. Growth indicators include regular content updates and social media activity. The partnership ecosystem is limited to affiliate marketing with Amazon. Strategic observations suggest opportunities to expand privacy and security transparency to build greater user trust.

Security posture

The website demonstrates a mature security posture for a small personal blog. HTTPS is enforced with HSTS enabled, ensuring encrypted communications and protection against protocol downgrade attacks. No security headers beyond HSTS were explicitly detected, and no vulnerable or outdated libraries were found in the scripts. The site does not expose sensitive data or credentials. However, the absence of published security policies, incident response contacts, or vulnerability disclosure mechanisms indicates room for improvement in security governance and transparency. Privacy compliance is weak due to missing privacy and cookie policies and lack of consent mechanisms, which could expose the site to regulatory risks under GDPR or similar frameworks. Overall, the security risk is low but could be enhanced by formalizing policies and user consent flows.

Recommendations

  1. Publish a comprehensive privacy policy page detailing data collection, usage, and user rights.
  2. Implement a cookie consent banner to comply with GDPR and other privacy regulations.
  3. Add a terms of service page to clarify user agreements and site usage policies.
  4. Develop and publish a security policy including incident response contacts to improve transparency.
  5. Consider adding a vulnerability disclosure or security.txt file to encourage responsible reporting.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
ButterYum
Description
ButterYum is a recipe blog full of beautiful food photographs by a cooking instructor and recipe developer. Italian recipes, baking recipes, American recipes, dinner recipes, dessert recipes, recipe process photos.
Key services
Recipe blogging, Food photography, Affiliate marketing via Amazon
Content quality
good
Branding
consistent

Technology

Stack
Squarespace, Google Analytics, Google Tag Manager, YUI JavaScript Library, Squarespace proprietary scripts
Platforms
Squarespace
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • HSTS enabled
  • No exposed sensitive data found
  • No vulnerable libraries detected

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is a personal recipe blog hosted on Squarespace
  2. Uses HTTPS with HSTS enabled
  3. No WHOIS data available from raw WHOIS output
  4. No explicit privacy policy or cookie consent mechanism found
  5. Active social media presence on multiple platforms
  6. Affiliate marketing via Amazon Associates program disclosed
  7. No security or incident response policies published
  8. Content is safe and family-friendly
  9. Good technical implementation with modern scripts and fonts
Technical notes

Notes

The website is built on the Squarespace CMS platform, utilizing its proprietary scripts and styles. It integrates Google Analytics and Google Tag Manager for visitor tracking and marketing analytics. The site uses modern web fonts from Google Fonts and loads asynchronously compressed JavaScript bundles for performance. The design is responsive and mobile-friendly, with good navigation clarity and content organization. Performance is moderate, typical for a Squarespace-hosted site with rich media content. Accessibility features are basic but present. SEO is supported by proper meta tags, Open Graph data, and structured JSON-LD schema for website and local business. Technical risks are minimal, with no outdated or vulnerable libraries detected. Opportunities exist to enhance privacy and security features to align with best practices.
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 butteryum.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 butteryum.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.