Security
- Known security holes in WordPress add-ons
- Outdated code libraries
- Security settings and HTTPS
A hacked site or a browser warning loses customers fast.
In-depth website audit
87 checks, every one that applies to your site, run on up to 20 of your pages, then a clear report that ranks what to fix first and explains how, in plain English.
Running WordPress? We check the plugins, themes and core version your site shows publicly against 40,000+ known security holes. How we check it
01What you get
Our own site
On 12 October 2026 it found six things to fix on riyostudio.dev. We fixed all six the same day, and the next audit came back A+.
02What it checks
A hacked site or a browser warning loses customers fast.
The checks that catch the gaps AI-built sites most often ship with. Exposed data is the first thing attackers look for.
Without email protection, anyone can send invoices that look like they came from you.
Slow pages lose visitors before they ever contact you.
Missing basics make it harder for Google to show your pages.
Visitors and privacy laws expect you to ask first.
03WordPress
Outdated plugins are the most common way WordPress sites are hacked. Attackers scan the internet for known weak versions and break in automatically, so we check yours the same way they would, without touching your site.
Each problem comes with what to update, remove or switch off, in plain English.
Only versions your site shows publicly can be checked.
Not on WordPress? Every other check on this page still applies.
04How it works
Add your web address and confirm you own the site or are authorised to have it audited.
Stripe handles the payment, in your local currency in many countries, and emails you a receipt and an invoice.
The audit runs straight after payment and your report is usually ready within a few minutes, at a private link.
05Questions
Yes. The audit is read-only: it reads your public pages, a small number of well-known public addresses, the home pages of a few of your subdomains and, if your site uses one, your Firebase database’s public address, the same way a visitor’s browser could. It doesn’t try to log in or inject anything, and nothing on your site is changed.
No. The audit works on any public website. If your site runs WordPress, it also checks the plugins, themes and core version your site shows publicly against more than 40,000 known security holes.
Yes. Your report stays at a private link, and anyone you share the link with can view it, so you can send it to your developer or IT provider. You can also print it or save it as a PDF, and ask us to delete it at any time. If you use your free re-check, the new report replaces the old one at the same link.
Yes. Stripe emails a receipt and an invoice to the address you give at checkout. If it doesn’t arrive, email [email protected] and we’ll send you a copy.
The audit is a point-in-time check of what can be seen publicly when it runs. It isn’t a guarantee that your site is secure, and it doesn’t include active tests such as injection, access-control or business-logic attacks. Those need a full, authorised manual penetration test. Because the report is delivered as soon as you pay, the audit is generally non-refundable once delivered, except where the Australian Consumer Law requires a refund.