Skip to main content

Security report for api.video

api.video · Technology · France

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

Security score

73/100

Risk levelMedium

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

api.video is a technology company specializing in providing a comprehensive video API platform that enables businesses and developers to host, manage, encode, and deliver on-demand and live-stream videos efficiently. The company targets developers, digital agencies, and enterprises seeking to integrate high-quality video content into their websites, software, or applications. With a strong market presence evidenced by thousands of users and notable clients, api.video offers a robust set of services including AI-powered transcription and summarization, video analytics, and a global delivery infrastructure. The technical infrastructure is modern and mature, leveraging Next.js for frontend, AWS for hosting assets, and integrating multiple analytics and marketing tools such as HubSpot, Google Tag Manager, and Microsoft Clarity. The website is well-optimized for performance, mobile responsiveness, and SEO, reflecting a high level of digital maturity. Security best practices are observed with HTTPS enforcement and appropriate security headers, although explicit security policies and incident response contacts are not publicly detailed. Overall, the security posture is strong with no evident vulnerabilities or exposed sensitive data. Privacy compliance is well addressed with clear privacy and cookie policies, including GDPR considerations. The domain WHOIS data is limited due to TLD restrictions and privacy protection but does not raise concerns given the professional website content and external trust signals. The risk assessment indicates a low risk profile with recommendations to enhance transparency by publishing dedicated security and incident response information. Strategic improvements in security communication and vulnerability disclosure would further strengthen trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
73/ 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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

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

  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

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

Keep watching api.video

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
72
Security headers
30
Email security
75
DNS health
85
Network security
100
GDPR outside view
73
Average
73

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

api.video operates in the competitive video API market, differentiating itself through an all-in-one platform that combines video hosting, encoding, delivery, and AI features. Its business model is SaaS/API-based, targeting developers and enterprises requiring scalable video solutions. The company demonstrates strong growth indicators with a large developer base and partnerships with major brands. Its ecosystem includes extensive SDKs, plugins, and integrations, facilitating adoption across various tech stacks. Revenue streams likely include subscription plans and usage-based pricing. The company maintains a professional online presence with comprehensive documentation and customer testimonials, supporting its market credibility and customer trust.

Security posture

The security maturity of api.video is solid, with HTTPS enforced and multiple security headers implemented. The website does not expose sensitive information and uses secure third-party services for forms and analytics. However, the absence of a publicly available security policy or incident response contact limits transparency. There is no evidence of vulnerability disclosure programs or security.txt files. Compliance with GDPR is indicated through privacy and cookie policies. The company should consider publishing explicit security policies and incident response procedures to enhance security culture and readiness. Overall, the security posture supports business continuity and data protection but can be improved in communication and formalization.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and commitments.
  2. Provide clear incident response contact information, such as a security@ or abuse@ email address.
  3. Implement and publicize a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  4. Enhance transparency around data retention and privacy practices to reinforce GDPR compliance.
  5. Regularly review and update third-party scripts and dependencies to mitigate potential vulnerabilities.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
api.video
Description
api.video lets you quickly and securely deliver on-demand and live-stream videos directly from your website, software, or app.
Key services
Video on demand, Live streaming, Video analytics, Video infrastructure, Video player, AI transcription and summarization
Content quality
excellent
Branding
consistent

Technology

Stack
React, Next.js, Google Fonts, HubSpot scripts, Google Tag Manager, Microsoft Clarity, LinkedIn Insight Tag, Facebook Pixel
Frameworks
Next.js
Platforms
AWS S3 (image hosting)
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Use of security headers
  • No exposed sensitive data in HTML
  • Secure forms with HubSpot integration

Analytics and tracking

Services
HubSpot Analytics, Google Analytics (via GTM), Microsoft Clarity
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
HubSpot Ads
Tracking pixels
Facebook Pixel, LinkedIn Insight Tag, Microsoft Clarity
Marketing tools
HubSpot
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with rich content and no blocking detected.
  2. Strong branding and consistent professional design.
  3. Comprehensive developer resources and API documentation available.
  4. Use of modern web technologies and analytics tools.
  5. Privacy and cookie policies are present and GDPR compliant.
  6. No explicit security policy or incident response contact found.
  7. WHOIS data limited due to TLD and privacy protection but no suspicious indicators.
Technical notes

Notes

The website is built on a modern technology stack including React and Next.js, ensuring fast rendering and good SEO. Hosting assets on AWS S3 provides scalability and reliability. Integration with HubSpot and Google Tag Manager supports marketing and analytics needs. The site is mobile-optimized and accessible, with a clean and professional design. Performance is fast with efficient loading of resources. No technical debt or outdated technologies were detected. Opportunities exist to further improve accessibility features and formalize security-related technical documentation. Overall, the technical implementation is robust and supports the business objectives effectively.
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

Earlier scans of this domain

  1. 73/100Medium29 findingsView report
Reviews of this site

Share your experience with api.video. 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 api.video.

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.