Skip to main content

Security report for blogspot.lt

Redirects to www.google.com; the website checks ran on that page, the DNS and email checks on blogspot.lt.

Google LLC · Technology · United States

Low risk. No critical or high findings.

Security score

93/100

Risk levelLow

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

Google LLC is a global leader in technology, primarily known for its search engine and advertising services. The company operates a vast ecosystem of products including cloud computing, software, and hardware, serving a broad general audience worldwide. As a subsidiary of Alphabet Inc., Google maintains a dominant market position with a comprehensive portfolio of digital services. The website reflects this stature with professional design, excellent content quality, and strong branding consistency. Technically, the website leverages modern web technologies and Google’s proprietary frameworks, hosted on Google Cloud Platform, ensuring fast performance and excellent mobile optimization. The site incorporates advanced SEO and accessibility features, providing a seamless user experience. Security is robust, with HTTPS enforced, comprehensive security headers, and adherence to best practices including a public bug bounty program. From a security and compliance perspective, Google demonstrates maturity with clear privacy and cookie policies, GDPR compliance, and dedicated incident response contacts. The domain registration details align perfectly with the business entity, reinforcing trust and legitimacy. No vulnerabilities or suspicious activities were detected, and the site employs extensive analytics and advertising tools transparently. Overall, Google’s website exemplifies a high standard of digital maturity, security posture, and business credibility, making it a trustworthy and authoritative online presence.

Scanned

NIS2 and GDPR posture

NIS2 outside view
80/ 100 · Low
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. 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.

    • Medium

      Missing Content-Security-Policy header

      A Content-Security-Policy-Report-Only header is set, but it only reports violations; nothing is blocked, so an injected script would still run.

      What to do: Start with "Content-Security-Policy: object-src 'none'; base-uri 'self'; frame-ancestors 'self'" and add a script-src that lists your script origins or uses nonces. Test with a Report-Only header first.

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

  3. Website hygiene

    Outdated scripts and CMS versions are how most small-business sites get compromised; a security.txt file tells researchers where to report what they find.

    • Medium

      HTTP does not redirect to HTTPS

      http://www.google.com/, http://google.com/ answer over unencrypted HTTP (status 200) instead of redirecting to HTTPS, so visitors who type the address or follow old links are not protected.

      What to do: Configure a permanent (301) redirect from every http:// URL to the same https:// URL, then enable HSTS.

Keep watching blogspot.lt

This scan found 10 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
77
Email security
100
DNS health
97
Network security
100
Website hygiene
90
GDPR outside view
97
Average
93

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 blogspot.lt, from OffSeq Breach.

No leaked records found

Breach holds no records for blogspot.lt right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

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

Google’s market positioning as a technology giant is reinforced by its diversified business model centered on advertising revenue and cloud services. The company’s competitive advantages include its dominant search engine, extensive data analytics capabilities, and a broad product ecosystem. Revenue streams are primarily from advertising but also include hardware sales and cloud services. Target customers range from individual users to enterprises globally. Growth indicators are strong, supported by continuous innovation and strategic acquisitions. The partnership ecosystem includes subsidiaries like YouTube and Android, enhancing market reach and service integration.

Security posture

Google exhibits a mature security posture with enforced HTTPS, comprehensive security headers, and a proactive vulnerability disclosure program. Compliance with international standards such as ISO 27001 and SOC 2 is evident. Data protection practices align with GDPR requirements, supported by a dedicated Data Protection Officer contact. Incident response readiness is high, with clear channels for reporting abuse and security incidents. No significant vulnerabilities or compliance gaps were identified. The security culture is reinforced by transparency and continuous monitoring.

Recommendations

  1. Maintain and regularly update security headers and SSL configurations to stay ahead of emerging threats.
  2. Enhance user privacy controls and transparency regarding data collection and retention.
  3. Continue active engagement with the bug bounty program to identify and remediate vulnerabilities promptly.
  4. Expand accessibility features to ensure compliance with evolving standards and improve user experience for all audiences.
  5. Monitor third-party integrations closely to mitigate supply chain risks.

Contact details published on the site

Addresses
Legal name
Google LLC
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Google LLC
Description
Google LLC is a multinational technology company specializing in Internet-related services and products including online advertising technologies, search engine, cloud computing, software, and hardware.
Key services
Search engine, Advertising services, Cloud computing, Software products, Hardware products
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, Google Fonts, HTML5, CSS3
Frameworks
Google internal frameworks
Platforms
Web
Performance
fast
Mobile
excellent
Accessibility
good
SEO
excellent

Security

Observed score
95/100
Good practices seen
  • HTTPS enforced
  • Secure cookies
  • Content Security Policy
  • Regular security audits
  • Bug bounty program

Analytics and tracking

Services
Google Analytics
Tracking level
extensive
Privacy practices
good

Advertising

Ad networks
Google Ads
Marketing tools
Google Marketing Platform
Transparency
excellent

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is professional, well-structured, and localized in German.
  3. Strong security posture with modern headers and HTTPS.
  4. Comprehensive privacy and cookie policies with consent mechanisms.
  5. Multiple Google-owned domains linked and integrated.
  6. No suspicious or malicious content detected.
  7. Advanced technical implementation with Google proprietary technologies.
  8. Extensive use of analytics and advertising tools with transparency.
  9. Clear business information and contact channels available.
Technical notes

Notes

The website is built on a custom CMS with extensive use of JavaScript and Google Fonts, hosted on Google Cloud Platform. Performance is optimized for fast loading and mobile responsiveness. SEO is well-implemented with proper meta tags and structured data. Accessibility is good but could be further enhanced. The technical infrastructure shows low technical debt and high modernization, supporting scalability and reliability. Potential risks include dependency on proprietary frameworks and extensive user tracking, which require ongoing management.
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 blogspot.lt. 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 blogspot.lt.

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.