Scanning policy
This service performs an external security assessment of a website when somebody enters its address. This page describes exactly what that involves, so anyone who sees our scanner in their logs can understand what happened and what to do about it.
How to recognise us
Every request we make carries a stable User-Agent that names this scanner and links back to this page. We do not rotate identities, disguise our requests, or attempt to avoid appearing in your logs.
What an assessment does
- Requests the site's home page over HTTPS, and again over plain HTTP, to see whether visitors are upgraded to an encrypted connection.
- Requests /.well-known/security.txt, a file published specifically so security issues can be reported.
- Follows redirects only within the same site, and only a small fixed number of them.
- Reads a bounded amount of each response — enough to inspect the page's markup, never the whole of a large page.
- Inspects the TLS certificate and, separately, whether the server still accepts the obsolete TLS 1.0 and 1.1 protocols.
- Makes ordinary public DNS queries (address, mail, name server, CAA and TXT records).
- Makes one RDAP lookup for the domain's public registration record.
What an assessment never does
- No login attempts, password guessing or credential testing of any kind.
- No exploitation. We observe configuration; we never attempt to take advantage of what we find.
- No destructive or modifying requests. Every request is a read.
- No scanning of ports other than the standard web ports.
- No crawling. We request a small fixed set of paths, not your whole site.
- No attempt to reach private, internal or cloud-metadata addresses. A hostname that resolves to one is refused.
How much traffic this generates
A complete assessment is a handful of requests — materially less than one person visiting your home page. Repeat requests for the same site within a few minutes reuse the previous result instead of contacting you again, and the service runs a small fixed number of assessments at a time.
What the free assessment cannot tell you
This is an external, unauthenticated view. It reports what a visitor's browser could observe, and it says so honestly when it could not establish something — an undetermined result is reported as undetermined rather than guessed. It is not a penetration test and does not attempt to find vulnerabilities in your application.
What we keep
A completed assessment is held in memory for a few minutes so that repeat requests for the same site do not cause another scan. When durable persistence is configured and a persistence write succeeds, the assessment is also written to a database and survives a restart of the service; where it is not configured, that short-lived copy in memory is all there is. We also write bounded operational log entries, which include the hostname assessed. The next section describes what a durable record contains.
Data handling and privacy
The free assessment can be used without an account. The service also has account functionality for signed-in features; public sign-up may be closed while that functionality is being rolled out, so an account may not be available to you. What follows describes a durable record, which exists only where durable persistence is configured and a persistence write succeeds. Storing a report never gates an assessment: if persistence is unavailable, the assessment still runs and the report is still produced.
What a durable record can contain
- The hostname assessed, together with the website and mail domains the assessment resolved it to.
- When the assessment ran, how long it took, and the state it finished in.
- The score and grade, any scoring cap that applied, and the coverage and control counts behind them.
- One structured row per check: its identifier, category, status, severity, confidence, and a fingerprint that allows the same finding to be recognised again later.
- A bounded, reviewed set of evidence values per check — for example an observed security-header value, the negotiated TLS protocol, a certificate issuer and validity dates, or a domain's registrar and registration date.
- The frozen report artifact: the serialised report is stored as the exact bytes that were issued, with its byte size and a digest of those bytes, so that later sharing and downloading use that same verified report rather than rescanning your site or recalculating a score. A download is then rendered from that frozen report as a standalone file.
- Version identifiers for the scanner, methodology, scoring configuration and content used, so an old report can be read in the terms it was written under.
- Where an account exists, the account and security data needed to operate it: the account email address; whether and when that mailbox was verified; the account's state; the version identifiers of the terms and privacy notice accepted, where one is recorded; temporary sign-in lockout state; the password verifier material needed to check a password; and one-way hashes of session tokens and of one-time sign-up and password-reset challenge tokens. A pending sign-up challenge also holds the email address it was requested for. Messages that verify a mailbox or reset a password are sent through the configured email delivery provider, which necessarily receives the address.
What a durable record does not contain
- The content of your pages. We read a bounded amount of each response to inspect its markup, and that markup is not retained in a durable record.
- Cookie names or values. Three checks evaluate whether a session-like cookie sets Secure, HttpOnly and SameSite; those attributes are assessed, and the cookie itself is not recorded.
- Credentials for the sites we assess. We never send any and never record any.
- Registrant contact details from a registration record. Where contacts are relevant, we record only whether one is present and how many there are.
- Plaintext passwords. A password is checked against stored verifier material derived from it, and the password itself is not stored. Session and challenge tokens are likewise not intentionally stored in a recoverable form: only one-way hashes of them are kept.
- Payment card details. The service does not collect or store them.
How long a durable record lasts
An anonymous assessment is written under a 30-day retention policy. Creating a share link can extend the owning assessment's expiry, but never past an absolute ceiling of 90 days measured from the original assessment — no number of share links can move a record beyond that ceiling. Expired records are removed by a bounded, repeatable deletion process, so removal follows expiry rather than occurring at the exact instant of it.
Backups
Where durable persistence is configured, the database is backed up so it can be recovered after a failure. Backups are encrypted, held outside the server, and used only for recovery — they are never a route to a report in ordinary use. One consequence is worth stating plainly rather than leaving for you to assume: because a backup is a snapshot of the whole database, a record removed from the live database may still exist inside an earlier encrypted backup. Those backups follow a 14-day retention policy and are scheduled for removal once they pass it. We do not claim a hard maximum, because a cleanup run can fail: if it does, an older backup stays until a later cleanup succeeds. Backups are not edited record by record — they expire as whole snapshots.
Share links and revocation
A report can be shared through a link. That link is a bearer capability: anyone holding a valid, unexpired share link can read the report it points at, so it is worth treating as the secret it is. A share link and the management capability for an assessment are separate secrets, and neither is intentionally stored in a form we can read back — we keep a one-way hash of each. An assessment's identifier is not a credential and grants no access on its own. The holder of a management capability can create share links and revoke them. Revoking a link prevents it being resolved successfully afterwards; it cannot retract a report that has already been viewed or downloaded, or one already in flight.
If you have a report emailed
Email delivery ships disabled and is available only where an operator has explicitly enabled it with valid configuration. Where it is enabled and used, the recipient address is transmitted to the configured email delivery provider, which necessarily receives the address and may process or retain it under its own terms and service practices — something this service does not control. We do not intentionally store that address in plaintext: we keep a keyed one-way digest of it instead. That digest is what lets a limit on how many times one report may be emailed to the same address be enforced, by letting the same address be recognised again under the same key, without holding the address itself.
Views, downloads and operational logs
We do not intentionally record successful report views or downloads as viewer analytics. Separately from that, bounded operational log entries are written in the ordinary course of running the service, and these can include the hostname assessed.
If you do not want your site assessed
Domain owners can ask to be excluded, and we honour that without asking for a justification. While an exclusion is active, a request to assess that domain is refused before any outbound activity — no DNS query, no HTTP request, no TLS handshake and no registration lookup. Adding an exclusion does not by itself remove assessments already stored: existing durable records for a domain can be removed by an operator on request. Neither exclusion nor removal can retract a report that was already returned or is already in flight.
contact@scancompass.com