Responsibility and disclaimer
Version 2026-10-27.1
fixasap only observes public responses to normal requests and never logs in, bypasses authentication or exploits vulnerabilities. You are solely responsible for the targets you look up and for how you use the results.
1. What fixasap does
fixasap sends one or two normal requests to the target, the same kind of request a web browser sends, and analyzes only the public response: headers, cookies, HTML, and the TLS certificate.
fixasap does not log in, does not bypass authentication, CAPTCHA, or anti-bot protection, does not exploit vulnerabilities, and does not send abnormal traffic.
2. No warranty
Results are provided as is and as available. They are signature-based estimates. False positives and misses are possible, and the confidence score is for reference only.
fixasap does not warrant that results are accurate, complete, or current, and to the maximum extent permitted by law is not liable for any loss arising from reliance on them.
3. Your responsibility
By submitting a target you confirm that you have the right to look it up: you own it, you are explicitly authorized by its owner, or you are checking publicly available information for a lawful purpose.
You must comply with all applicable laws, including Article 48 of the Act on Promotion of Information and Communications Network Utilization and Information Protection (Republic of Korea).
Any decision, action, or effect on a third party that results from your use of fixasap is solely your responsibility.
4. Prohibited use
Using fixasap for an unlawful purpose, to prepare an attack on a target you are not authorized to test, to circumvent rate limits or automate abuse, to resell results, or to interfere with the service.
Violations may lead to suspension, retention of records, and cooperation with law enforcement.
5. Records
Lookup records (targets, time, client address, TLS fingerprint, and consent version) are kept for operations and dispute handling for the period stated in the privacy policy.
6. Active scan
Active checks, when offered, are available only for targets whose ownership has been verified (DNS record, file, or meta tag). No active check is performed without verification.