Skip to main content

Security report for faia.com

Florida Association of Insurance Agents · Non-profit · United States

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

Security score

48/100

Risk levelHigh

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

The Florida Association of Insurance Agents (FAIA) operates as a non-profit membership organization dedicated to supporting Florida insurance agents through education, advocacy, and industry services. The website reflects a mature association with a broad offering of educational programs, advocacy resources, membership benefits, and preferred provider partnerships. The target audience is primarily insurance agents and agencies within Florida, with a focus on professional development and market access. The business model centers on membership dues, educational offerings, and partnerships with service providers. Technically, the website is built on Microsoft IIS with ASP.NET and Kentico CMS, utilizing common JavaScript libraries such as jQuery and Bootstrap. While the site is content-rich and professionally designed with clear navigation, it lacks a valid SSL certificate, which is a critical security deficiency. The absence of HTTPS undermines user trust and exposes visitors to potential risks. Privacy compliance is partial, with a privacy policy and terms of service present but no cookie consent mechanism. Analytics tools like Google Analytics and Microsoft Clarity are used, indicating moderate user tracking. Overall, the website is functional and credible but requires urgent security improvements to align with best practices.

Scanned

NIS2 and GDPR posture

GDPR outside view
18/ 100 · Critical
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. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

    • 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

  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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

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

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

Keep watching faia.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
0
Security headers
35
Email security
50
DNS health
85
Network security
100
GDPR outside view
18
Average
48

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

FAIA holds a strong position as a key industry association in Florida, providing essential services to insurance agents including education, advocacy, and market access. Its partnerships with preferred providers such as payment processors and IT service firms enhance its value proposition. The organization leverages events and member benefits to maintain engagement and growth. The website content and structure support a professional image and facilitate member interaction. The domain registration data aligns well with the business claims, reinforcing legitimacy. However, the lack of HTTPS and cookie consent may impact user confidence and regulatory compliance. The association's focus on Florida and insurance sectors is clear and consistent across content and linked domains.

Security posture

The website's security posture is weak due to the absence of a valid SSL certificate and lack of HTTPS support. This exposes users to risks such as data interception and undermines trust. Security headers are minimal, with only basic protections like X-Frame-Options present. Cookies are set with Secure and HttpOnly flags, and CSRF tokens are implemented, indicating some security awareness. No advanced security policies, incident response contacts, or vulnerability disclosures are found. The site does not implement HSTS or modern TLS protocols. Analytics and tracking scripts are present but no explicit privacy controls or cookie consent mechanisms are implemented. Immediate remediation of SSL/TLS and enhancement of security headers is recommended to improve the security posture.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  3. Upgrade server TLS protocols to support TLS 1.2 and TLS 1.3 and disable legacy protocols.
  4. Add Content Security Policy (CSP) headers to mitigate cross-site scripting and related attacks.
  5. Introduce a cookie consent banner and detailed cookie policy to comply with privacy regulations.
  6. Publish a security policy and incident response contact information to enhance transparency.
  7. Conduct regular security audits and vulnerability assessments to identify and remediate risks.
  8. Improve mobile optimization and accessibility features to enhance user experience.
  9. Enhance SEO by adding structured data (JSON-LD) and Open Graph metadata for better indexing.
  10. Maintain consistent branding and update content regularly to sustain trust and engagement.

Contact details published on the site

Addresses
Technical notes

Notes

The website is hosted on Microsoft IIS 8.5 and built using ASP.NET 4.0 with Kentico CMS. It uses common front-end libraries including jQuery 3.3.1, Bootstrap 3.3.7, and Swiper 3.4.1 for UI components and sliders. The site includes Google Analytics and Microsoft Clarity for user behavior tracking. Performance metrics are not available, but the site appears to have basic mobile responsiveness and accessibility. The lack of HTTPS and modern TLS support is a significant technical debt. The site uses server-side form handling with CSRF protection tokens. Opportunities exist to modernize the tech stack, improve performance, and enhance 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 faia.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 faia.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.