Skip to main content

Security report for shipany.ai

ShipAny · Technology · N/a

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

Security score

65/100

Risk levelMedium

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

ShipAny is a technology company providing a Next.js based boilerplate platform designed to accelerate the launch of AI SaaS startups. The company targets developers and founders seeking fast deployment with ready-made templates, integrated authentication, payment processing, and AI infrastructure. Their market position is that of a niche provider enabling rapid startup development with a one-time payment business model and tiered pricing plans. Technically, ShipAny leverages modern web technologies including Next.js, React, TailwindCSS, and integrates with platforms like Supabase, Stripe, and Vercel. The website demonstrates good digital maturity with SEO optimization, mobile responsiveness, and performance. Security posture is adequate with a valid SSL certificate and no known vulnerabilities, but lacks advanced protections such as HSTS, DNSSEC, and explicit security policies. Overall, the platform offers a professional and trustworthy experience with clear business focus and technical robustness.

Scanned

This is an earlier scan of shipany.ai. View the latest report

NIS2 and GDPR posture

GDPR outside view
43/ 100 · High
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. 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 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

    • 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

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

Keep watching shipany.ai

This scan found 20 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
60
Security headers
15
Email security
85
DNS health
85
Network security
100
GDPR outside view
43
Average
65

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

ShipAny operates in the AI SaaS technology sector, providing essential infrastructure and templates for startup founders and developers. Their competitive advantage lies in the speed of deployment and comprehensive integration of authentication, payments, and AI features. Revenue streams are primarily from one-time payments for different tiers of boilerplate packages. The target customer segment includes early-stage AI SaaS startups and developers seeking to reduce time-to-market. The company maintains an ecosystem of partnerships with Stripe, Supabase, Vercel, and Cloudflare, enhancing their service offering. Growth indicators include over 250 customers and 30+ components available. The presence of a Discord community and social media channels supports customer engagement and technical guidance.

Security posture

ShipAny exhibits a moderate security maturity level with foundational protections such as a valid SSL certificate and absence of known SSL vulnerabilities. However, the lack of HSTS, DNSSEC, CAA records, and a formal security policy or incident response page indicates gaps in advanced security controls and compliance readiness. No GDPR-specific compliance statements or cookie consent mechanisms were detected, which may pose regulatory risks. The absence of a vulnerability disclosure program or security.txt file reduces transparency for security researchers. Incident response readiness and data protection officer contact information are not publicly available, suggesting limited formal security governance. Overall, while basic security hygiene is observed, enhancements are recommended to strengthen trust and compliance.

Recommendations

  1. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload to enforce HTTPS and prevent downgrade attacks.
  2. Implement DNSSEC to protect DNS integrity and prevent spoofing.
  3. Add Certification Authority Authorization (CAA) DNS records to restrict certificate issuance to authorized CAs.
  4. Publish a comprehensive security policy and incident response plan on the website to improve transparency and preparedness.
  5. Introduce a cookie consent mechanism to comply with GDPR and other privacy regulations.
Technical notes

Notes

The website is built on a modern and scalable technology stack centered on Next.js and React, styled with TailwindCSS and Shadcn/UI components. Hosting is provided via Cloudflare with deployment options for Vercel and Cloudflare platforms. Integration with Supabase provides reliable data storage, while Stripe and Google OAuth handle payments and authentication respectively. The site demonstrates fast performance and good mobile optimization, though accessibility is basic. SEO is well addressed with meta tags and canonical links. The technical debt appears low with use of current frameworks and libraries. Opportunities exist to enhance security configurations and implement advanced compliance features to reduce technical risks impacting business continuity.
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. 64/100Medium33 findingsView report
Reviews of this site

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