Skip to main content

Security report for talgov.com

City of Tallahassee · Government · United States

Medium risk. 5 critical or high findings in SSL/TLS, GDPR outside view and 1 other check.

Security score

67/100

Risk levelMedium

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

The website talgov.com serves as the official online presence of the City of Tallahassee, Florida. It provides municipal information, community resources, and government services to residents and visitors. The site positions itself as a government entity focused on community engagement, environmental stewardship, and economic opportunity. The branding and content align with a large government organization serving a broad audience. Technically, the site employs common web technologies including jQuery, Google Tag Manager, Facebook SDK, and Font Awesome icons. It uses HTTPS and includes Open Graph metadata for social media integration. However, the site lacks visible privacy and cookie policies, security headers, and WHOIS domain registration data, which raises some concerns about compliance and transparency. The absence of WHOIS data is inconsistent with the official nature of the site and warrants further investigation. Overall, the site is functional and professional but could improve in privacy compliance and security best practices.

Scanned

NIS2 and GDPR posture

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

5 findings rated critical or high. Fix these first.

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

      SSL Certificate Expires Soon

      SSL certificate expires in 23 days

      What to do: Renew SSL certificate before expiration

      • NIS2 21(2)(h)
      • IR 2024/2690 9.2(c): Implementing Regulation (EU) 2024/2690, Annex point 9.2(c): Cryptography
      • NIST SC-17: NIST SP 800-53 Rev. 5 SC-17: Public Key Infrastructure Certificates

  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

  3. 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 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';…

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

Keep watching talgov.com

This scan found 23 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
37
Security headers
60
Email security
70
DNS health
75
Network security
100
GDPR outside view
58
Average
67

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

Talgov.com operates as a government portal for the City of Tallahassee, targeting residents, businesses, and visitors. Its business model is informational and service-oriented, typical of municipal websites. The site likely generates value through public service delivery and community engagement rather than commercial revenue. The presence of tracking tools like Google Analytics and Facebook Pixel indicates an interest in user engagement metrics. The lack of explicit business registration or VAT information is expected for a government entity. The site’s market position is authoritative within its geographic scope. Partnerships or subsidiaries are not evident from the data. Growth indicators and strategic partnerships are not disclosed. The site’s ecosystem includes social media integration primarily via Facebook.

Security posture

The website demonstrates a moderate security posture with HTTPS enabled and no obvious exposed sensitive data. However, the absence of key security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options reduces its defense-in-depth. No vulnerability disclosures or incident response contacts are published, which limits transparency and readiness for security incidents. The lack of privacy and cookie policies also indicates compliance gaps, particularly with GDPR and other data protection regulations. The use of third-party analytics and tracking scripts introduces potential privacy risks. Overall, while basic security is in place, the site would benefit from enhanced security headers, published policies, and incident response mechanisms to improve trust and compliance.

Recommendations

  1. Implement comprehensive privacy and cookie policies with user consent mechanisms to comply with GDPR and other regulations.
  2. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to strengthen security posture.
  3. Publish a vulnerability disclosure policy and incident response contact information to improve transparency and readiness.
  4. Improve mobile optimization and accessibility features to enhance user experience and compliance with accessibility standards.
  5. Investigate and resolve the WHOIS data inconsistency to ensure domain registration transparency and legitimacy.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
City of Tallahassee
Description
The official website of the City of Tallahassee, Florida, a city which remembers its past while focusing on the future – a vibrant capital city: fostering a strong sense of community, cherishing our beautiful, natural environment, and ensuring economic opportunities for all our citizens.
Key services
Community information, Government services, Economic development, Environmental stewardship
Content quality
good
Branding
consistent

Technology

Stack
jQuery, Google Tag Manager, Facebook SDK, Google Custom Search Engine, Font Awesome 6 Pro
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics (via Google Tag Manager), Facebook Analytics (via Facebook SDK)
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Google Analytics (via Google Tag Manager), Facebook Pixel (via Facebook SDK)
Marketing tools
Facebook SDK
Transparency
basic

Site quality

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

Key observations

  1. Website content is accessible and appears legitimate
  2. No WHOIS data available, raising questions about domain registration
  3. No explicit privacy, cookie, or terms of service policies found in provided content
  4. Use of modern tracking and analytics tools
  5. No security headers detected in provided data
  6. No contact emails or phone numbers explicitly found in provided HTML snippet
  7. No forms detected in provided HTML snippet
  8. No JSON-LD structured data found in provided snippet
  9. Website uses HTTPS and includes Open Graph metadata
  10. No WAF or blocking mechanisms detected
Technical notes

Notes

The website uses a standard technology stack including jQuery, Google Tag Manager, Facebook SDK, and Font Awesome icons. The HTML content is well-structured with proper meta tags and Open Graph data for SEO and social media sharing. Performance is moderate with asynchronous loading of scripts. Mobile optimization is basic but present. Accessibility features are minimal based on the provided data. The site does not appear to use a common CMS or framework explicitly. Hosting provider details are not available. There is no evidence of technical debt or deprecated libraries in the snippet provided. Opportunities exist to modernize security headers and enhance privacy 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 talgov.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 talgov.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.