USPA Nationwide Security
Free automated review

Free Website Security Audit

Get an initial look at selected security settings on your business website. Enter your website address and email, confirm your request, and receive a report of preliminary and automated findings.

The free review examines information available from your public homepage. Your report explains what the automated checks observed and identifies any checks that could not be completed.

Free automated review. No credit card required.

Start here

Request your free check

Enter the website address and the email address that should receive the report. A confirmation link verifies the inbox before anything runs.

Preliminary and automated

The review samples the public homepage only. It does not log in, submit forms or change anything on the website, and its findings describe selected public settings at the recorded time.

Enter a website you own or are authorized to have reviewed.

Only the hostname is used. Paths, query strings and sign-in details are not sent to the scanner.

Use an address at the domain you are checking. The verification link and your preliminary report go to this address.

See the Privacy Policy. Your details are used to confirm ownership of the website and to send the verification link and report.

Free automated review. No credit card required.

Scope

What Your Free Website Security Audit Covers

The review checks whether the public homepage can be reached over HTTPS, observes how HTTP requests are handled, and examines selected settings returned by the page. Where the response is available, it also reviews browser security headers, cookie attributes and resource references in the page markup. The report names the address checked and explains the limits of each observation.

  1. 01

    HTTPS and certificate observation

    Whether the public homepage answers over an encrypted connection with a certificate a browser would accept, and whether the certificate is issued to the hostname being checked.

    Why it matters. Encryption protects the page and anything a visitor types into it while the two travel between the browser and the server. A certificate warning is one of the fastest ways to lose a visitor, and browsers now label plain HTTP pages as not secure.

    A sound result: The homepage loads over HTTPS with no certificate warning for the hostname in the report.

  2. 02

    HTTP handling and HTTPS redirection

    What the plain HTTP address returns, and whether it sends the visitor to the encrypted address instead of serving a copy of the page.

    Why it matters. A page that answers over plain HTTP can be read or altered in transit. Sending every plain request to one encrypted address also keeps search engines and visitors on a single canonical URL.

    A sound result: A plain HTTP request redirects to HTTPS, ideally permanently, without serving content first.

  3. 03

    HTTP Strict Transport Security

    Whether the response carries a Strict-Transport-Security policy, and how long browsers are asked to remember it.

    Why it matters. Once a browser has seen the policy it refuses plain HTTP for that hostname before a request leaves the machine. That closes the opening moments of a session, where an attacker on the same network would otherwise try to downgrade the connection.

    A sound result: A policy with a long lifetime, extended to subdomains once the whole domain is encrypted.

  4. 04

    Content Security Policy

    Whether an enforcing policy, a report-only policy or a meta-delivered policy is present, and which directives it declares.

    Why it matters. A content security policy is the instruction that limits where scripts, styles, frames and images may load from. It is the control that decides whether an injected script runs as its author intended or fails quietly.

    A sound result: An enforcing policy sent as a response header, naming only origins the site actually uses.

  5. 05

    Framing controls

    Whether the page may be embedded by another origin, read from the effective response controls.

    Why it matters. Framing that a site did not intend is how clickjacking works: an attacker lays a transparent frame of your page over a page of their own, and a visitor clicks something they never agreed to.

    A sound result: Frame-ancestors in the policy, or X-Frame-Options set to deny or sameorigin, unless embedding is a deliberate feature.

  6. 06

    Content-type sniffing control

    Whether the response declares that browsers must not override its declared content type.

    Why it matters. Some browsers will guess at a file's type when the declaration is missing. A text file a visitor uploaded can then be treated as something executable, which turns an ordinary upload form into a risk.

    A sound result: The nosniff instruction on responses that serve user-submitted or uploaded files.

  7. 07

    Referrer policy

    How much address information the page tells browsers to send to other origins, and what arrives with outbound links.

    Why it matters. The referrer value can carry a private path, an account identifier or a reset token to whatever the visitor clicks next. A restrictive policy limits how much of your site travels with them.

    A sound result: A strict-origin-when-cross-origin policy, or something stricter.

  8. 08

    HTTP resource references in HTTPS markup

    Whether scripts, styles, frames, images or media in the markup are referenced over plain HTTP.

    Why it matters. Browsers block or downgrade some mixed content and warn on the rest. A single http:// reference left behind by an old widget can break a page or undermine the padlock in the address bar.

    A sound result: Every reference in the page markup uses HTTPS.

  9. 09

    Cookies observed on the public response

    Attribute observations only: Secure, HttpOnly, SameSite, lifetime and name prefix. Values are discarded immediately and never stored.

    Why it matters. A session cookie without Secure can travel over plain HTTP if the site ever uses it. Without HttpOnly a script can read it. Without SameSite it rides along on requests the visitor did not make.

    A sound result: Session cookies marked Secure and HttpOnly, with SameSite set and a short lifetime.

  10. 10

    Third-party script inventory

    The origins of externally hosted scripts referenced in the sampled page markup.

    Why it matters. Every external script runs with the authority of your own code. A tag manager nobody audits, an abandoned plugin or an unfamiliar loader is one of the most common ways a compromise reaches a business website.

    A sound result: A short list of origins you can name and justify, each one a choice rather than an inheritance.

