Skip to main content

Security report for heyweb.com

HeyWeb · Technology · N/a

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

Security score

62/100

Risk levelMedium

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

HeyWeb was a technology-focused SaaS platform designed to enable small business owners to rapidly create websites by converting their Facebook pages into fully functional websites. The service automated content updates from social media and provided features such as custom domains and newsletter signups. The website is currently closed, indicating the service is no longer active. The domain is well-established, registered since 2007, and uses reputable registrar and DNS providers, supporting its legitimacy. Technically, the website uses a modest tech stack including jQuery, typed.js, and Google Analytics for tracking. It is hosted with Cloudflare DNS and uses Gandi SAS as the registrar. The site is mobile optimized and has a good design and user experience, but lacks advanced accessibility features and comprehensive SEO optimization. No CMS or major frameworks were detected. From a security perspective, the site lacks DNSSEC, security headers, and visible privacy or cookie policies, which are critical for compliance and user trust. The domain is protected against unauthorized transfers but could improve DNS security. No WAF or blocking mechanisms were detected, and no sensitive data exposure was found. Overall, the security posture is moderate but requires improvements to meet modern standards. The overall risk is moderate with no critical vulnerabilities detected. Strategic recommendations include implementing DNSSEC, publishing privacy and cookie policies, adding security headers, and providing clear contact and incident response information to enhance trust and compliance.

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

8 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 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

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

Keep watching heyweb.com

This scan found 25 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
52
Security headers
30
Email security
85
DNS health
70
Network security
100
GDPR outside view
35
Average
62

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

HeyWeb positioned itself as a niche SaaS provider targeting small businesses seeking quick and easy website creation from their existing Facebook pages. Its competitive advantage was automation and ease of use, integrating social media content seamlessly. The business model relied on subscription or freemium SaaS offerings, though pricing details are not available. The company also developed related projects in travel and hotel guides, indicating a diversified portfolio. The lack of active service and minimal contact information suggests the business may be inactive or pivoted. The partnership ecosystem includes example customer sites and related projects under the same ownership, indicating a small but focused operational scope.

Security posture

The current security maturity level is basic. The domain uses clientTransferProhibited status and reputable registrar and DNS providers, but lacks DNSSEC and security headers. No privacy or cookie policies are published, indicating compliance gaps with GDPR and other regulations. Incident response readiness is not evident due to missing contact channels for security issues. The use of Google Analytics and Tag Manager introduces moderate user tracking without visible consent mechanisms. No critical vulnerabilities or exposed sensitive data were found, but the absence of security best practices and policies reduces overall security posture.

Recommendations

  1. Enable DNSSEC to secure DNS queries and prevent spoofing.
  2. Publish comprehensive privacy and cookie policies with GDPR compliance details.
  3. Implement security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Add clear contact information including security incident response channels (e.g., security@ or abuse@ emails).
  5. Review and minimize user tracking to comply with privacy regulations and improve transparency.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
HeyWeb
Description
HeyWeb was a service that allowed users to quickly create a website for their business by turning their Facebook page into a website. It automatically updated content from Facebook and Instagram and offered features like custom domains, mobile optimization, newsletter signups, and photo galleries.
Key services
Facebook page to website conversion, Automatic content updates from social media, Custom domain support, Mobile and tablet optimized websites, Newsletter signup integration, Photo gallery integration
Content quality
good
Branding
consistent

Technology

Stack
jQuery 2.2.4, typed.js, Google Analytics, Google Tag Manager, Cloudflare DNS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
40/100
Good practices seen
  • Domain status clientTransferProhibited set
  • Use of Cloudflare DNS servers

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 currently closed as a service.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact emails, phone numbers, or physical addresses provided.
  4. Uses Google Analytics and Google Tag Manager for tracking.
  5. No visible security headers or advanced security configurations.
  6. Domain is old and registered with a reputable registrar.
  7. Website content is business-oriented and safe for general audiences.
  8. No WAF or blocking mechanisms detected.
Technical notes

Notes

The website uses a lightweight technology stack with jQuery and typed.js for UI effects, and Google Analytics and Tag Manager for analytics. Hosting and DNS are managed via Cloudflare and Gandi SAS, reputable providers. The site is mobile optimized and has a clean, professional design. However, it lacks modern frameworks or CMS platforms, which may limit scalability and maintainability. Performance is moderate with asynchronous loading of analytics scripts. The absence of accessibility features and advanced SEO optimizations indicates room for technical improvement. No critical technical risks were identified, but modernization and security enhancements are recommended.
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 heyweb.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 heyweb.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.