Skip to main content

Security report for oldwomanfuck.net

Other · N/a

Medium risk. 8 critical or high findings in Email security, Security headers and 2 other checks.

Security score

61/100

Risk levelMedium

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

The website oldwomanfuck.net operates as an adult entertainment platform specializing in free streaming of mature and older woman pornographic videos. Established in 2015, it targets an adults-only audience with a niche focus on mature content. The business model relies on providing outbound links to external video content sources rather than hosting videos directly. The site maintains a basic design and limited branding consistency, with no visible privacy, cookie, or terms of service policies, and lacks contact or security information, which impacts its trustworthiness and compliance posture. Technically, the site uses standard HTML5, CSS3, and JavaScript with Cloudflare DNS services but lacks advanced frameworks or CMS detection. Performance and mobile optimization are basic, with no advanced SEO or accessibility features. Security posture is minimal; HTTPS is enabled but no security headers or cookie consent mechanisms are present. The domain is registered with Porkbun LLC since 2015, which aligns with the site's operational timeline and niche. Security evaluation reveals gaps including missing security headers, absence of privacy and cookie policies, and no incident response contacts. No forms or data collection mechanisms are present, reducing data exposure risks but also indicating limited user engagement features. The site sets cookies without consent mechanisms, which is a compliance concern. No analytics or tracking scripts were detected, suggesting minimal user tracking. Overall, the site scores low to moderate on content quality, technical implementation, security posture, privacy compliance, and business credibility. The lack of compliance documentation and security best practices are key vulnerabilities. Strategic recommendations include implementing privacy and cookie policies, adding security headers, enabling DNSSEC, and providing clear contact and incident response information to improve trust and compliance.

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

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

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

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

Keep watching oldwomanfuck.net

This scan found 24 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
65
Security headers
15
Email security
60
DNS health
75
Network security
100
GDPR outside view
50
Average
61

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

Oldwomanfuck.net occupies a niche segment within the adult entertainment industry, focusing exclusively on mature and older woman content. Its competitive advantage lies in its specialized content offering and free access model, relying on outbound links to other adult content providers. The business model appears to be traffic-driven, possibly monetized through affiliate or advertising partnerships, although no explicit ad networks or affiliate programs were detected on the site itself. The target customer segment is adults seeking mature-themed adult videos. The site has a small operational scale with no visible corporate structure or partnerships beyond linked external domains. Growth indicators are limited due to minimal site features and lack of engagement tools. The partnership ecosystem includes multiple related adult content domains, suggesting a network of similar niche sites. Strategic observations highlight the need for improved compliance and security posture to sustain market presence and user trust.

Security posture

The security maturity of oldwomanfuck.net is low. While HTTPS is enabled, the absence of critical security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options exposes the site to common web vulnerabilities. The lack of privacy and cookie policies, combined with no consent mechanisms despite cookie usage, indicates non-compliance with GDPR and other privacy regulations. No incident response or security contact information is provided, limiting the site's ability to handle security incidents effectively. The domain's DNSSEC is not enabled, which could expose DNS spoofing risks. No vulnerable libraries or scripts were detected, but the minimal technical stack and lack of modern security practices reduce overall security posture. The site does not collect user data via forms, which reduces attack surface but also limits user interaction. Overall, the site requires significant improvements in security best practices and compliance to reduce risk.

Recommendations

  1. Implement comprehensive privacy and cookie policies with clear GDPR compliance and consent mechanisms.
  2. Add standard security headers including Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy.
  3. Enable DNSSEC for the domain to enhance DNS security.
  4. Provide clear contact information including security incident response channels (e.g., security@ or abuse@ emails).
  5. Improve site design and branding consistency to enhance user trust and professionalism.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Website offering free streaming of mature and old woman adult videos, updated daily.
Key services
Free streaming of mature/old woman porn videos
Content quality
basic
Branding
moderate

Technology

Stack
HTML5, CSS3, JavaScript, Cloudflare DNS
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
40/100
Good practices seen
  • HTTPS enabled

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 contains explicit adult content focused on mature women.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact information or security policies provided.
  4. Site uses Cloudflare DNS but no DNSSEC enabled.
  5. No security headers detected in HTML content.
  6. Site design is basic with minimal branding consistency.
  7. Multiple outbound links to other adult content domains.
  8. No analytics or tracking scripts detected.
  9. Cookies are set but no consent mechanism present.
  10. No forms or data collection fields detected in HTML.
Technical notes

Notes

The website is built with basic HTML5, CSS3, and JavaScript without use of modern frameworks or CMS platforms. It uses Cloudflare for DNS hosting but does not enable DNSSEC. The site is moderately performant with basic mobile responsiveness but lacks advanced SEO and accessibility features. No analytics or tracking scripts are present, indicating minimal user data collection. The site sets cookies but lacks a consent mechanism. No forms or interactive elements are present, reducing complexity but also limiting engagement. The technical debt is moderate due to outdated security practices and minimal compliance features. Modernization opportunities include adopting a CMS for better content management, implementing security headers, and enhancing mobile and accessibility standards to improve overall user experience and security.
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 oldwomanfuck.net. 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 oldwomanfuck.net.

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.