Skip to main content

Security report for waskublog.com

Wasku · Media · N/a

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

Security score

52/100

Risk levelMedium

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

Wasku Blog is a niche adult-themed content website that publishes monthly posts featuring models and themed photo articles. The site targets an adult audience interested in beauty and modeling content, leveraging affiliate marketing and advertising as its primary business model. The website is built on WordPress with standard plugins and uses third-party widgets for cryptocurrency price display and affiliate banners. The technical infrastructure is moderate with basic mobile optimization and standard CMS usage. Security posture is basic with HTTPS enabled but lacking advanced security headers and privacy compliance documentation. The absence of privacy, cookie, and terms of service policies, as well as lack of verified contact information, reduces the site's trustworthiness and compliance standing. The WHOIS data for the subdomain is unavailable, limiting domain legitimacy verification. Overall, the site functions as a small-scale content publishing platform with room for improvement in security, privacy, and business transparency.

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

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 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';…

  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

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

Keep watching waskublog.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
67
Security headers
15
Email security
82
DNS health
80
Network security
20
GDPR outside view
50
Average
52

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 waskublog.com, from OffSeq Breach.

No leaked records found

Breach holds no records for waskublog.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

The website operates in the media sector focusing on adult content and modeling. It maintains a consistent monthly publishing schedule, indicating a stable content pipeline. Revenue streams appear to be primarily from affiliate marketing and advertising partnerships with related domains such as WaskuShop and WaskuPay. The target customer segment is adult users interested in beauty and modeling content. The partnership ecosystem includes multiple related domains under the Wasku brand umbrella, suggesting a small network of related sites. Growth indicators are limited due to lack of business disclosures. The business model is content-driven with monetization through affiliate links and ads.

Security posture

The security maturity level is basic. HTTPS is properly implemented, ensuring encrypted communication. However, the site lacks important security headers such as Content-Security-Policy, X-Frame-Options, and HSTS, which are critical for mitigating common web attacks. No privacy or cookie policies are present, indicating compliance gaps with GDPR and other privacy regulations. No incident response or security contact information is provided, limiting the ability to report vulnerabilities or incidents. The site uses third-party scripts and affiliate links, which may introduce additional risk if not properly vetted. Overall, the security posture requires enhancements to meet modern standards and regulatory requirements.

Recommendations

  1. Implement comprehensive privacy and cookie policies to improve GDPR compliance and user trust.
  2. Add security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to enhance protection against common web vulnerabilities.
  3. Provide clear contact information including a security or abuse email address to facilitate incident reporting and response.
  4. Conduct a security audit of third-party scripts and affiliate links to ensure they do not introduce vulnerabilities.
  5. Improve website transparency by adding terms of service and business contact details to enhance credibility.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Wasku
Description
Wasku Blog is a content website publishing monthly posts featuring models and themed photo articles, targeting an adult audience interested in beauty and modeling content.
Key services
Monthly blog posts featuring models, Affiliate marketing links, Advertising banners
Content quality
basic
Branding
moderate

Technology

Stack
WordPress 6.8.1, jQuery 3.7.1, Bootstrap 3.3.6, FontAwesome 4.7.0, PHP (implied by WordPress), LiveCoinWatch widget
Frameworks
WordPress
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
60/100
Good practices seen
  • HTTPS enabled
  • No exposed sensitive data in HTML

Analytics and tracking

Services
StatCounter
Tracking level
moderate
Privacy practices
poor

Advertising

Ad networks
StatCounter
Tracking pixels
StatCounter
Transparency
basic

Site quality

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

Key observations

  1. Website is a WordPress blog focused on adult-themed model content updated monthly.
  2. No privacy, cookie, or terms of service policies found on the site.
  3. No explicit contact emails or phone numbers found in the content.
  4. Site uses HTTPS and includes some third-party widgets and affiliate links.
  5. No advanced security headers detected; basic security posture.
  6. WHOIS data for the subdomain is unavailable, limiting domain trust assessment.
  7. Advertising and affiliate marketing are present but transparency is minimal.
  8. Site content and navigation are basic with moderate mobile optimization.
  9. No social media links or official company contact details found.
Technical notes

Notes

The website is built on WordPress 6.8.1 with common plugins and uses jQuery, Bootstrap 3.3.6, and FontAwesome 4.7.0 for UI components. The site includes third-party widgets such as LiveCoinWatch for cryptocurrency prices and StatCounter for analytics. The HTML structure is valid with responsive design elements, providing good mobile optimization. Performance is moderate with some external resources loaded. Accessibility features are basic, with some ARIA roles and screen-reader text present. SEO optimization is basic with meta tags and structured navigation but lacks advanced SEO features. Hosting provider details are not disclosed. Overall, the technical infrastructure is standard for a small WordPress blog but could benefit from modernization and enhanced security configurations.
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 waskublog.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 waskublog.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.