Skip to main content

Security report for liq.com.br

Other · Brazil

Partial score · DNS & email only

34/100

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

The website liq.com.br is currently inaccessible due to a 500 Internal Server Error caused by a server-side suPHP UID misconfiguration. This prevents any content from being served, resulting in no visible metadata, business information, or user-facing content. The site lacks HTTPS, security headers, privacy policies, contact information, and any form of digital maturity indicators. Consequently, the technical infrastructure appears minimal and improperly configured, leading to a poor security posture and very low trustworthiness. Without access to the actual website content or WHOIS data, a comprehensive analysis is severely limited.

Scanned

NIS2 and GDPR posture

GDPR outside view
15/ 100 · Critical
Checks completed
6of 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. 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

    • 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

  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

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

Keep watching liq.com.br

This scan found 18 issues across 5 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
0
Email security
70
DNS health
65
Network security
20
GDPR outside view
15
Average
34

Not counted

  • Security headers: did not complete in this scan.
  • 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 liq.com.br, from OffSeq Breach.

Total records
2,931
Employees
77
Customers
2,652
Third parties
202
Weak passwords
31%

Latest record dated 2026-06-10 · 50 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 liq.com.br.

Select it in the checkout above.

Masked preview

  • –gsuite.liq.com.br2026-06-10
  • –gsuite.liq.com.br2026-06-06
  • –gsuite.liq.com.br2026-05-29
  • –gsuite.liq.com.br2026-05-28
  • –gsuite.liq.com.br2026-05-28

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 lack of accessible content and metadata, no meaningful business intelligence can be derived. There is no information on market positioning, business model, services, or partnerships. The domain is Brazilian (.br), but no registrant or company details are available to assess legitimacy or business operations.

Security posture

The security posture is critically weak. The site does not use HTTPS, lacks security headers, and exposes a server error indicating misconfiguration. No privacy or incident response policies are present. These factors indicate a high risk of security vulnerabilities and poor compliance with data protection standards. The absence of contact or abuse channels further exacerbates the risk.

Recommendations

  1. Resolve the suPHP UID configuration error to restore website availability.
  2. Implement HTTPS with a valid SSL/TLS certificate to secure communications.
  3. Add standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Publish privacy and cookie policies to comply with GDPR and other regulations.
  5. Provide clear contact information including security incident response contacts.
  6. Conduct a full security audit to identify and remediate vulnerabilities.
  7. Improve website design and content to enhance user experience and trust.
  8. Establish monitoring and incident response processes for ongoing security management.
  9. Consider implementing a WAF or security service to protect against attacks.
  10. Regularly update and maintain server software and configurations.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
poor
Branding
inconsistent

Technology

Stack
PHP
Performance
slow
Mobile
poor
Accessibility
poor
SEO
poor

Security

Observed score
20/100

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 is currently inaccessible due to 500 Internal Server Error caused by suPHP UID misconfiguration
  2. No visible content, metadata, or business information available
  3. No privacy, cookie, or terms of service policies found
  4. No contact information or forms detected
  5. No external links or social media profiles found
  6. No security headers or HTTPS detected
  7. No analytics or advertising scripts detected
  8. Technical infrastructure appears minimal and misconfigured
  9. Security posture is poor with critical server error
  10. Unable to perform comprehensive analysis due to lack of accessible content
Technical notes

Notes

The website runs PHP but is currently non-functional due to a server error related to suPHP UID settings. No CMS or frameworks are detected. The site lacks HTTPS and security headers, indicating outdated or incomplete server configuration. Performance and accessibility cannot be assessed due to lack of content. The technical debt is high, and modernization is required to ensure operational stability 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 liq.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 liq.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.