Skip to main content

Security report for fflapi.com

FFL API · Technology · United States

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

Security score

62/100

Risk levelMedium

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

FFL API operates as a specialized technology platform providing API services for developers and firearm dealers in the USA. The company offers integration solutions with major ecommerce platforms such as BigCommerce, WooCommerce, Magento, and Volusion, enabling seamless access to Federal Firearms License (FFL) dealer data. The website positions itself as a centralized solution for firearm dealer directory and licensing data, targeting developers and firearm dealers seeking efficient integration capabilities. The business appears to be a small-sized entity founded around 2019, with a focus on niche market needs in the firearm and ecommerce sectors. Technically, the website is built on WordPress with Elementor and Yoast SEO plugins, leveraging modern web technologies including Google Analytics and Google Tag Manager for user tracking and performance monitoring. The site demonstrates good SEO practices, mobile optimization, and a professional design, although performance is moderate. The technical stack is standard for small to medium business websites, with no evident critical technical debt or outdated components. From a security perspective, the site enforces HTTPS and uses asynchronous loading for analytics scripts, but lacks explicit security headers and published security policies. No vulnerabilities or exposed sensitive data were detected in the HTML content. Privacy compliance is partially addressed with privacy and cookie policies present, but no active consent mechanism is implemented. The absence of WHOIS data for the domain raises concerns about domain registration transparency, impacting trustworthiness. No incident response or vulnerability disclosure information is available. Overall, the website presents a professional and functional platform with moderate security and privacy maturity. The main risk factors relate to domain registration opacity and incomplete privacy consent mechanisms. Strategic improvements in security headers, privacy compliance, and domain registration transparency would enhance trust and reduce risk.

Scanned

NIS2 and GDPR posture

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

  2. GDPR outside view

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

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

      Weak SSL Key Length

      SSL certificate uses 384-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching fflapi.com

This scan found 21 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
52
Security headers
65
Email security
70
DNS health
75
Network security
40
GDPR outside view
68
Average
62

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

FFL API occupies a niche market segment providing API access to firearm dealer data for ecommerce and developer audiences. Its competitive advantage lies in centralized, easy-to-integrate solutions compatible with popular ecommerce platforms. Revenue likely derives from subscription plans with tiered request limits. The target customers are ecommerce businesses, firearm dealers, and developers requiring FFL data integration. The company demonstrates growth potential through platform integrations and client testimonials. Partnerships with ecommerce platforms enhance market reach. The business model is service-oriented SaaS with a focus on compliance and data accuracy. Strategic observations include the need for improved domain transparency and enhanced privacy mechanisms to build greater customer confidence.

Security posture

The current security posture is moderate. HTTPS is enforced, and no sensitive data leakage is evident. However, the absence of key security headers such as Content-Security-Policy and X-Frame-Options reduces defense-in-depth. Privacy compliance is partial, with policies published but lacking active consent mechanisms. No incident response or vulnerability disclosure processes are visible, indicating potential gaps in security governance. The use of third-party analytics and tag management introduces moderate tracking and data collection risks. Overall, the security culture appears basic, suitable for a small business but requiring enhancements to meet higher compliance and security standards.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to strengthen browser security.
  2. Add an explicit cookie consent banner/mechanism to comply with GDPR and enhance user privacy transparency.
  3. Publish a formal security policy and incident response contact information to improve trust and preparedness.
  4. Verify and publish domain WHOIS information or use a reputable registrar to improve domain registration transparency.
  5. Regularly audit third-party scripts and dependencies to mitigate risks from vulnerable libraries or tracking tools.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
FFL API
Description
FFL API is a platform for developers and Firearm Dealers that integrate with Bigcommerce, Volusion, Magento and Custom Ecommerce Systems.
Key services
Zip Code API for FFL Dealers, FFL Locator web widget, Checkout Integrations with ecommerce platforms
Content quality
good
Branding
consistent

Technology

Stack
WordPress 6.8.1, Elementor 3.21.2, Yoast SEO plugin, Google Analytics, Google Tag Manager, Google Maps API, jQuery, Bootstrap
Frameworks
WordPress, Elementor
Platforms
BigCommerce, WooCommerce, Magento, Volusion
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of Google Tag Manager and Analytics with async loading

Analytics and tracking

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

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is a professional WordPress site using Elementor and Yoast SEO
  2. Provides API services for firearm dealer data integration
  3. No WHOIS data available, which is unusual and reduces trust
  4. No direct company contact emails or phone numbers found on homepage
  5. Privacy and cookie policies are present but no explicit consent mechanism detected
  6. No explicit security or incident response policies published
  7. Uses Google Analytics and Tag Manager for tracking
  8. No adult or questionable content detected
  9. Good SEO and structured data implementation
Technical notes

Notes

The website uses a modern WordPress CMS with Elementor page builder and Yoast SEO plugin, indicating a well-supported and widely used technology stack. Integration of Google Analytics and Tag Manager is standard for performance and user behavior tracking. The site loads external resources from trusted CDNs and Google APIs, including Google Maps for location services. Performance is moderate, with room for optimization in loading speed and accessibility. Mobile optimization is good, ensuring usability across devices. The technical infrastructure is typical for a small SaaS platform, with no critical technical debt detected. Opportunities exist to enhance security headers and privacy compliance features.
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 fflapi.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 fflapi.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.