The authorization requirement
No active scan runs against any target until that target is verified as owned or authorized.
This is the foundational rule that makes Scantinel a security tool rather than an attack platform. It is not a checkbox in our terms of service — it is a technical gate enforced by our systems at every scan phase.
| Verification method | How it works |
|---|---|
DNS TXT record | Add scantinel-verify=<token> as a TXT record on your apex domain |
HTTP verification file | Place a file at /.well-known/scantinel-verify/<token> on your web server |
HTML meta tag | Add <meta name="scantinel-verify" content="<token>"> to your homepage |
Email challenge | Scantinel sends the token to admin@, security@, or webmaster@ at your domain; you click to confirm |
What we never do — at any tier
- Denial of service or load testing. Never performed. Our scan rates are deliberately conservative and bounded.
- Destructive actions. We never delete, modify, or corrupt data. We never place backdoors.
- Real data exfiltration. If a vulnerability proof-of-concept exposes real user data, our evidence stops at demonstrating access. No real PII is retained.
- Credential misuse. Our credential-resilience tests stop at the first valid credential. We never use a found credential to log in or pivot.
- Scanning unauthorized targets. Our systems will not run active probes against any unverified asset. There is no override.
Scan rate limits and operational safety
We set conservative, bounded rate limits on all scanning activity. A typical active web scan generates traffic comparable to a busy-but-normal day’s worth of visitor requests — not a flood. Port scanning uses low-rate, bounded packet-rate scanning. Credential testing uses small, curated wordlists at low rates.
If you need to pause a scan in progress, you can revoke authorization for a target at any time from your dashboard — this immediately halts any in-progress active scan of that target.
Recognising Scantinel traffic
Active scans only ever reach targets whose ownership you have verified, and they start when you start them, so the timing in your logs matches a scan in your dashboard. A published list of the fixed IP addresses our scanners send from is in preparation; it will appear on this page so your WAF or IDS can allowlist it. Until then, if you need the source addresses before a scan, ask us through the contact form.
Data handling and security
All communication uses TLS 1.2 or higher. Scan reports and evidence artifacts are encrypted at rest (AES-256). Scan findings and reports are retained for 12 months after the last scan in which they were observed, then permanently deleted. You can request early deletion by contacting support.
We do not share your scan results with third parties. Infrastructure services process data as sub-processors under appropriate agreements. See our Privacy Policy for complete details.
Responsible disclosure
If you discover a security vulnerability in Scantinel’s own platform, please report it responsibly. Send it through our contact form with a description, reproduction steps, and proof-of-concept. We acknowledge within 24 hours and provide initial triage within 72 hours.
Read our full Responsible Disclosure Policy for complete terms.
Abuse reporting
If you believe your website was scanned by Scantinel without your authorization, report it through our contact form immediately. Every Scantinel scan has a complete authorization record. We investigate all abuse reports and respond within one business day.
Compliance posture
Scantinel reports are structured to support evidence gathering for OWASP Top 10 (2025), PCI DSS requirements 6 and 11, ISO 27001 / SOC 2, and GDPR. We do not claim certification to any of these frameworks — we help you gather evidence and remediate issues they require you to address.