Skip to main content
Web securityReviewed

Penetration testing services for websites, WordPress and web applications

Scoped security testing for the websites, online stores, web apps and AI tools Australian businesses run.

You get a written scope before testing, a report your developers can act on, and one retest after the fixes.

Security testing for what your customers can reach

Clever Ops tests the parts of a business that customers, and attackers, reach through a browser or an API: marketing websites, WordPress sites and WooCommerce stores, custom web applications and their APIs, apps made with AI builders such as Lovable or Bolt, and AI chatbots that answer customers or take actions for them.

We have built and run websites and web applications for Australian businesses for years, so the scoping questions are about how your application works, not only how big it is.

The service is narrow on purpose. We do not test office networks, staff laptops or Active Directory, we do not run phishing campaigns, and we do not provide managed IT, round-the-clock monitoring or emergency incident response. If that is what you need, the decision guide on this page names the kind of specialist to look for instead.

Every engagement follows the same shape. A free scoping call works out what you run and why you want it tested. You receive a written scope and quote, sign an authorisation for each target, and testing runs in an agreed window. The report comes back with evidence and fixes, and one retest records what your fixes changed.

The services, and where each one stops

Each service has a defined edge, because a test is only as useful as its scope is clear.

When an application spans more than one, such as a WordPress site with a custom booking plugin, the scoping call combines them.

Website security check

An external review of what anyone on the internet can see without logging in: certificates and transport security, security headers, cookie settings, exposed files and admin paths, and software versions visible from outside. It suits brochure and marketing sites on any platform, and it is the sensible first step when you are not sure what your site exposes.

It does not look behind a login, read source code or test business logic, so it is not a penetration test.

WordPress security audit

A WordPress review that follows each role that can log in, from subscriber through editor to administrator, and checks the login and password-reset flows, the installed plugin and theme versions with evidence, and how the admin area is exposed.

WooCommerce stores and member sites add customer accounts, orders and checkout pages to the scope. You get an update-priority list, so the riskiest plugins are dealt with first. Malware cleanup and emergency response are not part of it.

Web application and API penetration test

A signed-in test of a custom application, such as a Next.js, React or Node application with an API behind it. It covers authentication and sessions, what each role can see and change, whether one customer can reach another customer's records, the API called directly rather than only through the screens, payment and billing flows, file uploads and the business rules your app is meant to enforce.

Read-only code access can be added for a closer look at the riskiest areas. Larger and multi-tenant applications are scoped individually after a longer call.

Vibe-coded app security check

For apps made with Lovable, Bolt, Replit, Base44, v0, Cursor or a similar AI builder, usually on Supabase or Firebase. It concentrates on data exposure, authentication, secrets, payments and abuse: database rules that let one user read another user's data, keys shipped to the browser, gaps in sign-up and login, payment steps that can be skipped, and features that can be abused in bulk.

The report is written for a non-technical builder, with a plain-English checklist and fix instructions you can paste back into the builder.

AI chatbot and agent security test

A test of your chatbot or agent, not of the AI model behind it. It covers direct and indirect prompt injection, poisoned content in the documents the bot retrieves, actions the bot can be talked into taking, data it can be made to reveal, and usage that runs up your AI bill.

Every tool, integration or MCP server the agent can call is in scope, because that is where a manipulated answer becomes a real action.

Security fix sprint and retests

If your team does not have time to fix the findings, a security fix sprint covers remediation of known findings, from our report or from another tester's. It runs under its own statement of work, so you stay free to choose a different developer. Every test includes one consolidated retest, explained further down, and findings from another provider's report can be retested as a separate piece of work.

Scan, check, audit or penetration test

Providers use these words loosely, and the difference decides what a report can tell you.

The useful question is how far into the application the testing goes, and what it proves on the way.

A vulnerability scan compares what it can see against lists of known issues and reports possible problems, many of which need a person to confirm. A check or audit goes further, reviewing configuration and exposure from the outside or from an administrator's view and confirming which issues are real.

A penetration test signs in as each role, tries to break the rules the application is meant to enforce, and records evidence of what worked. A code review reads the source to find flaws a running test may not reach.

