Skip to main content

Security report for prettyincash.com

PrettyInCash · Media · N/a

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

Security score

71/100

Risk levelMedium

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

Pretty In Cash operates as an affiliate marketing platform specializing in legal amateur adult content, particularly focusing on teen amateur niches. The business model revolves around affiliate programs offering payments via ePassporte, checks, or wire transfers, targeting affiliates who can drive traffic to their content. The website has been active since 2007, indicating a stable presence in its niche market. The platform provides promotional tools and content to affiliates, aiming to convert traffic effectively. Technically, the website is built on a Ruby on Rails framework, utilizing Bootstrap for responsive design and hosted behind Amazon Cloudfront CDN. The site includes CSRF protection tokens in forms, indicating some security awareness. However, DNSSEC is not enabled, and no advanced security headers were detected, suggesting room for improvement in security hardening. The site performs moderately well with basic mobile optimization and SEO features. From a security perspective, the site uses HTTPS (implied by domain and modern standards), but lacks explicit security headers and privacy policies. No contact information or incident response channels are provided, which limits transparency and trust. The domain WHOIS data is consistent with the website's claims, showing a long registration period and clientTransferProhibited status, which supports legitimacy. The content is adult-oriented, confirmed by explicit keywords and references to legal compliance (18 U.S.C 2257), categorizing it as NSFW and intended for adults only. Overall, the site is functional and moderately credible within its niche but lacks comprehensive privacy, security, and contact transparency. Strategic improvements in security headers, privacy policies, and contact information would enhance 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

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

    • 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

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

Keep watching prettyincash.com

This scan found 21 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
50
Email security
85
DNS health
70
Network security
100
GDPR outside view
50
Average
71

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

Pretty In Cash holds a niche position in the adult affiliate marketing sector, focusing on legal amateur teen content. Its competitive advantage lies in its longevity since 2007 and specialized affiliate payment options. The business model is commission-based affiliate marketing, targeting affiliates who can generate volume traffic. Revenue streams include pay-per-sale and lifetime revenue share models. The absence of public contact details and privacy policies may limit broader market trust but is typical in adult affiliate niches. The partnership ecosystem is not explicitly detailed, and no related or subsidiary domains were identified. Growth indicators are limited from public data, but the presence of frequent promotions suggests active marketing efforts.

Security posture

The website demonstrates a basic security posture with HTTPS usage and CSRF token implementation in forms. However, the lack of DNSSEC, security headers (such as Content Security Policy, HSTS, X-Frame-Options), and absence of privacy and cookie policies indicate gaps in security best practices. No incident response or vulnerability disclosure mechanisms are visible, which could hinder timely response to security events. The domain registration is stable and consistent, reducing risk of domain hijacking. Overall, the security maturity is moderate but requires enhancements to meet higher compliance and protection standards.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement comprehensive security headers including CSP, HSTS, X-Frame-Options, and X-Content-Type-Options.
  3. Publish clear privacy and cookie policies with GDPR compliance statements to improve transparency and legal compliance.
  4. Provide explicit contact information including security or abuse contact channels to enhance incident response readiness.
  5. Regularly audit and update third-party libraries and frameworks to mitigate vulnerabilities and improve security posture.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
PrettyInCash
Description
Pretty In Cash and TeenGFs are legal real amateur programs online focusing on real amateur/home made teen content. They offer affiliate programs with payments via ePassporte, check, or wire and provide downloadable promotional content and tools.
Key services
Affiliate programs, Promotional content delivery, Payment processing via ePassporte, check, wire
Content quality
basic
Branding
moderate

Technology

Stack
Bootstrap (navbar classes), jQuery (implied by bootstrap usage), Rails authenticity token (csrf-token meta tag), Cloudfront CDN
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
55/100
Good practices seen
  • CSRF token implemented in forms
  • Domain status clientTransferProhibited

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is an affiliate marketing platform for adult amateur content.
  2. No privacy or cookie policies found on main page.
  3. Terms and conditions page is linked and likely present.
  4. No contact emails or phone numbers explicitly provided.
  5. Uses Cloudfront CDN and AWS DNS services.
  6. No social media links detected.
  7. CSRF protection implemented on login form.
  8. No security headers or advanced security policies detected.
  9. Content is adult-oriented with legal compliance references (18 U.S.C 2257).
Technical notes

Notes

The website is built on Ruby on Rails framework with Bootstrap for responsive design, hosted on Amazon Cloudfront CDN. The use of authenticity tokens indicates protection against CSRF attacks. Performance is moderate with basic SEO and accessibility features. The site lacks advanced technical SEO optimizations and accessibility compliance beyond basic levels. No CMS is explicitly detected, suggesting a custom or framework-based build. The absence of DNSSEC and security headers indicates technical debt in security configuration. Mobile optimization is good due to Bootstrap usage, but overall design and content quality are basic, reflecting a functional but not highly polished technical implementation.
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 prettyincash.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 prettyincash.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.