Website safeguards
The website enforces HTTPS, restrictive browser security policies, clickjacking protection, limited browser permissions, canonical-domain handling, and a read-only request surface.
Automated checks verify security headers, public routes, dependencies, and accidental credential exposure before release.
Responsible disclosure
If you believe you have found a security issue affecting this website, contact contact@aetherqlabs.com. Include the affected URL, a concise description, reproduction steps, and the potential impact.
Please avoid accessing data that does not belong to you, degrading service availability, using social engineering, or publicly disclosing an unresolved issue. We will acknowledge a credible report and coordinate an appropriate response.
Post-quantum posture
A compatible TLS 1.3 client has verified that the public website negotiates the hybrid X25519MLKEM768 key agreement. It combines a conventional elliptic-curve exchange with ML-KEM, the NIST-standardised post-quantum key-encapsulation mechanism, so that captured traffic is not protected by a classical exchange alone. Visitors without compatible browser support may use a conventional fallback.
AetherQ protects compatible website connections using hybrid X25519MLKEM768, combining established cryptography with NIST-standardised ML-KEM to reduce harvest-now, decrypt-later exposure.
Our website follows the same approach we bring to enterprise infrastructure: adopt post-quantum protection where it is production-ready, preserve interoperability during transition, continuously verify the cryptographic posture, and evolve authentication as browser and certificate standards mature. Public posture metadata is available at /.well-known/aetherq-crypto-posture.json.
Scope and assurance
This page describes safeguards for the public AetherQ website. It does not claim certification, validation, or a security guarantee for AetherQ products, customer environments, or third-party services.
Machine-readable disclosure information is available at /.well-known/security.txt.