Skip to main content

Security report for nanoapi.ai

Tekronix Inc · Technology

Low risk. No critical or high findings.

Security score

87/100

Risk levelLow

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

NanoAPI, operated by Tekronix Inc, offers a unified API platform for generative AI video and image models, enabling developers and businesses to access multiple AI models through a single API key and prepaid balance. The platform supports a variety of creative AI models including Genjutsu, Kling, Seedance, Veo, Wan for video, and Nano Banana, GPT Image, Seedream for images. The business model is pay-as-you-go, targeting developers and enterprises seeking scalable AI content generation solutions. The website demonstrates a high level of technical maturity, utilizing modern web frameworks such as Next.js and integrating analytics tools like Microsoft Clarity and Plausible Analytics. The site is well-optimized for performance, mobile responsiveness, and accessibility, with clear navigation and professional design.

Scanned

NIS2 and GDPR posture

NIS2 outside view
70/ 100 · Medium
GDPR outside view
90/ 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. GDPR outside view

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

    • Medium

      Trackers contacted without a consent banner

      Observed on the first page load as a new visitor, before any consent choice; Guard does not click the banner. The page contacted Microsoft Clarity (www.clarity.ms). No tracking cookies were seen, but no consent banner or consent platform was detected either.

      What to do: Confirm these services do not store or read anything on the visitor's device; otherwise load them only after consent.

  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.

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

This scan found 14 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
89
Security headers
53
Email security
89
DNS health
95
Network security
100
Website hygiene
95
GDPR outside view
90
Average
87

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention nanoapi.ai, from OffSeq Breach.

No leaked records found

Breach holds no records for nanoapi.ai right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

NanoAPI positions itself as a specialized provider in the generative AI space, focusing on video and image content creation APIs. Its competitive advantage lies in offering a single API endpoint for multiple AI models, simplifying integration and billing for customers. The pay-per-second or per-image pricing model aligns with usage-based billing trends in cloud services. The company appears to maintain partnerships or integrations with major AI technology providers such as OpenAI, Google, Alibaba, and ByteDance, enhancing its service offerings. The absence of explicit contact or privacy policies suggests areas for improvement in customer trust and regulatory compliance. The platform's ecosystem includes a developer console, API documentation, and live demos, indicating a developer-centric approach.

Security posture

The website enforces HTTPS and implements several security headers, reflecting good security hygiene. The mention of signed webhooks indicates attention to secure API interactions. No vulnerabilities or exposed sensitive data were detected in the HTML content. However, the lack of published security policies, incident response contacts, and vulnerability disclosure mechanisms represents a compliance gap. The site uses third-party analytics which may impact privacy compliance if not properly managed. Overall, the security posture is strong technically but could benefit from enhanced transparency and formalized security governance documentation.

Recommendations

  1. Publish comprehensive privacy and cookie policies to improve GDPR and privacy compliance.
  2. Add terms of service and security policy pages to enhance legal clarity and user trust.
  3. Implement and publicize a vulnerability disclosure program or security.txt file.
  4. Provide clear contact information for security incidents and general inquiries.
  5. Regularly review third-party scripts and analytics for privacy impact and compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Tekronix Inc
Description
One API key, one prepaid balance and one async task API for generative AI: Genjutsu, Kling 4.0, Seedance 2.5, Veo 3.1 and Wan 3.0 video, plus Nano Banana 2.1, GPT Image 2.5, GPT Image 2.6 and Seedream 5.0 Pro images.
Key services
Generative AI video models, Generative AI image models, Async task API, Developer console and API key management
Content quality
excellent
Branding
consistent

Technology

Stack
React (Next.js), JavaScript, CSS, Radix UI, Lucide Icons, Clarity Analytics
Frameworks
Next.js
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Signed webhooks mentioned
  • No exposed sensitive data in HTML
  • Use of async scripts
  • No inline scripts with eval

Analytics and tracking

Services
Microsoft Clarity, Plausible Analytics
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Microsoft Clarity, Plausible Analytics
Marketing tools
Plausible Analytics, Microsoft Clarity
Transparency
basic

Site quality

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

Key observations

  1. Website provides a unified API platform for generative AI video and image models.
  2. Content is rich with detailed model descriptions, pricing, and API usage instructions.
  3. No explicit privacy, cookie, or terms of service pages found in the HTML content.
  4. No direct contact emails, phone numbers, or physical addresses found on the main page.
  5. Uses modern web technologies and good security practices.
  6. Includes analytics scripts from Microsoft Clarity and Plausible.
  7. No signs of adult or questionable content.
  8. WHOIS data consistent with business identity.
Technical notes

Notes

NanoAPI's website is built on a modern React-based framework (Next.js) with optimized loading strategies including async scripts and preloading assets. The use of Radix UI components and Lucide icons contributes to a polished user interface. Performance is optimized with responsive design and accessibility considerations. The site integrates multiple external domains for analytics and content delivery but does not rely on a CMS. Hosting details are not explicit but the site appears stable and fast. Technical risks are minimal, though ongoing monitoring of third-party dependencies is advised to mitigate supply chain risks.
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 nanoapi.ai. 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 nanoapi.ai.

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.