Skip to main content

Security report for g.page

Technology · N/a

Low risk. 2 critical or high findings in GDPR outside view and SSL/TLS.

Security score

84/100

Risk levelLow

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

The analyzed website is a consent management page hosted on the subdomain consent.google.com, part of Google's infrastructure. It serves as a user interface for managing privacy consents related to Google's services, particularly for compliance with regulations such as GDPR. The page is minimalistic, focusing on consent UI elements and uses Google-hosted scripts and resources, ensuring fast performance and strong security. The domain is a subdomain of google.com, a globally recognized and trusted entity, which adds to its legitimacy and trustworthiness. From a technical perspective, the site employs modern JavaScript and is hosted on Google's infrastructure, providing excellent SSL/TLS security and fast loading times. Accessibility and SEO optimizations are basic but sufficient for the page's purpose. No forms or direct user data collection fields are present in the analyzed content, indicating a controlled data collection environment. Security posture is strong with HTTPS enforced and no visible vulnerabilities or exposed sensitive data. However, explicit privacy and cookie policies are not directly found on this page, which slightly impacts privacy compliance scoring. No contact or incident response information is provided here, likely because this page is part of a larger ecosystem where such information is centralized elsewhere. Overall, the website is low risk, highly legitimate, and professionally maintained. Strategic recommendations include linking or referencing explicit privacy and cookie policies on this page to improve transparency and compliance, and providing clear contact or support channels for privacy inquiries to enhance user trust.

Scanned

This is an earlier scan of g.page. View the latest report

NIS2 and GDPR posture

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

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

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

    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching g.page

This scan found 12 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
90
Email security
83
DNS health
90
Network security
100
GDPR outside view
68
Average
84

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

Google operates this consent management page as part of its compliance framework for privacy regulations globally. The page targets end-users of Google services, providing them with control over their data consents. Google's market position as a leading technology company and its extensive service ecosystem underpin the importance of such compliance mechanisms. The business model is primarily advertising and cloud services, with privacy compliance being a critical operational requirement. The consent page supports Google's broader ecosystem by ensuring regulatory adherence and user trust. No direct revenue streams are associated with this page, but it is essential for maintaining Google's reputation and legal standing. Partnerships and related domains are primarily internal Google properties, reflecting a tightly integrated infrastructure.

Security posture

The security posture of the consent.google.com page is robust, leveraging Google's secure hosting and HTTPS enforcement. No security headers were explicitly detected in the provided data, but Google's infrastructure typically includes strong security controls. There are no indications of vulnerabilities or exposed sensitive information. The lack of explicit privacy and cookie policies on this page is a minor compliance gap but likely addressed elsewhere in Google's ecosystem. Incident response and vulnerability disclosure mechanisms are not present on this page but are expected to be managed centrally by Google. Overall, the site demonstrates a mature security culture consistent with enterprise standards.

Recommendations

  1. Add explicit links or embedded content for privacy and cookie policies on the consent page to improve transparency and compliance.
  2. Include clear contact information or links to privacy support channels to enhance user trust and facilitate inquiries.
  3. Implement and display security headers explicitly to reinforce security posture and protect against common web vulnerabilities.
  4. Regularly audit and update consent mechanisms to align with evolving privacy regulations such as GDPR and NIS2.
  5. Enhance accessibility features to ensure compliance with standards and improve user experience for all users.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
basic
Branding
consistent

Technology

Stack
JavaScript, Google proprietary scripts
Performance
fast
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Content Security Policy (implied)

Analytics and tracking

Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
basic
User experience
basic
Content relevance
basic
Navigation
basic
Professionalism
basic
Trustworthiness
high
Technical notes

Notes

The website is built using modern JavaScript and Google proprietary scripts, hosted on Google's infrastructure with resources served from gstatic.com and other Google domains. The page is optimized for fast loading and mobile responsiveness, though accessibility and SEO optimizations are basic. No CMS or third-party frameworks were detected, indicating a custom-built solution. The technical implementation aligns with enterprise-grade standards, leveraging Google's global CDN and security infrastructure. There is minimal technical debt visible, and the site benefits from Google's continuous infrastructure improvements. Opportunities exist to enhance SEO metadata and accessibility compliance further.
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

Earlier scans of this domain

  1. 81/100 +7Low24 findingsView report
  2. 74/100Medium20 findingsView report
Reviews of this site

Share your experience with g.page. 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 g.page.

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.