No test finds every flaw. Each one covers what was in scope, on the build that was tested, during the window it ran. A good report states those limits plainly.

  • Scan: a quick inventory of known issues, useful between tests and weak as evidence on its own.
  • Check or audit: the right depth for sites without customer logins, and for WordPress sites where plugins and admin accounts are the main exposure.
  • Penetration test: the right depth when customers log in, pay, upload files or see data that belongs only to them.
  • Code review: worth adding when the riskiest logic sits in a handful of files that can be read directly.

If Clever Ops built or hosts your site

Clever Ops builds and hosts websites and applications for clients.

When we test something we built or run, we call it a security review, not an independent penetration test, and the report states who built and who hosts the system. The difference is independence: a tester who wrote the code or manages the server is checking their own work.

That matters when someone else will rely on the report. If a customer questionnaire, an auditor or a contract asks for an independent test, give the work to a provider with no part in building or running the system. If the review is for your own confidence before a launch or a major change, a review from people who already know the code can be the quicker route to fixes.

Five questions that decide the right test

The scoping call works through these in order.

Answer them beforehand and the call can go straight to the details.

What kind of application is it?

The platform shapes where things tend to go wrong. On WordPress it is plugins, themes and admin accounts. On Next.js it is the server-side code that decides who may do what: route handlers, server actions and middleware. On Supabase or Firebase it is the database rules the browser talks to directly. On a chatbot it is what the bot can read and what it can do.

How many routes does it have?

Count the pages and API endpoints that accept input or return data that is not public. A brochure site might have three forms. A software product can have a dozen screens with well over a hundred API endpoints behind them. Route count sets the size of a test far more than page count does, so ask your developer for the list from the routing files or the API documentation. Around 20 routes is where a small, fixed scope gives way to a larger one.

How many user roles and customer organisations?

Access control fails between people. Each role, such as customer, staff member and administrator, has to be tested against the others, and an app that serves several customer organisations from one database has to be tested between those organisations too.

That is why roles drive effort as much as routes do. Our sample report, written from a lab application, shows the stakes: its most serious finding let an ordinary user read and change another organisation's customer records.

When does it need to be finished?

Work back from the date. You need time for the test, time for your developers to fix what it finds, and time for the retest, ideally on a build that is not changing every day. If launch is close, test the flows that would hurt most if they failed, such as login, payments and anything that shows one customer's data, and schedule the rest. A customer questionnaire due date works the same way.

Who is asking for the test?

If the test is for your own confidence, scope it around risk. If a customer, auditor, insurer or tender asked for it, read their exact wording first. Some ask for an independent tester, some name an accreditation, and some want a recent report and proof that serious findings were fixed.

The wording decides whether we are the right provider, and it is better to settle that on the scoping call than after the report.

Which test fits your application

Find the row that matches what you run, check its routes, roles and deadline columns, then read across to the best starting point and what it leaves out. If two rows fit, bring both to the scoping call.

11 rows

Which test fits your application

