How to fix common security issues
Practical, vendor-neutral remediation for the issues our engine flags — each mapped to the compliance frameworks it touches.
Set up SPF, DKIM and DMARC to stop email spoofing
Without SPF, DKIM and an enforcing DMARC policy, anyone can send email that appears to come from your domain.
Add the HTTP security headers every site should send
HSTS, Content-Security-Policy, X-Content-Type-Options and X-Frame-Options are cheap, high-impact defences that most sites omit.
Fix TLS: valid certificate and modern protocols only
Your certificate must be valid and current, and the server should negotiate only TLS 1.2+ — never SSLv3, TLS 1.0 or 1.1.
Remove exposed .git, .env and backup files
A reachable .git directory, .env file, or database backup hands attackers your source code, credentials and secrets.
Disable directory listing
When a directory has no index file, some servers list its contents — exposing files you never meant to publish.
Publish a security.txt (RFC 9116)
A security.txt file tells researchers how to report a vulnerability to you responsibly.
Set Secure, HttpOnly and SameSite on cookies
Session cookies must carry the Secure, HttpOnly and SameSite attributes to resist theft and cross-site attacks.
Close exposed ports and admin services
Databases, caches and admin panels (3306, 6379, 27017, SSH) should never be reachable from the public internet.
Patch known CVEs and disable risky HTTP methods
Running software with published CVEs, or leaving methods like TRACE enabled, gives attackers a ready-made exploit.
Stop leaking software versions in headers and errors
Server, X-Powered-By and framework debug banners tell attackers exactly what you run and which exploits to try.
Harden your DNS: CAA, and no dangling records
A CAA record limits who can issue certificates for your domain, and stale records invite subdomain takeover.
Know and shrink your subdomain attack surface
Every subdomain is another way in. Forgotten staging, admin and legacy hosts are a favourite attacker foothold.
Protect registrant data and renew on time
Exposed registrant details fuel targeted phishing, and a lapsed domain can be hijacked outright.
Harden your CMS (WordPress and friends)
Enumerable users, exposed admin paths and outdated plugins make a CMS the most-attacked part of most sites.
See where your domain stands
Prove ownership and run a scan to get a graded, verifiable report of exactly what to fix.