Public launch assurance
KayZTeC LaunchGuard
Read-only launch-readiness audits for public websites and domains.
Published by KayZTeC Technologies (Private) Limited, Zimbabwe.
Bounded public checks. One point-in-time view. No changes to the target.
Read-only by design
LaunchGuard analyzes public HTTP(S) and DNS information. It does not sign in to, modify, deploy to, or otherwise change the website being assessed.
Audit surface
What LaunchGuard checks
A focused view of the public signals most likely to affect a website launch.
- 01
Web transport
HTTPS, redirects, response status, and security headers.
- 02
Public DNS
DNS, MX, SPF, and DMARC records, plus DKIM when selectors are supplied.
- 03
Discovery
robots.txt, sitemap, canonical URL, and core metadata.
- 04
Measurement
Common analytics and cookie-consent configuration.
- 05
Priorities
A scored and prioritized launch-readiness report.
Service boundaries
A bounded, point-in-time audit
LaunchGuard is anonymous and MCP-only. It is not an authenticated scanner, monitoring service, report-storage service, or subscription service.
What to expect
- No LaunchGuard user account is required.
- Checks run at a point in time; they are not continuous monitoring.
- DKIM records can be checked only when selectors are supplied.
- No report history is intentionally stored in a LaunchGuard application database.
- Operational and security logging is described separately in the privacy policy.
Network safety controls
- Private, local, internal, credential-bearing, and unsafe destinations are rejected.
- Redirect destinations are independently validated.
- Time, redirect-count, and response-size limits may affect results.
- Do not submit passwords, API keys, access tokens, private URLs, or other credentials.
LaunchGuard must not be used to overload or disrupt a service.
LaunchGuard must not be used to perform bulk scanning or load testing.
LaunchGuard must not be used to bypass access controls or rate limits.
LaunchGuard must not be used to test private or internal systems.
LaunchGuard must not be used to submit credentials or confidential URLs.
LaunchGuard must not be used to harvest personal information.
LaunchGuard must not be used to exploit vulnerabilities.
LaunchGuard must not be used to violate applicable law or third-party terms.
Interpret carefully
Limitations
LaunchGuard is not:
- a penetration test
- a vulnerability assessment
- a security certification
- a legal or regulatory opinion
- a guarantee of compliance
- a guarantee that a launch will succeed or be vulnerability-free
Reports are informational and point-in-time. They can contain false positives, false negatives, or stale DNS information, and results may be affected by CDNs, geolocation, caching, and bot-management systems. Independently verify important findings.
Plain answers
Frequently asked questions
Does LaunchGuard modify a website?
No. It reads bounded public HTTP(S) and DNS information and does not sign in to or change the target.
Does it require an account?
No LaunchGuard user account is required.
Are reports stored?
There is no LaunchGuard report-history database. Operational and security logging is addressed separately in the privacy policy.
Can any domain be audited?
No. Use it only for a domain you own, administer, or are explicitly authorized to assess.
Is it a penetration test?
No. LaunchGuard is a bounded launch-readiness audit, not a penetration test or vulnerability assessment.
Why is a DKIM selector required?
DKIM selectors cannot normally be enumerated reliably from public DNS, so a selector must be supplied for that check.