Skip to main content

Security report for cityofmobile.org

City of Mobile · Government · United States

Medium risk. 4 critical or high findings in Network security, SSL/TLS and 1 other check.

Security score

68/100

Risk levelMedium

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

The City of Mobile's official website serves as a comprehensive portal for residents, businesses, visitors, and government officials, providing extensive information on city services, events, government departments, and community resources. The site is well-structured with clear navigation and a professional design consistent with government standards. It leverages modern web technologies and integrates multiple trusted external services to enhance user experience and service delivery. The presence of a privacy policy and accessibility features further supports its commitment to user inclusivity and regulatory compliance. Technically, the website employs a robust technology stack including Bootstrap, jQuery, Google Analytics, Google Tag Manager, and Mapbox GL JS, among others. The site is mobile-optimized and accessible, though performance is moderate, likely due to the number of external scripts and resources. Security posture is generally strong with HTTPS enforced and use of reCAPTCHA; however, the absence of explicit security headers and a cookie consent mechanism indicates areas for improvement in compliance and security best practices. From a security perspective, no critical vulnerabilities or exposed sensitive data were detected. The lack of WHOIS data limits domain registration transparency, but the .gov domain and consistent website content support legitimacy. The site lacks a vulnerability disclosure policy and incident response information, which are recommended for enhanced security readiness. Overall, the website presents a trustworthy and professional digital presence for the City of Mobile but would benefit from enhanced security headers, privacy compliance mechanisms, and transparency in security policies. Strategically, the City of Mobile should prioritize implementing security headers, establishing a cookie consent mechanism to comply with privacy laws, and publishing clear security and incident response policies. These steps will strengthen u…

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

4 findings rated critical or high. Fix these first.

  1. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • High

      High-Risk Service Exposed: FTP

      Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer

      What to do: Consider restricting access to FTP or implementing strong authentication

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

  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 Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

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

  3. 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 cityofmobile.org

This scan found 15 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
67
Security headers
85
Email security
100
DNS health
80
Network security
20
GDPR outside view
53
Average
68

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 City of Mobile operates as a municipal government entity providing essential services to its residents, businesses, and visitors. Its market position is that of the primary authoritative source for city-related information and services. The business model is service-oriented, focusing on public administration, community engagement, and regulatory compliance. Revenue streams are typical of government entities, including business licenses, permits, and taxes. The target customer segments include local residents, business owners, tourists, and government officials. Growth indicators include ongoing infrastructure projects and digital service enhancements. The partnership ecosystem includes technology providers like Tyler Technologies and community organizations such as the Chamber of Commerce. The website reflects a mature operational model with a focus on transparency and accessibility.

Security posture

The website demonstrates a moderate to strong security maturity level with HTTPS enforced and use of Google reCAPTCHA to protect forms. No exposed sensitive data or vulnerable libraries were identified in the HTML content. However, the absence of key security headers such as Content-Security-Policy and Strict-Transport-Security reduces the overall security posture. There is no publicly available vulnerability disclosure or incident response information, which limits transparency and readiness. Compliance with privacy regulations is partial, as a privacy policy exists but no cookie consent mechanism is implemented despite tracking technologies. The security culture appears to be focused on basic protections but could be enhanced with more comprehensive policies and technical controls.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Strict-Transport-Security to enhance protection against common web attacks.
  2. Deploy a cookie consent banner or mechanism to comply with GDPR and other privacy regulations, especially given the use of tracking and analytics scripts.
  3. Publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting and improve security transparency.
  4. Develop and make publicly available incident response and security policies to demonstrate preparedness and build user trust.
  5. Regularly audit and update third-party scripts and libraries to mitigate risks from vulnerable dependencies.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
City of Mobile
Description
Official website of the City of Mobile, Alabama, providing information about city services, government, business, residents, visitors, and community events.
Key services
City services information, Event calendar, Business licensing and permits, Public safety information, Online payments, Mapping and GIS services, Community engagement
Content quality
good
Branding
consistent

Technology

Stack
jQuery, Bootstrap, FontAwesome, Google Analytics, Google Tag Manager, Mapbox GL JS, LightGallery, Moment.js, Google reCAPTCHA, Swiper.js, Constant Contact, Google Translate
Frameworks
Bootstrap 4
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of Google reCAPTCHA for forms
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Ad networks
simpli.fi
Marketing tools
Constant Contact
Transparency
basic

Site quality

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

Key observations

  1. Official city government website with comprehensive service information
  2. No WHOIS data available, limiting domain registration analysis
  3. No cookie consent mechanism detected despite use of tracking scripts
  4. No explicit security headers detected in HTML content
  5. Multiple external trusted government and community partner links
  6. Good accessibility features including screen reader support and skip links
  7. Use of modern JavaScript libraries and frameworks
  8. No signs of adult or inappropriate content
  9. Privacy policy present and accessible
  10. No terms of service or security policy pages found
Technical notes

Notes

The website uses a modern and diverse technology stack including Bootstrap for responsive design, jQuery for DOM manipulation, FontAwesome for icons, and Mapbox GL JS for mapping services. Analytics and marketing tools such as Google Analytics, Google Tag Manager, Constant Contact, and Simpli.fi are integrated for user tracking and engagement. The site is mobile-optimized and includes accessibility features like screen reader alerts and skip links. Performance is moderate, likely impacted by multiple external resources and scripts. There is no detected CMS, suggesting a custom or proprietary platform. Hosting provider details are not evident from the HTML content. Technical risks include the lack of security headers and cookie consent mechanisms, which could affect compliance and security posture.
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 cityofmobile.org. 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 cityofmobile.org.

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.