What you runRoutes and user rolesLaunch deadlineStart withNot included
Marketing or brochure website on any platform, with no customer loginsPublic pages and forms. Site administrators are the only people who log in.Fits a tight deadline: it needs no test accounts and covers only what will be public.Website security checkLogged-in areas, source code, business logic and load testing
WordPress site, including WooCommerce stores and member areasVisitors and administrators, plus customers or members if they log in. Each extra role adds checks.Check your host's testing policy early, in case it asks for notice or approval before testing begins.WordPress security auditMalware cleanup, emergency response and the hosting provider's own platform
Custom web app or software product built on Next.js, React, Node or similarUp to about 20 routes and two roles, such as customer and administrator, within one organisation.Test a stable build, leaving time before launch for your fixes and the retest.Web application and API penetration testSource code review unless code access is agreed, internal networks and load testing
Larger or multi-tenant web app, or one with complex billing, marketplace or payment logicMore than about 20 routes, three or more roles, or several customer organisations in one app.Start scoping well before launch, since access control fixes often touch many routes at once.Web application penetration test scoped on a longer call, or a referral for very logic-heavy appsFeatures added after the scope is agreed, which are scoped separately
API behind a mobile app or used by partners, with little or no web front endEach endpoint, and each key, token or account type that can call it.Test a staging API with seeded data so no real records change.Web application and API penetration test, with the API as the main targetThe mobile app itself and on-device testing
App made with Lovable, Bolt, Replit, Base44, v0 or Cursor, usually on Supabase or FirebaseUsually one or two roles. The main question is whether one user can read another user's records.Run it before real users sign up or payments go live, while the database rules are still easy to change.Vibe-coded app security checkRebuilding the app. Fixes come as instructions to paste back into your builder.
AI chatbot or agent on your website or inside your appThe bot, the documents and data it reads, and every tool or action it can call.Test before the bot gets access to customer data or the ability to act, and again when you add tools.AI chatbot and agent security testRed teaming of the underlying AI model, and the AI provider's own platform
Any application, when a tender, contract or payment provider requires CREST, a PCI Approved Scanning Vendor or a Qualified Security AssessorNot the deciding factor here. The named accreditation is.Confirm the requirement in writing before booking anyone, since a test from the wrong provider may not be accepted.Specialist referral to a provider that holds that accreditationClever Ops holds none of these accreditations
Office network, servers, Active Directory, staff devices, phishing or physical accessNot web routes. The targets are machines, accounts and people.Book a network or red team specialist directly. A web application test does not stand in for one.Specialist referralNot part of any Clever Ops service
A test of how much traffic the site can take, or a denial-of-service simulationAny size of site or app.Plan it with a specialist and get your hosting provider's written approval first.Load-testing specialistNot part of any Clever Ops service
A site that is compromised now, or one that needs malware cleanup or round-the-clock monitoringAny size of site or app.Act now. Contain the incident with an incident response specialist before any testing.Incident response specialist first, then a post-cleanup auditIncident response, forensics, malware cleanup and monitoring

What you run

Routes and user roles

  1. Marketing or brochure website on any platform, with no customer logins
    Routes and user roles
    Public pages and forms. Site administrators are the only people who log in.
    Launch deadline
    Fits a tight deadline: it needs no test accounts and covers only what will be public.
    Start with
    Website security check
    Not included
    Logged-in areas, source code, business logic and load testing
  2. WordPress site, including WooCommerce stores and member areas
    Routes and user roles
    Visitors and administrators, plus customers or members if they log in. Each extra role adds checks.
    Launch deadline
    Check your host's testing policy early, in case it asks for notice or approval before testing begins.
    Start with
    WordPress security audit
    Not included
    Malware cleanup, emergency response and the hosting provider's own platform
  3. Custom web app or software product built on Next.js, React, Node or similar
    Routes and user roles
    Up to about 20 routes and two roles, such as customer and administrator, within one organisation.
    Launch deadline
    Test a stable build, leaving time before launch for your fixes and the retest.
    Start with
    Web application and API penetration test
    Not included
    Source code review unless code access is agreed, internal networks and load testing
  4. Larger or multi-tenant web app, or one with complex billing, marketplace or payment logic
    Routes and user roles
    More than about 20 routes, three or more roles, or several customer organisations in one app.
    Launch deadline
    Start scoping well before launch, since access control fixes often touch many routes at once.
    Start with
    Web application penetration test scoped on a longer call, or a referral for very logic-heavy apps
    Not included
    Features added after the scope is agreed, which are scoped separately
  5. API behind a mobile app or used by partners, with little or no web front end
    Routes and user roles
    Each endpoint, and each key, token or account type that can call it.
    Launch deadline
    Test a staging API with seeded data so no real records change.
    Start with
    Web application and API penetration test, with the API as the main target
    Not included
    The mobile app itself and on-device testing
  6. App made with Lovable, Bolt, Replit, Base44, v0 or Cursor, usually on Supabase or Firebase
    Routes and user roles
    Usually one or two roles. The main question is whether one user can read another user's records.
    Launch deadline
    Run it before real users sign up or payments go live, while the database rules are still easy to change.
    Start with
    Vibe-coded app security check
    Not included
    Rebuilding the app. Fixes come as instructions to paste back into your builder.
  7. AI chatbot or agent on your website or inside your app
    Routes and user roles
    The bot, the documents and data it reads, and every tool or action it can call.
    Launch deadline
    Test before the bot gets access to customer data or the ability to act, and again when you add tools.
    Start with
    AI chatbot and agent security test
    Not included
    Red teaming of the underlying AI model, and the AI provider's own platform
  8. Any application, when a tender, contract or payment provider requires CREST, a PCI Approved Scanning Vendor or a Qualified Security Assessor
    Routes and user roles
    Not the deciding factor here. The named accreditation is.
    Launch deadline
    Confirm the requirement in writing before booking anyone, since a test from the wrong provider may not be accepted.
    Start with
    Specialist referral to a provider that holds that accreditation
    Not included
    Clever Ops holds none of these accreditations
  9. Office network, servers, Active Directory, staff devices, phishing or physical access
    Routes and user roles
    Not web routes. The targets are machines, accounts and people.
    Launch deadline
    Book a network or red team specialist directly. A web application test does not stand in for one.
    Start with
    Specialist referral
    Not included
    Not part of any Clever Ops service
  10. A test of how much traffic the site can take, or a denial-of-service simulation
    Routes and user roles
    Any size of site or app.
    Launch deadline
    Plan it with a specialist and get your hosting provider's written approval first.
    Start with
    Load-testing specialist
    Not included
    Not part of any Clever Ops service
  11. A site that is compromised now, or one that needs malware cleanup or round-the-clock monitoring
    Routes and user roles
    Any size of site or app.
    Launch deadline
    Act now. Contain the incident with an incident response specialist before any testing.
    Start with
    Incident response specialist first, then a post-cleanup audit
    Not included
    Incident response, forensics, malware cleanup and monitoring

