We check the servers, sign-ins and email settings your business depends on. The first check is read-only, so nothing changes while we look. You get the findings in plain language, sorted by priority, and we fix the most important things first.
It suits a business that relies on its website, a server or its email and wants to know where things stand.
What you get
A clear picture, then fixes in order
- A read-only check before anything changes.
- Findings in plain language, sorted by priority.
- Firewall rules that keep internal services off the internet.
- Server access by key, with password logins turned off.
- Two-step sign-in for administrator accounts.
- Limits on repeated failed sign-ins.
- Browser security headers, and private files kept out of public reach.
- Email authentication records (SPF, DKIM and DMARC) checked and set up.
- A backup before each change, and a way to undo it.
- Notes on what changed, what was tested, and what wasn’t.
The check
What a read-only check covers
Open any area to see what we look at and what a fix can look like. Looking changes nothing.
Firewall and open servicesWhat can be reached from the internet
What we look at
Which services on your server answer requests from the internet, and whether each one needs to.
What a fix can look like
Firewall rules that keep internal services off the internet.
Server accessHow people sign in to the server itself
What we look at
How people and tools sign in to the server, and whether it accepts passwords.
What a fix can look like
Access by key, with password logins turned off.
Administrator sign-insThe accounts that can change everything
What we look at
Whether administrator accounts ask for a second step when someone signs in.
What a fix can look like
Two-step sign-in for administrator accounts.
Failed sign-insWhat happens when someone keeps guessing
What we look at
Whether repeated failed sign-ins are limited.
What a fix can look like
Limits on repeated failed sign-ins.
Browser security headersSettings your site sends with every page
What we look at
The security settings your website sends to visitors’ browsers with each page.
What a fix can look like
Security headers added, so browsers apply safer rules to your pages.
Private filesFiles that shouldn’t open from the web
What we look at
Whether files meant to stay private can be opened by anyone who has the address.
What a fix can look like
Private files blocked from public view.
Email authenticationYour SPF, DKIM and DMARC records
What we look at
The records that tell other mail servers which senders may send mail as your domain.
What a fix can look like
Records checked and set up, so it’s harder for others to send mail that pretends to come from you.
How it works
Look first, then fix with a way back
Look first
A read-only check of your servers, sign-ins and email records. Nothing changes.
Findings by priority
You get plain-language findings, sorted so the most important come first.
Fix with a way back
We take a backup before each change and keep a way to undo it. Where a test copy can be made, we try changes there first.
Write it down
You get notes on what changed, what was tested, and what wasn’t.
Real example
A new server for JPG Insurance
JPG Insurance, an independent insurance agency in Las Vegas, moved its website to a new server. We set it up and tested it before the switch, and kept the old server running as a way back.
We then tightened firewall rules, turned off password logins for server access, turned on two-step sign-in for the administrator login, and added limits on failed sign-ins and browser security headers. We blocked private files from public view, and checked and set up the agency’s email authentication records.
After the switch
82 pages
crawled, with 0 broken links and 0 broken images.
81 of 81
addresses found on the old site land on a working page.
Questions
Common questions
Will the check change anything?
No. The first check is read-only. Nothing changes until you’ve seen the findings and know what will change.
What do I get from the check?
A list of findings in plain language, sorted by priority, so you can see what matters most.
What if a change causes a problem?
We take a backup before each change and keep a way to undo it. Where a test copy can be made, we try changes there first. Settings that exist only on the live server are changed after a backup.
Do you check email settings too?
Yes. We check your SPF, DKIM and DMARC records. They tell other mail servers which senders may send mail as your domain.
Will I know what was changed?
Yes. You get notes on what changed, what was tested, and what wasn’t.
Can you work with my host or setup?
It depends on what you have. Tell us on a call and we’ll say plainly whether we can help.
How much does it cost, and how long does it take?
It depends on how many servers, sites and accounts are involved. Book a call and we’ll talk it through.
Not sure what’s open on your server?
Tell us what you run and who looks after it now. We’ll reply by email within 48 hours to set up a call.