Skip to main content

Security report for longbeach.gov

City of Long Beach · Government · United States

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

Security score

66/100

Risk levelMedium

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

The City of Long Beach official website serves as a comprehensive portal for residents, businesses, visitors, and city employees. It provides detailed information about city officials, municipal services, business resources, visitor attractions, and employment opportunities. The site is well-structured with clear navigation and a professional design consistent with government standards. The target audience includes local residents, business owners, visitors, and municipal staff. The business model is that of a government service provider, focusing on transparency, accessibility, and community engagement.

Scanned

NIS2 and GDPR posture

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

6 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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

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

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

Keep watching longbeach.gov

This scan found 25 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. 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
62
Security headers
15
Email security
85
DNS health
80
Network security
100
GDPR outside view
53
Average
66

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

The website positions itself as the authoritative source for Long Beach city information, leveraging partnerships with local organizations and government entities. It supports multiple service categories including online payments, business licensing, public safety, and community development. The site integrates external trusted partners for workforce development, business assistance, and visitor information, enhancing its ecosystem. The presence of job listings and official news platforms indicates active community engagement and operational transparency.

Security posture

The website employs HTTPS and uses domain registration protections consistent with government standards. However, DNSSEC is not enabled, and no explicit security headers were detected in the provided data. There is no visible security or incident response policy on the site, and no cookie consent mechanism is implemented despite the use of tracking technologies. These gaps suggest room for improvement in security hardening and privacy compliance. The site does not expose sensitive data and uses reputable third-party services for analytics and media embedding.

Recommendations

  1. Enable DNSSEC to enhance DNS security and prevent spoofing.
  2. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Add a visible cookie consent banner to comply with privacy regulations and inform users about tracking.
  4. Publish explicit security and incident response policies to improve transparency and readiness.
  5. Regularly audit third-party scripts and tracking tools to minimize privacy risks and improve performance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
City of Long Beach
Description
Official website of the City of Long Beach providing information about city officials, services, business resources, residents' resources, visitor information, departments, and job opportunities.
Key services
City official contacts and information, Online payments and services, Business licensing and support, Resident services and resources, Visitor information and attractions, Job listings and employment resources
Content quality
good
Branding
consistent

Technology

Stack
jQuery, Bootstrap, Google Tag Manager, Google Translate, Trumba Calendar, StackAdapt, YouTube embed
Frameworks
Bootstrap
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
70/100
Good practices seen
  • HTTPS enabled
  • No exposed sensitive data in HTML
  • Use of serverTransferProhibited domain status

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Ad networks
StackAdapt
Marketing tools
StackAdapt
Transparency
basic

Site quality

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

Key observations

  1. Website is an official municipal government site with comprehensive city information.
  2. Content is well structured with clear navigation and multiple service categories.
  3. Use of multiple external trusted services for analytics, translation, and media embedding.
  4. No visible security policy or incident response information on the site.
  5. No cookie consent mechanism detected despite use of tracking scripts.
  6. WHOIS data is privacy protected but consistent with legitimate government domain.
  7. No signs of adult or questionable content; site is safe for general audiences.
Technical notes

Notes

The website uses a mature technology stack including jQuery, Bootstrap, Google Tag Manager, and Episerver CMS. It integrates multiple external services for translation, calendar events, and media content. The site is mobile optimized with responsive design and basic accessibility features. Performance is moderate, with some reliance on external scripts that may impact load times. The technical infrastructure is stable but could benefit from modernization efforts such as adopting newer JavaScript frameworks and improving SEO and accessibility compliance.
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 longbeach.gov. 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 longbeach.gov.

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.