What you need to provide

Testing begins once the authorisation and access are in place.

Lining these up while the scope is agreed keeps the testing window intact.

  • Written authorisation from the owner of each target, signed by someone who can approve testing for that business.
  • The exact targets: domains, subdomains and API addresses, plus anything that must be left alone, such as a checkout page run by your payment provider.
  • Your hosting provider's testing policy for each target, checked before testing begins in case it asks for notice or approval.
  • Test accounts: two for each role in scope, so access between users can be checked, and accounts in two separate customer organisations if your app serves more than one.
  • An environment to test. A staging copy that matches production is preferred. If production is the target, testing uses agreed windows and test data that is removed afterwards or listed for your team to remove.
  • A technical contact for the testing window who can answer questions, restore data and pause testing if something looks wrong.
  • Read-only code access, when it is part of the agreed scope, and the wording from any customer, auditor or insurer who asked for the test.

What the report gives you

The report is written for two readers: the person who decides what to fix first, and the developer who has to fix it.

Our sample report, built from a lab application, shows the format before you commit to anything.

Coverage references the OWASP Web Security Testing Guide and the Application Security Verification Standard 5.0. That describes what was checked. It is not a certificate or a compliance opinion.

  • An executive summary in business terms, with every finding listed at a glance.
  • The scope as tested: targets, roles, build, dates, and what was out of scope or not performed.
  • For each finding: a description, the evidence with secrets redacted, the business impact, a fix written for your stack and the criteria the retest will use.
  • Two ratings for each rated finding: a CVSS v3.1 technical score from 0.0 to 10.0, and a business-risk rating that weighs the data involved, how exposed the feature is, the controls already in place and the cost of disruption.
  • Each finding mapped to its OWASP Top 10:2025 category, which helps when a customer questionnaire asks about specific types of risk.
  • Checks that found nothing, recorded as negative results for the build and accounts tested rather than as proof that an area is sound.
  • A remediation plan in priority order, and a list of any test data left behind that needs removing.

Fixes and the retest

You choose who fixes the findings: your own developers, your agency, or a Clever Ops security fix sprint under a separate statement of work.

Keeping the fix work separate means the test result does not depend on who you hire to act on it.

Every test includes one consolidated retest. You request it within the window set in your statement of work, once the fixes are deployed to an identified build of the same application. The retest covers the reported findings within the agreed scope. New features and unrelated changes are scoped separately, because they were not part of the original test.

After the retest, each finding carries one of four statuses: fixed, partially fixed, still reproducible or not retested. A finding that was not retested is reported as not retested rather than as passed, so the updated report can go to a customer without overstating what changed.

When another provider is the better choice

Some work needs a different kind of provider.

