Terms of use
Version 0.1.0, November 18, 2026.
Terms of use
1. Purpose and acceptance
1.1. These terms govern the use of the attackscout.com website and the AttackScout service, published by Simon Raynaud, sole trader (autónomo), trading under the trade name Elerine, C/ Almazara n° 232, 30153 Corvera (Murcia), Spain, NIF (NIE) Y7168667H ("AttackScout", "we"). They apply to anyone who runs an audit, with or without an account ("you", "the user").
1.2. Audit without an account: by running an audit, you accept these terms. The sentence "By running the audit, you accept our terms of use", with a link, appears below the input field.
1.3. Account: when you sign up, you accept these terms by ticking a box that is not pre-ticked. We keep the accepted version, the date and time, and your truncated IP address as proof of acceptance (Law 34/2002, LSSI-CE, Art. 24; Law 7/1998 on general contract terms, Art. 5.1).
1.4. The paid service is also governed by the terms of sale and the data processing agreement (DPA). In the event of a conflict on a paid matter, the terms of sale prevail.
1.5. These terms are available at all times and can be downloaded and stored (LSSI-CE, Art. 27.4).
2. What AttackScout is, and what it is not
2.1. AttackScout reads what a domain shows to the internet, compares it with published rules and produces a dated check, an A-to-F grade based on a public method ("Our rules" page) and fix guides.
2.2. AttackScout is not: a regulatory audit, a penetration test, a certification, proof of compliance (for example with NIS2, ISO/IEC 27001 or Article 32 GDPR), or a guarantee that a website will never be hacked. A finding may be incomplete or wrong. The absence of findings does not prove the absence of risk.
2.3. Findings are valid at the date and time shown. They may change the next day.
2.4. The plain-language text of the monthly report is written automatically by an artificial intelligence model, using only the audit results, then checked automatically (every date and figure must exist in the results). The introduction of the weekly roundup of published vulnerabilities (CVEs) may also be written by an artificial intelligence model, then checked in the same way. These texts say so and may be wrong.
2.5. Definitions. In these terms, the terms of sale and the privacy policy:
- Public audit (level A): the reads in section 3.2, possible for any domain, without proof.
- Proof of ownership: a DNS record of type TXT provided by AttackScout (
_attackscout.<domain>, with the valueattackscout-verification=<token>), published by the customer on their domain (section 4). - In-depth check (level B): the checks reserved for domains whose ownership is proven (section 3.3).
3. What our probe does
3.1. Identification. Every request carries the User-Agent AttackScout-Probe/<version> (+https://attackscout.com/sonde). Pace: at most one request per second, per host name.
3.2. Level A — public audit, for any domain, without proof. The probe only reads what is public by nature:
- public DNS records (SPF, DKIM on common selectors, DMARC, MX, CAA, DNSSEC, NS, etc.);
- the TLS certificate and configuration, through handshakes;
- the home page only, through ordinary HTTP requests (headers, redirects, cookies, resources visible in the page);
- the public email policy
mta-sts, and therobots.txtandsecurity.txtfiles, which are designed to be read by robots (RFC 9309 and RFC 9116); - the BIMI logo declared by the holder in its DNS (at most 4 KiB read);
- third-party public sources, without contacting the website: Certificate Transparency logs, RDAP (domain expiry date), Google Web Risk.
At level A, the probe does not search for anything: no sensitive files, no brute-forced subdomains, no enumeration. Subdomains found in public logs are listed, not visited.
3.3. Level B — in-depth check, only after proof of ownership (section 4). In addition to level A, and only on host names of the verified domain:
- crawling of up to 50 pages per host name, from
sitemap.xmland internal links, respectingrobots.txt; - checking whether a few well-known sensitive files are present (for example
/.env): the probe reads at most the first bytes needed to recognize them (Rangeheader), keeps only "present / absent" and the address, never the content; - looking for secret keys in publicly served JavaScript: we keep the key type, the address and 4 characters, and never test a key;
- inventory of third-party scripts on payment pages reachable without a cart;
- looking for recently registered look-alike domains, through DNS and RDAP only;
- at most 70 requests per host name per audit.
The exact list of checks at each level is published on the "Our rules" page, and the probe's behavior on the "Our probe" page. We update these pages and this section before adding any new type of request.
3.4. Third-party platforms. A subdomain pointing to a third-party platform (online shop, CRM, help desk, website builder) only receives level A reads, even after proof of ownership: the domain holder controls the name, not the platform's system.
3.5. What the probe never does, at any level: port scans, requests to an IP address instead of a name, login attempts, form submissions, attack payloads, exploitation of a flaw, testing a key, password or token found, writing to your systems or anyone else's.
3.6. You are entitled to block our User-Agent or our addresses. The checks concerned will then show as "couldn't be checked".
3.7. Quotas. The public audit is limited per IP address and per domain, and protected by Cloudflare Turnstile. Beyond a quota, the audit is refused or the latest recent result is served.
4. Proof of ownership and authorization of the in-depth check
4.1. The proof. The in-depth check requires the proof of ownership: adding the record _attackscout.<domain>, of type TXT, with the value attackscout-verification=<token> to the domain's DNS. Only someone who manages the domain's DNS can add it: that is why it counts as authorization.
4.2. Your representations. By ticking the authorization box before verification, you represent and warrant that: a) you are the domain holder, or you are authorized in writing by its holder to have its security audited (for example, as an IT provider); b) you are entitled to have the website tested at its hosting provider and technical providers (CDN, shared hosting), within the limits of section 3; c) you have informed, where necessary, the people in your organization affected by the audit.
4.3. Mandate. If you act on behalf of a holder, you keep written proof of their authorization for the whole duration of the audit and 6 years afterward, and you send it to us on request. We are not a party to the contract between you and the holder.
4.4. Indemnity. You indemnify us against any claim by the actual domain holder, its hosting provider or a third party based on an inaccurate representation by you, including reasonable defense costs.
4.5. End of authorization. The authorization ends, and the in-depth check stops automatically:
- if the proof of ownership is no longer found at the daily re-check, then one hour later; in the event of repeated DNS failures, on the third day;
- if you withdraw the authorization from your account or by deleting the proof of ownership;
- if the domain is excluded at its holder's request (section 7);
- when the account is deleted.
4.6. Domain Connect. If you ask us to add the proof of ownership for you through Domain Connect, you give the authorization in section 4.2 before the write, which is then approved at your DNS provider. We write nothing else to your DNS.
4.7. Authorization log. To be able to prove, in the event of a complaint, that each in-depth check was authorized, we keep: the account identity, the domain, the value of the proof of ownership, the verification and end dates, the accepted version of these terms, the truncated IP address and the log of the in-depth check's requests (date, host name, path, response code, no content). This log is kept for 6 years after the authorization ends, even after the account is deleted, with restricted access and no other use (Regulation (EU) 2016/679, GDPR, Art. 17.3.e; Organic Law 3/2018, LOPDGDD, Art. 32).
5. What is prohibited
It is prohibited: a) to request an in-depth check of a domain over which you have no rights, or to bypass the proof of ownership; b) to use AttackScout to attack a system, prepare an attack, put pressure on a person, threaten them, demand money from them or disparage them; c) to publish or disclose results concerning a domain that is not yours, except to its holder; d) to present a result as an audit, a certification, proof of compliance or a security guarantee; e) to automate mass audits, scrape the website with robots or bypass quotas, Turnstile or the exclusion list; f) to resell the service or its results without our written consent (the partner program has its own terms); g) to use the service from a country subject to EU restrictive measures, or for a person targeted by them. The paid service is not offered to customers established in Russia, Belarus, Iran, North Korea, Syria and Cuba; h) to disrupt the service or test its security outside the responsible disclosure policy.
In the event of a breach, we may suspend the audit, the domain or the account (section 10).
6. Results
6.1. Audit without an account. The result is shown on a private page with an unguessable address, not indexed by search engines. Anyone with the link can see it. It is kept for 30 days, then deleted.
6.2. Details hidden without proof. Without proof of ownership, the finding and its risk are visible, but not the exploitable details (exact vulnerable version, exact path). The proof of ownership is free.
6.3. No publication. We never publish a domain's grade or result, or any ranking of domains. Only the holder of a verified domain may choose to display a badge, share a certificate or share its grade with a third party of its choice (section 9).
6.4. Statistics. We may publish aggregated, anonymous statistics (for example "43% of audited domains have no DMARC"), computed on at least 30 domains, without ever naming a domain.
7. Excluding a domain
7.1. A domain holder may ask, without giving reasons, that their domain no longer be audited. They confirm the request through a link sent to an address of the domain (postmaster@, webmaster@, admin@ or security@) or through a DNS record of type TXT, _attackscout-exclude.<domain>.
7.2. The exclusion applies to all audits: public, scheduled and prospecting. It overrides the proof of ownership: if an account has proven ownership of the domain, the in-depth check stops and the account is notified. The consequences for a paid domain are governed by the terms of sale.
7.3. We keep only the domain, the date and the confirmation method. The requester's email address is erased after confirmation.
8. Disputing a result
8.1. Does a result look wrong to you? Write to [email protected] or use the "Dispute this result" link, with the domain and the item concerned.
8.2. We reply within 7 days. During review, the item may be marked "disputed". If we were wrong, we correct the result and, if needed, the grading rule.
9. Badge, certificate and grade sharing
9.1. The holder of a verified, paid domain may display a badge or hand over a dated certificate, verifiable on a /verifier/<code> page. They only state: the date of the check, the grade, the scope ("settings visible from the internet") and a link to the method. The certificate is also attached to the monthly report: it covers 30 days and has the same limits (observed facts, no security guarantee).
9.2. It is prohibited to alter them, display them for another domain, after their withdrawal or with wording that suggests a certification, compliance or a security guarantee.
9.3. The badge and certificate are provided for your own use. AttackScout makes no commitment to third parties you show them to (insurer, customer, client). They are not an audit, a penetration test, a certification or proof of compliance.
9.4. The badge is served without cookies, and the IP address of your website's visitors is not recorded. We may withdraw a badge at any time, in particular if the grade changes or the authorization ends.
9.5. Sharing the grade. The holder of a verified, monitored domain may share its grade with a third party of its choice (for example a broker or an insurer), by means of a personal token that is dated (365 days at most) and revocable at any time. The third party only receives the grade, the date and level of the latest audit, the number of failing checks, the date of the proof of ownership and the link to the latest certificate; never the details of the findings. The share stops returning a score as soon as the proof of ownership or the monitoring ends. The holder is responsible for handing the token over to its recipient. The grade describes the state observed from the internet on a given date: it is neither a security guarantee nor a commitment to the insurer.
9.6. Technical evidence report. The holder of a monitored, verified domain may generate a technical evidence report: the dated list of the checks of the latest audit and their results, electronically signed by AttackScout (Ed25519) (simple electronic seal, not qualified within the meaning of the eIDAS Regulation). It records facts observed automatically from the internet. It is not an audit, a penetration test, a certification or proof of compliance, and AttackScout makes no commitment to the third parties to whom it is passed on. The holder chooses how long the verification link lasts (30, 90 or 365 days) and what the public page shows; the document's signature remains verifiable after the link expires.
9.7. Report recipients. The customer warrants that it has the right to add each recipient and to pass on to them the security findings for its domains. AttackScout only sends after the recipient has confirmed and lets them unsubscribe at any time. The report describes what was checked from the internet and when; it is neither a security guarantee nor a security certification. The shareable link to a report is personal, valid for 30 days, and disabled as soon as the recipient unsubscribes or is removed.
10. Account, security and suspension
10.1. You provide accurate information, keep access to your login email address under your control and notify us of any unauthorized use.
10.2. You may invite your provider or other people in your organization. You remain responsible for their actions in your account.
10.3. Alerts sent to Slack, Microsoft Teams or Discord are passed on to the service you choose, under its own terms. You are responsible for them.
10.4. We may suspend an audit, a domain or an account without notice in the event of a breach of these terms, a plausible complaint from a third party, a request from a hosting provider or an authority, or a risk to the security of the service. We inform you, unless the law or an authority prohibits it. The financial consequences are governed by the terms of sale.
11. Availability and liability for the free service
11.1. The free service is provided "as is", with no availability commitment.
11.2. Fix guides are an aid. You remain responsible for the changes you make at your hosting provider. Some changes may block legitimate services (for example an overly strict DMARC policy): each guide says so.
11.3. To the extent permitted by applicable law, AttackScout is not liable for indirect damages related to free use of the service. This limit does not apply in the event of fraud or gross negligence, or to damages that a law prohibits excluding.
12. Intellectual property
The service, the published method, the texts and the code remain our property. You may use the results for your own domains as you wish, subject to section 9. Your domains' data belong to you. You authorize us to use them in aggregated, anonymous form to improve the service and publish statistics (section 6.4). We do not sell any data.
13. Personal data
Processing is described in the privacy policy. For the in-depth check of a customer's domains, we act as a processor under the DPA.
14. Changes to these terms
We may change these terms. For accounts, we give notice by email at least 30 days before a significant change takes effect. If you refuse it, you may delete your account before that date. The version in force at the time of each proof of ownership is the one kept in the log.
15. Governing law and jurisdiction
These terms are governed by Spanish law. For disputes with professionals, see the "Governing law and jurisdiction" section of the terms of sale. Nothing in these terms deprives a user who is a consumer of the mandatory protections granted by the law of their habitual residence. For disputes relating to a subscription, see Articles 20 (business customers) and 24 (consumers) of the terms of sale.
16. Languages
These terms exist in French, English, Spanish, German, Italian and Portuguese. French is the language in which they were drafted: in the event of a discrepancy, the French version prevails. This clause does not deprive a consumer user of the protection afforded by the mandatory provisions of the law of their country of habitual residence (Regulation (EC) No 593/2008, Rome I, Art. 6).
17. Contact
[email protected] · Simon Raynaud (Elerine), C/ Almazara n° 232, 30153 Corvera (Murcia), Spain.