The free review does not test email authentication records, scan for malware, crawl the full site or attempt to exploit anything. Those checks are not part of this version, and no result here should be read as if they had been performed.

Method

How the Free Website Security Check Is Run

A security result is only worth as much as the method behind it. This is the entire sequence, from the address you submit to the report in your inbox, so you can judge the findings for yourself.

  1. 01

    You submit the address and mailbox

    The form accepts a public homepage address and asks you to confirm you own the site or have permission to request the checks. No path beyond the site root, no sign-in details, no port numbers.

  2. 02

    The mailbox is confirmed

    A verification link goes to an address at the website's own domain. Delivery is verified before any scan runs, so the tool cannot be used to email a report about someone else's site to a stranger.

  3. 03

    The public page is sampled once

    A small number of ordinary web requests are made from our servers to the homepage and to its plain HTTP counterpart. The report records the exact address sampled and the time it was observed.

  4. 04

    A fixed rule set is applied

    Each observation comes from an explicit, versioned rule rather than a judgement call. The same response produces the same finding, and a check that cannot complete is labelled as a limit rather than a result.

  5. 05

    The report is emailed to you

    You receive preliminary, automated findings with an explanation and a suggested next step for each one. The report states what was not examined, and the link to it expires after a period.

How to read it

Understanding Your Results

Each observation includes an explanation and a suggested next step. Some settings depend on how the website is built, so an automated result may need a developer or security professional to review it in context. A blocked request, timeout or incomplete response will be recorded as a limit of the review.

The free check examines selected information visible from outside the website. It does not access private systems, test logged-in features, review application source code or establish that a website is free of security weaknesses.

Status words in the report

Observed
The named setting was seen within the scope of this review. It is not a statement that the website is secure.
Review recommended
The observation is worth a person's attention, arranged by what a next review should cover first.
Informational
Context that explains the result without calling for action on its own.
Could not check
The check did not complete, for a stated reason. This is a limit of the review, not a finding about the website.
Not applicable
The observation does not apply to the sampled page.
Acting on the report

What the Findings Usually Call For

Most automated findings fall into five groups, and the order in which you take them changes how much work they cost. Transport first, then the headers that break nothing, then cookies, references and third-party scripts.

  1. First

    Transport: certificate, redirect, HSTS

    Confirm every hostname visitors use has a valid certificate, send plain HTTP to the encrypted address with a permanent redirect, then add a Strict-Transport-Security policy once you are certain nothing still depends on HTTP.

    Usually a hosting or CDN setting rather than a page-by-page change.

  2. Second

    The cheap headers: framing, nosniff, referrer

    These three cost nothing in page performance and rarely break anything. They are usually added in one place: the server configuration, the host's header settings or the CDN in front of the site.

    The fastest improvement most reports can point to.

  3. Third

    Cookies: Secure, HttpOnly, SameSite

    Set the attributes where the session cookie is issued, which is normally in your framework or platform configuration. Test sign-in and any embedded payment flow afterwards, because strict SameSite settings expose integrations that quietly relied on cross-site requests.

    Check embedded checkout and single sign-on before tightening SameSite.

  4. Fourth

    Mixed content: the last http:// references

    Search templates, page builders, old widgets and plugin settings for http:// references to scripts, styles, frames, images and media. One forgotten reference is enough to produce a warning in the address bar.

    Often inherited from a theme or a marketing tag added years ago.

  5. Fifth

    Third-party scripts: inventory, then policy

    List every external origin the site loads, remove the tags nobody can justify, and load the rest deliberately rather than by inheritance. Only then write the content security policy that names them, starting in report-only mode so you can see what breaks.

    The content security policy works best last, once the inventory is honest.

Where a site runs on a hosted builder, several of these settings are controlled by the host or the CDN in front of it rather than by the pages themselves. Check your platform's own documentation before editing templates, and change one group at a time so a broken page has an obvious cause.

Reference

Website Security Terms, Explained Plainly

The words in a security report should not require a translator. These are the terms the automated review uses, and what each one actually does for a website.

