Security Pulse

Free · 60 seconds · no login

See what criminals (and your customers) can see about your business, in 60 seconds.

Enter your business website and we'll run your Security Pulse: a 60-second external check of whether someone can spoof your email to your customers, whether your site's encryption is sound, and what your business exposes to the internet. Plain-English results, instantly.

We only read public information (the same data tools like MXToolbox use). This is an external snapshot, not a full audit, and we never change anything. Running a scan may (or may not) prompt a follow-up from us; no obligation either way.

What the Pulse checks

Five things anyone on the internet can see about your business.

Criminals look at these before they pick a target. Your customers' email systems look at them every time you send an email. Each one comes back green, amber or red, with a plain-English fix for anything that needs it.

Can someone send email as you?

We check the settings that stop criminals sending email that looks like it came from your business (known as DMARC, SPF and DKIM). Without them, a fake invoice can arrive from your real address.

Is your website's encryption sound?

Whether your site loads securely over HTTPS, sends visitors to the secure version automatically, and tells browsers to always use it.

What is your website giving away?

Whether your site sends the standard security settings browsers expect, and whether it advertises the exact server software it runs, which helps attackers look up known weaknesses.

Have any of your logins been stolen?

We look up your domain in a live database of logins stolen by password-stealing malware on infected computers. If your staff's logins are in it, that's a live problem worth fixing today.

Is your domain locked down?

Two settings at your domain provider: one makes your domain's records harder to tamper with, the other limits who can issue security certificates for your website.

And what to do about it

Every amber or red result comes with the fix, written for a person rather than an IT department. Do it yourself, hand it to whoever looks after your IT, or ask us.

How it works

Sixty seconds, and nothing on your side changes.

1. Enter your website

Just your business domain. No login, no software to install, and your email is optional.

2. We read the public record

We look up your domain's public records and visit your website, like any visitor would. We never touch your systems or change a thing.

3. You get a plain-English result

What's fine, what needs attention and what to do about it, on screen straight away. Add your email and we'll send you the full report and fix list.

The Pulse sees the outside. Most attacks start on the inside.

Staff sign-ins, backups, computers and the settings inside your systems can't be seen from the internet. The free 30-minute Security Scorecard covers them. No system access, no obligation, and you'll leave with at least three fixes you can use yourself, even if we never work together.

Questions we get

The Security Pulse, answered.

Is it safe to run on my business?

Yes. The Pulse only reads public information: your domain's public DNS records and an ordinary visit to your website, the same data tools like MXToolbox use. It never logs in, never scans your network and never changes anything.

Is it really free?

Yes. There's no login and no charge. You see your results on screen straight away.

Do I have to give my email?

No. Your email is optional. Add it if you'd like the full report and fix list sent to you.

Will someone call me?

Running a scan may prompt a follow-up from us, with no obligation either way. If you'd rather talk now, book a free Security Scorecard or call 1300 313 384.

Does a good result mean we're secure?

Not on its own. The Pulse only sees the outside of your business. The things that stop most attacks, like multi-factor sign-in, backups and protected computers, can't be seen from the internet. A good result means your public setup is sound; the Security Scorecard looks at the rest.

Why does a result say "couldn't check"?

Some settings can't always be confirmed from outside, for example email signing that depends on a setting name only your email provider knows. We show those as "couldn't check" rather than guess.