Saying so on the first call saves you a wasted scoping round.

  • A tender, panel or contract that requires a CREST-accredited provider. Clever Ops is not CREST accredited, so we refer that work to a provider that is.
  • A PCI DSS scan from an Approved Scanning Vendor, or an assessment by a Qualified Security Assessor. Clever Ops is neither.
  • Internal networks, servers, Active Directory, staff devices, red teaming, phishing or physical testing. These need a network or red team specialist.
  • Denial-of-service, load or volumetric testing, which is not part of any Clever Ops service.
  • A site that is hacked now, malware cleanup, forensics, incident response or round-the-clock monitoring. Call an incident response specialist first; once the site is clean, an audit can check the web application before you rely on it again.
  • Live Shopify storefronts and Laravel applications, which sit outside this service.
  • A certificate. A test report is evidence for a decision someone else makes, such as an auditor or a customer, and it is not a certification of your site.
  • Very logic-heavy applications, such as marketplaces, lending platforms or multi-tenant products with complex billing. We scope these individually and refer them when a larger firm is the better fit.

How to compare penetration testing companies

Price and turnaround are easy to compare.

What you keep is the report, so compare providers on what it will contain and how they scope it.

  • Ask for a sample report and read one finding end to end. Look for evidence you could reproduce, a business impact you understand and a fix your developer could start on.
  • Ask for the scope in writing: targets, routes, roles, environment, dates and exclusions. A quote without an exclusions list leaves you guessing about what was tested.
  • Ask how severity is rated, and whether technical scores are kept separate from business risk.
  • Ask what the retest covers, how long you have to request it, and how findings are marked afterwards.
  • Notice the scoping questions. A provider who asks how your roles, customer organisations and payments work is planning a test of your application. One who asks only for a URL is planning a scan.
  • If the person who asked for the test names an accreditation or wants independence, check both before you sign, including whether the provider built or hosts the system.

Explore the web security library

38 pages

Services

5 pages

  • Website Security Audit

    An external audit, reviewed by a person, of twelve things anyone on the internet can examine without logging in: your hostnames, certificates, headers, cookies, leftover files, admin screens and the code your site sends to every browser. Each result comes back with evidence, business impact and a fix, and the report states what an outside view cannot reach.

  • AI Chatbot Security

    A security test of the chatbot or agent your business runs, and every tool it can call. It checks prompt injection typed into the chat or hidden in documents, poisoned knowledge bases, actions the bot can be pushed into, data it can be made to reveal and usage that inflates your AI bill. The tool-permission threat matrix below is yours to use today.

  • Web Application Penetration Testing

    A signed-in test of your custom web application and the API behind it, run from test accounts in every role. This page sets out what a web app penetration test examines, how your routes, roles and business rules become test cases, and a worked scope for an invented twenty-route application, exclusions included.

  • Vulnerability Assessment

    A broad search of your website or web application for known kinds of weakness, from the open internet and from inside each signed-in role. A tester confirms each finding before it is reported. It is then ranked by what it exposes, who can reach it and whether attackers are known to use it, and it reaches you with an owner, a fix and the check that will show the fix worked.

  • Secure Code Review

    A security review of the source code behind your web application and its API. It follows the paths in scope that read or change data, looking at authorisation, secrets, untrusted input, dependencies and the assumptions AI-written code leaves unchecked. Code findings are confirmed against a running build where the scope allows, and the report marks any that rest on the code alone.

Platform guides

2 pages

  • WordPress Security Audit

    An audit that signs in as each role your site hands out, tests login and password reset, records every plugin and theme version with evidence, and ranks what to update first. WooCommerce stores and member sites add customer accounts, orders and checkout.

  • Next.js Security

    Middleware, Server Actions, route handlers, server components, caching and build-time secrets each fail in their own way. This guide shows how a Next.js application is tested at each of those points, which published advisories matter, and how to tell whether your deployment is affected.

Guides

