Skip to main content

Security report for flyingcarai.io

Flying Car AI · Technology

Low risk. No critical or high findings.

Security score

89/100

Risk levelLow

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

Flying Car AI is a niche technology company offering an innovative web-based AI video generation service that allows users to create personalized flying car videos using their own photos. The platform targets social media users who want to participate in the viral flying car trend by generating short, engaging videos without requiring technical skills or app installations. The business model is credit-based, with no subscription, providing flexibility and ease of use. The website is professionally designed with clear navigation, multiple scene templates, and transparent pricing, enhancing user experience and trust. Technically, the website leverages modern JavaScript frameworks (likely React) and integrates multiple analytics services including Google Analytics, Ahrefs, and Plausible. The site is mobile-optimized, fast-loading, and accessible, with proper SEO metadata and structured data enhancing discoverability. Payment processing is securely handled by a third-party provider (Waffo) over encrypted connections, ensuring user data protection during transactions. From a security perspective, the site enforces HTTPS and implements cookie consent mechanisms, but lacks explicit security policies, incident response contacts, and vulnerability disclosure information. No critical vulnerabilities or exposed sensitive data were detected. The WHOIS data is consistent with the website's business claims, supporting legitimacy. Overall, the security posture is good but could be improved by publishing dedicated security documentation and enhancing security headers. The overall risk assessment is low, with strong content quality, technical implementation, and privacy compliance. Strategic recommendations include adding a security policy page, publishing vulnerability disclosure details, and enhancing incident response readiness to further strengthen trust and compliance.

Scanned

NIS2 and GDPR posture

NIS2 outside view
70/ 100 · Medium
GDPR outside view
100/ 100 · Low
Checks completed
9of 9

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

The NIS2 figure counts only evidence anyone can see from the internet. 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

No critical or high findings. These medium findings are worth fixing next.

  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.

    • Medium

      Missing Strict-Transport-Security header

      Without HSTS, a visitor who types the address or follows an http:// link makes a first request over plain HTTP, which an attacker on the same network can intercept and keep unencrypted (SSL stripping).

      What to do: Send "Strict-Transport-Security: max-age=31536000; includeSubDomains" on HTTPS responses once every subdomain works over HTTPS (use max-age=31536000 alone otherwise).

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • Medium

      Missing Content-Security-Policy header

      No Content-Security-Policy is set, so if an attacker manages to inject a script (cross-site scripting), the browser runs it with full access to the page.

      What to do: Start with "Content-Security-Policy: object-src 'none'; base-uri 'self'; frame-ancestors 'self'" and add a script-src that lists your script origins or uses nonces. Test with a Report-Only header first.

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

      Missing X-Frame-Options header

      Other websites can load your pages inside an invisible frame and trick visitors into clicking buttons on them (clickjacking).

      What to do: Send "Content-Security-Policy: frame-ancestors 'self'" (or X-Frame-Options: SAMEORIGIN for older browsers).

  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.

    • Medium

      Weak Protocols Supported

      The server still accepts TLS 1.1 and TLS 1.0, deprecated by RFC 8996. Modern browsers no longer use them, but they let outdated clients connect with weak cryptography.

      What to do: Disable TLS 1.0 and 1.1; keep TLS 1.2 and TLS 1.3 (in CDN dashboards this is the "minimum TLS version" setting).

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

Keep watching flyingcarai.io

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
89
Security headers
53
Email security
89
DNS health
94
Network security
100
Website hygiene
95
GDPR outside view
100
Average
89

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.
  • Accessibility: Accessibility is a separate readout from security, so it is reported but not scored. 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

Flying Car AI occupies a unique position in the AI-generated video content market, capitalizing on a viral trend with a simple, user-friendly product. Its credit-based business model allows users to pay per video without subscription commitments, appealing to casual users and social media enthusiasts. The company focuses on personalization by allowing users to upload their own photos and cars, differentiating from generic viral clips. The partnership with Waffo for payment processing indicates a secure and professional transaction environment. The absence of phone or physical address contact suggests a lean, possibly startup-level operation. The use of multiple analytics tools reflects a data-driven approach to user engagement and marketing. Overall, the company demonstrates a clear market niche, competitive pricing, and a scalable digital product offering.

Security posture

The website demonstrates a mature security posture with mandatory HTTPS, encrypted payment processing, and cookie consent mechanisms aligned with GDPR requirements. However, the absence of a published security policy, incident response contacts, and vulnerability disclosure reduces transparency and preparedness for security incidents. No security headers were explicitly detected in the provided data, which could be improved to mitigate common web vulnerabilities. The site does not expose sensitive data or use vulnerable libraries based on the analysis. The WHOIS data is transparent and consistent, supporting domain legitimacy. To enhance security maturity, the company should publish dedicated security documentation, implement security headers, and establish clear incident response channels.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and controls.
  2. Implement and publicize a vulnerability disclosure program or security.txt file.
  3. Add security headers such as Content Security Policy (CSP), Strict-Transport-Security (HSTS), and X-Content-Type-Options.
  4. Provide incident response contact information (e.g., security@ or abuse@ email addresses).
  5. Regularly review and audit third-party scripts and analytics tools to minimize tracking and potential vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Flying Car AI
Description
Flying Car AI turns your photo into a 15 second video: you press Flight Mode and your car lifts off over traffic. Pick a scene, add a photo and post it.
Key services
AI-generated flying car videos from user photos, Multiple scene templates, Credit pack purchases for video generation
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, Google Analytics, Ahrefs Analytics, Plausible Analytics
Frameworks
Likely React or similar SPA framework
Platforms
Web
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Encrypted payment processing via Waffo
  • No sensitive data exposed in HTML
  • Cookie consent mechanism implemented

Analytics and tracking

Services
Google Analytics, Ahrefs Analytics, Plausible Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Ahrefs Analytics, Plausible Analytics
Marketing tools
Ahrefs Analytics, Plausible Analytics
Transparency
good

Site quality

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

Key observations

  1. Website provides a clear, focused AI video generation service.
  2. Strong user interface with multiple scene templates and easy photo upload.
  3. Transparent pricing with credit packs and no subscription.
  4. Good privacy and cookie compliance with consent mechanisms.
  5. Secure payment processing via third-party provider Waffo.
  6. No phone contact or physical address found; only email support.
  7. No explicit security policy or incident response contact published.
  8. No security.txt or vulnerability disclosure found.
  9. Use of multiple analytics tools with moderate tracking.
  10. No WAF or blocking detected; site fully accessible.
Technical notes

Notes

The website is built using modern web technologies, likely React or a similar JavaScript framework, with modulepreload hints and structured JSON-LD data for SEO. It integrates multiple analytics platforms for comprehensive user behavior tracking. The site is mobile-optimized with responsive design and accessibility features such as skip links and ARIA labels. Performance appears fast with preloaded fonts and images. Payment processing is outsourced to Waffo, ensuring secure transactions. No CMS or hosting provider is explicitly identified, suggesting a custom or cloud-based hosting solution. The technical implementation is robust, but could benefit from enhanced security headers and explicit hosting information for transparency.
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 flyingcarai.io. 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 flyingcarai.io.

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.