Skip to main content

Security report for business.site

Redirects to consent.google.com; the website checks ran on that page, the DNS and email checks on business.site.

Google LLC · Technology · United States

Low risk. No critical or high findings.

Security score

94/100

Risk levelLow

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

The analyzed website is a Google consent management interface designed to handle user privacy and cookie preferences for Google services. It serves as a functional page within Google's ecosystem, providing users with control over their data consent in compliance with privacy regulations. The site is part of Google's broader infrastructure and reflects the company's market leadership in technology and internet services. The page itself is not a commercial or marketing site but a technical component of Google's privacy compliance framework. Technically, the site employs modern web technologies including JavaScript, Material Design Components, and strong security practices such as HTTPS enforcement and Content Security Policy with nonce attributes. The hosting is managed by Google Cloud Platform, ensuring high performance and availability. The site is mobile-optimized and accessible at a basic level, suitable for its functional purpose. From a security perspective, the site demonstrates excellent SSL configuration and security headers, with no detected vulnerabilities or exposed sensitive data. The JavaScript includes advanced measures to prevent prototype pollution and enforce object sealing, indicating a mature security posture. However, the page lacks explicit privacy policy, cookie policy, or terms of service links, which are likely hosted elsewhere within Google's domain. Overall, the site is trustworthy and legitimate, with domain registration details consistent with Google LLC. There are no signs of blocking or WAF challenges, and the content is safe for general audiences. Strategic recommendations include maintaining up-to-date security policies, enhancing privacy compliance disclosures on related pages, and continuing regular security audits to uphold the high security standards.

Scanned

NIS2 and GDPR posture

NIS2 outside view
60/ 100 · Medium
GDPR outside view
97/ 100 · Low
Checks completed
9of 9

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

The NIS2 figure counts only evidence anyone can see from the internet. 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

No critical or high findings. These medium findings are worth fixing next.

  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.

    • Medium

      Weak SPF Policy

      The SPF record ends in "?all" (or has no "all"), so mail from unlisted servers gets a neutral result and SPF gives no protection against spoofing.

      What to do: End the record with "-all", or "~all" while you confirm every sender is listed.

    • Medium

      DMARC not enforcing

      The DMARC policy is p=none, so mail that fails authentication is still delivered; the record only collects reports.

      What to do: Review the aggregate reports, then move to p=quarantine and finally p=reject.

  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.

    • Medium

      Weak Protocols Supported

      The server still accepts TLS 1.1 and TLS 1.0, deprecated by RFC 8996. Modern browsers no longer use them, but they let outdated clients connect with weak cryptography.

      What to do: Disable TLS 1.0 and 1.1; keep TLS 1.2 and TLS 1.3 (in CDN dashboards this is the "minimum TLS version" setting).

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

Keep watching business.site

This scan found 8 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. 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
89
Security headers
100
Email security
80
DNS health
97
Network security
100
Website hygiene
95
GDPR outside view
97
Average
94

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.
  • Accessibility: Accessibility is a separate readout from security, so it is reported but not scored. 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 business.site, from OffSeq Breach.

Total records
623
Employees
0
Customers
448
Third parties
175
Weak passwords
22%

107 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 business.site.

Select it in the checkout above.

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

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Google LLC operates as a global technology leader with a diversified business model encompassing search, advertising, cloud services, and consumer products. This consent page is part of Google's compliance infrastructure, supporting GDPR and other privacy regulations by managing user consent. The business model relies heavily on data-driven advertising and cloud services, with a strong emphasis on user privacy controls to maintain regulatory compliance and user trust. Google's market position is dominant, with extensive partnerships and a broad customer base worldwide. The company's strategic focus includes innovation in AI, cloud computing, and privacy-enhancing technologies. This page reflects Google's commitment to privacy and regulatory adherence, which is critical for sustaining its advertising revenue streams and global operations.

Security posture

The website exhibits a high level of security maturity, leveraging HTTPS with strong SSL/TLS configurations and implementing security headers such as Strict-Transport-Security and Content-Security-Policy. The JavaScript code includes advanced protections against prototype pollution and enforces object sealing, which mitigates common attack vectors. No vulnerabilities or exposed sensitive data were detected in the analyzed content. However, the absence of explicit security or incident response policies on this page suggests these are managed centrally within Google's broader security framework. Compliance with GDPR is implied through the consent management functionality, but explicit documentation is not present here. The security posture is robust, reflecting Google's enterprise-grade security standards.

Recommendations

  1. Enhance visibility and accessibility of privacy and cookie policies linked directly from the consent page for improved user transparency.
  2. Include explicit incident response contact information or links to Google's security team to facilitate vulnerability reporting and user trust.
  3. Regularly update and audit Content Security Policy and JavaScript security measures to address emerging threats.
  4. Improve accessibility features to meet higher standards for users with disabilities.
  5. Consider integrating more comprehensive user guidance on consent choices to enhance user experience and compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Google LLC
Description
Google LLC provides a consent management interface for user privacy and cookie preferences related to Google services.
Key services
consent management, privacy controls, cookie preferences
Content quality
basic
Branding
consistent

Technology

Stack
JavaScript, HTML5, CSS3, Google APIs
Frameworks
Material Design Components (MDC)
Platforms
Web
Performance
fast
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Content Security Policy with nonce
  • Object prototype sealing and deletion to prevent prototype pollution

Analytics and tracking

Services
Google Analytics (implied)
Tracking level
moderate
Privacy practices
basic

Advertising

Ad networks
Google Ads (DoubleClick)
Tracking pixels
Google Ads tracking
Marketing tools
Google Ads, Google Analytics (implied)
Transparency
good

Site quality

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

Key observations

  1. Website is a Google consent management page for privacy and cookie preferences.
  2. Content is technical and functional rather than marketing or business-oriented.
  3. No direct contact information or business policies (privacy, cookie, TOS) are present on this page.
  4. Strong security practices observed in JavaScript and HTTPS usage.
  5. No signs of blocking or WAF challenges detected.
Technical notes

Notes

The website is built using modern web technologies including JavaScript with advanced security features, Material Design Components for UI consistency, and hosted on Google Cloud Platform ensuring high availability and performance. The page is optimized for mobile devices and includes performance monitoring scripts. The technical implementation is clean and secure, with no deprecated or vulnerable libraries detected. The site uses canonical links and meta tags appropriately, although SEO is minimal due to the page's functional nature. There is no CMS detected as this is a specialized consent interface. Overall, the technical infrastructure is robust and well-maintained, supporting Google's global service delivery.
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 business.site. 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 business.site.

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.