6 pages

  • Vibe Coding Security

    Apps made with Lovable, Bolt, Replit, Base44, v0 or Cursor can work well and still let one user read another user's data, ship secret keys to every browser or let a payment be skipped. Here is what goes wrong, a thirty-point check you can run yourself, and what a paid check adds.

  • Penetration Testing Methodology

    How Clever Ops tests web applications and their APIs, written for the person paying for the test. It covers how scope and authorisation are settled, what unauthenticated, authenticated and code-assisted testing each reach, how a finding is evidenced and rated, how testing behaves on a system people use, and how the retest records what your fixes changed.

  • Penetration Testing Cost

    What a penetration test costs depends on its scope. This guide shows what two Australian providers publish, as checked on 13 November 2026, explains each factor that moves the effort, and gives you a worksheet to scope your own test and line quotes up side by side.

  • Security Questionnaires

    A larger customer has sent a security questionnaire with a due date. This guide shows what the common questions are really asking, which of them a penetration test or security review can evidence and which it cannot, and how to word an honest answer when the true answer is "not yet".

  • Hacked Website

    What you do in the first hour after a website is hacked shapes how much you can recover and explain later. This guide puts that hour in order: stop the harm to visitors, keep the evidence, make the reporting decisions with the right advice, and hand the cleanup to a specialist. Clever Ops does not clean up hacked sites, so the guide also tells you who does.

  • OWASP Top 10

    What each of the ten risk categories means for a website or web application, how a tester checks for it without harming your site, what a fix usually involves, and what the list can and cannot tell you when you buy a security test.

Sample reports

1 page

  • Penetration Test Report Example

    A finished web application penetration test report from a lab application Clever Ops controls, with credentials and private values redacted. Each part shows what the report says, what a good report should show there, and what to ask a provider whose report leaves it out. It is a lab example, not client work and not independent assurance.

Browse the library

8 sections

  • Penetration Testing Templates15 pages

    Fifteen working documents for the buyer's side of a web application test, from house rules and release checks through quotes, permission and preparation to the remediation tracker and the retest. The table gives each one's format, its counted length, what to have to hand before you open it and the invented example it carries.

  • Penetration Testing Locations8 pages

    Clever Ops tests websites, web applications and APIs for businesses across Australia from its base in Gippsland, Victoria, and has no office in any of the cities below. The selector on this page sets the eight city pages side by side: the clock a test window is written in, the state privacy and procurement documents a public sector customer may work from, what remote testing asks of you, and the invented case each page works through.

  • Web Application Vulnerabilities45 pages

    Forty-five guides to vulnerabilities, defences and secure development, sorted into seven areas of an application. For each one the finder table gives what you notice first, where it lives, who can reach it, the OWASP category the guide itself names, and the lab, checklist or worksheet it hands you.

  • Web Application Security Platforms30 pages

    Thirty guides to the site builders, content management systems, store platforms, frameworks, runtimes, APIs, sign-in services, databases, hosts, payment webhooks and automation tools a site can be built from. The stack selector groups them by the part of the stack they cover and, for each one, gives what it helps you check, its asset counted, what to have ready, whether any row acts and where, and what the guide says about a Clever Ops service.

  • AI Application Security12 pages

    Ten guides in this library each cover one part of an application built on a large language model, from the text a user types to the bill the model runs up. Two more map those parts to OWASP's list and plan a test across them. The selector below asks eight questions about your own application, in the order a request travels through it, and for each one names the guides that cover it, the test pack each guide gives you, what to have ready and the evidence to keep.

  • Web Security Compliance Guides17 pages

    Guides for the point where someone asks your business for security evidence: a customer's questionnaire or contract, an insurer's proposal form, a question under a privacy law, prudential standard or other Act, an auditor or assessor, or a project about to go live. Each sets out what its documents say in their own words, leaves whether they apply to you with your adviser or the party it names, and comes with a table you work through for your own business. The buyer-evidence finder sets them side by side.

  • Web Security by Industry10 pages

    Ten guides, each built around one kind of business: healthcare practices, law firms, accounting practices, schools and edtech suppliers, online stores, SaaS products, financial-service businesses, real estate agencies, hospitality businesses and project-based firms. The workflow selector sets them side by side: the data each guide follows, the portals and sign-ins it covers, where it draws the payment boundary, how documents move, which laws and standards it quotes, its test table counted, and what it says about a Clever Ops service.

  • WordPress Plugin Vulnerabilities80 pages

    A register of the 80 WordPress plugin guides in this library. Each row gives the plugin's category, how many vulnerability records the source data lists for it, and the update guidance its guide gives, read from the same data the guide uses. Use it to check the plugins on your own site against their guides. It ranks no plugin and passes no verdict on any.

Free tools

