Skip to main content

Security report for googlemaps.com

Other · N/a

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

Security score

75/100

Risk levelMedium

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

The analyzed URL is a Google consent management page, likely used for GDPR compliance and user consent collection for Google Maps services. The domain consent.google.com does not appear in the WHOIS database, indicating it is a subdomain managed internally by Google and not separately registered. The page content is minimal and truncated, showing no privacy policy, cookie policy, or contact information. The technical infrastructure appears to be a custom Google UI for consent, but full technical details and security headers are not accessible. Due to the lack of WHOIS data and incomplete content, a comprehensive security and compliance evaluation is not possible. The site is presumed legitimate as a Google service but cannot be fully verified from the provided data.

Scanned

This is an earlier scan of googlemaps.com. 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

4 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 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

  3. 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 googlemaps.com

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

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

Total records
22
Employees
0
Customers
22
Third parties
0
Weak passwords
18%

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 googlemaps.com.

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

The domain is part of Google's ecosystem, serving as a consent interface for Google Maps users in Germany (indicated by 'gl=DE' and 'hl=de' parameters). The business model is Google's standard service delivery with integrated consent management for privacy compliance. No direct business contact or additional company information is available on this page. The target audience is end users accessing Google Maps who must provide consent for data processing. The domain is likely a service subdomain rather than a standalone business entity.

Security posture

The security posture cannot be fully assessed due to lack of access to full HTTP headers and incomplete page content. The page uses HTTPS as indicated by the base URL. No explicit security headers or vulnerability indicators are visible in the provided data. The page includes scripts related to consent UI and privacy enforcement but no exposed sensitive data or known vulnerabilities are detected. The absence of WHOIS data and domain registration details limits trust verification. No incident response or security policy information is found.

Recommendations

  1. Enable access to full WHOIS data or use internal Google domain registration records for trust verification
  2. Provide explicit links to privacy policy, cookie policy, and terms of service on consent pages for transparency
  3. Implement visible contact information or support channels for privacy and security inquiries
  4. Ensure security headers and best practices are documented and accessible for compliance audits
  5. Maintain clear documentation of consent mechanisms and data protection officer contact details
Site observations

Automated reading of the public site. Ratings are indicative.

None detected. WHOIS data shows no registration for consent.google.com; HTML content is truncated and minimal, indicating access to full content is blocked or restricted. No WAF challenge detected explicitly, but content is incomplete and WHOIS query failed. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Technology

Analytics and tracking

Site quality

Key observations

  1. WHOIS lookup failed, no domain registration data available for consent.google.com
  2. Page content is a Google consent interface, likely for GDPR compliance and user consent management
  3. No privacy policy, cookie policy, or terms of service explicitly found in the provided HTML snippet
  4. No contact information, security policies, or incident response details found
  5. No external links or social media links detected in the truncated HTML content
  6. No forms detected in the provided HTML snippet
  7. No explicit security headers or SSL configuration details available
  8. Content safety rating is safe; no adult or explicit content detected
  9. Page appears to be a consent management UI, minimal content and scripts related to consent handling
  10. Technical and business details are blocked or unavailable due to incomplete content and WHOIS failure
Technical notes

Notes

The page is built using Google's internal Consent UI framework with scripts enforcing consent and privacy controls. The technology stack includes modern JavaScript features and Google APIs. The page is optimized for mobile and desktop with responsive design elements. However, the provided HTML content is truncated and lacks full metadata, external links, or forms. No CMS or third-party hosting providers are identified. Performance and SEO optimization cannot be fully evaluated due to incomplete data. The page is likely hosted on Google's infrastructure with high availability and security standards.
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. 75/100Medium26 findingsView report
Reviews of this site

Share your experience with googlemaps.com. 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 googlemaps.com.

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.