Skip to main content

Security report for wimagguc.com

wimagguc · Media · N/a

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

Security score

67/100

Risk levelMedium

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

The website www.wimagguc.com is a personal newsletter hosted on the Substack platform, focusing on publishing articles and essays under the brand 'wimagguc'. The publication was launched approximately 9 months ago and targets a general audience interested in thoughtful media content. The business model revolves around subscription-based content delivery via Substack, with no direct company contact information or extensive business infrastructure visible on the site. Technically, the site leverages Substack's hosting and CDN services, uses HTTPS with good SSL configuration, and integrates third-party services like Sentry for error tracking and Calendly for scheduling. The site is mobile optimized and provides a good user experience with clear navigation and professional design. Security posture is solid with HTTPS enforced and no visible vulnerabilities, though additional security headers and incident response information could enhance trust. Privacy compliance is good, with clear links to Substack's privacy and terms pages and a cookie consent mechanism. Overall, the site is trustworthy and safe for general audiences, but the lack of WHOIS data and direct contact information limits full business credibility assessment.

Scanned

NIS2 and GDPR posture

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

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

    • 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

  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
    • 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 wimagguc.com

This scan found 23 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
57
Security headers
45
Email security
70
DNS health
70
Network security
100
GDPR outside view
58
Average
67

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention wimagguc.com, from OffSeq Breach.

No leaked records found

Breach holds no records for wimagguc.com right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

wimagguc operates as a small-scale media publication within the newsletter sector, leveraging Substack's platform for content distribution and subscription management. The publication focuses on delivering curated essays and articles, appealing to readers interested in intellectual and cultural topics. The business benefits from Substack's ecosystem, including integrated payment processing and audience management, but lacks independent domain registration transparency. There are no visible partnerships or subsidiaries, and the revenue model is primarily subscription-based. Growth indicators include recent launch and active content updates. The absence of direct contact details and certifications suggests a lean operation focused on content rather than corporate scale.

Security posture

The website demonstrates a good security posture with HTTPS enabled and no exposed sensitive data. Use of Sentry for error monitoring indicates proactive error and incident tracking. However, the absence of advanced security headers such as Content-Security-Policy and lack of a published security policy or incident response contact reduces the overall security maturity. No vulnerability disclosures or security certifications are present. The site does not expose forms collecting sensitive data beyond standard subscription sign-ups managed by Substack, which likely handles compliance and security at the platform level. Overall, the security risk is low but could be improved with additional transparency and controls.

Recommendations

  1. Add security headers like Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to enhance protection.
  2. Publish a security policy or incident response page with contact information for vulnerability reporting.
  3. Consider adding a security.txt file to facilitate responsible vulnerability disclosure.
  4. Provide clearer business contact information to improve credibility and trust.
  5. Regularly review third-party scripts and dependencies to avoid vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
wimagguc
Description
public beta since 1984. Click to read wimagguc, a Substack publication. Launched 9 months ago.
Key services
Newsletter content publishing, Subscription management
Content quality
good
Branding
consistent

Technology

Stack
Substack platform, Sentry error tracking, Google Fonts, Calendly embed
Platforms
Substack
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data
  • Use of Sentry for error monitoring

Analytics and tracking

Services
Sentry
Tracking level
minimal
Privacy practices
good

Advertising

Marketing tools
Sentry
Transparency
basic

Site quality

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

Key observations

  1. Website is a Substack-hosted newsletter with active content and subscription options.
  2. No direct company contact emails or phone numbers found on the site.
  3. Privacy and cookie policies are present and linked to Substack's official pages.
  4. No security.txt or vulnerability disclosure information found.
  5. No signs of WAF or content blocking detected.
  6. WHOIS data is unavailable, likely due to platform-managed domain privacy.
  7. Site uses modern web technologies and is mobile optimized.
  8. Content is safe and suitable for general audiences.
Technical notes

Notes

The website is built on the Substack platform, utilizing its CDN and hosting infrastructure. It uses modern web standards including responsive design, Google Fonts, and integrates third-party services such as Sentry for error tracking and Calendly for scheduling. The site loads multiple CSS bundles and uses JSON-LD structured data for SEO. Performance is moderate, with good mobile optimization and accessibility basics in place. There is no evidence of legacy or vulnerable libraries. The site benefits from Substack's managed environment but could improve by implementing additional security headers and accessibility enhancements. Overall, the technical implementation is solid for a content-focused newsletter.
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 wimagguc.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 wimagguc.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.