Skip to main content

Security report for must.ee

Agentuur MUST · Other · Estonia

Low risk. 3 critical or high findings in Security headers and SSL/TLS.

Security score

81/100

Risk levelLow

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

Agentuur MUST is a small Estonian event organizing company with a Facebook presence dating back to 2009. Their Facebook page serves as their primary digital footprint, offering basic business information, contact details, and social proof through likes and followers. The company targets clients seeking event management services locally. Technically, the page leverages Facebook's robust platform, ensuring good performance, mobile optimization, and security through HTTPS and standard security headers. However, the page lacks explicit privacy, cookie, and security policies, which limits compliance and trust signals. No vulnerability disclosure or incident response information is provided, indicating room for improvement in security transparency. Overall, the business appears legitimate and consistent with its domain registration data, but enhancing privacy and security disclosures would strengthen its digital maturity and user trust.

Scanned

NIS2 and GDPR posture

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

3 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"

  2. 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

      SSL Certificate Expires Soon

      SSL certificate expires in 8 days

      What to do: Renew SSL certificate before expiration

      • NIS2 21(2)(h)
      • IR 2024/2690 9.2(c): Implementing Regulation (EU) 2024/2690, Annex point 9.2(c): Cryptography
      • NIST SC-17: NIST SP 800-53 Rev. 5 SC-17: Public Key Infrastructure Certificates
    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching must.ee

This scan found 14 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
65
Security headers
70
Email security
70
DNS health
90
Network security
100
GDPR outside view
88
Average
81

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

Agentuur MUST operates in the event management sector, focusing on organizing events since 2009. Their business model is service-oriented, targeting local clients and event attendees. The Facebook page shows moderate engagement with over 1,000 likes and followers, indicating a stable but small market presence. The company provides direct contact channels including phone and email, and links to their official website must.ee, suggesting a partnership or primary business site. There is no evidence of subsidiaries or parent companies. The business leverages Facebook's marketing and analytics tools for outreach and audience engagement. Growth opportunities include expanding digital presence beyond Facebook and formalizing privacy and security policies to meet regulatory requirements.

Security posture

The Facebook-hosted page benefits from Facebook's strong security infrastructure, including HTTPS enforcement and standard security headers. No exposed sensitive data or vulnerable libraries were detected in the page source. However, the absence of published privacy policies, cookie consent mechanisms, and incident response contacts represents compliance gaps, especially under GDPR. No vulnerability disclosure or security.txt files were found, limiting transparency for security researchers. The security posture is solid from a technical hosting perspective but lacks organizational security communication and user privacy assurances. Enhancing these areas would improve compliance and reduce risk exposure.

Recommendations

  1. Publish a clear and accessible privacy policy linked on the Facebook page or official website.
  2. Implement a cookie consent mechanism if tracking or cookies are used to comply with GDPR.
  3. Provide incident response contact information such as security@ or abuse@ email addresses.
  4. Consider adding a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  5. Enhance accessibility features and SEO metadata to improve user experience and discoverability.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Agentuur MUST
Description
Agentuur MUST is an event organizing company established since 2009, described as 'Sündmuste korraldajad. Aastast 2009.' on their Facebook page.
Key services
Event organization
Content quality
basic
Branding
consistent

Technology

Stack
React, JavaScript, Facebook platform
Frameworks
React
Platforms
Facebook
Performance
fast
Mobile
good
Accessibility
basic
SEO
basic

Security

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

Analytics and tracking

Services
Facebook Analytics
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
Facebook Pixel
Marketing tools
Facebook Marketing Tools
Transparency
basic

Site quality

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

Key observations

  1. Website is a Facebook business page for Agentuur MUST, an event organizing company.
  2. No explicit privacy, cookie, or terms of service policies found on the page.
  3. Contact information including phone and email is clearly provided.
  4. The site uses Facebook's platform and technologies, ensuring good security and performance.
  5. No security or incident response policies are published.
  6. No vulnerability disclosure or security.txt found.
  7. The business appears small and local with a moderate social media presence.
Technical notes

Notes

The website is a Facebook business page utilizing React and Facebook's proprietary CMS and hosting infrastructure. The page loads quickly and is mobile optimized, leveraging Facebook's global CDN and security features. Meta tags for Open Graph and Twitter cards are properly configured for social sharing. The page uses Facebook's JavaScript libraries and tracking pixels for analytics and marketing. No CMS other than Facebook's platform is detected. The technical implementation is modern and robust but limited by the constraints of the Facebook platform. There is no evidence of custom hosting or third-party CMS. Performance and security are strong due to Facebook's infrastructure, but the business should focus on improving compliance and transparency aspects.
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 must.ee. 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 must.ee.

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.