Sample monthly report

Every month, a clear report on your security

What was checked, what was fixed, what is coming next. This is the report a customer receives every month, here for a fictional company. Keep it, or pass it on to your IT provider.

A4 PDF, same content as this page.

AttackScout

Monthly security report — October 2026

Issued on 1 November 2026

Fictional example: the company, the domains (reserved for examples, .example) and the findings are made up.

Atelier Durand

Monitored sites: atelier-durand.example, boutique.atelier-durand.example

What monitoring brought you this month

Checks run
1,240
Issues spotted as soon as they appeared
1
Deadlines avoided
1
Issues fixed since monitoring began
7
Grade change
C → B
Estimated time saved
about 10 h

Estimate, not measured: 10 minutes to redo by hand the audit of one domain, 62 audits this month.

Your grade

B

Last six months

  1. May 2026D
  2. Jun 2026D
  3. Jul 2026C
  4. Aug 2026C
  5. Sep 2026C
  6. Oct 2026B

At a glance

Your grade is B, up from last month (C).

2 issues fixed this month. 4 issues left to address, including 1 urgent one.

Next deadline: End of PHP 8.2 security fixes, on 31 December 2026.

What we monitored

31 days of monitoring, 6 check families, 1,240 checks, all run from the internet.

What is left to fix

Broken now — A real risk, starting today.

  • PHP 8.1 no longer gets updatesatelier-durand.exampleatelier-durand.example runs PHP 8.1, which has had no security fixes since 31 December 2025. A flaw found tomorrow will never be fixed.

Fix this month — Not urgent, but don't let it slide.

  • DMARC is only monitoringatelier-durand.exampleThe DMARC policy of atelier-durand.example is "none": email imitating your address is reported, not blocked.
    Technical details
    Rule applied
    A2 : DMARC is watching but not yet protecting
    With "p=none", emails spoofing your address are only reported, not blocked.
    Reference
    To check it yourself
    dig +short TXT _dmarc.atelier-durand.example

    Command to run in a terminal. It only reads public information.

To plan — Useful improvements, no immediate risk.

  • Browsers are not told to stay on HTTPSboutique.atelier-durand.exampleboutique.atelier-durand.example does not send the HSTS header: on public Wi-Fi, a visitor can be diverted to an unencrypted version of the site.
    Technical details
    Rule applied
    A13 : HTTPS is not enforced in browsers
    Without the HSTS header, a client's first visit over public Wi-Fi can be hijacked. One line to add.
    Reference
    To check it yourself
    curl -sI https://boutique.atelier-durand.example/ | grep -i strict-transport-security

    Command to run in a terminal. It only reads public information.

  • No contact to report a flawatelier-durand.exampleatelier-durand.example does not publish a security.txt file: someone who finds a flaw does not know whom to tell.
    Technical details
    Rule applied
    B9 : No security.txt file
    The /.well-known/security.txt file tells researchers how to report a vulnerability to you. Two lines are enough: Contact and Expires (RFC 9116).
    Reference

Fixed this month

  • Certificate renewed before it expiredboutique.atelier-durand.example7 October 2026Before: Was expiring on 9 October 2026After: Valid until 5 January 2027
  • SPF record fixedatelier-durand.example21 October 2026Before: 12 DNS lookups, over the limit of 10: SPF ignoredAfter: 7 DNS lookups: SPF valid

Upcoming deadlines

  • — End of PHP 8.2 security fixesAfter this date, PHP 8.2 gets no more security fixes. Ask your host for version 8.4 before then.
  • — Certificate of boutique.atelier-durand.example expiresRenewal is automatic: we will check that it happened and warn you 30 days ahead if it did not.
  • — Domain name atelier-durand.example renewalAuto-renewal is on at the registrar. Check that the card on file is still valid.
  • — Certificates capped at 100 daysNew certificates will last 100 days at most. Renewing by hand will no longer be workable: it must be automatic.

Calendar for the next six months

November 2026
Nothing planned
December 2026
31: End of PHP 8.2 security fixes
January 2027
5: Certificate of boutique.atelier-durand.example expires
February 2027
8: Domain name atelier-durand.example renewal
March 2027
15: Certificates capped at 100 days
April 2027
Nothing planned

Your email

Your email gets delivered, but it can still be spoofed

SPF and DKIM are in place and your messages get through. But DMARC is only monitoring: a scammer can still send email that looks like it comes from you.

What we recommend

  • Move atelier-durand.example to PHP 8.4Who: Your IT provider · By: 30 November 2026
  • Switch the DMARC policy of atelier-durand.example to "quarantine"Who: You · By: 30 November 2026
  • Move boutique.atelier-durand.example to PHP 8.4Who: Your IT provider · By: 15 December 2026
  • Turn on HSTS for boutique.atelier-durand.exampleWho: Your IT provider · By: 31 December 2026
  • Publish a security.txt file on atelier-durand.exampleWho: You · By: 31 December 2026

Monitoring provided by AttackScout.

Checks run from the internet, without intrusion, by the AttackScout-Probe probe. The in-depth check only runs once you have proven the domain is yours.

Get yours, every month

Daily monitoring of a domain includes this report, as a web page and a PDF, sent on the 1st of every month.

Partners in our program (hosting providers, service providers): the same report, under your name and with your logo (white label). The probe stays identifiable and the proof of ownership stays mandatory.

Check my website for free