Skip to main content

Security report for emo-mruczek.pl

Other · Poland

Medium risk. 9 critical or high findings in GDPR outside view, Email security and 2 other checks.

Security score

56/100

Risk levelMedium

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

The website emo-mruczek.pl is a personal site created recently in 2024, featuring minimal content centered around personal interests and social links. It does not represent a commercial business or professional entity. The site includes a simple design with basic HTML and CSS, linking to personal GitHub and MyAnimeList profiles, and some hobbyist webrings. There is no evidence of business operations, e-commerce, or professional services. Technically, the site is basic with no advanced frameworks or CMS detected, and no analytics or tracking technologies in use. Security posture is weak due to lack of HTTPS information and absence of security headers. No privacy or cookie policies are present, and no contact information is provided, limiting trust and compliance. WHOIS data is transparent and consistent with a personal site, registered under an individual name with no privacy protection. Overall, the site is safe for general audiences but lacks professional and security maturity.

Scanned

NIS2 and GDPR posture

GDPR outside view
15/ 100 · Critical
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

9 findings rated critical or high. Fix these first.

  1. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

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

  3. 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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • 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';…

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

Keep watching emo-mruczek.pl

This scan found 27 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
15
Email security
60
DNS health
75
Network security
100
GDPR outside view
15
Average
56

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

The site does not operate as a business but rather as a personal or hobbyist web presence. There is no clear business model, revenue stream, or market positioning. The target audience appears to be general internet users interested in the owner's personal interests and social profiles. The lack of business information, certifications, or contact details indicates no commercial intent. External links to niche communities and personal profiles suggest a small-scale, informal web presence without partnerships or subsidiaries.

Security posture

Security maturity is low. The site lacks HTTPS confirmation and security headers, which are critical for protecting user data and preventing common web attacks. No forms or data collection mechanisms reduce attack surface but also limit functionality. Absence of privacy and cookie policies indicates non-compliance with GDPR and related regulations. No incident response or vulnerability disclosure information is provided. The WHOIS data is public and consistent, which is positive for transparency but no advanced security measures are evident.

Recommendations

  1. Implement HTTPS with a valid SSL certificate to secure all connections.
  2. Add standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish privacy and cookie policies to improve compliance and user trust.
  4. Provide clear contact information or a contact form for communication and incident reporting.
  5. Consider adding basic analytics and SEO improvements to enhance site visibility and user experience.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Personal website with minimal content, featuring a cat image and links to personal pages and social profiles. No clear business description or commercial activity.
Content quality
basic
Branding
moderate

Technology

Stack
HTML5, CSS3
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
30/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a personal site with minimal content and no commercial activity.
  2. No privacy, cookie, or terms of service policies present.
  3. No contact emails or phone numbers provided.
  4. No security headers or HTTPS information available.
  5. WHOIS data is transparent and consistent with site purpose.
  6. External links point to personal social profiles and related hobbyist communities.
  7. No analytics or tracking technologies detected.
  8. Site design is simple with basic CSS styling and no advanced frameworks.
  9. No forms or data collection mechanisms present.
Technical notes

Notes

The website is built with simple HTML and CSS without any detected JavaScript frameworks or CMS platforms. The site uses local images and external links but no scripts or analytics services. Performance is likely moderate given the minimal content and styling. Mobile optimization and accessibility are basic but could be improved. SEO is minimal with no meta tags or structured data present. Hosting provider and SSL status are not explicitly detected from the provided data. Overall, the technical implementation is minimal and suitable for a personal hobby site but lacks modern web 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 emo-mruczek.pl. 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 emo-mruczek.pl.

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.