worldngayon_ tools

Website security scanner

Check if a website is hardened or weak. Detects the CMS, checks SSL, security headers, cookies and exposed files, and shows the exact fixes.

Enter a website to check if it is hardened or weak. You get a grade, the CMS it runs on, and the exact fixes to apply.

What the scanner checks

Encryption (HTTPS, the HTTP-to-HTTPS redirect, SSL expiry, TLS version, mixed content), security headers (HSTS, Content-Security-Policy, clickjacking protection, X-Content-Type-Options, Referrer-Policy, Permissions-Policy), information leaks (server, PHP and CMS versions), cookie flags, and exposed files such as .git folders, .env files and phpinfo pages. On WordPress it also checks debug.log, xmlrpc.php, user listing through the REST API, readme.html and open upload folders.

CMS detection and hardening

It recognizes WordPress, Joomla, Drupal, Magento, PrestaShop, OpenCart, Shopify, Wix, Squarespace, Webflow, Ghost, Blogger, Next.js and Laravel, then gives a hardening checklist for that platform. For WordPress that includes updates, a firewall plugin, two-factor login, DISALLOW_FILE_EDIT, blocking PHP in uploads and off-site backups.

Why it matters for Filipino small businesses and creators

Most hacked small-business sites are not targeted. Bots scan the whole internet for the same few weaknesses: outdated plugins, exposed config files and missing headers. Fixing the items in your report closes the doors those bots look for. On shared hosting like Hostinger, most fixes take minutes in .htaccess or a security plugin. Pair it with the job offer scam scorer and the password generator.

Questions

Is it safe and legal to scan a website?
The scan only reads what any visitor already receives, plus a few well-known file paths. It never tries passwords, never sends attack payloads and never shows the contents of exposed files. Only scan sites you own, manage or have permission to check.
Why does a hardened site still need the checklist?
An outside scan cannot see outdated plugins with known holes, weak admin passwords, malware in the database or server settings that are not visible over HTTP. The checklist covers those.
How is the grade worked out?
Every site starts at 100. Each problem takes points off by severity: critical 25, high 12, medium 6, low 2. A critical exposure, like a public .git folder or .env file, caps the grade at D no matter the score.
Can I scan the same site again after fixing things?
Yes. Results are reused for 15 minutes to keep the scanner fast, so wait 15 minutes after your changes and scan again.
Is anything stored?
Only a short-lived cached result and a rate-limit counter, both deleted automatically. Nothing is tied to your name or email.

More in Cybersecurity