15 tools

  • Security Headers Checker

    Check the HTTP security headers of a public page, or paste headers you copied. Compare each value with the OWASP proposal and copy fixes for Next.js, WordPress or Apache.

  • SSL Checker

    Check the certificate a public site presents, the chain it sends and which TLS versions connect from our server, then work through a renewal and remediation checklist with sources.

  • CSP Checker

    Paste a CSP header or meta tag to see each directive and its fallback, test an address against it and copy a tightened policy. It all runs in your browser.

  • HSTS Checker

    Paste your header to check it against RFC 6797, see what each max-age, includeSubDomains and preload combination does over time, and copy the exact header. It runs in your browser.

  • security.txt Checker

    Read both security.txt addresses of a site, check the file against RFC 9116, see the days left before it expires, then correct it in your browser and copy the result.

  • DMARC Checker

    Paste a DMARC record to check it against RFC 9989, see the policy it requests for sample SPF and DKIM results, and copy a corrected record. It runs in your browser.

  • DNS Security Checker

    See the NS, SOA, CAA, MX, SPF and DMARC records that public resolvers return for your domain, the DS answer for it, and a suggested order for any changes.

  • Redirect Checker

    Trace where a public address redirects, hop by hop: status codes, Location values, HTTPS changes, host changes and loops. Then plan a cleaner chain and export it.

  • Cookie Flags Checker

    Paste Set-Cookie lines to see what Secure, HttpOnly, SameSite, Domain, Path and Partitioned do for each cookie, then test request scenarios. It runs in your browser.

  • JavaScript Bundle Secret Scanner

    Paste a built JavaScript file from your own site and find API keys, tokens and private keys shipped by mistake. Findings are redacted, and the scan runs in your browser.

  • Supabase RLS Checklist

    Record what anon and authenticated should reach in each table, paste your policy SQL, and copy two-user test cases and read-only SQL checks. It runs in your browser.

  • Firebase Security Rules Checklist

    Say who may read and write each path, and get a test matrix of allow and deny cases for your Cloud Firestore, Realtime Database or Cloud Storage rules. It runs in your browser.

  • Pentest Scope Estimator

    List the systems you own or hold written permission to test and get a target register, an exclusions list and an effort range in person-days. Your answers stay in your browser.

  • Security Questionnaire Assistant

    Keep an evidence library, paste a customer's questions and record your own answers with an owner and a status. It matches by keyword in your browser and never writes an answer.

  • SRI Hash Generator

    Hash a file or pasted code with SHA-256, SHA-384 or SHA-512, check an existing integrity attribute and copy script or link markup. It all runs in your browser.

  • Free Business Tools & Calculators

    Free calculators, generators and checks for Australian businesses, with instant results and no sign-up.

Frequently asked questions

Clever Ops quotes each test after a scoping call instead of publishing prices, because the cost follows the scope: routes, roles, customer organisations, APIs, code access and production constraints. The penetration testing cost guide explains how those drivers change the effort and what the Australian market publishes.

No. A website security check reviews what is visible without logging in: certificates, headers, cookies, exposed files and visible software versions. A penetration test signs in as each role and tries to break the application's rules. If customers log in, pay or upload anything, the check is a starting point and the penetration test is the right depth.

Only if the party asking for the test requires one, so check the exact wording in the tender, contract or questionnaire. If it requires CREST, we refer you to an accredited provider, because Clever Ops is not CREST accredited. If it asks for a competent or independent tester without naming a scheme, the scoping call will confirm whether we fit.

Yes, as a security review. The report states that Clever Ops built or hosts the system, so it is not presented as an independent test. If a customer or auditor asks for independence, use a provider with no part in the build or the hosting.

Testing is planned to avoid it. Denial-of-service and load testing are excluded, test accounts and test data stand in for real customers, and any risk to production is agreed in writing before testing begins. Where a staging copy matches production, testing there is the lower-risk option.

If you want us to. A security fix sprint covers remediation of reported findings under its own statement of work, so you can equally hand the report to your own developers or another agency. Either way, one retest of the reported findings comes with the test.

Yes. Clever Ops is an Australian consultancy based in Gippsland, Victoria, and the service is offered to businesses anywhere in Australia. The scoping call, report and retest work the same way wherever you are based.

Scope the right test for your application

Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.