What an attacker sees on a small business website, and what I missed on my own client's
I build a small tool that checks a website from the outside, the way an attacker would look at it: exposed files (.env, .git), outdated CMS and plugins matched against the ENISA (EUVD) and CISA KEV lists, TLS and headers
I build a small tool that checks a website from the outside, the way an attacker would look at it: exposed files (.env, .git), outdated CMS and plugins matched against the ENISA (EUVD) and CISA KEV lists, TLS and headers, SPF/DKIM/DMARC, cookies set before consent.
The first real run was on a client site I maintain myself. 60 out of 100, and a plugin with a known 9.9 vulnerability that I had missed for a long time. After updating and cleaning up: 86.
A few choices I made:
- It fingerprints the stack first and only runs what fits. WordPress is not Laravel.
- It only checks a domain after you upload a small proof file, and it identifies itself in your logs.
- It never exploits anything and never tries passwords.
- The report ends with a repair guide you can paste into Claude or ChatGPT.
The interface is Spanish (itvweb.es) or German (domainwaechter.de) so far. 3 analyses a month are free.
I'm looking for people who try it on their own site and tell me what is wrong or missing.
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.