Skip to main content

Security report for splove.com.br

Other · Brazil

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

Security score

63/100

Risk levelMedium

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

The website splove.com.br is currently inaccessible due to a Cloudflare Web Application Firewall (WAF) block, which prevents any meaningful content from being retrieved or analyzed. As a result, no business information, contact details, or policies are available for review. The site appears to be protected by Cloudflare, but this security measure is currently blocking access, likely triggered by suspicious activity or automated requests. Without access to the actual website content, it is impossible to assess the company's market position, services, or technical infrastructure in detail. From a technical perspective, the site relies on Cloudflare for security and DNS services. However, no additional technologies, CMS, or frameworks could be identified due to the block. The absence of metadata, structured data, or SEO elements further limits the digital maturity assessment. Security posture cannot be fully evaluated, but the presence of a WAF indicates some level of security awareness. No security headers or SSL configuration details were available. The security posture is currently weak from an external perspective because legitimate users are blocked, which impacts user experience and trust. No privacy, cookie, or terms of service policies were found, indicating potential compliance gaps. The lack of contact information and business details further reduces credibility and trustworthiness. Overall, the website's risk profile is elevated due to inaccessibility and lack of transparency. Strategic recommendations include resolving the WAF blocking issues for legitimate users, publishing comprehensive privacy and security policies, and improving transparency with clear contact and business information. Enhancing SEO and accessibility will also improve user experience and trust.

Scanned

NIS2 and GDPR posture

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

7 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 splove.com.br

This scan found 25 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
75
Security headers
30
Email security
70
DNS health
65
Network security
100
GDPR outside view
35
Average
63

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

Total records
235
Employees
2
Customers
233
Third parties
0
Weak passwords
43%

Latest record dated 2025-07-20 · 3 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for splove.com.br.

Select it in the checkout above.

Masked preview

  • –splove.com.br2025-07-20
  • –splove.com.br2025-04-15

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)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

Due to the complete block by Cloudflare WAF, no direct business intelligence data could be extracted. The domain is registered with Cloudflare name servers and is active, but no registrant or company information is available. The lack of accessible content prevents analysis of market positioning, competitive advantages, or business model. No partnerships, subsidiaries, or revenue streams could be identified. The domain appears to target a Brazilian audience based on the country code top-level domain (.br), but no further segmentation or growth indicators are available.

Security posture

The website is protected by Cloudflare's WAF, which is currently blocking access, indicating a security mechanism is in place to prevent attacks. However, this also results in poor user experience and potential loss of legitimate traffic. No security headers or SSL configuration details were found in the provided data. No incident response or vulnerability disclosure information is published. The absence of privacy and cookie policies suggests compliance gaps with GDPR and other regulations. Overall, the security posture is immature from a transparency and compliance standpoint, despite the presence of a WAF.

Recommendations

  1. Resolve Cloudflare WAF blocking issues to allow legitimate user access and improve user experience.
  2. Publish comprehensive privacy, cookie, and terms of service policies to enhance compliance and transparency.
  3. Add clear contact information including emails and phone numbers to improve business credibility.
  4. Implement and verify security headers (e.g., Content-Security-Policy, X-Frame-Options) and ensure SSL/TLS is properly configured.
  5. Incorporate structured data and metadata to improve SEO and accessibility.
Site observations

Automated reading of the public site. Ratings are indicative.

Cloudflare detected. Website access is blocked by Cloudflare security service with a block page displayed. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Stack
Cloudflare
SEO
poor

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website content is completely blocked by Cloudflare WAF with no accessible business content.
  2. No metadata, structured data, or business information is present in the HTML.
  3. No contact information, policies, or forms are available.
  4. Only external link is to Cloudflare error and support pages.
  5. No analytics or advertising scripts detected.
  6. No security headers or SSL configuration details available from provided data.
  7. WHOIS data shows domain is active with Cloudflare name servers but no registrant details.
Technical notes

Notes

The website is hosted behind Cloudflare, which provides DNS and security services. No CMS or additional frameworks were detected due to the block page. The HTML content is minimal and serves only as a Cloudflare block notification. No analytics, advertising, or tracking scripts were found. The site lacks metadata, structured data, and SEO optimization. Performance, mobile optimization, and accessibility cannot be assessed due to lack of content. The technical implementation is currently insufficient to support a professional online presence.
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 splove.com.br. 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 splove.com.br.

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.