Skip to main content

Security report for fatlove.net

Other · N/a

High risk. 8 critical or high findings in GDPR outside view, SSL/TLS and 2 other checks.

Security score

47/100

Risk levelHigh

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

The website fatlove.net currently serves as a parked domain with minimal content focused on advertising and domain sale inquiries. There is no active business or product information presented, and the domain appears to lack proper registration data. The technical infrastructure relies on basic HTML, CSS, and JavaScript with advertising scripts from Google Adsense and Bodis. No advanced frameworks or CMS platforms are detected. Security posture is weak due to the absence of HTTPS, security headers, and privacy compliance mechanisms. The lack of contact information and business details further diminishes trust and credibility. Overall, the site presents a low-risk profile but offers limited value or engagement for visitors.

Scanned

NIS2 and GDPR posture

GDPR outside view
28/ 100 · High
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. GDPR outside view

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

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

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

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

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

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
0
Security headers
20
Email security
50
DNS health
85
Network security
100
GDPR outside view
28
Average
47

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 domain fatlove.net does not currently represent an active business entity. It functions primarily as a domain parking page with monetization through advertising networks. There is no identifiable company, no contact details, and no clear market positioning. The business model is limited to domain resale and ad revenue generation. No partnerships or subsidiaries are evident. The lack of WHOIS data and minimal content suggest the domain may be unregistered, expired, or held for speculative purposes. This limits any meaningful business intelligence insights or growth indicators.

Security posture

Security maturity is low. The site lacks HTTPS, exposing users to potential interception risks. No security headers are present to mitigate common web vulnerabilities. Advertising scripts increase the attack surface but are standard for parked domains. There is no evidence of incident response policies, vulnerability disclosures, or data protection officers. Privacy compliance is minimal with no cookie consent or GDPR indicators. The site does not collect user data via forms, reducing exposure but also limiting engagement. Overall, the security posture is insufficient for any serious business operations.

Recommendations

  1. Implement HTTPS with a valid SSL certificate to secure user connections.
  2. Add standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Develop and publish comprehensive privacy and cookie policies with consent mechanisms.
  4. Provide clear and verifiable contact information to improve business credibility.
  5. Consider removing or securing advertising scripts to reduce potential vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
The website appears to be a parked domain with advertising and a sales inquiry link for the domain fatlove.net. It does not provide business or product information.
Content quality
poor
Branding
inconsistent

Technology

Stack
HTML5, CSS3, JavaScript, Google Adsense, Bodis domain parking scripts
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
30/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Ad networks
Google Adsense, Bodis
Tracking pixels
Google Ad Services
Transparency
poor

Site quality

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

Key observations

  1. Website is a parked domain with advertising and domain sale message
  2. No business or product information provided
  3. No contact information or company details available
  4. No HTTPS detected in provided data (HTTP URL used)
  5. No security headers or advanced security features detected
  6. Advertising scripts from Google Adsense and Bodis present
  7. No privacy or cookie consent mechanisms implemented
  8. WHOIS data unavailable indicating possible unregistered or expired domain
  9. No adult or explicit content detected
  10. No WAF or security blocking mechanisms detected
Technical notes

Notes

The website uses basic web technologies including HTML5, CSS3, and JavaScript. Advertising is integrated via Google Adsense and Bodis scripts. There is no detected CMS or advanced framework. The site is moderately optimized for mobile but lacks accessibility features. Performance is average with no explicit indicators of optimization or caching. The domain uses a subdomain (ww25) typical of parked or redirect domains. No hosting provider or infrastructure details are evident. The technical setup is minimal and suitable only for domain parking purposes.
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 fatlove.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 fatlove.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.