HTTPS
The encrypted form of the web protocol. The browser and the server agree on keys, then exchange the page over a connection nobody in between can read or alter.
TLS certificate
The document a server presents to prove it holds the keys for a hostname. A certificate issued to a different name produces the warning every visitor recognises.
HSTS
HTTP Strict Transport Security. A response instruction that tells the browser to refuse plain HTTP for that hostname, for a stated number of seconds, before the first request is sent.
CSP
Content Security Policy. A list of rules in the response that says which origins may supply scripts, styles, frames, images and connections for that page.
Clickjacking
Embedding a page inside another site and disguising the frame, so a visitor's click lands on a control they cannot see.
MIME sniffing
A browser's habit of guessing a file's type when the declaration is missing or vague. Guesswork is how an uploaded text file becomes a script.
Referrer
The address a browser sends along with an outbound request, telling the destination where the visitor came from. Useful for analytics, risky when the address itself is private.
Mixed content
A page served over HTTPS that still loads scripts, styles, frames, images or media over plain HTTP. The browser treats the whole page as weakened.
Cookie attributes
Instructions attached to a cookie: Secure limits it to encrypted connections, HttpOnly hides it from scripts, and SameSite decides whether other sites can trigger requests that carry it.
Penetration test
A scoped, authorised attempt to find and exploit weaknesses in systems, usually by people working against an agreed plan. An automated public-page review is not one, and should never be read as a substitute.
Who it is for

Who Runs a Free Website Security Check

The review was written for the person who owns the website and has to decide what to do next, not for a security team with a console already open.

Owners of a small business website

The site was built years ago, a marketing tag was added by someone else, and nobody has looked at the response headers since. The report names what is missing in plain language.

Web and marketing agencies

A client handover or a rebuild is due. The automated review gives a dated, recorded baseline to compare against after the new site goes live.

Office managers and IT generalists

Security is one part of a role that covers everything else. The report separates the settings that can be fixed in an afternoon from the ones that need a developer.

Nonprofits, clinics and contractors

The site collects enquiries and sometimes payment details, but there is no security team. A short list of priorities is more useful than a dashboard.

Developers preparing a header policy

Before writing a content security policy, it helps to know which third-party origins the page actually loads. The inventory is the starting point, not the finish line.

Operators after a migration

A new host, a new CDN or a rebuilt theme can silently drop headers that used to be present. Re-running the check after a change is the point of recording a baseline.

Paid service

Request a Full Website Security Assessment

If you need a deeper review, ask USPA about a paid website security assessment. We can discuss your website, the questions raised by the automated report, and the scope of work needed to evaluate your concerns. The assessment scope and fee will be agreed before work begins.

Full assessments are paid services.

Answers

Questions about the free website security audit

Is the website security audit free?
The automated public-page review and its emailed report are free. A full assessment is a separate paid service with an agreed scope and fee.
What does the automated check examine?
It samples the public homepage and selected connection, header, cookie and page-resource settings. The report lists the checks that completed and any limitations.
Is a free website security audit the same as a penetration test?
No. A penetration test is a scoped, authorised attempt to exploit weaknesses, usually by people working against an agreed plan. This review only reads what the public homepage returns and never attempts exploitation. A clean result is not evidence that a site has been tested.
Does it work on WordPress, Wix, Squarespace or Shopify sites?
Yes, provided the public homepage answers ordinary web requests. Where the site runs on a hosted platform, several of the settings in the report are controlled by the host, the platform or the CDN in front of it, and some checks may come back as could not check rather than as a finding.
Do I need to own the website?
You must own the website or have permission to request the described checks. The form records your authorization, and the delivery address must sit on the website's own domain, so a client's mailbox is what confirms a client's site.
Will the check change my website?
The scanner makes a small number of ordinary public web requests. It does not log in, submit website forms, modify files or attempt to exploit a weakness.
How long does the review take?
The verification email arrives within minutes and the report follows once the public page has been sampled. If a scan cannot complete, the report says so and states the reason instead of guessing at a result.
Will running a check affect my site's performance or search rankings?
No. The review asks for a handful of public pages once. It does not crawl the site, change any content or add anything to the pages a search engine sees.
Should I run it again after making changes?
Yes, and that is the point of a recorded baseline. Response headers are easy to lose during a host migration, a CDN change or a theme rebuild, so a second dated report shows whether the fixes held. Repeat requests are rate limited per address and per website.
Does a report with no review items mean my website is secure?
The result applies to the checks that completed on the sampled page at the recorded time. Weaknesses may exist in features and systems outside that scope.
Where can I read the terms behind the checks?
The privacy policy covers what is stored for a request and how long it is kept. The report itself lists every limitation that applied to your review.
How do I arrange a full assessment?
Use Request a Full Assessment to tell USPA about your website and concerns. The team will discuss the scope and pricing before any paid work begins.

Need a deeper review?

Full assessments are paid services. USPA will discuss your website, the questions raised by the automated report, and the scope and fee before any work begins.

    ×
    Chat With a Human