Creator plans in preparation · Scanning and payments are not open

Built a tool with AI?
Understand risks before launch

A subtitle tool, a member site, your first small service.
Understand security risks in plain language, get fix tasks for your coding AI and check again after changes.

Free checks need no sign-in, DNS setup or server credentials. Only submit websites you own or are authorized to check. No connection or scan occurs while the service is unavailable.

No public address yet? View a sample report.

Start with your own tool · Plain-language Chinese reports · Clear tested and untested coverage

Check, fix and verify again

This is the planned workflow. Confirm permission for a free check; website control verification is required only for deep checks.

01

Provide your own URL

Confirm permission for the free check, without DNS setup or a verification file. Deep checks require separate website control verification.

02

Understand risks and evidence

See what data or costs could be affected, what we observed and what remains unconfirmed.

03

Ask your coding AI to fix it

Copy a task with fix goals and acceptance checks, then review the changes. Aegis does not deploy them for you.

04

Retest the same scope

Compare before-and-after evidence. Failed checks or changed scope are marked unconfirmed.

Focus on practical risks in small tools

Planned checks depend on the supported platform and the information you authorize.

Public website settings

Observable HTTPS, response settings and public exposure. This is not a full penetration test.

Secrets and keys

Identify suspected secrets and mask evidence. Public-use keys are not automatically classified as leaks.

Code and dependencies

The planned deep check reviews limited snapshots and dependencies without running your code or arbitrary commands.

Data and storage settings

Review authorized settings. Without backend evidence, we do not claim private data or login permissions have passed.

Results are planned to use LabSpace Intelligence. Self-service results are not a human audit; human review is quoted separately.

Start free. Go deeper when needed.

Initial plan proposal · Not available for purchase · No subscription required

Free initial check

Understand risks observable from the URL

NT$0

  • One authorized URL
  • One URL check every 30 days
  • Plain-language Chinese results and evidence
  • Clear lists of untested and unconfirmed items
Ask about the pilot

Main plan · In preparation, not yet for sale

Pre-launch check

For small tools preparing to go public

NT$499per check

  • 1 website (verified as yours via DNS first)
  • One deep check with plain-language results
  • Fix tasks for your coding AI
  • Two same-scope retests within 14 days after completion
  • Self-service; human review costs extra
  • Login-permission and code checks: coming later
Ask about the check plan

Human review

When you need an engineer's judgment

Quoted by scope

  • Confirm the issue and required evidence first
  • Explicit review scope and deliverables
  • Support time and cost agreed in advance
  • Not included in the NT$499 plan
Ask about options

Charges start only after deep-check and retest acceptance. Supported platforms, project limits and data handling are confirmed before purchase. Results are not a security guarantee.

Know the problem and how to fix it

Plain-language impact

Explain who could access what data or misuse which services, with traceable evidence.

Actionable fix tasks

Package fix goals and acceptance checks for your coding AI.

Clear check boundaries

Distinguish observations, inferences and untested areas. A single score cannot hide the unknown.

What should you check before launching an AI-built website?

A working website does not prove that its data and permissions are protected. Separate public settings, account access and transaction flows to understand what remains untested.

Seven observations in a free URL check

  • HTTPS connection
  • Content Security Policy (CSP)
  • Protection against framing
  • X-Content-Type-Options (nosniff)
  • Cookie Secure attribute
  • Cookie HttpOnly attribute
  • Cookie SameSite attribute

These observations cover one limited response from the public homepage. The check does not read the page body, sign in or modify data. No findings do not prove safety; if no cookie is returned, login-cookie protection cannot be determined.

What does a deeper assessment need?

Member websites: two test accounts

Checking whether one member can read another member's data requires authorization, a dedicated test environment and synthetic accounts. Homepage headers cannot answer this question; this deeper assessment is still planned.

Subtitle and upload tools: storage settings

Determining whether private videos are exposed or paid API secrets are leaked requires authorized settings or a limited source snapshot. The current free check does not inspect these inputs or verify file-access permissions.

Paid tools: isolated transaction flows

Order isolation, server-side pricing and duplicate-charge behavior need an isolated environment and test data. They are outside the seven URL observations and are not yet available for self-service assessment.

How can you turn a finding into a task for your coding AI?

Illustrative example, not a measured report for any website

Suppose a homepage response lacks nosniff: first verify correct Content-Type values for HTML, CSS, JavaScript and uploaded files, then configure X-Content-Type-Options: nosniff. Do not disable existing protections just to pass a check.

For verification, confirm that the original URL returns the header and that the page and its resources still load correctly. This verifies the setting only, not fixes for XSS, authentication or authorization.

Frequently asked questions

Who is Aegis for?

Aegis is designed for individuals building websites and small tools, with or without AI, to understand security risks, actionable fixes and retest results before launch.

Can I scan my website or pay now?

Initial checks and report saving have been verified on controlled UAT test sites. General public website scanning and live payments are not yet available; entering a URL does not mean a scan has started.

Is this antivirus or a full penetration test?

Aegis is designed to check websites and tools you build, rather than protect your computer from malware. The current controlled HTTP engine checks response headers and cookie settings only. It is not a full penetration test or a guarantee of website security.

What are the planned price and retest terms?

The planned offering is a free initial check and a NT$499 one-time deep check with two same-scope retests within 14 days. Human assistance is quoted separately. These are planned terms; purchasing is not open and full coverage is not yet available.

What does a report provide?

Current controlled-case reports include findings, original evidence, plain-language impact and fix tasks for your development AI, with tested, skipped and failed coverage. Explanations support Traditional Chinese and English while evidence stays in its original form. Reports are not human-reviewed.

Can I check someone else’s website?

The planned free check covers HTTPS, security headers and cookie settings on the public homepage. Confirm that you have permission; no verification file or DNS setup is required. Deep checks still require website control verification. Public scanning is not available yet. Do not submit third-party websites, passwords, keys or personal data lists.

Do I need to upload credentials or configure DNS for the free check?

No. Once available, paste your website URL, confirm permission and complete the CAPTCHA to run a check without registering. Reports remain in the original browser for up to 24 hours. Sign in only to save a report or use deep checks. Deep checks also require website control verification. Public checks are not available yet.

Do I need Aegis if I already asked AI to review my code?

AI code review can suggest fixes, but deployed responses and behavior still need verification. Aegis aims to connect reproducible observations, repair tasks and rechecks. The current free check covers only seven external observations and does not replace code review or deeper authorization tests.

Is my website safe to launch if all seven checks pass?

These seven checks cannot determine launch readiness on their own. Authentication, member-data isolation, source code, databases, dependencies and other pages are outside the free check. No findings do not mean that these areas passed.

Can I use it without knowing how to configure DNS?

The free check is designed to require a URL, authorization confirmation and a CAPTCHA, without registration or DNS setup. Sign in only to save the report. Deeper assessments separately confirm site control, test accounts and supported scope. General public access is not yet open.

Built a tool with AI too?

Interested in the pilot or need help? Leave a message. We will send an acknowledgment and our team will respond.

10–4,000 characters. Do not include passwords, API keys, private files or lists of personal data.

Case-insensitive; valid for 5 minutes. Refresh the image if needed, or contact us by email.

You can also email[email protected]